Analytics and attribution

What is the Meta Conversions API and how does it work?

The Conversions API sends events such as purchases from your server straight to Meta, so ads still get conversion data when the browser Pixel misses it.

The Conversions API, often called CAPI, is a direct connection between your server and Meta. Instead of relying only on the Pixel in the visitor's browser, your store or a server container sends events such as ViewContent, AddToCart and Purchase straight to Meta. Each event can carry hashed customer data, like email or phone, which helps Meta match it to a person.

Browser tracking loses data to ad blockers, browser privacy limits and slow pages. CAPI fills those gaps, so Meta's delivery system optimises on more complete data. Meta recommends running the Pixel and CAPI together. On Shopify you can switch it on in the official Meta app. On other platforms, stores often use server-side GTM or a partner integration.

When both sources send the same event, Meta needs to know it is one purchase, not two. That is deduplication. The recommended method is to send the same event name and the same event ID from the Pixel and the server. Meta keeps the first event it receives and discards matching duplicates that arrive within 48 hours.

E-commerce example

A store has 200 orders a week in its backend. Meta Events Manager shows 150 Purchase events from the Pixel, because some buyers block tracking. After the store adds CAPI with matching event IDs, Events Manager shows Purchase events from both browser and server, deduplicated. Reported purchases move closer to the 200 in the backend, and campaigns optimise on more of the store's real sales.

Typical mistakes

  1. Sending server events without an event ID that matches the Pixel. Meta counts the purchase twice, and ROAS looks better than it really is.
  2. Sending CAPI events for visitors who did not consent. Moving tracking to the server does not remove your obligations under GDPR.
  3. Passing too few customer parameters. Without hashed email, phone or the fbp and fbc identifiers, Meta matches fewer events and the gain from CAPI stays small.

How we use it at Pleroma

Before we scale Meta spend, we compare Purchase events in Events Manager with backend orders for the same week. A large gap, or a count above the backend, usually means CAPI or deduplication needs fixing first.

Questions and answers

Does the Conversions API replace the Meta Pixel?

No. Meta recommends running both, with deduplication. The Pixel captures browser signals, and CAPI covers what the browser misses.

How do I check if CAPI is working?

Open Events Manager and check the sources of each event: both browser and server should appear. Look at the deduplication status and the Event Match Quality score. Then compare purchases in Meta with orders in your store backend for the same days.

Want us to look at these numbers in your store?

30 minutes on your store and channels. You hear what to fix first.

Book a call