On this page
Install the helper and read what it says
The Meta Pixel Helper is Meta’s Chrome extension (an Edge build installs the same way). Add it from the Chrome Web Store, pin it to the toolbar, then reload the page you are testing. The icon shows a number badge: the number of Pixel events it caught on that page.
Open it and you get one entry per Pixel ID. Green with a checkmark means the event fired with valid data. Yellow flags a warning, for example a missing value or currency on Purchase. Red, or a gray icon with no badge, means no Pixel loaded at all. TikTok has its own TikTok Pixel Helper, and Google uses Tag Assistant, so use each platform’s tool for its own tag.
The helper only works on the page you have open, so test the exact URL and the exact action. A Purchase event will not appear until you complete a checkout, and a Lead event not until the form submits. Use a test order or a test submission each time you change something.
If the extension shows nothing on a page you know has the Pixel, reload with the extension open, not before. The helper attaches to a tab when it loads, and a tab opened before installation will not report.
If the helper finds no Pixel
Check where the base code lives. It should sit in the head of every page, or in a tag manager container that publishes on every page. A container saved but never published is the most common cause. A cache or CDN serving an older template is the second.
Then rule out the browser. An ad blocker, strict tracking protection, or a consent banner that has not been accepted can all stop the Pixel from loading, and the helper then reports nothing. Test in a clean profile with extensions off. If you use Tag Manager, the setup is in Google Tag Manager basics.
One more cause worth checking is a single-page app. If your site loads new views without a full page load, the base code runs once and later events must be fired by your own code. The helper will show only the first PageView unless your developer triggers the others.
On Shopify, WordPress and similar platforms the Pixel is usually installed by an app or channel connection rather than pasted code. Check that the sales channel is connected to the right dataset and that a second, manually pasted copy is not running beside it.
Is your tracking counting every conversion?
Runs tracking health checks on your pixels and tags. Sends a weekly performance review.
If the helper shows warnings or the wrong Pixel
A wrong Pixel ID usually means a copied snippet from an old account or a staging site. Compare the ID in the helper with the dataset ID in Events Manager. Two Pixels on one page is allowed but is a common source of doubled events, so confirm both are intended.
For parameter warnings, open the event’s details. Purchase needs value and currency. A page reload event firing on a thank-you page every time someone refreshes inflates conversions, so trigger it on the order confirmation, once. A Pixel that fires on page load for a button click was set up on the wrong trigger.
Yellow warnings are worth fixing even when conversions still record, because missing parameters lower the quality of the signal Meta optimizes on. Catalog campaigns in particular need content IDs that match your product feed exactly.
Check the event match details when a Purchase or Lead event arrives without customer information. Advanced matching, which hashes the email or phone a visitor types into a form, is a setting in the dataset, and turning it on improves attribution for people who are logged out.
Confirm in Events Manager, not just the browser
The helper only proves your browser sent something. Open Events Manager, choose the dataset, and use Test Events with your site URL to watch live events arrive. If the helper is green but nothing shows up there, the event is reaching the wrong dataset or is being filtered by an aggregated event setting.
For a lasting fix on blocked browser traffic, add server events alongside the Pixel, which the Conversions API guide walks through. Sprites can run a tracking health check on a schedule, reading Pixel and Conversions API events by source and flagging gaps, and propose the fix as an approval card.
Allow time for Ads Manager to catch up. Events appear in Events Manager within minutes, but campaign reporting can lag by hours, and conversions are credited to the attribution window you chose, not the day the click happened.
When you have fixed the cause, write down what it was. Pixel failures return after theme changes, plugin updates and consent tool changes, and a one-line note saves the next debugging session from starting at zero.
Questions
What do the Pixel Helper colors mean?
Green means the Pixel found the event and its data is valid. Yellow means it fired but has a warning, such as a missing parameter. Red or no badge means no working Pixel was detected on that page.
Why is my Facebook Pixel not working?
Usually the base code is missing from some pages, the tag manager container was never published, the wrong Pixel ID is installed, or a blocker or consent banner is stopping it. The helper tells you which of these you have.
Is there a Meta Pixel Helper for Firefox?
Meta’s helper is a Chrome extension, and it also installs on Chromium browsers such as Edge. In Firefox, use the Test Events tool in Events Manager to watch events arrive.
Is there a TikTok Pixel Helper?
Yes, TikTok publishes its own Pixel Helper extension for Chrome. It reads the TikTok Pixel only. See the TikTok Pixel guide for setup.
The helper is green but Ads Manager shows no conversions. Why?
Reporting lags and attribution windows apply, and the event may be going to a different dataset than the one your campaign optimizes for. Check Test Events first, then the campaign’s conversion event setting.