The Meta Conversions API, Explained for Store Owners

By Kestrel Ads · · 6 min read

If you run Facebook or Instagram ads, Meta needs to know which ads lead to purchases. The Pixel used to do that alone. Today it misses too much, and the Conversions API is how stores fill the gap.

Pixel vs Conversions API

The Meta Pixel is code in the visitor's browser that tells Meta when someone views a product, adds to cart or buys. Ad blockers, browser privacy features, phone settings and declined cookie banners all stop some of those messages getting through.

The Conversions API (often shortened to CAPI) sends the same events from your store's server straight to Meta. Because it doesn't depend on the browser, more purchases arrive, and Meta's delivery system has better data to find buyers.

Why it matters for your results

Meta's campaigns learn from purchases. If a share of them never arrive, the system learns less, optimises worse, and your reports show fewer sales than actually happened, which can make good ads look like losers. Sending purchases from the server too means better learning and more accurate reporting.

Setting it up

  • Shopify: the Facebook & Instagram app (Meta's sales channel) sets up both the Pixel and the Conversions API. Choose the highest customer data-sharing setting it offers.
  • WooCommerce: Meta's official plugin, or a well-maintained tracking plugin, can send server events. Avoid running two tools that both send purchases.
  • Custom sites: send events from your server with the Conversions API, or use a partner integration or server-side tag manager.

Avoid double counting

When both the Pixel and the Conversions API send the same purchase, Meta needs a way to tell they're one event. They should share the same event name and the same event ID; Meta then keeps one and discards the copy. Official integrations do this for you. Hand-built setups are where doubles usually creep in.

A quick check: in Events Manager, purchases received over a week should be close to your store's real order count, not double it.

Event Match Quality

Events Manager scores how well each event can be matched to a Meta account, from details like a hashed email or phone number sent with it. Higher scores mean more purchases get credited to the right ads. Sending customer details with server events (hashed, as the integrations do automatically) usually improves it.

Respect consent

Where privacy law requires it, only send marketing events for visitors who agreed to them. Server-side tracking isn't a way round consent; it's a more reliable way to send the data you're allowed to send.

Free ads audit

See what we'd change.

Want a second pair of eyes on your ads? We'll look at your Meta and Google ads and your store, and send a short, honest review. Free.

Get a free audit

Keep reading