GA4 Tracking Audit Checklist: Find and Fix Broken Events, Conversions, and UTM Data

Overview

GA4 tracking is not finished when a tag has been added to a website. A useful audit checks the entire measurement path: a visitor takes an action, the website or tag manager sends an event, GA4 receives and processes it, the event is classified correctly, and the resulting data appears in the reports used for decisions.

The goal is not to make every interaction a conversion. The goal is to make important business outcomes reliable, understandable, and connected to their marketing source. Start by listing the actions that matter, such as a completed lead form, purchase, demo request, phone click, account creation, or qualified booking. A website tracking plan can help document each event, its parameters, business purpose, and owner.

For each tracked action, record five details:

• Event name: The name sent to GA4.
• Trigger: The user action or technical condition that sends it.
• Parameters: The useful context, such as form name, product, value, or page.
• Key event status: Whether the action is treated as a primary outcome in GA4.
• Validation method: How you will confirm that the event fires once and appears correctly.

Keep this record separate from assumptions about attribution. GA4 can show where a session came from, but campaign attribution depends on consistent UTM parameters, redirects, landing-page behavior, consent settings, cross-domain configuration, and the reporting dimension selected.

Checklist by scenario

1. Before testing any event

• Confirm that the correct GA4 measurement ID is installed on the intended site or environment.
• Check whether a tag manager, website plugin, hard-coded tag, or multiple systems are sending data.
• Inspect the implementation for duplicate page views or duplicate event tags.
• Write down the expected event name and parameters before testing.
• Use a test environment or a clearly identified test action where possible.
• Open GA4 debugging or real-time validation tools and confirm that the test session is identifiable.

Do not rely on a single report for immediate validation. Processing and reporting behavior can differ by report, so first confirm that the request is sent and received, then verify how it appears in the relevant report after the data is available.

2. Auditing GA4 event tracking

• Trigger each important action from the page where a real visitor would take it.
• Confirm the event fires only after the intended action, not on page load or when a form is merely viewed.
• Check that the event fires once per completed action.
• Review spelling, capitalization, and naming consistency across similar events.
• Verify that parameters contain useful values rather than blank, default, or test values.
• Check that sensitive information is not being placed in event names, URLs, or parameters.
• Confirm that the event is visible in GA4 and that any required custom dimensions or metrics are configured for reporting.

Form tracking deserves special attention. A successful submission may not produce a unique thank-you page, and a form can fail without changing the URL. If the form is tracked through a data-layer event, callback, confirmation message, or backend integration, test both success and failure paths. A click on the submit button is usually weaker evidence than a confirmed submission.

3. Auditing conversions and key events

• List the actions that represent meaningful business outcomes.
• Confirm that each primary outcome is marked as a key event in the correct GA4 property.
• Separate primary outcomes from supporting interactions such as scrolls, brochure views, or button clicks.
• Check whether revenue or lead values are passed consistently and use the intended currency or unit.
• Test duplicate submissions, browser refreshes, back-button behavior, and confirmation-page reloads.
• Compare GA4 counts with a source of record, such as a form database, order system, or CRM, while documenting why the numbers may differ.

Conversion tracking should support decisions, not inflate performance. If several events describe the same outcome, decide which event belongs in executive KPI reporting and which events are useful for diagnosis. For a deeper review of the journey between steps, see this guide to funnel analysis in GA4.

4. Auditing UTM parameters and campaign attribution

• Use a consistent structure for utm_source, utm_medium, and utm_campaign.
• Add utm_content or utm_term only when the extra detail will be used in reporting.
• Standardize capitalization, separators, abbreviations, and naming conventions.
• Test every campaign link from the actual ad, email, social post, QR code, or partner placement.
• Follow the link through redirects and confirm that UTM parameters remain available on the landing page.
• Check that internal links do not overwrite the original campaign information.
• Review campaign reports for unexpected values such as missing sources, inconsistent medium names, or test campaign names.

A practical campaign naming convention is more valuable than a complicated one. Decide how your team will represent channel, audience, offer, market, and date, then document the rules in a shared campaign attribution checklist. An utm_medium value should describe the marketing method consistently enough to support comparisons.

