Monitor your first website free, no card needed. Explore SENRIKO

Meta Pixel checker

Free Meta Pixel Checker

Find the Meta (Facebook) pixels on a page, check that Meta knows each ID, and see which events a visit sends.

Paste a page address. We open it once in a real browser, read the pixel IDs from the HTML, the published GTM container and the requests the browser sends, and ask Meta whether it serves settings for each ID.

No access to your Meta account. We keep event names and pixel IDs only, never the data an event carries.

We open the page once in a real browser from Germany. The site's analytics may count that visit as one page view. We click nothing and send nothing.

example.com/pricingExample
  • Pixel IDDetected1234567890123456
  • Known to MetaDetected
  • PageView sentDetectedPageView
  • Lead set upLikely configuredLead

The pixel loaded, Meta knows its ID, and PageView was sent. Lead is written in the page's code and waits for a form.

What it looks for

What the Meta Pixel checker reads

A pixel shows up in the page's code, in a GTM container and in the requests the browser sends to Meta. The check reads all of them and shows the evidence behind every finding.

  • fbq('init', '…')

    The init call

    fbq('init', …) with a pixel ID, in the page's code or in the GTM container.

  • facebook.com/tr?id=…

    The noscript image

    The image pixel for browsers without JavaScript. It names the ID and shows nothing about the browser code.

  • fbevents.js

    The pixel library

    fbevents.js loading in the browser. It shows the library arrived, not that an event was sent.

  • fbq('track', 'Lead')

    Events

    PageView, Lead, Purchase and custom events, each marked as sent in this visit or only written in the code.

  • signals/config/…

    Whether Meta knows the ID

    Meta serves a settings file for every pixel it knows. No settings means the ID may be mistyped or deleted.

  • fbq.getState()

    Pixels that started

    The pixel IDs the library reports as started in the page. We read the IDs and nothing else from it.

Reading the answer

Four words, and where each one came from

Every line of the result carries one of four words, and under it the evidence at its own level. A tag seen sending data is a stronger fact than an ID seen in the HTML, and the result never passes the weaker one off as the stronger.

Detected
The browser saw it load or send a request in this visit.
Likely configured
It is in the page's code or in the published container, and nothing ran it while we watched.
Not observed
We did not see it in this visit. That is not the same as broken: it may wait for consent, a click or a server.
Unable to verify
We could not look: a bot check, an error or a page that did not open.

The levels of evidence, weakest first

  1. In the HTMLThe ID is written somewhere in the HTML the server sent.
  2. In the containerThe published GTM container, as Google serves it to every visitor, sets it up.
  3. In the code, not runThe page's code would send it, for example in a click handler, and nothing ran that code.
  4. LoadedIts script or container loaded in a real browser.
  5. Request sentThe browser sent a request with its ID or event. That shows the request left the page, not that the platform accepted it.
Troubleshooting

Why the Meta Pixel is not firing: six common causes

When Events Manager shows nothing, or the wrong events, the cause is usually on this list. Each card says what the checker shows when it happens.

  • 01

    The pixel ID is wrong

    A mistyped ID, or one from an old Business account, sends events nowhere useful. The checker asks Meta whether it serves settings for each ID and flags the ones it does not.

  • 02

    The pixel is installed twice

    A theme and a plugin can each add the pixel, so every PageView goes out twice. Two different IDs get a row each, with the events each sent. The same ID added twice shows as one row, so look in the page source for a second fbq('init') with that ID.

  • 03

    The pixel waits for consent

    Many banners hold the pixel until Accept all. This check does not press it, so a held pixel reads as not observed. The Cookie Consent Checker shows what the pixel does after Accept all.

  • 04

    Lead fires on every page load

    A Lead or Purchase event placed in the base code fires for every visitor on every page. If the result shows Lead sent on an ordinary page load, the event is in the wrong place.

  • 05

    The ID comes from a GTM variable

    When a pixel tag in Tag Manager takes its ID from a variable, the container does not show the number. The result says so, and the visit still shows the ID if the pixel starts.

  • 06

    Events go only through the Conversions API

    Events sent from a server never pass through the browser. A site that relies on the Conversions API can look quiet here while Events Manager is full, and the result says what it could not see.

