Analytics Not Blocked by Ad Blockers: The Complete Guide

The number in your analytics dashboard is not your traffic — it's the slice of it that wasn't blocked, didn't reject a banner, and happened to be measured correctly. This guide explains the three things that quietly shrink that number, how to measure your own gap, and how to fix it.

Your analytics undercount, and the tool never tells you

Most site owners treat their analytics number as ground truth. It isn't. Three independent mechanisms strip visitors out of the count before they ever reach your dashboard — and none of them produce an error, an asterisk, or a warning. The dashboard just shows a smaller, confident, wrong number.

For a developer or tech audience, the combined effect routinely puts Google Analytics at 45–55% of real traffic. For a general consumer site it's better, but a 20–30% undercount is still common. Here are the three causes, what each one costs you, and where to read the deep dive on each.

Cause 1 — Ad blockers drop the script entirely

The Google Analytics script (gtag.js) is on every major ad-blocking list. uBlock Origin blocks it with its default filters (40M+ installs on Chrome alone). Brave blocks it with Shields on Standard (70M+ monthly users). Firefox blocks it in Strict mode. When the script is blocked, it never loads, and the visit is never recorded.

Industry studies put ad-blocker adoption between 25% and 45%, skewing higher for developer, tech and privacy-conscious readers. That entire slice is invisible to GA — not estimated, not flagged, simply absent.

Cause 2 — Cookie consent drop-off

If you run a cookie banner, GA only fires after the visitor accepts. Everyone who dismisses, ignores, or rejects the banner is excluded. With acceptance rates typically between 40% and 75%, you can lose a quarter to a half of your remaining audience here — and the survivors are a biased sample, because the people who actively click "accept" behave differently from those who don't.

Cause 3 — Wall-clock timing inflates the wrong metric

This one doesn't shrink your visit count — it corrupts your engagement metrics. GA measures time on page as wall-clock time: open a tab, leave for 20 minutes, come back and close it, and GA logs a 20-minute session. For content sites the gap between reported session duration and real attention is typically 3–5×, which makes thin pages look engaging and hides the ones people actually read.

How to measure your own gap

You don't have to take industry averages on faith. The cleanest way to size your own undercount is to run a first-party analytics tool alongside GA for two weeks and compare totals. Whatever first-party shows above GA is, roughly, what GA was missing — the blocked visitors plus the consent rejecters. For most sites Logly shows 20–40% more pageviews than GA; for developer audiences, more.

This isn't first-party overcounting. It's the blocked-and-rejected slice becoming visible for the first time. Step-by-step method: How to Measure How Much Traffic Your Analytics Is Missing.

The fix: first-party, no-cookie analytics

The reason ad blockers can drop GA is that GA loads third-party script from a known tracking domain. A tool that serves its script from your own domain, sets no cookie, and stores no personal data isn't on the blocking lists and doesn't need a consent banner — so all three causes above disappear at once. The script fires for everyone, there's no banner to reject, and you can choose to measure real attention instead of wall-clock time.

That's the entire design goal of Logly: a first-party, cookieless endpoint that records the visitors GA can't see.

"Don't privacy-first tools get blocked too?"

Partly — and this is the part most comparison articles get wrong. Privacy-first analytics like Plausible and Fathom are far less blocked than GA, but their default cloud script still loads from a shared third-party domain that some aggressive blocklists catch. The way around it (a first-party proxy or domain) exists for all of them, but it's setup you have to do. If accurate counts are the whole point, it's worth comparing how each tool behaves out of the box:

• Logly vs Plausible — both privacy-first; where the blocking and setup differ.
• Logly vs Fathom — same question, head to head.
• Logly vs Google Analytics 4 — the baseline this whole guide is about.