What Is Meta Conversions API (CAPI)?
Meta Conversions API (CAPI) is a server-to-server event pipeline that sends conversions from your server, tag manager, or ecommerce backend directly to Meta, bypassing the browser. It runs alongside the Meta Pixel and, when configured with matching event IDs, deduplicates so a single purchase counts once even when both channels fire.
Formula
Both Pixel and CAPI should send the same event_id for the same real-world event. Meta drops the duplicate within a short window (typically the same session). Without event_id, both count and Meta's optimiser inflates the audience it thinks converted.
CAPI in practice, Dhaka D2C
A Bangladesh apparel brand runs Meta Pixel only. Reported purchases in Meta: 620 per month. After adding CAPI via server-side GTM with hashed email, phone, and IP forwarded, plus deduplicated event_id, reported purchases climb to 812, matching Shopify within 4 percent. Ad Manager ROAS goes from 2.1 to 2.7 on the same spend because Meta finally sees the conversions its ads actually caused.
Benchmarks
- Typical purchase-event recovery from Pixel-only to Pixel plus CAPI: 15 to 40 percent, higher on iOS-heavy traffic.
- Event Match Quality (EMQ) target: 7.0 out of 10 or higher on purchase events.
- Fields with the biggest EMQ lift: hashed email, hashed phone, external_id, client IP plus user agent.
- Server-side GTM as CAPI source: adds 200 to 400ms latency, negligible for post-conversion events.
Meta's own case study library documents advertisers reporting 15 to 40 percent additional conversions attributed after adding CAPI on top of the Pixel, with the largest lifts on iOS-dominant catalogues after ATT.
Why it matters
iOS 14.5 ATT, ITP, and third-party cookie deprecation have cut Pixel-only signal by 20 to 40 percent on most accounts. CAPI is the only way to keep Meta's auction and Advantage+ delivery seeing the real conversion picture. An account without CAPI in 2026 is not just under-reporting, it is bidding on incomplete signal.
Common mistakes
- 1.Sending CAPI events without event_id. Meta cannot deduplicate, so Ads Manager double-counts and CPA looks artificially low until Meta reconciles.
- 2.Forgetting to hash PII (SHA-256) before sending. Meta rejects the fields silently and EMQ stays under 5.
- 3.Firing CAPI on non-conversion pageviews. Wastes signal budget and pollutes conversion events for optimisation.
- 4.Relying on the Shopify or WordPress native CAPI plugin without QA. Most send incomplete match data; run Events Manager Test Events on every install.
Put Meta Conversions API to work
Free calculators
Related services
FAQs about Meta Conversions API
Is CAPI a replacement for the Meta Pixel?
No. Meta's guidance is to run both. The Pixel captures fast browser signals and enables Automatic Advanced Matching; CAPI captures server-confirmed events that survive cookie loss. Deduplication by event_id ensures each conversion counts once.
How do I know CAPI is working?
Open Meta Events Manager, run Test Events, and confirm each event arrives from both Pixel (browser) and CAPI (server) with the same event_id. Then check Event Match Quality; purchase events should score 7.0 or higher within a week of clean data.
Do I need server-side GTM to run CAPI?
No, but it is the cleanest path. Alternatives: Meta's Conversions API Gateway on your server, Shopify or WordPress native integrations, or a direct backend post-purchase call. Server-side GTM wins on match quality and future-proofs GA4 and Google Ads at the same time.
Does CAPI fix attribution to Meta specifically or across channels?
CAPI is Meta-specific. For Google Ads, the equivalent is Enhanced Conversions plus offline conversion uploads. For a unified stack, run server-side GTM as the shared source of truth and fan events out to Meta CAPI, Google Ads, and GA4 from one place.
What about privacy and consent?
CAPI still respects consent. Only send events for users who granted marketing consent. Consent Mode v2 signals should be honoured on the server side before forwarding to Meta, otherwise you are non-compliant in the EEA and UK regardless of how the event was captured.
Related terms
Browser pixel is client-side and blocked by ITP; CAPI is server-side and survives cookie loss.
Meta's 0 to 10 score of how well events match to a Meta user.
Running Tag Manager on your own server to improve match + control.
Google's consent signalling API; required in EEA for ad measurement.
How long after a click or view Meta can still credit a conversion.