Conversions API
Also called CAPI
By the AdFlint research team · Last reviewed July 2026
Sends conversion events to Meta from your server or CRM instead of the visitor's browser, bypassing client-side signal loss.
Your backend posts events straight to Meta's endpoint with hashed customer parameters and the browser identifiers fbp and fbc for matching. You add it because pixel-only setups lose events to blockers and tracking prevention, and because server events can carry offline or delayed outcomes. Send the same event from both sources with a shared event_id so Meta deduplicates; skip that and you will double-count purchases and mislead the bidding system.
Conversions API compared with
The settings this gets confused with, and how to tell them apart.
You should not need to know this to advertise.
AdFlint handles the settings for you, inside the Google and Meta accounts you already own.
Try AdFlint free