The error nobody sees
Open your browser console on a site running Google Analytics with an ad blocker active and you will often find a familiar line: a request to the analytics endpoint failed, blocked by the client. No visible error, no broken page. The visitor browses normally and simply never appears in your reports.
That is the whole problem: blocked analytics fails silently, so the data looks complete.
Why it gets blocked
Ad blocking extensions. The major blocklists include Google Analytics domains by default, because the same infrastructure supports advertising products.
Browser tracking protection. Several browsers ship with tracking protection enabled by default, and privacy-focused browsers block known analytics endpoints out of the box.
DNS-level filtering. Network-wide blockers used at home and in offices resolve tracking domains to nothing, which removes the request before it is made.
Corporate policy. Many company networks block third-party analytics wholesale.
How much traffic does it cost?
There is no universal number, because it depends entirely on your audience. The pattern is consistent, though:
- Technical and developer audiences have the highest blocked rates by a wide margin.
- Privacy-conscious and European audiences block more than average.
- Mainstream consumer and mobile audiences block least.
If your site serves developers, assume a large fraction of your real traffic is missing from Google Analytics. If it serves a general consumer audience on mobile, the gap is smaller but still real.
How to measure your own blocked rate
You do not have to guess. Compare two sources that count differently:
1. Server logs or CDN analytics — these count requests that reached your infrastructure and cannot be blocked by the client. Filter out bots as best you can.
2. Your analytics tool — which counts only visitors whose browser executed and delivered the tracking call.
The gap between the two, after bot filtering, is roughly your blocked rate. It is usually larger than people expect, and seeing your own number is more persuasive than any industry statistic.
Why it matters beyond the vanity metric
Under-counting is not just a smaller number — it is a biased number. The visitors who block analytics are not a random sample. They skew towards technical users, privacy-aware users and specific geographies.
That bias distorts decisions. Your most technical traffic source looks weaker than it is. A feature that appeals to privacy-conscious users looks like it has no audience. A conversion rate looks higher than reality because the denominator is missing.
What actually helps
A first-party, lightweight script. Analytics served from your own domain, with no advertising infrastructure behind it, is blocked far less often — because blocklists target known advertising and tracking endpoints, not every script on the web.
Not requiring a consent banner. Every visitor who declines consent is a visitor missing from your data. A cookieless tool that does not need the banner keeps them in the dataset.
Server-side measurement, for teams with the engineering capacity to run it — although this raises its own questions about transparency and consent that should be answered before implementing it.
The uncomfortable conclusion
If a large share of your visitors have decided they do not want to be tracked by an advertising company, that decision is not going to reverse. The realistic options are to accept a biased dataset, or to measure in a way that respects the preference — and gets counted.