Free Facebook Pixel Checker: is your Meta Pixel actually installed?

No signup, nothing stored. Checking somebody else's site is fine: this only reads what every visitor's browser already downloads.

This checks the page your address serves to a normal visitor, as a plain request that does not run the page's scripts, and it opens any Google Tag Manager container it finds and reads inside it. Nothing is stored, no signup is asked for, and the answer is the same one you would get by opening the page source yourself with more patience than most people have.

How to check this yourself, without any tool

Open your site in Chrome, right click, choose View Page Source, and search the page for fbq. If it appears, a pixel is loading directly in the HTML. If it does not appear, search for GTM- instead: a match there means your tags live inside Google Tag Manager and the page source will never show them, which is exactly where most checkers give up and hand you a wrong answer. The other reliable route is Meta's own Pixel Helper extension, which reads the page after scripts have run.

Installed is not the same as working

A pixel that only fires PageView tells Meta that a human loaded a page and nothing else. It never learns that anyone filled the form, called, or booked. Meta then optimises for the only outcome it can see, which is cheap visits, so you get more traffic and not more customers, and the reporting cannot tell you which ad produced work. This is a common state on live advertiser sites, and it looks fine from the inside because the dashboard is full of numbers.

More than one pixel ID is not the same problem as the same pixel twice

Two different pixel IDs on one page, which is what the check above reports when it lists more than one, usually means an agency installed one and a website builder plugin installed another. Both fire, and each one records every event once, so nothing is doubled. What you lose is a single view: the same visitor is recorded in two separate reports that cannot be added together, and whoever owns the other pixel is building audiences out of your traffic. Worth finding out whose it is before removing anything.

The case that really does double count cannot be seen from the page

The same pixel ID installed twice, typically once by the theme and again inside a tag manager, does fire every event twice. Conversions double, your reported cost per lead halves on paper, and you scale spend against a number that was never real. No checker that reads page source can tell you this, including this one, because a normal single install already writes the id more than once: the init call carries it and so does the noscript image that covers visitors without JavaScript. Meta's Events Manager is where it shows up, as duplicate events on the pixel itself.

Why the pixel misses more than it used to

Browser tracking prevention, ad blockers and iOS privacy settings can each stop a browser side pixel from reporting. Depending on the audience, a meaningful share of real conversions never reach Meta at all, which shows up as your ads account claiming fewer leads than your inbox contains. The usual remedy is server side tracking through the Conversions API, which reports from your server instead of from the visitor's browser.

Common questions

Does this find a pixel installed through Google Tag Manager?

Yes, and that is the main reason it exists. When a GTM container is present it is fetched and read through, so a pixel inside it is found. If a container is present but cannot be opened, the answer given is cannot tell rather than no.

Why does it say no pixel when Meta Events Manager shows activity?

Usually because the pixel is only on some pages, most often the thank you page, and not on the address you checked. Try the exact page your ads send people to. It can also happen when the pixel loads only after a cookie banner is accepted, in which case it is genuinely absent for anyone who does not accept.

Is a Meta Pixel and a Facebook Pixel the same thing?

Yes. It was renamed to Meta Pixel when the company was renamed, and the code still uses the function name fbq. Anything written about the Facebook Pixel applies unchanged.

Can I check somebody else's website with this?

Yes. It only reads what any visitor's browser already downloads, so there is nothing private in it and nothing that a competitor could not see by viewing your page source.