Meta Pixel and Conversions API, explained

Why tracking comes first

If Meta cannot see what happens after someone clicks your ad, it can only optimize for clicks. To optimize for sales or leads, it needs to know when those happen. That is what the Pixel and the Conversions API do.

Meta Pixel

A small piece of code on your website that runs in the visitor's browser and reports actions (events) back to Meta.

Conversions API (CAPI)

A way for your server or store platform to send the same events to Meta directly, without relying on the browser.

Event

An action such as PageView, ViewContent, AddToCart, InitiateCheckout, Purchase or Lead.

Deduplication

When Pixel and CAPI both send an event, a shared event ID lets Meta count it once, not twice.

Why both? Ad blockers, browser privacy settings and iPhone tracking limits stop some Pixel events from arriving. CAPI fills those gaps from your server, so Meta sees more of your real sales, which improves both reporting and optimization.

Setting it up

1. 1

   Create a dataset

   In Events Manager, create a Pixel (Meta groups Pixel and CAPI data as a dataset) inside your Business portfolio.

2. 2

   Use your platform's integration

   Shopify, WooCommerce, Wix and many store builders have a Meta integration that installs the Pixel and CAPI for you. This is the easiest route.

3. 3

   Or add it by hand

   Paste the Pixel base code on every page and fire Purchase or Lead on the thank-you page. Ask a developer to set up CAPI from your server, with matching event IDs.

4. 4

   Test it

   Use the test events tool in Events Manager, place a test order or enquiry, and check the event arrives with the right value.

Finally, verify your domain in business settings (usually a DNS TXT record or a meta tag). It proves you own the site, protects your links from misuse and lets you control which events matter most for your domain.