Facebook Pixel Checker: How to Verify Your Meta Pixel Works
A Facebook pixel checker is any tool that confirms the Meta Pixel loads on a page, carries the right pixel ID and sends the events you expect. The quickest is Meta's free Pixel Helper extension for Chrome; the most reliable is the Test Events tool in Events Manager, because it shows what Meta actually receives.
Facebook Pixel and Meta Pixel are the same code under two names, and most people still search for the old one. On a client site the question is rarely whether a pixel exists. It's whether it is the right pixel, firing the right events, after the last redesign.
What a working Meta Pixel looks like in the code
The base code loads fbevents.js from connect.facebook.net, then makes two calls:
fbq('init', '123456789012345');
fbq('track', 'PageView');
The number in init is the pixel ID, the same one Events Manager shows next to the pixel's name. A <noscript> image pointing to facebook.com/tr covers browsers without JavaScript. Standard events such as Lead, AddToCart or Purchase are further fbq('track', ...) calls, placed on the action they measure.
How to use Meta Pixel Helper
Meta Pixel Helper is a free Chrome extension that lists every pixel on the current page and the events each one fired. To use it:
- Install Meta Pixel Helper from the Chrome Web Store.
- Turn off your ad blocker for the site and accept the cookie banner.
- Open the page and click the extension icon. The badge shows how many pixels it found.
- Expand each pixel to see its ID and the events it sent, with their parameters.
- Complete the action you track (a form, an add to cart) and check that the new event appears.
Events that went through cleanly are marked as successful. Warnings and errors point to the usual suspects: no pixel on the page, a pixel that tried to load and failed, the same event sent twice, or an event with missing or badly formatted parameters, such as a Purchase without value or currency. A duplicated PageView almost always means the pixel is installed twice, typically in the theme and in Google Tag Manager.
The extension only sees the browser. It can't tell you whether Meta accepted the data or what the server sends.
Checking events in Events Manager
Events Manager is the reliable check because it shows what reached Meta. Open the pixel, go to the Test events tab, enter the site URL and open the site from there. Each event you trigger shows up in the list within moments, labelled as coming from the browser or the server. The Overview tab shows activity over time and when the pixel last received an event, and the diagnostics area lists problems Meta has spotted, such as duplicates or missing parameters.
A Facebook pixel checker with no extension: the network tab
Open DevTools, go to Network, filter on facebook.com/tr and reload. Each request is a hit: the query string carries id= with the pixel ID and ev= with the event name, for example ev=PageView. If fbevents.js loads but no tr request follows, the init call is missing or consent is holding the pixel back.
Where does the Conversions API fit?
The Conversions API (CAPI) sends events from the server straight to Meta, so neither Pixel Helper nor the network tab will ever show them. Test events does, marked as server events. When pixel and CAPI both send the same event, they need the same event name and event_id so Meta can deduplicate them; otherwise conversions are counted twice. There is a less obvious risk too: if the pixel vanishes but CAPI keeps running, Events Manager still shows traffic and the gap goes unnoticed.
Why does the Meta Pixel stop working?
The pixel rarely breaks with an error on the page. These are the common causes:
- a new theme or redesign that drops the snippet from the header template
- a move to Google Tag Manager where the hardcoded pixel is removed before the GTM tag is published, or both are left in
- a CMP change that puts the pixel in a category whose trigger never fires, or blocks it for everyone
- an ID copied from another client's site or from a starter theme, so the data lands in someone else's account
- landing pages on a builder or subdomain that don't load the code
The wrong ID is the sneakiest one. Pixel Helper shows a pixel firing happily, and only comparing the ID with the one in the client's Events Manager reveals it. For banner problems, see our guide to cookie banner monitoring.
Keeping an eye on the pixel across client sites
A manual check tells you how things stand today. Deltio reads each monitored URL and sends an email or Slack alert when the Meta Pixel appears, disappears or changes ID, along with GA4, GTM and the other tags it tracks. If the pixel runs inside GTM, Deltio sees the container rather than the pixel in it. It doesn't verify events, parameters or CAPI, so Test events remains the check after any change to forms or checkout. More on the approach in marketing tag monitoring.
Starter costs £24 a month, £20 billed annually, and you can try it free for 14 days.
Frequently asked questions
- Is Meta Pixel Helper free?
- Yes. Meta Pixel Helper is a free Chrome extension published by Meta. It works on any site you can open in Chrome and needs no access to the ad account.
- Can I check a Facebook pixel without Chrome?
- Yes. Open the browser developer tools on the Network tab and filter on facebook.com/tr: every request is a pixel hit, with the pixel ID in the id parameter and the event name in the ev parameter. This works in Safari, Firefox and Edge.
- How do I find which pixel ID a website uses?
- View the page source and search for fbq('init', the number that follows is the pixel ID. If the pixel is deployed through Google Tag Manager it won't be in the source, so use Pixel Helper or the network tab instead.
- Why does Events Manager show fewer events than my analytics?
- Visitors who refuse marketing cookies, use an ad blocker or block third-party scripts never send pixel events. Some gap is normal, which is why many advertisers add the Conversions API, but a sudden fall to zero usually means the pixel or its trigger broke.
- Does Deltio check that Meta Pixel events fire?
- No. Deltio detects whether the Meta Pixel is present on each monitored URL and alerts you when it appears, disappears or its ID changes. It doesn't check events, parameters, consent signals or the Conversions API.