Skip to article
On this page

Meta Pixel explained: what it is and how to check it

NyXi

NyXi

7 min read

What the Meta Pixel does, what its 15 or 16 digit ID identifies, how standard events and the Conversions API fit together, and how to tell whether yours is installed once or twice.

A long run of digits with no letters in front of it, sitting in the Advertising section of your Tag Explorer results, is almost always the Meta Pixel. It is the code that reports what people do on your website back to Facebook and Instagram advertising. Paste your page into Tag Explorer to see this tag on your own site.

You may have seen it called the Facebook Pixel, the Meta Pixel, or simply a data source, depending on which screen you were looking at. It is the same thing, and the number is the part worth understanding, because it decides which advertising account receives everything your site reports.

What it actually does

The pixel loads a small script from connect.facebook.net and creates a function called fbq(). From that point the page can report activity: a page view on load, then whatever else has been wired up, such as an enquiry form being submitted or an order completed.

Meta puts those reports to three separate jobs.

  • Measurement. Which ads produced enquiries and sales, rather than just clicks.
  • Optimisation. Meta’s delivery system learns what your buyers have in common and goes looking for more of them. An ad account with no conversion signal has nothing to learn from, so it optimises for the cheapest clicks it can find.
  • Audiences. Retargeting lists built from behaviour, such as everyone who viewed a product page and did not order.

The second one is why a broken pixel costs more than a reporting gap. You lose the numbers, and you quietly degrade how the ads are delivered.

What the ID means

A pixel ID is a bare number, normally 15 or 16 digits, with no prefix: something of the shape 123456789012345. It is not a secret, and it is visible in your page source to anyone who looks.

You will find yours in Events Manager under Data sources, beside the pixel name. Compare it with what a scan of your site reports. If they do not match, your ads are reporting into an account you are not reading.

Because it is plain digits, it is the easiest tracking code on a page to misread. A LinkedIn partner ID, a Microsoft UET tag ID and a Pinterest tag ID are also bare numbers. Length is a rough tell, since the Meta ID is usually the longest, but the reliable answer is to read the tag type.

One detail surprises people: a pixel belongs to a business portfolio, not to a website. The same pixel can serve several sites and be shared with an agency, which is exactly why ownership is the step most often skipped at handover.

Standard events, custom events and the Conversions API

Meta publishes a fixed vocabulary of standard events: PageView, ViewContent, Lead, CompleteRegistration, AddToCart, InitiateCheckout, Purchase and a handful more. Capitalisation must match exactly. purchase in lower case is not the standard event, it is a custom event with an unfortunate name, and it will not appear where you expect to select it. Anything genuinely outside the list is a custom event, which is fine: you can still optimise and build audiences on it.

The Conversions API is the server-side companion. Your server reports the sale instead of the browser, so the report survives ad blockers and the browser tracking restrictions that keep tightening. It is not a replacement. Meta expects both, with each event carrying a shared event_id so the two copies of one sale are matched and counted once.

The three shapes it takes in Tag Manager

If the pixel lives in Google Tag Manager, it will be one of three things, and it matters because they are not equally visible.

  1. A Custom HTML tag with the snippet pasted into it. This is the oldest approach and still the most common on an inherited site. The container file gives up the tag type but not the pixel ID.
  2. The older community template that Meta took over from its original third party author. Widely installed and still working.
  3. Meta’s own official template, now published in the Tag Manager Community Template Gallery, which can read an existing GA4 style data layer and map ecommerce events to the standard event names for you.

And a fourth possibility, which is not Tag Manager at all: the pixel is injected by a plugin, a theme option, or a platform integration such as Shopify or a WooCommerce extension. That is fine on its own. It becomes a problem the day somebody also adds it to Tag Manager without checking.

What this looks like in Tag Explorer

Tag Explorer draws your page as a tree. Each Tag Manager container is a branch, its tags are leaves underneath, and anything hard coded into the page HTML sits under DIRECT ON PAGE.

A Meta Pixel installed through a proper template appears as an Advertising card with the pixel ID as the card title and the tag type as the subtitle, and a copy button for the ID. Installed as Custom HTML, it shows up under the Custom colour with the tag type as the title, no ID and no copy button. That is normal rather than a fault, but it does mean a scan cannot confirm which pixel that tag is feeding.

