Tracking enquiries in GA4 for service businesses - a practical key events guide
For a service business — a plumber, a dentist, a solicitor — the website has one job: make the phone ring. Yet open a typical GA4 property for one of these businesses and you'll find either no enquiry tracking at all, or a "key event" counting something meaningless, like every page view of the contact page.
If you're an agency reporting to these clients, this setup work is quietly load-bearing: every monthly report you ever send will rest on whether these numbers mean what they claim. Here's the practical version.
What counts as an enquiry
An enquiry is a visitor doing something that puts them in the client's pipeline. For most service businesses that's some mix of:
- Clicking a phone number on the site (
tel:link clicks) - Submitting a contact or quote form
- Clicking an email address (
mailto:) - Starting a booking (for dentists, clinics, anyone with online booking)
- WhatsApp or SMS link clicks, increasingly, for trades
What is not an enquiry: visiting the contact page (intent, not action), spending a long time on the site, or any of GA4's automatic engagement metrics. If the client wouldn't recognise it as "someone trying to hire me", it doesn't belong in the enquiry count.
The setup, in order of effort
Phone clicks are the big one for trades, and GA4 doesn't track them by default. The clean route is a Google Tag Manager trigger on clicks of links beginning tel:, firing an event — name it something a human recognises, like phone_call_click. If the site is WordPress, several form/tracking plugins can emit this without GTM, but GTM keeps it theme-proof.
Form submissions: the reliable pattern is firing an event on the form's success state — the thank-you page or the success message — not on the submit button click, which also counts failed validations and double-clicks. If the form plugin pushes its own events to the data layer (most major WordPress form plugins do), use those.
Then mark them as key events in GA4: Admin → Events → toggle "Mark as key event" on each. Only enquiry-shaped events get the toggle — which brings us to the mistakes.
The three ways these numbers lie
Inflation by eagerness. Marking session_start, scroll or first_visit as key events makes the number big and meaningless — and a client who once hears "you had 300 key events" will not enjoy the recount when someone defines the term properly. One real enquiry is worth more in a report than fifty engagement pings, because it can survive scrutiny.
Double counting. A visitor clicks the phone number twice, or the form fires its event on each validation attempt. Where the tooling allows, count once per session, and test the form's failure states yourself before trusting its success event.
The invisible phone calls. The ceiling on all of this honesty: GA4 only sees calls that started as clicks on the website. A customer who reads the number off the screen and dials it on the landline, or calls straight from the Google Business Profile listing without ever touching the site, is invisible to Analytics. For local businesses that second group is substantial — profile calls live in Google Business Profile's own data, not GA4, and belong in reports as their own clearly-labelled section. Never present GA4 enquiries as "all enquiries"; present them as "enquiries from the website", which is what they are.
Reporting them without jargon
Having set this up properly, don't then waste it by reporting "key event conversions" to a heating engineer. Use the client's own noun — bookings, enquiries, jobs, quotes — and attach the comparison that makes it meaningful: against last month and the same month last year, because service trades are seasonal and month-on-month alone misleads.
The sentence a client deserves is: "The website produced 47 enquiries in July — 9 more than June, and a third more than last July." Every word of that is checkable against the setup you just built.
Where this fits in the bigger picture
Enquiry tracking is the bridge between "SEO metrics" and "money" — it's what lets a report connect a page's visits to the phone actually ringing, which is the page-by-page analysis clients value most. It's fiddly, one-off setup work, and it pays back every month afterwards.
When the tracking exists, our reports pick the key events up automatically — you choose which events count as enquiries per client, and the report does the rest in plain English. The sample shows how "47 enquiries" reads in context.
YourReporting sends white-label monthly SEO reports your clients actually read — £39–£129 a month, never per client.