5. Auditing cross-domain journeys and integrations

• Test journeys that move between domains, subdomains, checkout providers, booking platforms, or payment pages.
• Confirm that the visitor does not appear as a new referral from your own business or vendor domain.
• Check that the session and campaign context persist across the intended journey.
• Verify that Google Ads conversion tracking and other advertising integrations use the intended GA4 events or independent tags.
• Review Meta pixel tracking or other platform tags separately; matching event names does not guarantee matching counts.
• Test from the landing page through the final confirmation, not just one domain at a time.

Cross-domain tracking is especially important when the conversion happens outside the main website. Record every domain involved and identify which system owns the final confirmation. If a vendor changes its checkout flow, repeat the full journey test rather than assuming the previous configuration still works.

What to double-check

After the basic tests pass, review the areas that often create plausible but misleading numbers:

• Duplicate implementations: The same GA4 event may be sent by both a plugin and a tag manager.
• Trigger timing: A click trigger may fire even when validation fails, while a success trigger may depend on a fragile page element.
• Event parameters: A parameter can be sent correctly but remain difficult to use in reports until its reporting configuration is complete.
• Attribution scope: Acquisition reports, session reports, and user-level views may answer different questions.
• Direct traffic: Missing campaign parameters, app-to-web transitions, privacy controls, redirects, and untagged links can all affect how visits are classified.
• Self-referrals: Unexpected referrals from payment, booking, or subdomains can indicate a broken cross-domain journey.
• Time zones and date ranges: Compare systems using the same reporting period and account settings where possible.
• Filters and audiences: Internal traffic rules, test data, or report filters can make two valid reports appear inconsistent.
• Consent and browser behavior: Some users or environments may not generate the same observable data as a fully measurable test session. Document the measurement assumptions instead of treating every gap as a tag failure.

Keep a defect log with the issue, affected event, evidence, owner, proposed fix, test date, and final result. This turns an analytics audit from a one-time inspection into a useful maintenance record.

Common mistakes

• Testing only with a browser extension: Tools can show that a request exists, but they do not prove that the event has the correct business meaning or appears correctly in reporting.
• Counting button clicks as completed conversions: A click may be interrupted by validation errors, blocked payment, or a failed form submission.
• Changing names without a migration plan: Renaming events can break historical comparisons, dashboards, audiences, and advertising integrations.
• Using inconsistent UTM capitalization: Values that look similar to people may become separate rows in a report.
• Ignoring redirects: A tracking link may be correct before a redirect but lose parameters or change destinations along the way.
• Comparing platforms as if they measure identically: GA4, ad platforms, CRM systems, and payment tools can use different counting rules, attribution windows, and processing methods.
• Auditing only the homepage: A tracking script can work on one template and fail on a landing page, checkout step, embedded form, or application route.
• Failing to record ownership: An event without an owner is likely to become unreliable after a redesign or tool change.

When numbers disagree, do not immediately edit tags. First identify the exact metric, date range, source system, counting method, and user journey being compared. Then isolate the first point where the numbers diverge.

When to revisit

Run this GA4 tracking audit before each major seasonal planning cycle and after any change that could affect the visitor journey. That includes a redesign, CMS migration, checkout or booking-provider change, new form tool, tag-manager update, advertising integration, domain change, consent implementation change, or campaign naming revision.

A lighter monthly review can check whether key event volumes, campaign names, self-referrals, and form totals look plausible. A deeper audit is appropriate when a conversion rate changes unexpectedly, paid traffic appears to lose attribution, a dashboard stops updating, or CRM and analytics totals diverge more than usual.

End every audit with three actions: fix the highest-impact defect, assign an owner and deadline for remaining issues, and save the test evidence. Re-run the affected scenario after deployment, then update the tracking plan and campaign conventions. For ongoing reporting, connect the audit to a clear KPI framework; the landing page KPI checklist and Looker Studio dashboard guidance can help keep measurement tied to decisions rather than isolated event counts.