Google Analytics shows no data received from your website yet: causes and fixes

When Google Analytics shows no data, or keeps saying that no data has been received from your website yet, the cause is almost always one of six things: your site still runs a dead Universal Analytics code, the GA4 tag is missing or carries the wrong measurement ID, your install is too recent, your cookie banner blocks GA4 entirely, a filter or data stream is set up wrong, or part of your visitors block the tag. You can find the right cause in fifteen minutes by working from the page source towards the reports, not the other way round.

This guide is about the moment your reports are empty or nearly empty. If your numbers are there but wrong (untagged campaigns, duplicate pageviews, your own domain showing up as a referrer), read the Google Analytics tracking errors that make your GA4 data unusable.

How common is this?

More common than you would think, especially at smaller professional firms. In our own scan of 39 Belgian websites on 6 October 2026, 14 sites showed no analytics or advertising tag at all in their HTML. Four sites only had a Universal Analytics ID left in the source code. A check in a real browser confirmed that two of them were indeed running dead UA tracking; the other two loaded GA4 another way, for example through Google Tag Manager. That last point is a lesson in itself: a look at the page source alone is not enough to conclude that you measure nothing.

Cause 1: your site still runs 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, access to the interface and the API is gone too, including your historical UA data.

The code keeps loading in the meantime. Your site shows no error, so nobody notices until someone opens a report. That explains why we still come across these dead tags so often.

Fix: create a GA4 property, install the Google tag with your G- ID and remove the old UA code, so your theme or plugin stops sending requests to a service that no longer exists. The difference between the two systems is covered in GA4 vs Universal Analytics, and the setup for a B2B site in how to set up Google Analytics 4 for B2B.

Cause 2: the GA4 tag is 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 in your tag belongs to another property or another data stream, for example the one of a test environment.
• GTM container not published. The tag is ready in Google Tag Manager, works in preview, but nobody clicked Submit.
• Container not on every page. A new page template, a landing page builder or a separate webshop does not load the GTM snippet.
• Tag on the wrong trigger, or with an exception that excludes more pages than intended.

Fix: open your site, find which G- ID loads in the source code or in Tag Assistant, and compare it with the ID in GA4 under Admin, Data streams. Then publish the container and test again.

Cause 3: your install is too recent

If you just installed GA4 and the interface says no data has been received yet, waiting is sometimes the whole answer. Google writes that data collection may take up to 30 minutes to begin, and 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.

If you see visitors in the real-time report, your tag works and you just need a day of patience. If that report is still empty after half an hour while you browse the site yourself, move on to the next causes.

Cause 4: your cookie banner blocks 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, and 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.

In advanced consent mode the tags load straight away with status denied and send cookieless pings. That gives Google enough to model the missing data. Which variant fits depends on your privacy policy and on how much you steer on paid traffic; we work through that choice in Consent Mode v2.

The opposite mistake also exists: a banner that blocks nothing. GA4 then seems to work, but you set cookies before anyone consented. How to check that yourself in five minutes is explained in how to check cookies on a website. If a drop in your reports coincides with a banner change, check the configuration of your consent tool first, for example Cookiebot, before you start tinkering with GA4 itself.

Cause 5: filters, internal traffic or the wrong data stream

Sometimes the data does come in, but drops out before it reaches your report:

• An internal traffic filter that is set too broadly, for example an IP range that also covers your visitors.
• A data stream for the wrong domain, so you look at an empty stream while your real data sits in another property.
• A report with a comparison or filter you once set yourself and forgot.
• The wrong property in the selector at the top, common at agencies or companies with several sites.

Check the data filters (active or in testing mode) and the data streams under Admin, and verify that the URL of your stream matches the domain you measure on.

Cause 6: ad blockers and browsers that block measurement

Part of your visitors block Google Analytics with an ad blocker or a privacy feature in their browser. That never explains a report with zero visitors, but it does explain a structural gap with your server logs or your CRM. With a B2B audience full of technical profiles, that gap can be bigger. Server-side tagging changes where and how your data is processed and gives you more control over what reaches Google. It does not replace consent. Read what it does and does not solve in server-side tagging.

The overview: symptom, cause, check and fix

How to test it in fifteen minutes

1. Page source. Open your site, view the page source and search for G-, UA- and GTM-. That tells you what should load.
2. Tag Assistant. Connect your site in Tag Assistant and look at which tags fire, with which ID and which consent status.
3. The network request. Open your browser’s developer tools, Network tab, filter on collect and reload the page. A request to g/collect carrying your G- ID means data is leaving. If something only appears after a click on the banner, you are working with basic consent mode.
4. DebugView. With Tag Assistant or GTM preview, debug mode is switched on automatically, Google explains. Your own events then show live in DebugView, under Admin, Data display.
5. Property settings. Only when all previous steps show data do you look at filters, data streams and report settings.

Want to see what your site loads before anyone clicks the banner? Use our cookie scanner: it shows which cookies and tags fire without any button being pressed.

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. With a tracking audit we map what your site measures today, what is missing and what is not compliant. If you want the measurement set up correctly straight away, with consent, GA4 and conversions, our tracking specialist does it for you. Pricing on request.

Frequently asked questions