GA4 Audit Checklist: 40 Issues to Check Before You Trust Your Data

Overview

A GA4 audit is a structured review of whether your analytics setup still reflects reality. That matters because GA4 rarely fails in one obvious way. More often, tracking degrades gradually: a tag stops firing on one template, a form event changes name after a redesign, a cross-domain session breaks, or traffic attribution becomes inconsistent because UTM parameters are incomplete.

The source material behind this topic makes the core point clearly: GA4 is powerful only when it is set up correctly, and regular audits help identify broken tags, missing conversions, and attribution gaps before they distort decisions. The safest evergreen way to think about an audit is not as a one-time clean-up, but as a recurring maintenance process.

Use the checklist below as a living document. You do not need every item for every site, but you should be able to explain why each item is either correct, intentionally excluded, or still in progress.

The 40-point GA4 audit checklist at a glance

1. Confirm the correct GA4 property is in use.
2. Check the right web data stream is active.
3. Verify the Measurement ID matches the implementation.
4. Make sure no duplicate GA4 tags are firing.
5. Confirm Google Tag Manager or direct gtag deployment is documented.
6. Check enhanced measurement settings against site needs.
7. Review internal traffic rules.
8. Review unwanted referral settings.
9. Verify cross-domain tracking for all connected domains.
10. Check data retention settings.
11. Confirm timezone and currency are correct.
12. Review user access and governance.
13. Check consent mode or privacy controls are behaving as expected.
14. Verify page_view fires once per page load where intended.
15. Check session_start and first_visit patterns for anomalies.
16. Validate key recommended events.
17. Validate custom event naming conventions.
18. Check parameter consistency across similar events.
19. Confirm form tracking works on all key forms.
20. Check file downloads, outbound clicks, and site search if relevant.
21. Verify ecommerce events if applicable.
22. Confirm conversions are marked correctly in GA4.
23. Make sure conversion events fire only once per intended action.
24. Review lead qualification stages versus tracked conversions.
25. Check event counts against back-end or CRM reality where possible.
26. Verify traffic source dimensions populate as expected.
27. Test UTM parameters using real campaign URLs.
28. Check channel grouping logic in reports.
29. Review paid media integrations, including Google Ads where applicable.
30. Check landing page analytics for major campaigns.
31. Verify referral traffic is not absorbing self-referrals.
32. Look for sudden spikes in direct or unassigned traffic.
33. Review key reports and explorations for decision-usefulness.
34. Confirm important dimensions and metrics are available in reporting.
35. Check Looker Studio or dashboard dependencies.
36. Inspect debug tools during live testing.
37. Review annotations or change logs outside GA4.
38. Check subdomain behavior and session continuity.
39. Verify filters, comparisons, and definitions used by stakeholders.
40. Document issues, owners, priority, and next review date.

Checklist by scenario

The most useful GA4 audit is organized by risk area. Start with the foundation, then move toward events, conversions, and attribution.

1. Property and stream setup

These are the checks that determine whether data is entering the right place and being interpreted in the right context.

• Property and stream: Make sure the site points to the correct GA4 property and the intended data stream. This sounds basic, but multi-brand and staging environments often create confusion.
• Measurement ID: Compare the Measurement ID in your site or tag manager with the stream settings in GA4.
• Duplicate tags: Use browser tools, Tag Assistant, or GTM preview to check whether GA4 is firing twice via both hardcoded and GTM implementations.
• Enhanced measurement: Review whether page views, scrolls, outbound clicks, site search, file downloads, and video engagement are useful for your site. Leave on what supports analysis; turn off what adds noise.
• Timezone and currency: A wrong timezone can make daily reporting and campaign analysis unreliable. Currency mismatches can distort revenue reporting.
• Data retention: Confirm settings align with your reporting needs, especially for trend analysis and explorations.
• Access control: Audit admin permissions. Too many editors create drift. Too few creates bottlenecks.

2. Privacy, referrals, and domain behavior

Many data quality issues are caused by session handling and privacy configuration rather than event setup alone.

