Data & Tracking
Google Analytics shows no data received from your website yet: causes and fixes
Copy for AI
An empty GA4 report almost always has one of six causes.
When Google Analytics shows no data, or keeps saying “no data received from your website yet”, check these first:
- a dead Universal Analytics code
- a missing GA4 tag or a wrong measurement ID
- an install that’s simply too recent
- a cookie banner that blocks GA4
- a filter or data stream set up wrong
- visitors who block the tag
The verdict: work from the page source towards the reports, never the other way round. That finds the cause in about fifteen minutes.
This guide is for empty or nearly empty reports. If your numbers are there but wrong (untagged campaigns, duplicate pageviews, your own domain as a referrer), read the Google Analytics tracking errors that make your GA4 data unusable.
How common is “no data received from your website yet”?
More common than you’d think, especially at smaller professional firms.
What our scan of 39 Belgian sites showed
We scanned 39 Belgian websites on 6 October 2026. Here’s what the HTML showed:
Fourteen sites showed no analytics or advertising tag at all.
Four only had a Universal Analytics ID left in the source code.
A check in a real browser confirmed that two of those four really ran dead UA tracking.
The other two loaded GA4 another way, for example through Google Tag Manager.
Lesson: the page source alone doesn’t prove you measure nothing.
Cause 1: is your site still running Universal Analytics?
If the ID in your source code starts with UA-, you measure nothing.
According to Google, standard Universal Analytics properties stopped processing data starting 1 July 2023. Universal Analytics 360 got an extension until 1 July 2024.
Since the week of 1 July 2024, the interface and the API are gone too. That includes your historical UA data.
Why nobody notices
The old code keeps loading. There’s no error message.
So nobody notices until someone opens a report.
That’s why we still come across these dead tags so often.
Fix: create a GA4 property and install the Google tag with your G- ID.
Then remove the old UA code, so your theme or plugin stops calling a service that no longer exists.
The differences between both systems are in GA4 vs Universal Analytics. The setup for a B2B site is in how to set up Google Analytics 4 for B2B.
Cause 2: is the GA4 tag missing, wrong or not published?
The second big group is a GA4 install that never really went live. The classics:
- Wrong measurement ID: the
G-code belongs to another property or stream. - GTM container not published: it works in preview, but nobody clicked Submit.
- Container not on every page: a new template or webshop skips the snippet.
- Wrong trigger: or an exception that excludes too many pages.
For example, the G- ID might belong to your test environment’s stream.
Everything fires. Yet your live property stays empty.
How to find the ID that actually loads
Open your site and look which G- ID loads, in the source code or in Tag Assistant.
Compare it with the ID in GA4 under Admin, Data streams.
Then publish the Google Tag Manager container and test again.
Rule of thumb: one site, one live G- ID, one published container.
Cause 3: is your GA4 install just too recent?
Sometimes waiting is the whole answer.
Google writes that data collection may take up to 30 minutes to begin. It recommends the Realtime report to verify that data is coming in.
Standard reports take longer.
Data processing can take 24 to 48 hours, and figures may still change during that period.
Check Realtime first
See visitors in the real-time report? Then your tag works.
You just need a day of patience.
Once processing catches up, the standard reports fill in. Here’s what that looks like in a working property, filtered on one source:
GA4 Traffic acquisition in our own property, last 90 days, October 2026: 58 sessions from chatgpt.com.
Is Realtime still empty after half an hour while you browse the site yourself? Move on to the next causes.
Cause 4: does your cookie banner block GA4?
This is the most common cause of a sudden drop after a new or changed cookie banner.
In basic consent mode, Google tags are blocked until the visitor interacts with the consent banner. Google adds that no data at all is sent before that interaction, not even the default consent status.
If someone declines, or simply closes the banner, you never see that visitor.
Basic versus advanced consent mode
In advanced consent mode the tags load straight away with status denied.
They send cookieless pings, which give Google enough to model the missing data.
The right variant depends on your privacy policy and on how much you steer on paid traffic. We work through that choice in Consent Mode v2.
| Basic consent mode | Advanced consent mode | |
|---|---|---|
| Tags before a choice | Blocked | Load with status denied |
| Data before a choice | Nothing at all | Cookieless pings |
| Modelling of gaps | No | Yes |
The opposite mistake
A banner that blocks nothing also exists.
GA4 then seems to work. But you’re setting cookies before anyone consented.
You can check that yourself in five minutes with how to check cookies on a website.
Does a drop in your reports coincide with a banner change? Check your consent tool first, for example Cookiebot, before you touch GA4 itself.
Cause 5: are filters, internal traffic or the wrong data stream hiding data?
Sometimes the data does come in, but drops out before it reaches your report:
- Internal traffic filter: set too broadly, for example an IP range covering visitors.
- Wrong data stream: you look at an empty stream, the data sits elsewhere.
- Forgotten comparison or filter: one you once set on a report yourself.
- Wrong property: picked in the selector, common with several sites.
Check the data filters (active or in testing mode) and the data streams under Admin.
Then verify that your stream’s URL matches the domain you measure on.
Watch out: note each filter’s state, testing or active, before you change anything.
Cause 6: do ad blockers and browsers block measurement?
Part of your visitors block Google Analytics with an ad blocker or a browser privacy feature.
That never explains a report with zero visitors.
It does explain a structural gap with your server logs or your CRM.
Why B2B sites feel this more
With a B2B audience full of technical profiles, that gap can be bigger.
Server-side tagging changes where and how your data is processed.
It gives you more control over what reaches Google. It doesn’t replace consent.
Read what it does and doesn’t solve in server-side tagging.
The overview: symptom, cause, check and fix
Match your symptom to a row, then run the check in the third column:
| Symptom | Likely cause | Check | Fix |
|---|---|---|---|
| Reports empty since July 2023 | Only a UA- code | Page source, search for UA- and G- | Install GA4, remove the UA code |
| New property, nothing yet | Installed too recently | Realtime report after 30 minutes | Wait 24 to 48 hours for standard reports |
| Realtime stays empty | Tag missing or wrong measurement ID | Tag Assistant, network request to g/collect | Correct G- ID, publish the container |
| Sudden drop after a banner change | Basic consent mode or a consent error | Tag Assistant, Consent tab | Reconfigure consent defaults and tags |
| Data in Realtime, not in reports | Filter or wrong property | Admin, Data filters and Data streams | Adjust the filter, pick the right property |
| GA4 counts less than your CRM | Ad blockers, declined consent | Compare with server logs or leads | Server-side tagging, advanced consent mode |
How to test it in fifteen minutes
Run these five checks in this order.
Each one rules out a layer.
Step 1: read the page source
Open your site, view the page source and search for G-, UA- and GTM-.
That tells you what should load.
Step 2: open Tag Assistant
Connect your site in Tag Assistant.
Then look at which tags fire, with which ID and which consent status.
Step 3: watch the network request
Open your browser’s developer tools, Network tab, and filter on collect.
Reload the page.
A request to g/collect carrying your G- ID means data is leaving.
Tip: if a request only appears after a click on the banner, you’re working with basic consent mode.
Step 4: check DebugView
With Tag Assistant or GTM preview, debug mode switches on automatically, Google explains.
Your own events then show live in DebugView, under Admin, Data display.
Step 5: only then, the property settings
Look at filters, data streams and report settings only when all previous steps show data.
Want to see what your site loads before anyone clicks the banner? Our cookie scanner shows which cookies and tags fire without a single click.
When should you have this checked?
You can often fix the six causes above yourself.
It gets harder when consent, Google Tag Manager, GA4 and Google Ads all play a part.
Or when nobody remembers who placed which tag. That’s when it’s worth a second pair of eyes.
With a tracking audit we map what your site measures today, what’s missing and what isn’t compliant.
Want it set up correctly straight away, with consent, GA4 and conversions? Our tracking specialist does it for you. It’s priced on request.
Frequently asked questions
Why does Google Analytics say no data received from your website yet?
Usually because your site still only loads a Universal Analytics code, the GA4 tag is missing or has the wrong measurement ID, the install is less than 24 to 48 hours old, or your cookie banner blocks GA4 until someone consents. Work through the checks in the order of this guide.
Does Universal Analytics still work?
No. Standard Universal Analytics properties have not processed data since 1 July 2023, and since July 2024 the interface and your historical data are no longer available either. A UA- code on your site sends nothing useful.
How long does it take before GA4 shows data?
Data collection can take up to 30 minutes to begin; the Realtime report is the fastest check. Standard reports can lag 24 to 48 hours behind.
Why do I see fewer visitors since my new cookie banner?
Because GA4 no longer measures visitors who decline or do not respond, or in advanced consent mode only receives cookieless pings. That is the expected result of correct consent, not an error. Do check that the banner is set up correctly and that declining does not also hit visitors who did consent.
How do I know my GA4 tag works without waiting?
Check in your browser’s network traffic whether a request to g/collect with your G- ID leaves, and open DebugView through Tag Assistant. If your own visit shows there, the tag works.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.