Free tool
Is your tracking blocked by ad blockers?
Enter your website. We find its tracking tags and test every request they make against EasyPrivacy, the tracking list uBlock Origin turns on by default and Brave Shields also uses, including the exceptions it makes for your site.
Free, no sign-up. The address you check is not stored.
How the check works
It reads your page the way a crawler does and finds the tags in its source: Google Tag Manager, the Google tag, Meta, TikTok, LinkedIn, Microsoft, Pinterest and Snap. For a Tag Manager container it also reads the published container, where the GA4 tag and any server-side address are kept.
For each tag it rebuilds the two requests that matter: the script the tag loads and the hit it sends for a page view. Each one is matched against the current EasyPrivacy list by the same kind of engine an ad blocker runs, as the request type the tag really uses.
It cannot see tags that a cookie banner or a script bundle adds after the page has loaded. Those are blocked by the same rules, they are just not in the page source.
Why moving Tag Manager to your own domain is not enough
EasyPrivacy blocks the address every GA4 hit uses, /g/collect?v=2, on any host. A server-side container on metrics.yoursite.com loads, but its page views still match the rule, and ad blockers drop them.
It also blocks beacons sent to another site's address. Hits only get through when they go to your own domain and carry nothing a list can recognise. That is what SignalHost does: your own tagging domain, and every request encoded.
Questions
Is the check free?
Yes. There is no account and no catch beyond a limit of a few checks per hour, and the address you check is not stored.
Which ad blockers use EasyPrivacy?
uBlock Origin turns it on by default, and Brave's built-in Shields use it too. Other blockers ship their own lists with very similar rules, so a request EasyPrivacy blocks is blocked by most of them.
Why does my analytics show fewer visitors than my server?
Visitors with an ad blocker never send the hits this check marks as blocked, so Analytics never hears of them. Server-side tagging on your own domain, with encoded requests, brings those visits back.