Start free
Kunads / Glossary / Conversions API (CAPI)

Conversions API (CAPI)

Updated 2026-11-19 · Editorial policy

The Conversions API (CAPI) is Meta's way to send events such as purchases, leads and sign-ups straight from your server to Meta, instead of only from the Meta Pixel running in the visitor's browser. Because the data leaves your server, browser settings, connection drops and ad blockers do not stop it.

It handles web, app and offline events. Meta's older, separate Offline Conversions API was discontinued in May 2025; offline events now go to a dataset through the Conversions API.

Do I still need the Meta Pixel if I use CAPI?

You can keep both, and Meta supports sending the same events from each; if you have a pixel, Events Manager can also add the Conversions API for website events in one click. Meta describes two set-ups:

How does Meta deduplicate pixel and CAPI events?

Meta treats two events as one when event_name matches and event_id matches, or, as a fallback, when event_name matches and external_id or fbp matches. When both arrive, Meta keeps the one received first. Partner integrations such as Shopify and WooCommerce add these parameters for you; a custom build has to add them in code.

The counting rule that follows from it:

Unique events = browser events + server events − matched pairs

Worked example: 100 purchases

A shop takes 100 orders on a day. Both the pixel and the server send Purchase events.

Unique purchases Meta can work with: 82 + 97 − 79 = 100. Of those, 79 arrived from both sources, 3 from the pixel only (82 − 79) and 18 from the server only (97 − 79). Check: 79 + 3 + 18 = 100.

Bar chart: of 100 orders, 79 reached Meta from both pixel and server, 18 from the server only and 3 from the pixel only.

Now the same day with event_id missing on the server events and no external_id or fbp to fall back on: nothing pairs up, and Events Manager shows 82 + 97 = 179 purchases for 100 orders. Meta's own help page names mismatched or missing event_id as the most common deduplication problem.

An edge case: the event_id that is unique but different

A common custom build generates the browser event_id from a random string at checkout and the server event_id from the order number. Both are unique, both look correct in testing, and none of them ever pair. The symptom is a purchase count close to the sum of both sources, as in the 179 above. The fix is to create one identifier when the order is placed, usually the order ID, and pass the same value to the pixel and to the server call.

What sending from the server makes possible

Set-up errors

Sending profit instead of revenue

Kunads can send real profit or won-deal value back to Meta through the Conversions API as a separate conversion, opt-in per account. How that works for lead businesses is covered in sending CRM won deals to Meta and Google. Google's counterpart for the same idea is the Data Manager API, and for website tags enhanced conversions.

Related: server-side tracking, offline conversions, POAS.

Would rather not do this by hand? Kunads' agents check every campaign against your margin each day and propose a fix you approve or ignore.

Audit my ads for free Try Kunads, no card

CAPI and offline sales

Can I send offline sales with the Conversions API?

Yes. Meta's separate Offline Conversions API was discontinued in May 2025, and offline events now go to datasets through the Conversions API, a partner integration or a manual upload in Events Manager.