Mockingbird

Explainer

What is the Meta pixel? Cost, cookies, the Pixel Helper and what to check when it is not working

The Meta pixel is a piece of code you put on your website so Meta can log what people do there, such as a purchase, and connect it to your ads. None of the Meta pages we read puts a price on it, it does use cookies, and you need it (or the Conversions API) only if you want website actions measured or optimised for. If it is not working, start with the Test events tool and the Diagnostics tab in Events Manager.

Last updated

What is the Meta pixel?

Meta's Business Help Centre page about the pixel defines it as a piece of code on your website that lets you measure your Meta advertising by understanding the actions people take there. Each logged action is called an event. Meta lists three uses: showing ads to the right people (including past visitors), bidding towards people likely to take an action such as a purchase, and measuring results. The developer documentation is more literal: it is a snippet of JavaScript that loads a small library and fires whenever a visitor does something you have chosen to track.

On naming: Meta's page about Events Manager says it is gradually introducing datasets, and the Data sources page now asks you to select your dataset. A dataset can hold website, app and offline events together. Meta's page on dataset creation says a dataset created from a pixel keeps the same ID. So "pixel" and "dataset" may both appear on your screen for the same thing.

Is the Meta pixel free?

None of the Meta pages we read lists a price for the pixel, and the setup steps create one in Events Manager without a payment step. We did not find a sentence from Meta that says "free" about the pixel itself, so treat that as our reading. What does cost money is the advertising, and a developer's time if you install the code by hand.

Meta is explicit about the Conversions API. Its comparison of setup options lists the Meta-enabled, web-only version as free, says commerce platforms such as Shopify, WooCommerce, Wix or BigCommerce add it at no additional cost, and says a direct integration costs whatever your development and maintenance cost.

Is the Meta pixel necessary?

Not for every advertiser. Nothing in these pages says an ad cannot run without it. In practice it is needed when the result you care about happens on your website: without the pixel or the Conversions API, Meta has no record of the purchase to report, to build an audience from, or to optimise delivery towards. Our post on attribution settings covers how those recorded events are then credited to an ad.

If your ads aim at results inside Meta's apps, such as messages or video views, that is a weaker case. That is our inference from what the pixel does, not a statement by Meta.

Where it is created and how it is installed

Meta's setup page gives the path: in Events Manager click Connect data, choose Web, name the pixel and create it. You then enter your website address and Meta checks whether a partner integration is available. There are two jobs: install the base code, then set up events.

  • Partner integration. Meta's partner integrations page names WordPress, WooCommerce, Shopify, BigCommerce, Squarespace and Google Tag Manager among others, and says most need no manual code editing.
  • Manual code. The developer get-started page says to place the base code in the head section of every page you want tracked. The base code sends a PageView event on each page load by itself.
  • Events. Meta's list of standard events has 17 predefined names, including ViewContent, AddToCart, InitiateCheckout, Lead and Purchase. Anything else can be sent as a custom event with a name you choose.

Does the Meta pixel use cookies?

Yes. The pixel is not itself a cookie: it is code that reads and sets cookies. Meta's page on cookie settings for the pixel says it can use first-party cookies (owned by your site) and third-party cookies (owned by another site), and that using both is the default. You can switch first-party cookies off under Settings for the pixel in Events Manager, which Meta says makes measurement less accurate. The developer page on fbp and fbc names the cookies: _fbp, an identifier saved for your domain, and _fbc, which stores the click ID from an ad click.

On consent, the same help page says Meta's terms require you to tell visitors clearly how you use cookies and share data. Meta's developer page on the GDPR says each business is responsible for its own compliance, and documents a consent call that pauses the pixel until a visitor agrees. Whether you need a banner depends on where your visitors are. This is general information, not legal advice. Read your regulator's own guidance: in the UK, the ICO's guidance on storage and access technologies, which has a section on tracking pixels; in Australia, the OAIC's guidance on tracking pixels.

Meta pixel vs Conversions API

They are two routes for the same events, and Meta recommends using both. The pixel sends from the visitor's browser. The Conversions API sends from a server, which Meta says makes it less affected by browser loading errors, connectivity problems and ad blockers.

Meta pixel and Conversions API, as Meta's pages describe them, October 2026
Meta pixelConversions API
Sends fromThe visitor's browserYour server, website platform or CRM
Reliability, per MetaRelies on browser data, which can be blocked or lostLess affected by loading errors, connectivity issues and ad blockers
CoversWebsite eventsWebsite, app, offline and messaging events
Typical setupPartner integration or code in the page headPartner integration, Meta-enabled web-only version, or a developer build

Sending the same purchase by both routes would count it twice, so Meta deduplicates. Its page on deduplication says the two events must share the same event name and the same event ID. The developer page adds that this applies when both arrive within 48 hours. Meta says partner integrations such as Shopify and WooCommerce handle this for you.

