The GA4 Events Every Service Business Should Track (and What to Ignore)

Open most service business GA4 accounts and you’ll find one of two problems: almost nothing is tracked, or everything is tracked and none of it is useful.

Good tracking sits in the middle. It records the few actions that show real buying intent, adds a small set of signals that explain behaviour, and ignores the noise. Here is a practical guide to what to track in GA4, what to leave out and how to keep it clean.

The tracking pyramid

Track from the top down. Most of your effort belongs in the first two layers.

Key events Supporting signals Noise: track sparingly or ignore Leads, calls, bookings Form starts, video, CTAs

Illustrative model.

1Start with business questions, not events

Before you set up anything, write down what you actually need to know. For a service business it’s usually short: How many real enquiries came in? Where did they come from? Which service pages produce them? Where do people give up?

The fix

For every event you plan to track, finish this sentence: “If this number changes, I will…” If you can’t, the event probably isn’t worth tracking.

2The events to track and mark as key events

These are the actions that show a visitor is ready to talk to you. In GA4, mark them as key events (previously called conversions) so they appear in your reports and can feed Google Ads.

Event nameWhat it tells youKey event?
generate_leadA form (quote, contact, audit) was submittedYes
click_to_callSomeone tapped your phone numberYes
book_appointmentA booking or calendar slot was confirmedYes
click_emailSomeone clicked a mailto linkYes
chat_startedA visitor opened a chat and sent a messageYes
click_directionsA local visitor asked for directions to youOptional
The fix
  • Fire generate_lead only on a confirmed submission, on the thank-you state or success callback, not on the button click
  • Track phone taps with a link-click trigger on tel: links in Google Tag Manager
  • Use a call-tracking tool for calls that don’t start from a link, since GA4 can’t see those

3Supporting events that explain behaviour

These don’t count as leads, but they show why people convert or don’t. Track them, but don’t mark them as key events.

form_start, to spot forms people begin but abandon
Views of key service and pricing pages
Video plays and completions on important pages
Clicks on your main call to action buttons
File downloads, such as brochures or guides
Scroll depth on long service pages
The fix

Compare form starts with form submissions. A large gap points to a form that is too long, confusing or broken, and it’s often one of the quickest wins you can find.

4What to ignore (or at least not call a conversion)

Most of the mess in GA4 comes from tracking activity and treating it as intent.

Page views marked as conversions
Every button and link click
Scroll events on every page
Time on site as a success measure
Total sessions with no source or quality context
Dozens of near-duplicate custom events
The fix

If a metric goes up when your business doesn’t get more customers, it’s a vanity metric. Keep it out of your key events and out of your monthly report.

5Name events consistently and add useful parameters

Messy names make reports hard to read months later. Pick a simple convention and stick to it: lowercase words separated by underscores, verbs first. Then add parameters that answer the questions from step one.

event: generate_lead
form_name: free_inspection
service_type: roof_replacement
location: washington_dc
page_type: service_page
The fix

Register the parameters you’ll actually report on (such as service_type) as custom dimensions in GA4. Otherwise they are collected but won’t appear in standard reports.

6Connect events to real leads and revenue

A GA4 event tells you someone submitted a form. It doesn’t tell you whether the lead was good, or whether it turned into a job. To close that gap, link your website data to your CRM.

Source / UTM→Landing page→generate_lead→CRM record→Booked job
The fix
  • Use consistent UTM parameters on ads, emails and social links
  • Store the source and landing page in hidden form fields so they reach your CRM
  • Log lead quality and outcome in the CRM, so you can see which sources bring in real customers, not just form fills

On our builds for home service and B2B clients such as Trusted Roof and Active Pulse, this is the layer that turns tracking from a report into a decision tool.

7Test it, protect it and review it monthly

Tracking breaks quietly. A theme update, a new form plugin or a redesign can stop events firing without any warning.

The fix
  • Test each event in GA4 DebugView with Tag Assistant or GTM preview before going live
  • Filter out internal traffic, such as your team and your agency
  • Re-test after every site change
  • Review key events, sources and form drop-off monthly, and change one thing at a time

Quick checklist: is your GA4 set up properly?

  • Do you track form submissions, click-to-call and bookings as key events?
  • Do form events fire only on successful submission?
  • Do you have call tracking for calls that don’t start from a link?
  • Are page views and generic clicks kept out of your key events?
  • Do your event names follow one consistent convention?
  • Do leads carry their source into your CRM?
  • Is internal traffic filtered, and do you test tracking after site changes?

If you answered “no” to more than two of these, your reports are probably telling you a less accurate story than you think.

Not sure what your tracking is really telling you?

At Ashall & Co., we set up GA4, Tag Manager, call tracking and lead reporting for service businesses and B2B companies. We start with an audit, so you can see what’s missing, what’s misleading and what to fix first.

Get a Free Audit →

Frequently Asked Questions

What is a key event in GA4?

A key event is an event you mark as important to your business, such as a form submission or a click on your phone number. GA4 used to call these conversions. Key events appear in your reports and can be imported into Google Ads.

What events should a service business track in GA4?

At minimum: form submissions, click-to-call, booking or quote requests and email clicks. Supporting events such as form starts, video plays and key page views help you understand why visitors do or don’t convert.

Does GA4 track phone calls automatically?

No. GA4 doesn’t automatically know when someone calls. You can track taps on phone links with a custom event, and use a call-tracking tool to capture calls that start from a number displayed on the page or from ads.

How many events should I track?

Fewer than you think. Start with the handful that map to real business decisions, then add supporting events only when they answer a specific question. A long, messy event list makes reports harder to use.

What should I not track as a conversion?

Avoid marking page views, scrolls, generic button clicks or time on site as key events. They show activity, not intent, and they make your conversion numbers look better than reality.

How do I test that my GA4 events work?

Use GA4’s DebugView together with Google Tag Assistant or GTM preview mode, trigger each action yourself, and check that the event and its parameters appear correctly. Repeat after any site change.

Can Ashall & Co. set up GA4 tracking for my business?

Yes. We set up GA4, Google Tag Manager, call tracking and lead reporting for service businesses and B2B companies, so every enquiry can be tied back to the page and source that produced it.

How do I get started?

Book a free audit through our contact page. We’ll review your current tracking, show you what’s missing or misleading, and give you clear priorities.