free · no signup
Meta Pixel checker
Check if the Meta Pixel is installed on any page. Spot duplicate installs, render-blocking loads and GTM double-counting, then verify events by hand.
Scans the page's HTML in seconds. It also reports every other tracking script it finds.
about Meta Pixel
Why it breaks quietly.
The Meta Pixel is the fbevents.js script plus an fbq('init') call with your pixel ID. It reports page views and conversion events back to Meta so ads can optimize and attribute. Every campaign's reported results depend on it.
It breaks quietly because nothing on the page looks wrong when it does. A theme update drops the snippet, a plugin adds a second copy, or a Purchase event goes out without a value, and Ads Manager keeps showing numbers that are just less true than last week.
what the free scan checks
Whether Meta Pixel is in the page
The scan fetches the page's HTML and matches the vendor's script URL and install snippet.
Whether it blocks rendering
A script tag without async or defer delays the page from painting. Marketing scripts never need to.
Whether it's installed more than once
Duplicate installs usually send every event twice and inflate conversions.
Whether GTM and hardcoded tags overlap
Google Tag Manager next to a hardcoded GA4 or Meta Pixel is a double-counting risk if the same tag also fires inside GTM.
How exposed the page is to blockers
A server-side readiness grade: whether tags load from domains blocklists target, and whether conversions have a server-side path.
It reads the HTML, so tags injected later (inside GTM, for example) don't show up, and it can't see events fire. That's what verification is for.
common failures
How Meta Pixel goes dark.
The pixel is installed twice
A Shopify or WordPress integration and a hand-pasted snippet both load the pixel. Each one sends PageView and Purchase, so conversions double and cost per result looks better than it is.
fbq('track') runs before fbq('init')
Events queued before the pixel is initialized with an ID have nowhere to go. This happens when a conversion snippet is placed above the base code or loaded by a faster script.
Purchase events are missing value or currency
Meta needs value and currency on Purchase to report revenue and run value optimization. Without them the event still counts, but ROAS reads as zero and value-based bidding has nothing to learn from.
Browser and server events are not deduplicated
If you also send events through the Conversions API, both copies need the same event_id and event name. Without a shared ID Meta counts the browser event and the server event as two conversions.
Hardcoded pixel plus a GTM pixel
The base code sits in the theme and a Meta tag also fires inside Google Tag Manager. Both initialize, both track, and every event lands twice.
by hand
Check it yourself, step by step.
- 1
Install the Meta Pixel Helper Chrome extension, load the page and confirm it shows exactly one pixel ID with no errors or warnings.
- 2
Open Events Manager, pick the pixel, go to Test Events, enter your site URL and click through a conversion. Each event should appear once.
- 3
Complete a test purchase and check that the Purchase event in Test Events carries a value and a currency.
- 4
In Chrome DevTools, open the Network tab, filter for facebook.com/tr and make sure each event fires one request, not two.
- 5
If you use the Conversions API, check the event's deduplication details in Events Manager to confirm browser and server events are being matched.
questions
Asked and answered.
Can this check tell me if Meta Pixel events are firing?+
No. The free check reads your page's served HTML, so it can see whether the pixel script is present, installed more than once, render-blocking or sitting next to GTM. It cannot see a pixel injected at runtime or confirm an event reached Meta. TracerKit's Verification tier watches real fires, alerts when a tag goes silent and reconciles your counts against Meta.
Why does Pixel Helper show two pixels on my site?+
Usually an e-commerce integration and a manually added snippet are both loading it, or a second pixel ID was left behind from an old ad account. Keep one install path and remove the other.
Do I still need the pixel if I use the Conversions API?+
Meta recommends running both. The pixel captures browser context and the Conversions API fills gaps from ad blockers and browser restrictions, as long as both share an event_id for deduplication.
check other tags
Know Meta Pixel is firing, every hour of every day.
Verification watches each tag on real traffic and emails you the moment one goes silent. 14-day trial, no card.