GA4 Reporting Checklist: Verify Before You Trust Data

Before you make any marketing decisions based on GA4 data, verify these 10 critical elements. Most GA4 implementations we audit have at least 3-4 of these issues—and even one of them can lead to flawed reports that steer your budget in the wrong direction.

Before You Start: Prerequisites

Before diving into the checklist, make sure you have the right access and tools in place:

• Admin access to your GA4 property (you will need to verify settings, not just view reports)
• Google Tag Manager access if your implementation uses GTM (most do)
• Debug View enabled in GA4 — navigate to Admin > Debug View to confirm
• A test conversion you can trigger manually (for example, a form submission on a staging site)

If your setup uses server-side tracking, also confirm access to your server-side GTM container, since some events may fire from the server rather than the browser.

The 10-Point GA4 Audit Checklist

1. Data Stream Configuration

Your data stream is the foundation of everything in GA4. If it is misconfigured, every report downstream is affected.

Check that your data stream is configured correctly:

• Enhanced measurement events are enabled appropriately (page views, scrolls, outbound clicks, site search, video engagement, file downloads)
• Internal traffic filters are set up so your own team’s visits do not inflate metrics
• Referral exclusions include payment providers (Stripe, PayPal) and authentication flows (Auth0, Okta) — otherwise these show as referral sources and break session attribution

A common mistake is leaving enhanced measurement fully on without reviewing which events are relevant. For example, enabling scroll tracking on single-screen landing pages generates noise without insight.

2. Conversion Events

Verify your conversion tracking:

• Key conversions are marked as conversion events (called “key events” in newer GA4 versions)
• Conversion counting is set appropriately — “once per event” for purchases, “once per session” for lead forms
• Values are being passed correctly for e-commerce events (revenue, tax, shipping)

If you run paid media campaigns, your conversion data feeds directly into Google Ads bid strategies. Incorrect values here mean your automated bidding optimizes toward the wrong targets.

3. User Identification

Review your user identification setup:

• User ID is implemented if you have authenticated users (logged-in accounts)
• Google Signals is enabled (with privacy considerations — note that enabling Signals may apply thresholding that hides data in smaller segments)
• Reporting identity is set to your preferred method (Blended, Observed, or Device-based)

Getting user identification right reduces duplicate user counts and gives you a clearer picture of cross-device behavior.

4. Event Parameters

Check that critical events have proper parameters:

• E-commerce events include all required parameters (items, value, currency, transaction_id)
• Custom events follow GA4 naming conventions (lowercase, underscores, no spaces)
• Parameter values are within character limits (100 characters for event names, 500 for parameter values)

5. Cross-Domain Tracking

If you have multiple domains (for example, a main site and a separate checkout or booking system):

• Cross-domain measurement is configured in GA4’s data stream settings
• Linker parameters are being passed correctly between domains
• Self-referrals are excluded so domain transitions do not start new sessions

Without cross-domain tracking, a user who starts on yoursite.com and completes a purchase on checkout.yoursite.com appears as two separate sessions from two sources, making attribution impossible.

6. Consent Mode

For GDPR and ePrivacy compliance in the EU:

• Consent Mode v2 is implemented with both ad_storage and analytics_storage parameters
• Default consent states are set to denied before the user interacts with your consent banner
• Consent updates fire correctly when a user grants or denies permission
• Google’s behavioral modeling is enabled to fill gaps from non-consenting users

Misconfigured consent mode is one of the most common issues we see in EU-based GA4 setups. It creates both legal exposure and significant data loss — sometimes 30-60% of traffic goes untracked.

7. Debug View Validation

Use GA4 Debug View to verify events in real time:

• Events fire at the right moments (not too early, not duplicated)
• Parameters contain expected values (not undefined, null, or empty strings)
• No duplicate events are firing for the same user action

Debug View shows data immediately, while standard GA4 reports can take 24-48 hours. This makes it essential for validating changes before you assume they are working.

8. Real-Time Reports

Cross-check with real-time data in GA4’s reporting interface:

• Traffic appears immediately after you visit the site
• Conversions register correctly when you trigger a test event
• Geographic data is accurate (not showing your location incorrectly)

Real-time reports serve as a quick sanity check, but do not rely on them for detailed analysis — they sample heavily on high-traffic properties.

9. Historical Data Comparison

If you migrated from Universal Analytics (or have been running GA4 for over 6 months):

• Traffic patterns match expectations (seasonal trends, weekday/weekend patterns)
• Conversion rates are in reasonable ranges compared to prior benchmarks
• User counts align with expected differences (GA4 typically reports fewer users than UA due to different session and user counting methodologies)

Sudden drops or spikes that do not correlate with real business changes usually point to a tracking issue, not an actual traffic shift.

10. BigQuery Export

If using BigQuery for advanced analysis:

• Export is enabled and active (daily or streaming)
• Data is appearing in BigQuery tables with the expected date partitions
• Schema matches expectations — check that custom dimensions and event parameters are populating correctly

BigQuery export gives you access to raw, unsampled data. For advertisers spending significant budgets, this is essential for building custom Looker Studio dashboards and running attribution models that go beyond GA4’s built-in reports.

Common Mistakes to Avoid

Even experienced teams make these errors:

1. Not filtering internal traffic — Your team visits the site daily. Without IP or header-based filters, their activity inflates engagement metrics and pollutes conversion data.

2. Ignoring data thresholds — GA4 applies thresholding when Google Signals is enabled and audience sizes are small. If you see “(other)” rows or missing data, this is often the cause — not a tracking failure.

3. Forgetting to re-test after changes — Every GTM container update, CMS migration, or consent banner change can break existing tracking. Build a post-deployment verification step into your release process.

4. Treating all conversions equally — A newsletter signup and a purchase are not equal. Use different conversion counting methods and assign appropriate values so your paid media reporting reflects actual business impact.

5. Skipping Consent Mode in the EU — Without Consent Mode, you lose data from every user who does not consent, and you risk non-compliance with GDPR. Both problems are avoidable.

Next Steps

If you found issues in your GA4 setup, don’t panic. Most of these can be fixed without losing historical data. Prioritize the items that directly affect your conversion tracking and paid media attribution first — those have the highest business impact.

For a broader look at how tracking fits into your overall measurement strategy, read our GTM server-side tracking guide and our GA4 e-commerce tracking setup walkthrough.

Need help? Get a free analytics audit and we’ll walk you through exactly what needs fixing.