Guide

Meta Pixel not firing? How to find the cause

A pixel that stops firing gives no error and the site looks normal. Here is how to confirm it, and the causes to check in the order they usually turn up.

  • Free
  • No signup
  • About 20 seconds
  • Nothing lands in your reports

Not ready to scan? See a sample report

1. Confirm it really sends nothing

Open the page in a private window with ad blockers off, open the browser's developer tools, go to the Network panel and filter for facebook.com/tr. Reload. A standard install sends a PageView on every page, with your Pixel ID as id=. No request means nothing reached Meta from this visit.

Or scan the page above: it does the same thing in a real browser and lists every request, with the Pixel ID and event names.

2. Work through the causes

The trigger does not fire on this page

If the pixel lives in a tag manager, check the trigger. A page-path condition or a renamed event is the usual culprit after a site change.

A JavaScript error stops the snippet

Look in the Console for errors before the pixel code runs. A broken script earlier on the page can stop everything after it.

The Pixel ID is wrong or deleted

Compare the ID in fbq('init', …) with Events Manager. A template placeholder or a truncated ID sends data nowhere.

The browser blocks the request

A Content-Security-Policy that does not allow Meta's address makes the browser refuse the request. See pixel blocked by CSP.

The cookie banner is holding it

Before a choice, silence may be correct. Accept the banner and check again. If it still sends nothing after accepting, the fault is elsewhere.

How each cause shows up in TagZ

  • Silent with a known Pixel ID: Meta Pixel is installed but sent nothing.
  • Loader failing: Meta Pixel cannot load.
  • Refused by the site's policy: Meta Pixel is blocked by this site’s own security policy.
  • Firing to a bad ID: Meta Pixel is sending to an ID that does not look valid.
  • Waiting behind a banner the scan could not answer: not verified, which is not the same as broken.

A scan is one look. Tags break later.

A theme update, a plugin, a new cookie banner, someone tidying up an old account: tracking rarely breaks loudly. TagZ monitoring runs this same check every six hours in a real browser and emails you when a tag that was working stops sending, after a second scan has confirmed it.

$7.99 a month for one website, billed yearly ($95.88 a year), or $2.63 a site per month on the Agency plan for 25 sites, billed yearly. See all plans.

Check your own site now

One address, about twenty seconds, in a real browser.

  • Free
  • No signup
  • About 20 seconds
  • Nothing lands in your reports
Meta Pixel not firing? How to find the cause · TagZ