• Internal traffic: Exclude or identify office and developer traffic if it materially affects reporting.
• Unwanted referrals: Add payment gateways, booking tools, and known self-referral sources where appropriate.
• Cross-domain tracking: If users move between main site, checkout, scheduler, help center, or app domain, verify session continuity. Broken cross domain tracking is one of the most common causes of campaign attribution loss.
• Consent behavior: Check whether GA4 loads and records data in line with your consent setup. Audit both accepted and declined states.
• Subdomains: Confirm blog, shop, and app subdomains are tracked as intended, with consistent session logic.

3. Event tracking quality

This is where GA4 implementation quality becomes visible. Event collection should be complete, intentional, and consistent.

• page_view: Verify it fires once on standard page loads and behaves correctly on single-page application routes if relevant.
• Automatic lifecycle events: Scan for unusual patterns in session_start and first_visit. Sudden jumps can suggest duplicate tagging or environment issues.
• Recommended events: For leads, sign-ups, purchases, downloads, video starts, and searches, confirm you use GA4-friendly naming where possible.
• Custom event naming: Standardize names. Avoid near-duplicates like form_submit, submit_form, and lead_form_submit all describing the same action.
• Parameters: Make sure similar events carry the same supporting parameters, such as form name, page type, plan, product category, or content group.
• Form tracking: Test every important form: contact, demo, newsletter, quote, lead magnet, and checkout steps if relevant. Confirm the event fires only after a real success state, not on button click alone.
• Site search: If internal search matters, verify search terms are detected properly.
• File downloads and outbound clicks: Check whether these interactions are recorded for key assets and partner links.
• Ecommerce: If applicable, review item-level events across the funnel, not just purchase. Missing add_to_cart or begin_checkout events makes funnel analysis weak.

4. Conversion tracking and business alignment

Not every event should be a conversion. Your audit should distinguish between activity and outcome.

• Conversion selection: Confirm only meaningful business outcomes are marked as conversions in GA4.
• Single-fire logic: A thank-you page refresh or duplicate event trigger can inflate leads or purchases.
• Lead stages: If the sales process includes raw lead, qualified lead, booked call, and closed customer, define which stages belong in GA4 and which belong in CRM reporting.
• Back-end comparison: Compare GA4 conversion trends with CRM, ecommerce platform, or form database totals. They will not always match exactly, but large unexplained gaps deserve investigation.
• Primary reporting metric: Make sure teams are not optimizing around weak proxies when better conversion signals exist.

5. Campaign tracking and attribution

Even when events fire correctly, attribution can still fail. Audit how visits and conversions are classified.

• UTM parameters: Test campaign URLs and confirm source, medium, and campaign values populate as expected.
• Consistency: Standardize naming conventions. Mixed values like PaidSocial, paid-social, and social_paid reduce clean reporting.
• Google Ads linkage: If you run Google Ads conversion tracking, verify account links and imported conversions where relevant.
• Other platforms: Review how Meta pixel tracking or other ad platforms compare with GA4 so stakeholders understand differences in attribution model and counting logic.
• Direct and unassigned traffic: A rise here often signals UTM gaps, redirects stripping parameters, or cross-domain issues.
• Landing page analytics: Check major campaign landing pages for realistic sessions, engagement, and conversion patterns.
• Self-referrals: If your own domains appear as referrals, attribution is probably breaking mid-journey.

6. Reporting and stakeholder usability

A technically correct setup still fails if nobody can use the data reliably.

• Core reports: Confirm your standard acquisition, landing page, conversion, and funnel views answer common business questions.
• Definitions: Align on what counts as a session, engaged session, lead, qualified lead, and conversion.
• Dashboards: Review Looker Studio dashboard logic, calculated fields, blended data sources, and broken filters.
• Dependencies: Document any report that relies on custom definitions, imported data, or manual spreadsheet work.
• Change log: Keep an external record of tag releases, redesigns, consent updates, and campaign naming changes. GA4 data makes more sense when there is context.

