For AI agents: the full docs index is at /docs/llms.txt. Append .md to any docs URL for Markdown.
Skip to content
Proxy Docs
Esc
↑↓navigate↵open⌘Jpreview
On this page

Meta pixel not firing: how to check and fix it

A Meta pixel that is not firing is nearly always a setup problem on the website, not a Meta outage. Check it with Meta's browser extension. Steps in order.

This is nearly always a setup problem on your website, so waiting will not fix it. The Meta pixel is a small piece of tracking code, and it only records visits if it is installed once, in the right place, and not blocked. Check it with Meta’s own browser extension first.

Sources: Meta’s developer docs and two practitioner guides, checked November 2026.

Try this, in order

  1. Install Meta’s checker extension. In the Chrome Web Store search for “Meta Ads Data Advisor”, click Add to Chrome, then Add extension.
  2. Open your website and click the extension icon. It shows each pixel on the page with a status: Active (working), Warning (not set up correctly) or Inactive (not sending events correctly).
  3. Turn off ad blockers and privacy extensions, reload, and check again. Meta lists browser settings and privacy tools blocking the pixel as a common cause.
  4. Click into the pixel or event in the extension and apply the fix it suggests.

If that did not work

Work through Meta’s list of common setup errors:

  • The code is on the page twice. Remove the duplicate. A likely cause is a site plugin and a tag manager both adding it.
  • The base code is in the wrong place. It belongs in the head section of the page.
  • The code is missing from the page you care about. Add it to every page you want to track, such as the thank-you page.
  • It loads through a tag manager or inside a frame. Check the tag is published and not being blocked.
  • An event shows Error. Meta uses that status for a critical setup issue such as blocked parameters or duplicate events. Fix what the extension names.
  • A purchase event lacks details. The checker flags missing value, currency or content_ids.

Practitioners add causes Meta’s list leaves out, as in this developer’s guide to the six causes:

  • A cookie consent banner. The pixel stays silent until a visitor accepts, and sometimes after, if the tag is not wired to the consent choice. That guide calls it “the #1 cause in the EU”. Test before and after accepting marketing cookies.
  • Checkout happens elsewhere. Purchases made through a redirect (such as PayPal) or on another domain or inside a frame may never reach a page with your pixel.

If the extension shows nothing at all on the page, practitioners read that as an install or trigger problem, per Trackingplan’s guide.

When to stop and contact Meta

If the extension shows the pixel as Active on your site and Events Manager still shows nothing after a day, contact Meta through the Business Help Center. If the extension shows Inactive, the fix is on the website: go to whoever maintains the site or its tag manager, not to Meta.

The detail

  • Statuses and common errors are from Meta’s pixel checker documentation. Event statuses are Active, Inactive, Warning, Error and Auto-detected.
  • Edge: the extension is also on Microsoft Edge Add-ons. Meta notes some languages are not supported there.
  • How it shows up elsewhere. A website audience that depends on the pixel reports one of three states on the custom audience: 421 “No pixel. Your Facebook pixel hasn’t been installed on your website yet”, 422 “Pixel not firing. Your Facebook pixel isn’t firing”, 423 “Invalid pixel. Your Facebook pixel is invalid”.
  • Knock-on effects. Missing events can leave an audience too small or an ad set in Learning limited.

While tracking is fixed, you can still see what competitors are running. Proxy reads the public ad libraries from your AI assistant. It does not manage ad accounts or pixels.

Was this page helpful?