GA4 reports are built from events, and events are only as good as their setup: consistent names, real conversions marked as key events, parameters that carry data, and filters that keep your own team out of the numbers. Eight checks, done by hand or automatically in two minutes.
Tracking Auditor scores GA4 event quality as one of five audit dimensions, using 30 days of your live data. Your first audit is free.
Run a free audit →Write down the actions that matter (purchases, leads, sign-ups, key engagement) before looking at GA4. Then compare that list against Reports → Engagement → Events. Anything on your list with no matching event is invisible to reporting. Anything in GA4 that nobody can explain is noise.
sign_up, signup and SignUp are three different events to GA4, and each splits your data. Look for near-duplicate names, mixed casing and spaces. A naming mess usually means several people have added tracking over the years without a shared standard.
In Admin → Key events, check what's marked. page_view, session_start or scroll marked as key events flood reports with meaningless 'conversions', and if those import into Google Ads, bidding optimises toward them. Key events should map one-to-one to the business actions from step one.
For each key event, confirm something actually sends it: a GTM tag, a hard-coded gtag call, or an auto-collected event. A key event with no live source silently records zero. Cross-referencing events against container tags is the check that catches conversions that died in a site update.
An event firing is not the same as an event carrying data. Check that purchase carries value, currency and transaction_id, that form events say which form, and that custom parameters are registered as custom dimensions. Unregistered parameters are collected but unusable in reports.
Admin → Data streams → Configure tag settings → Define internal traffic, plus the internal traffic filter under Data settings → Data filters (it ships in 'testing' mode and does nothing until activated). Your own team's sessions inflate engagement and pollute conversion rates.
Enhanced measurement auto-collects scrolls, outbound clicks, site search, video and file downloads. Check what's enabled against what you actually use, and watch for collisions where a manually tagged event duplicates an auto-collected one.
Three settings that quietly shape every report: data retention defaults to two months (explorations lose history beyond it), a wrong currency corrupts every revenue figure, and a wrong time zone shifts session boundaries. All three live in Admin and take minutes to fix.
session_start counted as a conversion. Reports show thousands of 'conversions' that mean nothing.
sign_up, signup and new_user_registration, each with a fraction of the real total.
The key event is configured; nothing has sent it since the checkout was rebuilt.
The event fires, the revenue field is empty, and ROAS reads zero.
Defined, configured, and never activated. The office IP has been in the data all along.
Months of collected data that no report can display.
Event quality is one of five dimensions in a complete tracking audit. The full process is in the Google Analytics audit guide. The conversion side of events gets its own deep dive in the conversion tracking audit guide, and the tags that send them are covered in the GTM audit guide.
A GA4 event audit reviews the events a property collects against what the business needs to measure. It checks naming consistency, that key events map to real conversions with working sources, that parameters carry usable data, and that internal traffic, retention, currency and time zone settings aren't corrupting reports.
Reports → Engagement → Events shows events with data in the selected date range. Admin → Events shows the events GA4 has seen recently along with key-event toggles. For live debugging, DebugView under Admin shows events arriving in real time from a device with debug mode enabled.
Only actions with business value: purchases, qualified leads, sign-ups, booked demos. Auto-collected events like page_view, session_start and scroll should not be key events. If a key event wouldn't be worth money to the business, it's diluting your conversion data and any ad bidding built on it.
The usual causes, in order: the tag or trigger stopped firing after a site change, consent settings block the event for most visitors, the event fires but under a different name than you expect, or the parameter you're looking for was never registered as a custom dimension. Tracing the event from the site through GTM to DebugView finds which link broke.
Yes. Tracking Auditor reads your GA4 property and GTM container together, cross-references key events against the tags meant to send them, and scores event quality as one of five dimensions in a full tracking audit.
Connect GA4 and GTM read-only and Tracking Auditor reviews your events against 30 days of live data, cross-checks key events against their tags, and scores event quality alongside the other four dimensions. Your first audit is free, no card required.
Run your free audit