What is Meta Pixel and what are standard events?
It was once called the Facebook Pixel. Where it sits in the ecommerce marketing technology stack is on the technologies index.
What does Meta Pixel do?
It is a tracking pixel: code that sends visitor actions from the browser to an ad platform. What Meta receives feeds its conversion reporting and the audiences you build from website traffic.
In practice, set-up has two parts:
- Install the Pixel on the site. The base code needs to load on every page. How it gets there depends on your site and shop platform.
- Set up events. Standard events such as
Purchasetell Meta which action happened. Each event carries its own details, such as order value and currency.
Audiences are built from this data. A custom audience is a Meta targeting option for people you already have a connection with, including website traffic. A conversion in your reports depends on which events you sent and how the platform counts them.
Why do e-commerce brands use it?
Because Meta ads need to learn what a sale looks like. The Pixel is the common route for telling Meta that a purchase, a basket or a product view happened.
That makes it the first place to check when Meta numbers and shop numbers disagree.
How do we implement it?
Install and check
Load the base code on every page, then confirm the Pixel fires. The route depends on your site and shop platform.
Send events properly
Use Meta's standard event names exactly, with value and currency on purchases.
Add the server route
Meta recommends the Conversions API alongside the Pixel. Use the same event name and ID on both, and check deduplication.
Recheck after changes
Theme changes and app installs can break the Pixel. Settle consent timing with your lawyer and consent platform.
When should you not rely on it alone?
Do not rely on the Pixel alone when Meta is a major channel and your numbers do not reconcile. Add the server route, and check deduplication.
Do not touch it at all when you do not run Meta ads and have no plan to. A Pixel with no purpose is code you do not need to run.
If you are unsure, our tracking audit is free. See Analytics & tracking.
What does it cost in effort?
No figures. The effort is:
- Install. Choose a set-up route, then confirm the Pixel fires on every page.
- Events. Decide which events to send and with what values.
- Naming. Use Meta's standard event names exactly. For deduplication, the event name must match on the Pixel and the server1.
- Redundancy. Adding CAPI and handling event deduplication.
- Upkeep. Theme changes and app installs can break the Pixel without any warning.
Pitfalls
Improvised names
A home-made spelling of a standard event is not the event Meta expects. Copy the names from Meta's list.
Missing value and currency
Our view: a purchase sent without them tells Meta a sale happened, not what it was worth.
Browser-only dependence
A Pixel alone misses events the browser never sends, for example when a page fails to load. Meta recommends adding the Conversions API, with deduplication1.
Double counting
Run the Pixel and CAPI together, and Meta needs the same event name and event ID on both1. See Meta pixel and Conversions API deduplication.
Consent timing
When the Pixel may fire, relative to a visitor's consent, is a decision for your lawyer and your consent platform. We do not give legal advice.
Our take: Core
We rate Meta Pixel Core. This is our view, not a market fact.
If you run Meta ads, you need a working Pixel. It is not optional and it is not new. But it is no longer enough on its own. Meta recommends running the Conversions API (CAPI) alongside it, a set-up it calls redundant1. That is a better reason to rate the combination Core than to rate the Pixel alone.
For ZFD: We check the Pixel first, because everything else sits on top of it.
FAQ
What is Meta Pixel?
It is Meta's code snippet that reports actions on your site from the browser to Meta. The Conversions API is its server-side counterpart1.
Is Meta Pixel the same as the Facebook Pixel?
Yes. Facebook Pixel is the old name.
Do I need the Conversions API as well as the Pixel?
Meta recommends running both for the best ad performance1. With both, you need deduplication on the same event name and event ID.
Why does Meta report a different number of purchases from my shop?
Several reasons are possible: missed events, double counting, different counting rules. Start with the Pixel and its events.
Does the event name matter?
Yes. Use the standard name exactly, and send the same name from the Pixel and the server so Meta can deduplicate1.
Sources
Let’s find what’s actually working.
Next step. Want someone to check your Pixel against your orders? Talk to us about your tracking setup. See also our Analytics & tracking service.