Is your Meta Pixel firing, and who blocks it?
Meta Pixel Helper shows what your own browser sees. This loads your page in a clean browser, finds every pixel ID, tests the pixel against four ad blockers and checks whether the fbclid from an ad click makes it into _fbc. Your other tags are checked in the same scan.
We load public pages only. Every tracking request the page makes stops in our browser, so GA4, Google Ads, Meta and the other ad platforms never receive it. Scan results may be used in aggregate for published studies. Terms
What the Meta Pixel check looks at
The pixel loading is the easy part. These are the parts that decide whether Meta can match a purchase to an ad.
Not what’s installed. What gets through.
Other checkers list your tags. This one asks which conversions the ad platforms will never hear about, and why.
Every platform at once, in a clean browser.
Meta Pixel Helper and Tag Assistant each check one platform, in your own browser. They’re the right tools for watching events fire live. This is the one that shows what ad blockers do to all of them.
| This checker | Meta Pixel Helper | Tag Assistant | |
|---|---|---|---|
| Platforms in one check | Every ad and analytics tag | Meta Pixel | Google tags |
| Where it runs | A clean browser on our side | Your own browser | Your own browser |
| What you need | Nothing | A Chrome extension | Google’s web app, connected to your browser |
| What ad blockers do to each tag | Four blockers | No | No |
| Click IDs followed to the cookie | Six click IDs | No | No |
| Watch events live as you click | No | Yes | Yes |
A scan reads your page. The tracking stops in our browser.
Scan your own site, a client’s or a prospect’s. The checker loads the page the way a first-time visitor does, and records every tracking request without letting it leave.
The opening line of your next pitch.
Scan a prospect’s site and send them what their tracking is missing. The fix is yours to sell.
The agency program →Questions about the checker
How is this different from Meta Pixel Helper?
Pixel Helper is a Chrome extension that shows the pixel events in your own browser as you click around, which is the best way to debug events live. This checker runs in a clean browser on our side, with nothing to install, and adds what Pixel Helper can’t show: what four ad blockers do to the pixel, whether the fbclid survives into _fbc, and every other ad tag on the page.
Does the checker see my Conversions API events?
No. The Conversions API runs from your server to Meta, so no page scan can see it. The checker does report a server-side endpoint when the page sends data to one, like a first-party sGTM subdomain.
Is the tracking checker free?
Yes. The score, the top problems, the tag map and the ad blocker test are free with no signup. The full report, with every finding and fix steps for your platform, comes by email.
Will a scan show up in my analytics or ad accounts?
Not from the browser. We record every tracking request the page makes and stop it there, so GA4, Google Ads, Meta and the other ad platforms never receive it. Your server still sees the page load, like any visit, so a tool that counts visits from server logs, or sends an event from your server when a page loads, can count it.
Which ad blockers do you test?
uBlock Origin, Brave Shields, AdGuard, and DNS blocking with hagezi Multi PRO and AdGuard’s CNAME tracker list, as Pi-hole and NextDNS use them. Today we match each request against those blockers’ default lists, and every report names the list versions and the date. Running each blocker in its real browser is coming soon.
How is the score worked out?
It weights the four things that lose conversions: ad tags blocked, click IDs lost, consent gaps and a broken conversion page. It only counts the checks that ran, and it’s a heuristic, not a measurement of your lost revenue.
Why couldn’t you scan my site?
Usually its bot protection refused a headless browser. We never solve or get around a CAPTCHA, so the report says it couldn’t scan the site. Your developer can allow the checker, or you can try another page on the same site.
What do you do with scan results?
We store the result so your report link works. Scan results may be used in aggregate for published studies, such as what share of sites run server-side tracking. We load public pages only and store no visitor data.
Find out what your pixels are missing.
The ad platforms optimize on the conversions they receive. See which ones they don’t.
Free · No extension · No signup