The block-rate report
Which analytics tools are actually blocked?
Across 10 providers we have enough data to publish, Meta Pixel is the most blocked at 46.7%. The average across measured providers is 31.6%. Every number is measured directly across engaged visitors — no panel, no modelling.
Block rate by provider
- 46.7%
Meta Pixel
The Meta Pixel powers Facebook and Instagram ad attribution. When it is blocked, conversions go unreported and ad optimization degrades.
- 40%
Google Analytics 4
Google Analytics 4 is Google's web and app analytics. It is one of the most aggressively blocked endpoints on the web.
- 39.6%
Mixpanel
Mixpanel is an event-analytics platform. Blocked users are invisible to its funnels and cohorts.
- 38.2%
Hotjar
Hotjar records heatmaps and session replays. Blocked sessions never appear in your recordings.
- 35.5%
Segment
Segment is a customer-data pipeline that fans events out to other tools. A block at the source starves everything downstream.
- 35.1%
Amplitude
Amplitude is a product-analytics platform. Blocked clients drop out of every behavioral report.
- 26.3%
Optimizely
Optimizely runs A/B tests and feature experiments. When its CDN is blocked, experiment assignment and conversion tracking silently stop.
- 24.7%
Google Tag Manager
Google Tag Manager loads your other tags. When GTM itself is blocked, every tag it manages goes dark at once.
- 20%
PostHog
PostHog is a product-analytics and session-recording platform. Blocked users send no events, so funnels and retention undercount.
- 9.9%
Intercom
Intercom powers in-app chat and messaging. A blocked widget means those users can't reach support through it.
"—" means we don't yet have enough measured samples to publish a trustworthy rate for that provider. Prefer raw data? Get it as JSON.
How we get the number right
Detecting ad and content blockers is genuinely hard: a blocked request and a network error look alike, filter lists match domains rather than filenames, and loader snippets keep a global defined even when the CDN behind them is blocked. A naive "is the global truthy?" check reports loaded for blocked users and quietly undercounts the real block rate.
blockrate is built to avoid that. It checks each provider's real post-load global (not the loader stub), uses per-provider ground-truth probes against the actual CDN, and reports through a first-party endpoint so the measurement itself isn't the thing getting blocked. The result is a number you can trust per provider — which is the whole point. Read how it works.
The population: these rates are measured across blockrate.app's own visitors and participating customer sites, so they skew technical; read them as an upper bound on a general audience. Checks from our interactive demo page are excluded, because people toggle their blockers there to watch the tool work.
Measure your own stack
These are aggregate numbers. Your audience is more technical or more privacy-minded than average, so your real block rate is probably higher. blockrate is an open-source library that measures it, per provider, on your own site.