GA4 Audit Checklist: 12 Checks Before You Trust a Report

A GA4 report is only useful when the collection layer is trustworthy. Before a team uses GA4 to judge campaign performance, run a compact audit that covers configuration, event quality, consent, and reporting logic.

1. Confirm the property and stream setup

Check that the web data stream matches the production domain, enhanced measurement is intentional, internal traffic filters are active, and cross-domain tracking is configured for checkout or app flows.

2. Review key events

List every event marked as a key event and map it to a real business outcome. Remove duplicate or legacy conversions that inflate performance.

3. Validate ecommerce events

For ecommerce sites, inspect view_item, add_to_cart, begin_checkout, and purchase. Confirm item arrays, transaction IDs, revenue, currency, tax, and shipping values are populated consistently.

4. Check traffic quality

Look for spikes in direct traffic, missing UTMs, self-referrals, payment gateway referrals, and abnormal hostname patterns. These issues often explain sudden attribution changes.

5. Compare GA4 with source systems

GA4 will not match your backend perfectly, but large gaps should be explained. Compare orders, revenue, leads, and signups against CRM or ecommerce records for the same date range.

Run this audit monthly and after every major website release. Small tracking regressions become expensive when they silently shape bidding and budget decisions.