The signals worth reading on your result:

  • A duplicate banner with the affected cards tinted red and carrying an attention badge. This is the most common Meta finding, because the pixel arrives so easily from two directions at once.
  • Where each copy sits. One under a container and one under DIRECT ON PAGE is the classic plugin plus Tag Manager collision.
  • The insights panel below the tree, which raises softer advisories such as two different IDs of the same family reporting from one page.

Two limits are worth stating plainly. The published container file never contains the human names you gave your tags, only the tag type and the tracking ID. And the tool reads the published container, so a pixel sitting unsubmitted in a Tag Manager workspace will not appear.

A scan proves the pixel is installed. It cannot prove it fired. For that, use Preview mode in Tag Manager, the Network tab in your browser developer tools, or the Test events screen in Events Manager.

What to do if it is missing, duplicated or dead

Missing. No Meta card while Meta ads are running means the campaigns are buying clicks with no idea which of them worked, and the gap cannot be filled in later. Check the pixel exists in your container, that its trigger covers every page rather than the homepage alone, and that the version was actually published. Then scan a thank you or order confirmation page, since a pixel present on the homepage and absent at the finish line is common and easily missed.

Duplicated. Two cards with the same ID means every page view and every sale is counted twice, which inflates results and distorts what the delivery system learns. Remove the hard coded or plugin copy rather than the Tag Manager one, because the copy nobody remembers adding is the copy nobody will maintain. Two cards with different IDs is a different fault: the site is feeding two accounts. Decide which one you actually advertise from, and check any audiences built on the other before deleting anything.

Dead or stale. A pixel does not expire, so age alone is not a problem. What goes stale is the account behind it, usually a pixel belonging to a previous agency’s business portfolio, still collecting, with nobody on your side able to open the reports or audiences it has built. Create a pixel in a portfolio you own, install that one, and treat the old audiences as lost rather than negotiating for them indefinitely. A pixel left behind after campaigns stopped is harmless to your data but still a third party script on every page, so remove it.

Run your site through Tag Explorer and look at how many Meta cards come back, and where each one sits in the tree. A duplicate pixel and an orphaned pixel are both signs of a setup that has been added to by several people over several years, which is exactly the kind of tangle our rebuilds and rescues work exists to sort out.

Frequently asked questions

What does a Meta Pixel ID look like?

It is a bare number, usually 15 or 16 digits, with no letters and no prefix, for example 123456789012345. You will find yours in Meta Events Manager under Data sources, where it sits beside the pixel name. Because it is just digits, it is easy to mistake for a LinkedIn partner ID or a Microsoft UET tag ID, so always read the tag type as well as the number.

Is one pixel on two websites a problem?

It is allowed and sometimes deliberate, because a pixel belongs to a business portfolio rather than to a single site. The downside is that all of the activity lands in one pool, so audiences and conversion counts mix the two sites together. If you need to report on them separately, or you are likely to sell or hand over one of them, give each site its own pixel.

Why is my pixel counting purchases twice?

The two usual causes are the pixel being installed twice on the page, once by a plugin or theme and once through Google Tag Manager, or the browser pixel and the Conversions API both reporting the same sale without a shared event ID to match them on. The first shows up in a page scan as a duplicate. The second does not, because the server copy never touches the browser, so it has to be checked in Events Manager.

Do I still need the pixel if I have the Conversions API?

Yes, in almost every case. Meta treats the two as a pair: the browser pixel captures the detail of the visit, the server API survives ad blockers and browser tracking restrictions, and events sent by both carry the same event ID so they are counted once. Running the API alone is a deliberate, more technical setup and is not the normal starting point.

Can Tag Explorer see a pixel installed as a Custom HTML tag?

It sees the tag, but often not the number. A Custom HTML tag has no public ID field, so the card shows the tag type as its title with no copy button, and the pixel ID stays inside the code. If you suspect a pixel is hiding in a Custom HTML tag, open that tag in Google Tag Manager and read the ID from the snippet.

More articles