The Meta Pixel isn't firing on your site, or Events Manager doesn't see it. Because the pixel runs client-side, the cause usually sits in a few places between the browser and Meta. Here's how to isolate it.
Symptoms
- No events arrive from the site in Meta Events Manager.
- Pixel Helper / Test Events catch nothing.
- Conversions aren't measured, even though the pixel "is deployed".
What to check
- 1. Is the pixel even on the page? Verify the pixel code / tag loads (in GTM preview or devtools Network → fbevents).
- 2. Is an ad-blocker blocking it? The Meta Pixel is a frequent ad-blocker target. Test in a browser with no extensions. (This is exactly what server-side via the Conversions API addresses.)
- 3. Is consent blocking it? If the pixel is tied to consent and you test without it, it won't fire — that's not a bug. See Consent Mode blocking measurement.
- 4. The right Pixel ID? A typo in the ID sends data into the void.
How to verify the fix
Use the Test Events tab in Events Manager and walk the site — events should arrive. For reliability through ad-blockers, run the pixel and the Conversions API together with deduplication.