Google Analytics showing no data? It's usually one of four things

Here is the finding that reframes this whole question: of 936 live sites our scanner audited recently, 37% had no working Google Analytics at all. Not misconfigured. Absent, dead, or disconnected. Nearly all of those sites belong to people who would tell you, sincerely, that analytics is installed, because at some point somebody installed something.

So if your property shows no data, you are not in a weird edge case. You are in the most common measurement state on the internet. The empty dashboard has four usual causes.

Skip the archaeology if you want. A free Mimetic scan checks your live site from the outside, tells you which of the four this is, and if the answer is "nothing is installed," sets up a Google Analytics property you own, one click, in minutes.

1. The tag is not there (or it's a corpse)

The most common cause is the simplest: nothing on the page sends data. A theme update wiped the header snippet. A replatform launched clean. Or the tag that is there is a Universal Analytics UA- tag, dead since Google shut that system off in 2023, still sitting in page sources across the web sending data into the void.

The subtler corpse: Google Tag Manager. We find GTM on 45% of the sites we audit, and a GTM container is one extra failure layer: a container that was created but never published, or published without an analytics tag inside, loads flawlessly and measures nothing.

The tell: Realtime cannot see your own visit. Everything else in this article assumes you checked this first.

2. The data goes somewhere you are not looking

Businesses accumulate properties: the agency's, the founder's first attempt, the plugin's auto-created one. Among sites with working GA4, our scans find one in five running two or more properties at once. "No data" is very often "data, arriving faithfully, into the other property." The tell: the measurement ID in your page source does not match the property open in your other tab.

3. Consent kills it before it sends

29% of the sites we audit fire trackers before any consent decision, and 28% have consent configurations that drop data outright. The failure that produces a truly empty property: a banner shipped with denied-by-default for everyone, everywhere, including markets where that was never required. The visitors most likely to ignore a banner are all visitors; denied-by-default plus an ignored banner equals a property that flatlines the day the banner ships. That launch date is the tell.

4. You are testing through your own blocker

Roughly one in five browsers blocks analytics requests outright. If the developer checking whether analytics works is running one, they can stare at a perfectly healthy setup and see nothing. Test in a clean private window, blocker off, before concluding anything. This also means your numbers permanently run below reality, for everyone, which matters when you compare analytics against platform orders and wonder about the gap.

The part worth sitting with

We also found 67 sites running ad pixels with no analytics behind them: money going into paid traffic with literally no measurement of what happens after the click. That is the extreme end of a spectrum most sites are on somewhere: the gap between what owners believe is measured and what actually is. The belief forms at install time; the reality decays with every theme update, banner, and replatform after that. Nobody re-checks, because nothing visibly breaks.

Any competent developer, or an AI assistant with your page source, can fix causes one through four once identified. Identification is the part that requires actually looking, at your live site, from outside, the way a visitor's browser sees it.

Mimetic scans your site free and reports what is actually measured versus what you think is, then ships fixes as pull requests you review. No analytics at all? It provisions Google Analytics and Search Console you own, one click. Related: GA4 not tracking conversions, conversion tracking setup.