GA4 Audit Checklist: Find Broken Events, Missing Conversions, and Tracking Gaps

Overview

GA4 data can look plausible while still being incomplete. A pageview may be recorded even when a form submission is not. A campaign may receive traffic while its UTM parameters are inconsistent. A purchase may appear in a payment system but fail to reach GA4, Google Ads, or another reporting destination.

The purpose of a GA4 audit is not to make every report match perfectly. It is to establish whether the tracking setup reflects the actions that matter to the business, whether those actions are recorded once, and whether the resulting data can support conversion tracking and campaign attribution.

Keep a written tracking plan alongside this process. For each important event, document its name, trigger, parameters, destination, business purpose, owner, and validation method. The Website Tracking Plan Template can help organize that information before you begin.

Work through the audit in four layers:

• Collection: Is the site or app sending the expected data?
• Definition: Are events, parameters, and key events named and configured correctly?
• Attribution: Are source, medium, campaign, referral, and cross-domain settings preserving useful context?
• Reporting: Do GA4 reports and connected platforms show results that can be reconciled with operational systems?

Checklist by scenario

1. Before a routine quarterly or seasonal review

• Confirm that the correct GA4 property and web data stream are being used.
• Check that the measurement ID in the live site matches the intended property.
• Review data stream settings and confirm that enhanced measurement reflects the current site structure.
• Test page views, scrolls, outbound clicks, site searches, video interactions, and file downloads where those actions are relevant.
• Review custom events created since the last audit. Remove, document, or replace events that are no longer used.
• Verify that important events are marked as key events rather than assuming every recorded event is a conversion.
• Check event names and parameters for consistent spelling, capitalization, and expected values.
• Compare important totals with a suitable operational source, such as a lead database, ecommerce platform, booking system, or form platform.

2. After a website redesign or tag-management change

• Test the homepage, landing pages, navigation, forms, checkout, confirmation pages, and error states.
• Confirm that the GA4 tag loads on every intended page and does not load twice.
• Submit each primary form using a test record and verify the expected event in DebugView or another testing workflow.
• Check single-page application routes if the site changes content without a full page reload.
• Test buttons and links whose HTML, CSS classes, IDs, or DOM structure changed during development.
• Verify that event parameters still capture useful details, such as form name, product ID, plan, location, or content type.
• Review consent-mode and consent-management behavior in permitted test conditions so that tags respond consistently to the site’s consent choices.
• Confirm that internal traffic filters, developer traffic filters, and other data filters are not excluding legitimate users.

3. Before launching paid or partner campaigns

• Use a documented UTM naming convention for source, medium, campaign, term, and content.
• Check that campaign URLs resolve correctly, retain their parameters, and do not redirect through a page that strips them.
• Confirm that lowercase and naming rules are applied consistently to prevent fragmented campaign reports.
• Test the landing page and the complete conversion path from a tagged URL.
• Review referral exclusions for payment providers, booking tools, authentication services, and other domains that users may visit during conversion.
• Confirm cross-domain tracking when a journey moves between related domains or subdomains.
• Verify that Google Ads conversion tracking, Meta pixel tracking, or other platform tags are assigned to the correct actions and are not duplicated.
• Record the campaign launch date, destination URL, expected conversion, and responsible owner.

For a deeper campaign review, use the Campaign Attribution Checklist. A consistent naming system is also covered in the Campaign Attribution Guide.

4. When conversions or revenue appear lower than expected

• Confirm that the event is firing at the intended point in the journey, not only when a page happens to load.
• Check whether the event is being blocked by consent settings, browser behavior, validation errors, or an ad blocker.
• Look for duplicate submissions caused by repeated clicks, reloads, or both a button trigger and a confirmation-page trigger.
• Review recent changes to forms, checkout providers, payment flows, and thank-you pages.
• Compare event counts with unique transaction IDs, lead IDs, or booking references where available.
• Check whether an event parameter required for revenue or item reporting is missing or formatted incorrectly.
• Review attribution and reporting date ranges before concluding that tracking is broken.
• Inspect funnel steps to identify whether the issue is collection, user behavior, or a genuine conversion-rate problem.

The Funnel Analysis in GA4 guide is useful when the tracking is present but the path to conversion needs closer examination.

What to double-check

Event quality

Names should describe actions clearly and use one consistent format. Parameters should answer reporting questions rather than capture every available detail. For example, a form submission event may need a form name and location, while sensitive personal information should not be sent as an event parameter. Confirm that important events are distinct enough to analyze but not so numerous that reporting becomes difficult to maintain.

Key events and conversion definitions

Separate meaningful business outcomes from supporting interactions. A purchase, qualified lead, completed booking, or subscription may be a primary key event. A brochure download or pricing-page view may be useful as a secondary event without being treated as an equivalent outcome. Document the distinction so that dashboards and campaign evaluations do not mix unlike actions.

Attribution and referrals

Check whether campaign parameters remain available through redirects and whether internal or payment-related domains are creating artificial referral sources. Review direct traffic carefully: it can represent genuinely unattributed visits, but it can also reflect lost campaign parameters or journeys that cross domains without suitable configuration. Attribution settings should be documented, not changed simply to make a channel appear stronger.

Validation and reconciliation

Use a controlled test for each critical conversion. Record the test URL, device, browser, consent choice, action taken, expected event, and observed result. Then compare aggregated GA4 data with another system over a defined period. Differences do not automatically prove an error because platforms can use different counting rules, time zones, filters, and attribution logic. The goal is to explain material differences and identify gaps that require correction.

For the broader implementation sequence, see the GA4 Setup Checklist and the related GA4 Tracking Audit Checklist.

Common mistakes

• Auditing only the GA4 interface: Reports show what was collected, not necessarily what should have been collected. Test the live experience and inspect the implementation.
• Assuming an event equals a conversion: An event may fire correctly while still being the wrong business outcome to optimize toward.
• Ignoring duplicate tags: Multiple containers, plugins, hard-coded scripts, or platform integrations can record the same action more than once.
• Using inconsistent UTM values: Variations such as “Paid Social,” “paid-social,” and “paid_social” can split one channel across several report rows.
• Changing attribution settings without documentation: A setting change can alter how historical or future reporting is interpreted. Record the reason, date, and expected effect.
• Testing only on desktop: Mobile menus, embedded forms, consent banners, and payment flows can behave differently on smaller screens.
• Fixing data without preserving context: Before changing event names or parameters, document the old setup and decide how reporting continuity will be handled.
• Judging campaigns too early: Allow time for data processing and account for the conversion window, sales cycle, and volume needed for a useful comparison.

When to revisit

Run a focused GA4 audit before seasonal planning cycles, major campaign launches, and reporting reviews. Repeat it after a redesign, analytics migration, tag-manager change, consent-banner update, CRM or checkout integration, domain move, or significant change to forms and conversion paths.

A lightweight monthly check can cover critical conversions, campaign parameters, referral sources, and recent implementation changes. A more complete quarterly review can include enhanced measurement, custom events, key events, filters, cross-domain tracking, connected advertising platforms, and reconciliation with operational data.

End every audit with a short action log:

1. List each issue and its business impact.
2. Assign an owner and a target date.
3. Describe the expected behavior after the fix.
4. Retest the affected journey in a controlled environment.
5. Record the implementation date and update the tracking plan.
6. Recheck reports after enough data has accumulated to confirm the change.

Keep this checklist with your measurement documentation and revisit it whenever the underlying website, campaign process, or reporting requirements change. Reliable conversion tracking is not a one-time setup task; it is a maintenance practice that protects the quality of marketing analytics and the decisions built on it.