What is the Meta Pixel Helper?

It is a free browser extension that shows which pixels and events fire on a page, and it has a new name. Meta's help page now calls it Meta Ads Data Advisor (formerly Meta Pixel Helper). It runs in Google Chrome and Microsoft Edge. Besides checking, Meta says it can set up the pixel and Conversions API through Google Tag Manager or Shopify and suggest fixes that it applies with your approval.

Meta's install page links to the Chrome Web Store and the Edge Add-ons store. Get it from those links, not from a search result. If you still have the old Pixel Helper Chrome extension, the same page says it now appears under the new name and asks you to review its permissions when you reactivate it. A number on the icon is the count of pixel events fired on the page; no badge means no pixel was found. Meta says to disable ad blockers so the extension can detect your pixel.

Meta pixel not working: what to check first

Meta's best-practice page says that once a PageView reaches Meta, the pixel's status is set to Active. None of the pages we read defines a "No activity yet" or "not active" label, so we cannot quote Meta on it. It suggests no event has arrived, and these checks are the ones Meta gives.

  1. 01

    Load a page and look for PageView

    Open a page that carries the base code, then check the pixel in Events Manager. Meta's developer page says to wait a few minutes and refresh if nothing shows.
  2. 02

    Use Test events

    In Events Manager, open Data sources, select the pixel, click Test events and open your site from there. Meta's Test events page says activity is recorded only while that tab stays open, and that normal reporting can lag by 30 minutes or more. If nothing appears within a minute, its troubleshooting page says to disable ad blockers, refresh and try another browser.
  3. 03

    Read the Diagnostics tab

    Meta's Diagnostics page says each issue comes with a description and steps to resolve it, marked red for critical or yellow for a warning.
  4. 04

    Check the code is still there

    Meta's page on a drop in website events lists the common causes: base code removed or moved in a website update, broken event code, moved or renamed pages, site downtime, and a domain allow or block list that shuts out your own site.

Meta pixel not tracking purchases is usually an event problem, not a pixel problem, because the base code sends only PageView. Meta's pages point to these:

  • The Purchase event is missing from the confirmation page, or fires somewhere else.
  • The name is misspelt. Events are case-sensitive, so "purchase" becomes a custom event, not a Purchase.
  • Value or currency is missing or malformed. The developer reference marks both as required for Purchase, and Meta's list of error messages asks for a three-letter currency code and a plain number.
  • Purchases are over-counted: the same list has an error for four or more Purchase events on one order, and a warning when pixel and Conversions API values disagree.

Sources

Questions people ask

What is the Meta pixel?

Meta describes the pixel as a piece of code you put on your website so you can measure your Meta advertising by the actions people take there. Each logged action, such as a purchase, is called an event. In Events Manager it may now appear as a dataset, which keeps the same ID.

Is the Meta pixel free?

None of the Meta help pages we read on 13 October 2026 lists a price for the pixel, and the setup steps create one in Events Manager without a payment step. Meta does list its Meta-enabled, web-only Conversions API as free. The costs are the ads themselves and any developer time to install the code.

Does the Meta pixel use cookies?

Yes. The pixel is code, not a cookie, but Meta says it uses both first-party and third-party cookies by default, and you can turn first-party cookies off in the pixel's settings in Events Manager. Whether you need visitor consent depends on your visitors' location, so check your regulator's guidance; this is general information, not legal advice.

What is the Meta Pixel Helper and why is my Meta pixel not working?

The Meta Pixel Helper is now called Meta Ads Data Advisor, a free extension for Chrome and Edge that shows which pixels and events fire on a page. If the pixel is not working, Meta's own checks are to load a page and look for a PageView in Events Manager, use the Test events tool with ad blockers off, and read the Diagnostics tab.

Try it on your own competitors.

$9 for 7 days. Paste a competitor's Page and see their best ad rebuilt for your brand.

Start 7-day trial · $9

More from the blog

  • Pause, stop or delete a campaignHow to pause, stop, delete or extend a Meta (Facebook) ad campaign in Ads Manager, and what each does to spend, billing, results and the learning phase.
  • Advantage+ audience explainedWhat Advantage+ audience is, what Meta does with the targeting you enter, which inputs are hard limits, and how to switch to original audience options.
  • Advantage+ vs manual placementsAdvantage+ placements vs manual placements on Meta: the current placement list, what excluding one changes, the 5% limited spend option and account controls.

Keep reading

Mockingbird is an independent product from Onwards Analytics and is not affiliated with, endorsed by or sponsored by Meta. Meta, Facebook, Instagram, Meta Ads Manager and the Meta Ad Library are trademarks of Meta Platforms, Inc. Meta changes its tools often; check Meta's own help pages for the current detail before you rely on it.