By hand

How to check if the Meta Pixel is installed, step by step

The checker above covers the first two steps in one visit, reads pixels set up in GTM and asks Meta about each ID. The last two run in your own browser and your Meta account.

  1. Step 1

    Search the page source

    Press Ctrl+U and search for fbq('init' and facebook.com/tr. The number after init is the pixel ID.

    fbq('init', '…')
  2. Step 2

    Watch the requests

    In DevTools, open Network, filter by facebook.com/tr and reload. Each request with ev=PageView and your pixel ID is an event the browser sent.

    facebook.com/tr?ev=PageView
  3. Step 3

    Try Meta Pixel Helper

    The Chrome extension shows the pixels and events on the page you have open, with warnings about common setup mistakes.

  4. Step 4

    Test in Events Manager

    Open Test events for your pixel and use the site. Browser and Conversions API events appear as they arrive, which confirms Meta received them.

Compared

Meta Pixel checker, Pixel Helper or Events Manager: when to use which

The checker needs only a link. Pixel Helper needs Chrome and an extension, and Events Manager needs access to the business account.

Needs a page address

This Meta Pixel checker

No extension and no Meta login. It opens the page in a clean browser, lists every pixel with the events it sent, checks that Meta knows each ID and reads pixels set up in GTM. It sees one page load and sends no form.

Needs Chrome and the extension

Meta Pixel Helper

Shows pixels and events live in your own browser as you click around, with Meta's own warnings. What it shows depends on your cookies, your consent choice and your other extensions.

Needs access to the business account

Meta Events Manager

Shows what Meta received, from the browser and from the Conversions API, and how the two are matched and deduplicated. It cannot show a page where the pixel never loaded.

Questions

Meta Pixel checker: common questions

How do I check if a Meta (Facebook) Pixel is installed?
Paste the page address above. The result lists every pixel ID we found, where we found it, whether it loaded and which events it sent while we watched.
Is the Meta Pixel the same as the Facebook Pixel?
Yes. Meta renamed the Facebook Pixel to the Meta Pixel in 2022. The fbq code and the fbevents.js library stayed the same, so the checker finds old and new installs alike.
Where do I find my Meta Pixel ID?
In Meta Events Manager, under Data sources, select your pixel. The ID is the long number shown with it. Compare it with the IDs the checker found.
What does it mean if Meta does not know the pixel ID?
Meta serves settings for every pixel it knows. When it serves none, the ID on the page may be mistyped, from an old account or deleted. Check the ID in Events Manager.
Why is Lead or Purchase not shown as sent?
Those events usually fire after a form is sent or an order is placed. This check does neither, so it shows them as written in the code or set up in the container, never as sent.
Can you see the Conversions API?
No. The Conversions API sends events from a server straight to Meta, and they never pass through the browser. We cannot tell whether it runs or whether its events are deduplicated with the pixel's.
Can I check the pixel on a site I do not own?
Yes. The checker reads what any visitor's browser receives, so it works on any public page. It shows pixel IDs and event names, never the data those events carry.
Is it safe to run this on my site?
It is one visit, like one person opening one page, from a browser that names itself as SENRIKO. It clicks nothing and sends no form. We keep event names and IDs, never the data an event carries. The result is kept for 24 hours.
The other tools

The other free tools

Check a page in one tool and open the result in another without waiting again. The four tag tools share one visit, and the two consent tools share three.

Limits

What this cannot tell you

  • 01

    We do not send forms, add to cart or buy, so events that fire on those are shown as set up, never as sent.

  • 02

    Events sent through the Conversions API go from a server to Meta and are not visible to a browser check.

  • 03

    We do not answer the cookie banner here. A pixel held until consent stays silent in this check.

  • 04

    A request that left the browser is not proof that Meta accepted the event. Events Manager shows that.

Verify my domain and test a real conversionCheck another page