Skip to content
Free ad blocker scan

Test which analytics requests ad blockers stop

Paste a URL. We load it in a real browser running uBlock Origin and show you every analytics, advertising, and consent tag that didn't make it.

Public pages only. The scan takes about 15 seconds and loads the page once, the same way a visitor would.

Need to test a login, consent choice or checkout action?

Continue in your own Chrome session. Use DevTools to identify failed requests, then test supported recovery with Introtrace. The extension popup shows relay attempts rather than every blocked resource.

Continue testing in your own browser →

Example report

What a blocked request tells you

Illustrative examples, not a live scan or measured results for your site. Your report may contain different tools or no blocked requests.

GTM container script blocked

A blocked gtm.js request means tags that depend on that container may not start. Check the container before investigating each downstream tool.

Diagnose a blocked GTM container

GA4 measurement request blocked

A blocked /g/collect request shows an attempted measurement was stopped. Compare the same action with blocking off and on, then verify receipt in GA4.

Diagnose a blocked GA4 request

An incomplete scan can retain requests already observed, but it cannot establish that everything else loaded successfully. A clean scan does not test actions that were never performed. For recovery verification, follow our three-run GA4 testing checklist, which includes a recorded Brave example.

Measured, not estimated

What the scanner actually does

No modelling and no extrapolation from browser market share — this is the browser's own account of what happened on your page.

The scan launches a real Chromium browser with uBlock Origin installed and its default filter lists compiled, navigates to your URL the way a visitor would, and records every network request the extension refused.

Results are grouped by the tool a request belongs to, because a list of blocked hostnames is not something anyone can act on. Seeing cdn.cookielaw.org in a log is noise; seeing "OneTrust — blocked" is a finding.

Each tool is then sorted into one of two buckets, and the distinction matters because the two failures look identical in your reports while being completely different problems:

Blocked on the way in

The tool's own JavaScript never downloaded, so it never ran. Anything waiting on it — every tag gated behind a consent banner, for instance — stayed blocked too.

Blocked on the way out

The script loaded and ran normally, but the request carrying its data was dropped. The visit happened, the code executed, and the measurement simply never arrived.

Interpreting the output

How to read your results

A scan covers one page at one moment. Use these checks when interpreting your results.

This is one blocker configuration. The scan uses uBlock Origin with default lists, rather than a sample of your actual visitors. Firefox's default protection and Safari's ITP work differently — they mostly restrict the cookies behind a request rather than dropping the request itself, so the session is counted but a returning visitor is misattributed as new. The scan measures outright blocking, which is the more visible failure but not the only one.

It describes one page, at one moment. Tags that fire only at checkout, after a consent choice, or on a different template won't appear. Scanning a landing page and a conversion page usually tells you more than scanning either alone.

A clean result deserves a second look. Nothing blocked is good news only if your tags were there to be blocked. If a page carries no third-party analytics at all, the scan cannot tell you whether its analytics integration is working.

To investigate broader gaps, compare equivalent analytics and server-side metrics over the same period. The scan identifies blocked requests. A log comparison is a diagnostic starting point; account for bots, consent choices, and differences between requests and sessions.

Sources: Backlinko — Ad Blocker Usage Statistics · Brave — Shields · WebKit — Intelligent Tracking Prevention · Mozilla — Enhanced Tracking Protection in Firefox

Next steps

What you can do about blocked tags

Introtrace serves blocked scripts and relays blocked measurement calls through cdn.introtrace.com by default. Paid plans support your own subdomain via CNAME. Verify recovery using the same page and blocker configuration.

1

Fix the inbound blocks first

A blocked loader takes everything downstream with it. A consent platform that never renders holds back every tag waiting on consent, so one fix here often restores several tools at once.

2

Then the outbound drops

These are narrower — the tool works, only its data is lost — but they are the ones most likely to go unnoticed, because nothing on the page appears broken.

3

Mind the load order

Any first-party recovery depends on its own script having loaded. Place it directly in the page head, before your tag manager and consent snippet, then verify that recovery works with your tag loading order.

4

Re-scan afterwards

The same scan is the check. Check the recovery requests and confirm receipt in your analytics tools. A tool disappearing from the blocked list alone does not prove event delivery.

Ad blocker scanner FAQ

How do I check if my analytics are blocked by ad blockers?

Paste your URL above. The scanner loads your page in a real Chromium browser with uBlock Origin installed and reports every request the blocker stopped, grouped by the tool it belongs to. It takes about 15 seconds and needs nothing installed on your site.

Which ad blocker does this test against?

uBlock Origin with its default filter lists. Results describe that browser configuration, page, and test visit. Other browsers, filter lists, consent choices, and user actions can produce different results.

What is the difference between a blocked script and a blocked measurement call?

A blocked script never ran at all — the browser refused to download it, so nothing that depended on it executed either. A blocked measurement call means the script did run, but the request carrying its data was dropped on the way out. The first breaks the tool; the second silently loses the data while everything appears to work. The scan reports them separately because they fail differently and are fixed differently.

Why does the scan show my consent banner as blocked?

Consent platforms like OneTrust and Cookiebot load from third-party CDNs that appear on standard filter lists. When the loader is blocked the banner never renders, so every tag waiting on consent stays blocked too — one blocked request can account for all your missing analytics.

Does a clean scan mean ad blockers aren't costing me data?

Not necessarily. It means uBlock Origin blocked nothing on the page that was scanned. Tags that only load on other pages, after a consent choice, or during checkout would not appear. It is also worth confirming your tags are actually present — a page with no analytics at all scans clean for the wrong reason.

Can I scan a page that requires a login?

No. The scanner loads pages anonymously, exactly as a first-time visitor would, so anything behind authentication is out of reach. Scan the public equivalent — a landing page, product page, or your home page — since those carry the same tag configuration in most setups.

Ready to test recovery?

Introtrace serves blocked scripts and relays blocked measurement calls through its proxy. Free to start with 20,000 recovered signals per 30 days.