Meta Conversions API: Setup Guide for Marketing Teams
What the Meta Conversions API does, how deduplication and match keys work, the setup options compared, and the mistakes that quietly break measurement.
Vendo Team
Marketing data and reporting
The Meta Conversions API (CAPI) lets you send conversion events to Meta from your servers instead of relying only on the browser pixel. For most advertisers it is the single highest-impact server-side integration, because Meta both optimizes delivery and reports results from the events it receives.
How it works
Your systems send events — purchases, leads, registrations — to Meta's API with:
- An event name and event identifier. The identifier is what lets Meta deduplicate a server event against the matching pixel event. Send the same identifier from both paths.
- Match keys. Hashed email and phone, click identifiers from the ad (captured at landing), browser identifiers where available, and your own external identifier. Meta matches these against accounts; the more consistent your keys, the higher your Event Match Quality.
- Value, currency, and timestamp. Meta optimizes toward value when you send it reliably.
Meta's Events Manager shows received events, deduplication behavior, and match-quality diagnostics per event type — check it during setup rather than after a week of spend.
Setup options
- Direct API integration. Full control; your engineers own payloads, hashing, retries, and monitoring.
- A server-side tag manager. Moves tags off the browser; you still own the container, identity capture, and upkeep.
- A managed pipeline such as Vendo's conversion signals. Your storefront, payment, and CRM sources feed mapped, deduplicated events; delivery history stays inspectable. This is the least engineering-heavy path to backend-truth events (refunds and CRM stages included).
Which is right depends on who maintains it in month six, not week one.
The mistakes that quietly break it
- No shared event identifier. Conversions double-count, or Meta discards a source. This is the most common failure and it looks like success — numbers go up.
- Inconsistent normalization. The same email must be trimmed, lowercased, and hashed identically every time, or match quality drops.
- Ignoring consent state. Send events with the user's consent signals and exclude records without a valid basis.
- Sending only what the pixel already saw. The value of CAPI is backend truth. If the server path merely mirrors browser events, coverage barely improves.
- Late events. Batches that arrive days later fall outside attribution windows and stop informing optimization.
Measuring the result
Compare three numbers per campaign period: conversions in your source of truth, conversions Meta reported before, and after. Expect reported conversions and match quality to rise; interpret gains carefully — part is genuinely recovered signal, part is reattribution of conversions you already had. The signal recovery playbook covers how to keep that honest, and Vendo's signal recovery methodology documents the measurement behind it.
For the wider context — Google, TikTok, and the rest — start from the server-side tracking guide.
Frequently Asked Questions
Do I still need the Meta pixel with the Conversions API?
Meta recommends running both. The pixel contributes browser context and the server path contributes completeness; a shared event identifier lets Meta deduplicate them into one event.
What is Event Match Quality?
A per-event score in Meta Events Manager estimating how well your match keys (hashed email, phone, click IDs, and so on) let Meta match events to accounts. More and cleaner keys generally raise it — and raise how much of your signal Meta can use.
What causes double-counted conversions after enabling CAPI?
Almost always missing or mismatched deduplication: pixel and server events need the same event name and the same event identifier. If they differ, Meta treats them as two conversions.