A troubleshooting guide to measuring traffic properly (GA4 basics)

A troubleshooting guide to measuring traffic properly (GA4 basics)

Getting reliable traffic data from GA4 is a practical requirement for any site that makes decisions from analytics, not a one-time setup task. This guide walks through the common failure points you will encounter when implementing GA4 and gives step-by-step checks to resolve them. It assumes you have a basic property and web data stream created, but it does not depend on any particular tag manager or CMS. The aim is to help you identify whether traffic is missing, duplicated, or misattributed and to restore trust in the numbers you use for optimisation and reporting.

Start with a simple diagnostic workflow that isolates the problem quickly so you do not chase unrelated settings. First confirm that the property and stream IDs in your site code match the GA4 property you expect. Second, confirm whether the issue is immediate (no hits appearing) or subtle (spikes, duplicates or misattribution). Third, use the debug tools that come with GA4 and your browser to capture a single user journey and compare the events you see in real time with what you expect. These steps will reveal whether the issue is a tagging problem, a configuration problem within GA4, or an outside factor such as consent settings or proxies.

• Verify the measurement ID in your site source matches the GA4 stream.
• Use GA4 DebugView to watch real-time events from your browser.
• Check Consent Mode and cookie banners for blocked hits.
• Inspect server-side redirects or proxies that may strip query parameters.
• Confirm any filters, data streams or internal traffic rules are not excluding valid sessions.

Tag installation problems are the most common cause of missing traffic and are usually straightforward to fix. If DebugView shows no events, clear caches and disable extensions that could block scripts, then reload the page in an incognito window with developer tools open to see network calls to mate-api or the measurement endpoint. If you use a tag manager, publish your container and use the tag manager preview mode to confirm the GA4 tag fires on the pages you expect. When tags fire but events do not appear, check for duplicate installations where a direct gtag snippet and a tag manager both send hits, which can create inflated counts unless configured to avoid duplication.

Misattribution and unusual traffic patterns often come from configuration issues rather than data loss. High levels of 'direct' traffic usually indicate missing referrer data due to incorrect cross-domain settings, broken redirect chains or blocked referrers from privacy tools. Check your referral exclusion list and cross-domain linking configuration if you operate across multiple domains so user sessions remain connected. For duplicate events, review event naming and parameters; small differences in casing or parameter labels create separate metrics in GA4. If you see a sudden drop in sessions, verify any new privacy or consent changes deployed on the site that might prevent the measurement script from running.

Events and conversions deserve particular attention because they drive goals and revenue calculations. Use the DebugView to validate that custom events carry expected parameters and that conversions are marked correctly in the GA4 interface. For ecommerce, verify that the purchase event includes transaction_id and value parameters consistently; missing transaction IDs are the most frequent cause of duplicate or missing revenue records. When you change event names or parameter structure, update any downstream reports and audiences immediately to avoid miscounting during the transition period. For more builds and experiments, visit my main RC projects page.

Final verification and ongoing practices help prevent recurring problems and restore confidence in your analytics. After making fixes, allow 24 to 48 hours for data to settle for aggregated reports while continuing to use DebugView and real-time reports for immediate validation. Maintain a short checklist to run after deployments that includes checking the measurement ID, previewing GTM containers, and confirming consent behaviour on commonly used browsers and devices. Keep documentation of your event definitions and a versioned record of changes to tag or server configurations so you can trace the cause of future anomalies. For more practical posts on diagnosing site and tracking issues, see this collection on our blog about SEO and growth strategies: SEO & Growth.