What to double-check

Some issues are easy to miss because the account appears healthy at first glance. These deserve extra attention during any analytics audit.

Duplicate measurement

One of the fastest ways to ruin GA4 data accuracy is to fire the same event from more than one source. This often happens after migrations, plugin installs, or partial GTM rollouts. If sessions look inflated, event counts jump unexpectedly, or conversion rates look unusually strong, check for duplicate tags first.

Form submissions that track intent, not completion

Many sites record a conversion when someone clicks a submit button. That is not the same as a completed form. Use success-state tracking whenever possible: a thank-you page, confirmation message visibility, or validated callback from the form system.

Cross-domain breaks during checkout or booking

If a user starts on your main site and finishes on another domain, campaign attribution may reset unless cross domain tracking is configured correctly. In practice, this can make paid campaigns look weaker and direct traffic look stronger than they really are.

Channel noise caused by inconsistent UTMs

A robust UTM strategy matters because GA4 can only classify what you pass to it. Audit the URLs used by email, paid social, partnerships, and offline QR campaigns. A simple naming standard often improves campaign attribution more than a complex dashboard rebuild.

Report trust versus report convenience

Teams often rely on the dashboard that is easiest to access, not the one with the cleanest logic. Reconcile headline numbers between GA4, ad platforms, CRM, and any marketing dashboard template before performance reviews. Small differences are normal; unexplained differences should be documented.

Common mistakes

Most GA4 problems are not caused by one dramatic setup error. They come from ordinary changes that nobody re-tested.

• Treating setup as finished: A correct launch does not guarantee ongoing tracking quality.
• Marking too many events as conversions: This makes optimization noisy and reporting less useful.
• Ignoring attribution hygiene: Incomplete UTM parameters and broken referral exclusions quietly weaken campaign reporting.
• Using inconsistent event names: This creates fragmented reports and messy exploration work.
• Skipping real-user testing: A tag that fires in preview mode may still fail on certain devices, templates, or consent states.
• Not comparing against business systems: GA4 should be directionally consistent with CRM or transaction records, even if totals differ.
• Overlooking dashboard logic: Reporting errors can come from Looker Studio calculations as easily as from GA4 itself.
• Failing to document decisions: Without naming rules, ownership, and change history, the same errors return.

If you run experimentation or conversion rate optimization work, measurement discipline matters even more. A weak analytics foundation makes test readouts less trustworthy. For a related framework on forming stronger testing ideas, see Design Better A/B Tests by Mining Academic and Trade Literature for Hypothesis Validation.

When to revisit

The best GA4 audit checklist is the one you actually reuse. Revisit this process on a schedule and whenever your inputs change.

• Before seasonal planning cycles: Check conversion tracking, campaign attribution, and landing page analytics before budget is committed.
• When workflows or tools change: New form providers, booking tools, payment systems, cookie banners, and CMS templates often affect website tracking.
• After redesigns or migrations: Test key journeys immediately, not weeks later when reporting gaps appear.
• After major campaign launches: Validate UTM parameters, paid integrations, and landing page behavior with live traffic.
• Quarterly for most sites: A light recurring review catches drift before it becomes a reporting crisis.

A simple recurring audit routine

1. List your top five business-critical user actions.
2. Test each action manually in debug mode.
3. Check whether the right event name, parameters, and conversion status appear.
4. Review attribution for one live campaign URL from each major channel.
5. Compare GA4 totals against one outside system.
6. Document any gaps, assign an owner, and set a retest date.

If your reporting stack is expanding beyond GA4 into dashboards, predictive models, or high-volume event processing, it is worth thinking about tracking quality as infrastructure rather than just tagging. Two useful follow-on reads are Modeling Networking Bottlenecks for High-Volume Tracking Systems and Estimating Your Cloud TCO for AI-Enhanced Analytics.

The practical takeaway is simple: do not trust GA4 by default, and do not distrust it by habit. Audit it. A calm, repeatable review process is what turns web analytics from a source of debate into a usable decision system.