The short answer
Decide which actions count as an enquiry, record each one as an event the moment it happens, and check that the record is right. An event is a named action sent to your analytics tool, such as a form being sent. Once events exist, you can see which channels and pages produce them.
Most service businesses need only a handful of events. The care goes into making each one accurate and testing it. We set these up as part of our tracking and analytics service, so this comes from doing the work.
What counts as a conversion
A conversion is an action that signals someone wants to deal with you. For a service business the list is short.
- A form sent: contact, quote request, callback or survey request.
- A phone number tapped on a mobile.
- A call connected and answered.
- A booking made through an online diary or booking tool.
- An email address clicked.
- A chat or WhatsApp conversation started, if you offer one.
These are not equal. A booking or a completed quote form is a firm enquiry. A tapped phone number or a clicked email address shows intent, but you cannot be sure the call or email followed. Keep the two groups apart in reports so that weak signals do not inflate the total. Where this sits in the wider picture is covered in our guide to website tracking and analytics.
How each one is measured
The methods below are the usual ones. Most are set up through a tag manager, and a separate guide explains what Google Tag Manager does.
| Action | Usual method | What to watch |
|---|---|---|
| Form sent | Thank-you page view, or an event on successful submission | Count accepted forms, not button presses |
| Phone number tapped | Click event on the phone link | Counts taps, not conversations |
| Call connected | Call tracking number | Ties each call to a source |
| Booking made | The booking tool's confirmation event | The tool may sit on another web address |
| Email clicked | Click event on the email link | Counts clicks, not emails sent |
Forms
There are two common approaches. Either the form sends people to a separate thank-you page and you count views of that page, or the form signals a successful submission and that signal becomes the event. The thank-you page is simple and easy to check. The event approach suits forms that show a message without leaving the page.
Phone calls
A click-to-call event tells you someone tapped the number on a phone. It misses people who read the number on a desktop and dial it. Call tracking closes that gap. The service gives you numbers that forward to your normal line, and can show different visitors different numbers according to how they arrived. Deciding which source deserves the credit is a subject of its own, covered in marketing attribution explained. If calls are recorded, callers generally need to be told, so check the rules that apply to you.
Bookings
Booking tools often sit in a frame on your page or on their own web address, so your site cannot always see the confirmation. Many can send a confirmation event to GA4 or Tag Manager, or return people to a page on your site afterwards. Check what your tool supports before choosing a method.

Name events consistently
Names matter more than they seem. If one form is recorded as contact_form, another as Form Submit and a third as lead, nobody can add them up a year later. Pick a pattern and write it down.
- Use lower case with underscores, and the same word order every time.
- Name the action, not the page: quote_form_sent, phone_tap, booking_made.
- Where GA4 has a recommended event name that fits, such as generate_lead, use it.
- Add detail as a parameter (an extra label on the event), such as which form or which branch, instead of inventing a new event each time.
- Keep a one-page list of every event, what triggers it and who set it up.
Test that it works
Tracking that has not been tested should not be trusted. Do each action yourself and watch for it to arrive. GA4 and Tag Manager both have preview or debug views that show events as they happen.
- Send every form with realistic details and confirm one event appears, not two.
- Send a form with a deliberate error and confirm no event appears.
- Tap the phone number on a mobile.
- Ring each call tracking number and confirm it reaches the right phone.
- Make and cancel a test booking.
- Repeat after declining cookies, to see what your consent banner allows.
- Repeat whenever the website, form tool or booking tool changes.
Put a recurring test in the diary. Forms break quietly, and the first sign is often a slow month.
Connect enquiries to your CRM
Analytics can tell you an enquiry happened. Only your CRM (the system where you record leads and customers) can tell you whether it became a sale. To join the two, the source has to travel with the enquiry. In practice that usually means hidden fields on the form that capture the channel and campaign, and a call tracking service and booking tool that pass their details into the CRM.
Once the source sits on each record, you can compare channels on customers won, not just enquiries received. Imagine a firm whose adverts bring many forms and whose search listings bring fewer. If the CRM shows the search enquiries become customers far more often, the budget decision changes.
Common mistakes
- Counting button clicks on a form instead of successful submissions.
- Treating phone taps as answered calls.
- Firing the same event twice from two different set-ups.
- Giving every form a differently styled event name.
- Never testing after the site or a plugin is updated.
- Leaving the source out of the CRM, so nobody can tell which enquiries became customers.
Common questions
Do we need call tracking, or is a click event enough?
If the phone is a minor route in, a click event may be enough. If most enquiries arrive by phone, call tracking is usually worth having, because it counts real calls and ties them to a source.
Will customers see a different phone number?
They may. Tracking numbers forward to your normal line, so calls are answered as usual. Ask the provider how the numbers are displayed and what happens to them if you ever leave.
Can enquiries be counted if a visitor declines cookies?
Partly. The form still arrives and the phone still rings, so your own records can count them. What you usually lose is the link back to the channel, so some enquiries show no known source. Check current guidance on what needs consent in your situation.
How many events should we have?
As few as cover your real enquiry routes. For most service businesses that is a handful. A long list tends to mean nobody looks at any of it.
What to do next
List every way someone can get in touch through your website, then try each one today and see whether anything records it. That list is the start of a tracking plan, and the gaps are usually obvious once it is written down.
If you want a second opinion, ask for a free 24-hour audit. A founder records a personal video walkthrough of your website within 24 hours, which can cover how easy it is to enquire and what could be measured. No call is needed, and a 15-minute call is optional.
Want this applied to your website?
George or Nicholas will record a personal walkthrough of your site within 24 hours.
Not ready for an audit? See Tracking and analytics.
