The Meta Pixel is Meta's browser-side tracking code. When someone visits your site, the pixel fires events that tell Meta what they did. Without it, Meta can't optimise for purchases, report sales or build website audiences, so for an online store a working pixel is non-negotiable.
Standard events for e-commerce
Meta defines standard events so its systems understand what each action means. The core funnel for a store:
- ViewContent: a product page view.
- AddToCart: an item added to the cart.
- InitiateCheckout: checkout started.
- Purchase: an order completed.
Others, such as Search, AddPaymentInfo, Lead and CompleteRegistration, are useful where they match your funnel. Use the standard name wherever one fits, because Meta's systems understand those without extra setup.
Parameters that matter
Events are far more useful with parameters attached:
- value and currency on Purchase, and ideally on AddToCart and InitiateCheckout. Without them, Meta can't report revenue, calculate ROAS or optimise for value.
- content_ids and content_type, which connect events to catalogue products for Advantage+ catalog ads.
- contents and num_items for orders with several products.
Keep value consistent. Decide whether it includes tax and delivery, and match whatever you compare it with in your store reports.
How to set it up
- Create the pixel in Events Manager (Meta may call it a dataset).
- Install it through your platform's integration where one exists. On Shopify, Meta's official app sets up the pixel and Conversions API together. Otherwise, add the base code and events directly or through a tag manager.
- Use Test events in Events Manager and the Meta Pixel Helper browser extension to confirm each event fires once, with the right parameters.
- Add the Conversions API so events still reach Meta when browsers block or limit the pixel.
If you sell in a sensitive category such as health and wellness, Meta may restrict which events and parameters it accepts for optimisation, so check Events Manager for any notices about your dataset.
Common mistakes
- Duplicate Purchase events from two installations, such as a theme snippet plus an app.
- Purchase firing again when a customer reloads or revisits the thank-you page.
- Missing currency, or value sent as text with a currency symbol.
- Relying on the pixel alone. Ad blockers, browser privacy features and Apple's tracking limits all stop some browser events reaching Meta.
For a platform-specific walkthrough, see Meta Pixel and Conversions API on Shopify.
Frequently asked questions
Is the Facebook pixel the same as the Meta Pixel?
Yes. The Facebook pixel was renamed the Meta Pixel when the company became Meta. It's the same code and the same Events Manager setup, and it tracks website actions for ads on both Facebook and Instagram.
Do I still need the Meta Pixel if I use the Conversions API?
Yes, in most setups. Meta recommends running both, with deduplication, because the pixel captures browser signals the server can't and the Conversions API catches events the browser misses. Together they give Meta the most complete picture.
How do I check if my Meta Pixel is working?
Open Events Manager and use Test events while you browse your site, add to cart and place a test order. The Meta Pixel Helper browser extension also shows which events fire on each page. Each action should fire once, with value and currency on Purchase.
