wesaw
FRGet started

Conversions API

Also known as: CAPI, Meta Conversions API, Facebook Conversions API

The Conversions API, often shortened to CAPI, lets a shop send eligible conversion events to Meta from a server. The destination request does not pass through the shopper's browser. Consent, available signals, destination permissions and the delivery response still determine what can be sent and verified.

How is the Conversions API different from the Meta pixel?

The Meta pixel emits from the browser; Conversions API sends from a server. The two can carry complementary signals. Compatible event names and identifiers allow Meta to recognise a pair, but recording both emissions does not verify its final merge.

Does the Conversions API replace the pixel?

No, and Meta does not recommend replacing it. The pixel still supplies signals the server does not see, such as browsing behaviour before checkout. The two are meant to run together, matched on a shared event identifier so that a sale reported twice is still counted once.

What does the Conversions API not fix?

It does not recover consent a shopper refused, and it does not identify anyone the shop does not already know. The Conversions API changes where the report is sent from, not what the shop is allowed to know. A sale from a shopper who declined tracking stays out.

Sources

  • wesaw scores 9.3 out of 10 on purchase events, read from Meta Events Manager on 21 August 2026. The same store read 8.0 on 18 August, when only the server half was reporting.wesaw, own test store

Last reviewed: