How to set up GA4 events that are actually useful
22 November 2026
GA4 can track almost anything, which is exactly why so many reports are full of noise. Here's how to tell useful events from useless ones, and how to set up tracking you can make decisions with.

Mandy McGregor
director, sales, seo, web, oral history

Google Analytics 4 (GA4) records almost everything as an event: page views, clicks, scrolls, form submissions and purchases. That makes it flexible, but it also makes it easy to end up with a report full of events that nobody looks at, while the ones that show real enquiries are missing or wrong. Here's how to tell useful events from useless ones, and how to set up tracking you can actually make decisions with.
What is an event in GA4?
An event is a single action someone takes on your website, like viewing a page, clicking a phone number or submitting a form. GA4 collects some events automatically, more through enhanced measurement (scrolls, outbound clicks, file downloads, site search and video engagement), and you can add Google's recommended events or your own custom events, usually with Google Tag Manager. The events that matter most to your business can then be marked as key events, so they show up as results in your reports and can be used in Google Ads.
What makes an event useful?
Before you track anything, ask four questions. If the answer to any of them is no, the event probably isn't worth setting up.
Is it tied to a business outcome? A useful event shows someone getting closer to becoming a customer: an enquiry, a call, a booking or a sale.
Will anyone act on it? If nobody will change a page, a campaign or a budget because of the number, it's just noise.
Does it fire at the right moment? A form event should fire when the form is successfully sent, not when someone clicks the button and gets an error.
Is it named clearly and consistently? Anyone on your team should be able to read the event name and know exactly what happened.
Useful events worth tracking
For most service businesses, a small set of well-built events tells you far more than dozens of clicks. These are the ones we set up first:
Successful form submissions (generate_lead). Fire the event on the thank-you message or confirmation page, and add a parameter for which form was used, such as contact, quote or newsletter.
Phone number clicks. On mobile, a tap on your phone number is often the moment someone becomes a lead. Track clicks on tel: links. This matters even more for local businesses, where many customers call straight from Google Maps (see 10 reasons to localise your SEO strategy).
Email address clicks. Track clicks on mailto: links, so enquiries that start in someone's email app aren't invisible.
Bookings and quote requests. If you use a booking tool or a quote form, track the completed booking or request, not the first step.
Purchases and checkout steps. For online stores, use Google's recommended ecommerce events (view_item, add_to_cart, begin_checkout, purchase) so you can see where people drop out.
Downloads that matter. Brochures, price lists and menus show genuine interest. Enhanced measurement can track file downloads for you.
Clicks to important outside platforms. If customers book or buy on another website, track the outbound click so the lead isn't lost from your reports.
Mark only your most valuable actions, usually form submissions, calls and bookings or purchases, as key events. If everything is a key event, nothing stands out.
Events that just add noise
These are the events we most often find when we audit a GA4 account. They make reports harder to read, and some of them give you numbers that are simply wrong:
Every button click. Tracking all clicks creates a long list of events with no clear meaning. Track the clicks that lead to an outcome instead.
Form button clicks instead of form submissions. These fire even when the form has errors or the visitor gives up, so your lead numbers look higher than they are.
Duplicate events. GA4 installed twice (for example through both your website platform and Google Tag Manager) doubles your page views and events. A custom event that copies an enhanced measurement event does the same. It's worth checking whenever you redesign or rebuild your website.
Events that fire on every page load. An event that fires whenever a page opens usually says nothing more than the page view already does.
Inconsistent names. Form_Submit, form_submit and formSubmit show up as three separate events. Pick one naming style, ideally lowercase with underscores, and stick to it.
Personal information in events. Never send names, email addresses or phone numbers into GA4. It goes against Google's policies and puts your account at risk.
Too many key events. Marking page views, scrolls or time on page as key events inflates your results and makes it hard to see what's really working.
How to set up GA4 events properly
Start with your business questions. Write down what you need to know, such as "How many quote requests do we get from Google Ads?" Each question points to an event.
Use Google's recommended event names where you can. Names like generate_lead and purchase work better with GA4 reports and Google Ads than names you invent.
Build events in Google Tag Manager with the right trigger. Trigger on success: a thank-you page, a confirmation message or a completed booking.
Add helpful parameters. Parameters such as form name or service type give each event context. Register the ones you want to report on as custom dimensions in GA4.
Test before you publish. Use Tag Manager's Preview mode and GA4's DebugView to check each event fires once, at the right time, with the right details.
Mark your key events. Turn on key event status only for the actions that represent real leads or sales.
Keep a simple tracking plan. List every event, what triggers it and why it exists. It makes future changes much easier and stops tracking from creeping back into noise.
A quick GA4 event checklist
GA4 is installed once, not twice.
Form events fire on successful submission only.
Phone and email clicks are tracked.
Event names are consistent and easy to understand.
Only your most valuable actions are key events.
No personal information is sent to GA4.
Every event has been tested in DebugView.
Need a hand with your GA4 setup?
Smokeylemon sets up and audits GA4 and Google Tag Manager for businesses in Taranaki and across New Zealand, so you can see exactly which channels bring in enquiries. Find out more about our Google Ads, SEO and marketing strategy services, or start a conversation with our team.
Share this post