GA4 Data Stream Validation: How to Verify Your Setup Is Correct

Verifying the Measurement ID Is Correctly Implemented

The measurement ID (G-XXXXXXXXXX) must be correctly deployed on every page of the site and must match the data stream configured in GA4 Admin.

A mismatch (caused by copying from a different property, using a staging measurement ID in production, or deploying a measurement ID that has since been deprecated) means events are either going to the wrong property or being rejected entirely.

To validate, inspect the GA4 network requests in your browser developer tools: filter for requests to "google analytics. com/g/collect" and look for the "tid" parameter, which should match your measurement ID exactly.

Then cross reference against your GA4 Admin to confirm the measurement ID belongs to the correct property. Also check that the measurement ID is firing on all critical pages, not just the homepage.

A sampling check across product pages, checkout steps, and confirmation pages ensures the tag is consistently deployed rather than only on the pages that were tested during implementation.

Enhanced Measurement Settings: What to Enable and Disable

GA4's enhanced measurement feature automatically tracks several interaction types without custom code: page views, scrolls (90% threshold), outbound clicks, site search, video engagement (for YouTube embeds with JS API support), and file downloads.

These are useful defaults, but they require validation rather than blind trust. The scroll trigger fires at 90% page depth.

For most content pages this is appropriate, but for very long pages or single page applications where the DOM continuously adds content, the 90% trigger may fire multiple times or not at all.

Site search tracking requires that your search results URL include a query parameter. If your search uses a POST request or a non standard URL structure, the automatic tracking will miss searches entirely.

Video engagement only works for YouTube embeds with the JS API parameter added. Embeds without this parameter will not fire video events.

Audit each enhanced measurement setting against your actual site implementation rather than assuming they work correctly by default.

Cross-Referencing Stream Data with Realtime Reports

The fastest validation method for a data stream is the Realtime report in GA4 combined with DebugView.

Visiting your own site (without an active internal traffic filter to keep it simple for this test) should produce events visible in Realtime within 5 to 10 seconds.

If no events appear after a page load, the tag is either not firing, firing with the wrong measurement ID, or being blocked by a browser extension or CSP policy.

Content Security Policy headers that do not include Google Analytics domains in their connect src directive will silently block all GA4 requests without any visible error in the browser UI.

This is a common cause of GA4 "not receiving data" reports in organisations with strict security teams.

Checking the browser console for CSP violation errors alongside the network request inspection gives you a complete picture of whether the data stream connection is genuinely healthy.