GA4 events every service business should track

A service business should track the actions that lead to an enquiry: form submissions, phone calls, WhatsApp clicks, email clicks, booking steps and downloads of brochures or proposals. Mark the most important of these as key events in GA4. Page views alone tell you who visited, but not who became a lead.

Why track events at all?

A website for a clinic, school, agency, consultancy or travel firm exists to produce a conversation. Visits are a means. If you only look at traffic, you cannot tell which pages, campaigns or sources bring people who actually get in touch.

Events turn behaviour into numbers. Once they exist, you can compare sources, find pages that lose people, and judge a campaign by leads instead of clicks.

What does GA4 record on its own?

Out of the box, GA4 collects page views, sessions and first visits. With enhanced measurement on, it also records scrolls, outbound clicks, site search, file downloads and some video plays. That is a start, but it does not know about your forms, buttons or bookings. You have to set those up.

Which events should you add?

Here is a practical list for most service businesses. Use Google's recommended event names where they exist, since they feed standard reports and integrations.

Lead events. These are your most important ones:

• generate_lead: fired when a contact, quote or enquiry form is submitted successfully. Add parameters such as form name and service of interest.
• whatsapp_click: when someone clicks a WhatsApp button or link.
• phone_click: when someone taps a phone number on mobile.
• email_click: when someone clicks a mailto link.

Booking events, if you take bookings:

• booking_start and booking_complete, or begin_checkout and purchase if payment happens online.

Content and interest events:

• file_download: brochures, price sheets or proposals.
• scroll depth at meaningful points, if not already captured.
• video_start and video_complete for important videos.

Navigation events:

• cta_click with a parameter for which button, to compare the header button against page buttons.
• search, for on-site search terms, which show what people cannot find.

Mark generate_lead, booking_complete or purchase, and any call or WhatsApp event you treat as a real lead as key events.

How do you name events and parameters?

Consistency saves trouble later. Use lowercase with underscores. Choose a pattern and stick to it. Put the variable detail in parameters, not in the event name. So use one cta_click event with a parameter cta_location, not separate events like cta_click_header and cta_click_footer.

Keep a short tracking plan document: event name, when it fires, parameters, and who asked for it. When someone leaves the team, the plan stays.

How do you set events up?

There are three common ways.

1. Mark GA4's automatic or recommended events and create events in the GA4 interface from existing ones, for example from a thank-you page view.
2. Use Google Tag Manager to fire events on clicks and form submissions, with no code change on each edit.
3. Send events from your own code for actions that happen on the server, such as a payment confirmed by a gateway webhook.

For forms, prefer firing the event when the submission succeeds, not when the button is clicked. Otherwise failed or spam submissions are counted as leads. For payments, record the final confirmation from the server so the numbers match your accounts.

How do you check the data is right?

Open DebugView in GA4 and use Tag Assistant while you click through the site. Submit each form, click each button, and complete a test booking, on desktop and on a phone. Check that each event fires once, with the right parameters.

After a week, compare GA4 leads with the real leads in your inbox or CRM. They will not match perfectly because of ad blockers and consent choices, but a large gap means something is broken.

What about consent and privacy?

Analytics that uses cookies or identifiers requires a thought-through consent set-up, especially for visitors in regions with strict rules. In India, the Digital Personal Data Protection Act, 2023 requires notice and consent for processing personal data. Our guide to cookie consent for Google Analytics in India and the Gulf goes through the choices, including Google Consent Mode. Never send names, emails or phone numbers as event parameters to GA4. Google's terms prohibit sending personally identifiable information to Analytics.

How long is the data kept?

For standard GA4 properties, the event data retention setting can be 2 months or 14 months, according to Google's documentation. The default is 2 months, so change it to 14 months in the property's data settings soon after creating it. Standard reports use aggregated data and are not affected, but custom explorations are limited by this setting.

What should you look at once events are flowing?

Start with four views. Leads by source and medium, to see which channels bring enquiries. Leads by landing page, to see which pages persuade. The path from first visit to enquiry, to find where people leave. And mobile versus desktop lead rates, which often reveal a form problem on phones.

Review them monthly and write down one change to try. If you want these numbers on one page for your team, see how to build a business dashboard people use.

Where can we help?

If your current tracking is missing, duplicated or doubtful, a Digital Health Check will show it along with speed, security and SEO basics. We set up and audit tracking under GA4 and analytics setup and the wider Data & Analytics pillar. This is the kind of work we do. To talk about yours, Let's Talk.