// Tracking and data

What Is the Meta Pixel and How to Check Your Install

The Meta Pixel sends events from the browser to a Meta dataset. Read the standard event list, the install order, and how to find events sent wrongly.

What Is the Meta Pixel and How to Check Your Install

The Meta Pixel is a code snippet that sends events from the visitor browser to a Meta dataset. Those events feed ad reports, retargetingRetargetingShowing ads to people who already interacted with you, for example opened a page or sent a chat.Open the glossary audiences, and campaign optimisation.

Meta uses the word dataset for the container that receives pixelPixelA piece of code on a web page that tells the ad platform somebody opened the page or took an action.What is the Meta Pixel? events and server events from the same source.

Standard events and custom events

Standard events use names Meta recognises, so reports and optimisation work without extra setup. Custom events use your own names and need extra rules before they can be read.

Standard eventWhen to send itKey parameters
ViewContentA product or service page openscontent_ids, value
LeadA prospect form is sentcontent_name
AddToCartA product enters the cartcontent_ids, value
PurchasePayment completesvalue, currency

Send value and currency on the Purchase event. Without those two fields, value reports and value-based bidding cannot work.

Install order

01Install base codePlace the pixel code onevery page of the site.02Add eventsSend standard events onthe actions that carryvalue.03CheckRead Test Events andEvents Manager for 7days.04Add the serverAdd the Conversions APICAPIA server path that sends conversion data from your system to the ad platform, without depending on the buyer browser.What is the Conversions API (CAPI)?for the same events.

Scroll the diagram sideways

Check first, add later. Adding six events at once makes every error hard to trace.

The errors we find most often

  • Purchase sits on the cart page, so the purchase count inflates.
  • The pixel code is installed twice, so every event counts double.
  • The purchase value carries thousand separators, so Meta reads a wrong number.
  • A custom event replaces an action that already has a standard name.
Any page opensPageView is sent on every page.Product pageViewContent is sent once with content_ids.CartAddToCart fires on the button press, not on page load.Thank you pagePurchase is sent once with value and currency.

Scroll the diagram sideways

One action, one event. An event placed on the wrong page produces a wrong report.

How to check the install

  1. Open Events Manager, then select your dataset.
  2. Run Test Events, then make one test purchase.
  3. Check the event name, value, and currency on the row that appears.
  4. Read the Diagnostics warnings, then fix every item marked as an error.
  5. Repeat the check after each theme or checkout change.

Questions and answers

Is the pixel still useful after the Conversions API? Yes. The pixel carries browser signals such as fbp and fbc that tie an event to the ad click. Meta asks you to run both paths together.

Why is the pixel event count lower than my order count? Script blockers, cookie refusals, and network failures cut browser sends. Add the Conversions API to close part of that gap.

How many pixels does one site need? One dataset per site is enough in most cases. Two datasets split the campaign learning data into two small pieces.

// references

Official sources

We checked every claim on this page against the documents below on 11 September 2026. Open the source before you change a live system.

// next step

Need help to apply this?

Send your target. We check the context and write the first step before implementation.