Troubleshooting guide to measuring traffic properly (GA4 basics)

Troubleshooting guide to measuring traffic properly (GA4 basics)

Getting readable, actionable traffic data from GA4 requires more than flipping a switch, and this guide focuses on practical troubleshooting steps to get measurements back on track. If you have sudden drops, duplicates, or unexplained spikes in sessions or conversions, you need a systematic approach rather than guesswork. This article walks through the common causes of faulty data, the checks to run in the interface and the browser, and the configuration points that most often cause problems for small sites and growing organisations.

Start with the tag and property setup because most errors stem from incorrect installation or multiple tags on the same pages. Confirm the Measurement ID matches the property you expect and that a single tag fires once per page load unless you intentionally send additional events. If you use Google Tag Manager, check the preview mode to verify triggers and tag firing conditions, and for single-page applications ensure page_view events are sent on virtual route changes so page metrics remain accurate.

Next, validate the data flow inside GA4 using DebugView and the real-time reports, as these show whether events reach the property immediately. Use the browser developer tools to inspect outgoing analytics requests and to spot blocked requests caused by ad blockers, strict cookie settings or consent banners that prevent measurement. If events appear in DebugView but not in standard reports, allow up to 24 hours for processing and watch for event or parameter sampling that may affect aggregated reports in large properties.

Configuration errors in GA4 settings can silently distort numbers, so check filters, internal traffic rules, and bot filtering to ensure you are not excluding legitimate visits or including test traffic. Misconfigured referral exclusions or missing cross-domain tracking are common causes of session fragmentation and self-referrals that make acquisition reports confusing. Review your list of domains in cross-domain settings and ensure any proxying or redirects preserve the client ID so sessions are stitched correctly across subdomains and third-party checkout flows.

Attribution and campaign tagging are frequent sources of disagreement between systems, so standardise your UTM parameters and be consistent with campaign naming conventions to avoid splitting traffic across multiple channels. Remember that GA4 attribution differs from Universal Analytics in default lookback and reporting, so conversion counts may change when you migrate. Check that conversions are set as events in the property and that you have not created duplicate conversion definitions that record the same event more than once.

Use a short checklist when troubleshooting: verify the exact Measurement ID on your pages, confirm a single tag fires per page, test with DebugView and real-time reports, inspect outgoing requests in the network tab, review filters and internal traffic rules, audit cross-domain and referral settings, and corroborate key metrics against server logs or hosting analytics where possible. For a curated set of posts and further reading on related tactics, see the collection in the SEO & Growth category on this site. For more builds and experiments, visit my main RC projects page.