How to Measure How Much Traffic Your Analytics Is Missing

Industry averages tell you ad blockers hide 25–45% of your traffic. But your number depends on your audience — and you can measure it directly in two weeks instead of guessing.

Why averages aren't enough

The undercounting problem is real, but the size of it varies wildly. A developer tool's audience might block 45% of the time; a local bakery's customers, maybe 10%. Planning around the average is like dressing for the average global temperature. You want your number.

The good news: measuring it is straightforward and doesn't require touching your existing setup.

The method: run two trackers in parallel

The cleanest way to size your gap is to run a first-party analytics tool alongside your current analytics for two weeks, then compare totals for the same pages over the same window. Your current tool is blocked for some visitors; a first-party tool that isn't on block lists records them. The difference is your undercount.

1. Add a first-party tracker on the same pages your current analytics covers. It loads from your own domain, so ad blockers don't drop it. (One async script tag — it won't affect performance.)
2. Wait two full weeks. A week minimum, but two smooths out weekday/weekend and any single viral day.
3. Compare pageviews for the same date range and the same pages. Use totals, not real-time — both tools need time to finalize.

Reading the result

Take the gap as a percentage of the first-party number, because that's the one closer to reality:

Typical results: 20–40% for most sites, higher for developer, tech and privacy audiences, lower for general consumer traffic. If you also run a cookie banner, part of the gap is consent drop-off rather than blocking — both count as traffic you couldn't see.

Things that throw the number off

• Different page scope. Make sure both tools are on the same set of pages. If one is missing from your blog, the comparison is apples to oranges.
• Bot filtering differences. Tools filter bots differently. A reputable first-party tool filters known bots; if your numbers look implausibly high, check the bot-handling docs.
• Comparing time-on-page. Don't — that's a separate measurement problem. See why session duration is usually wrong. For the undercount test, compare pageviews and visitors only.

What to do with the number

Once you know your real undercount, two things change. First, every conversion rate you've calculated is too high — you were dividing by a traffic number that excluded a third of visitors. Second, you can decide whether the blocked segment matters enough to switch your source of truth. For most content sites and SaaS products, once you've seen the gap, the first-party number simply becomes the one you trust.