A client called me last month convinced his new website had crashed. Three days of visitors, he said, and Google Analytics was showing zero. The site was fine. The traffic was real. The tracking was broken. This happens more often than people expect, and almost every time the cause is one of a handful of predictable mistakes.
Start By Confirming the Tracking Code Actually Fires
Before you assume anything is wrong with your account, check whether the GA4 tag is firing on the page at all. Open your site in an incognito window, right click and choose inspect, then go to the network tab and filter for “collect”. Reload the page and watch for a request to Google’s servers. If nothing shows up, GA4 is not firing, and the problem is on the site, not inside your analytics account.
This single check saves hours of guessing. If the tag fires and you still see zero traffic in GA4, the issue is almost always a reporting delay or a filter, not a broken installation.
Check For a Duplicate Or Missing Measurement ID
One of the most common causes of GA4 showing no data is a mismatched measurement ID. If you set up GA4 through Google Tag Manager, confirm the configuration tag is pointing at the correct property, not an old test property or a property that was deleted during a migration.
It is easy to copy the wrong ID when you have more than one GA4 property for testing and production. Open your GA4 admin panel, go to data streams, and copy the measurement ID directly from there. Paste it into your tag configuration rather than retyping it. A single transposed character will send your data nowhere and GA4 will never throw an error to warn you.
Look At Your Consent Mode and Cookie Banner Setup
If you run a consent management platform like CookieYes, your cookie banner may be blocking analytics tags until a visitor explicitly accepts tracking. Depending on how consent mode is configured, this can mean a large share of visitors never trigger a GA4 event at all, especially if the default state denies analytics storage.
Check your consent mode configuration in Google Tag Manager under the consent overview. If analytics storage defaults to denied and your banner has a bug or an aggressive default region setting, you can lose most of your traffic data without any error appearing anywhere. This is worth testing directly: load your site as a new visitor, decline cookies, then accept them, and watch the network tab each time to see what actually changes.
Regional consent rules can quietly cut off traffic
Some consent tools apply strict defaults only to visitors detected in certain regions, but misconfigured IP detection can apply those strict defaults globally. If your audience is mostly US based but your banner is set up with EU style defaults, you may be blocking tracking for visitors who should never have seen that banner behavior in the first place.
Rule Out a Google Tag Manager Publishing Issue
If you manage your tags through Google Tag Manager, it is possible to build and test a tag correctly in preview mode, then forget to publish the container. Preview mode will show the tag firing perfectly, which creates false confidence. Meanwhile the live site is still running whatever was published last, which might be an older version without the GA4 tag at all.
Check the container’s publish history in Tag Manager and confirm the most recent version includes the GA4 configuration tag, and confirm that version is the one marked live. This single step catches a surprising number of zero traffic cases.
Remember GA4 Reporting Has a Natural Delay
Even with everything set up correctly, GA4 does not show real time results in every report. Standard reports can take anywhere from a few hours up to a full day to populate, depending on the report type. If you are checking standard reports immediately after launching a site, give it time before assuming something is broken.
The Realtime report is the one exception. If you load your site yourself and nothing shows up in Realtime within a minute or two, that is a genuine signal of a tracking problem rather than a reporting delay, and you should go back to checking the network tab.
When To Bring In Help
Most zero traffic issues trace back to one of the causes above: a tag that never fires, a wrong measurement ID, a consent mode default that blocks analytics, or an unpublished Tag Manager container. Working through them in order usually finds the problem within twenty minutes.
If you have checked all of these and your GA4 property is still showing no data, the setup may need a closer look at how your tags, triggers, and consent configuration interact. That is exactly the kind of diagnostic work we handle at Dany.Net. Reach out and we can walk through your account together and get your data flowing again.