Conversions API

One-Line Definition

The Conversions API (CAPI) is a server-side tracking solution from Meta that sends conversion events directly from your server (or CRM, or offline data source) to Meta's ad systems, bypassing the browser and its privacy restrictions to improve attribution accuracy.

Real-Life Analogy

Think of browser-based tracking (the Meta Pixel) as a messenger running through a crowded city during a thunderstorm. The messenger has to dodge ad blockers, cookie consent walls, iOS App Tracking Transparency prompts, and browser restrictions like Safari's Intelligent Tracking Prevention. By the time they arrive, they may be soaking wet, late, or may never show up at all.

The Conversions API is like sending the same message through a private courier with a direct phone line to the recipient. The message originates from a trusted source (your server), travels a reliable path, and arrives intact — even if the "messenger" (the browser) never made it out the door.

In short: the Pixel asks the *browser* to deliver the news. CAPI asks *your own backend* to deliver it.

Core Formula

At its simplest, every Conversions API event is a structured payload:

CAPI Event = event_name + event_time + user_data (hashed) + event_source_url + action_source + custom_data

Where:

- event_name — the standard or custom event (e.g., Purchase, AddToCart, Lead)

- event_time — Unix timestamp of when the event occurred (Meta accepts up to 7 days back)

- user_data — hashed identifiers (email, phone, name, external_id, fbp, fbc, client IP, user agent) using SHA-256

- action_source — where the event happened (website, app, physical_store, phone_call, chat, email, other)

- custom_data — value, currency, content_ids, contents, num_items

The match quality score — Meta's 0–10 rating of how well your events match user profiles — is driven almost entirely by how rich and accurate your user_data field is. A score of 6.0+ is considered healthy; top advertisers typically run 7.5–9.0.

Comparison with Related Terms

The critical distinction: Pixel and CAPI are not competitors — they are complements. Best practice is to run both simultaneously and deduplicate using event_id so Meta counts each conversion exactly once.

Use Cases

1. iOS-heavy DTC stores. With Apple's App Tracking Transparency (ATT), roughly 75%+ of iOS users opt out of cross-app tracking. Pixel-only advertisers report 15–30% under-reported conversions on iOS. CAPI recovers most of that gap by using server-side identifiers like hashed email and external_id.

2. High-AOV purchase tracking. For a store selling $200+ items, missed conversions distort ROAS calculations badly. Sending Purchase events via CAPI with value and currency ensures Meta's algorithm optimizes toward real revenue, not just clicks.

3. Subscription and lead-gen funnels. When the conversion happens in your CRM (e.g., a qualified lead 3 days after signup), only CAPI can send that offline event back to Meta with action_source: "offline" or "website".

4. Post-purchase upsells and refunds. Server-side events let you send Refund or SubscriptionCancelled events, keeping Meta's optimization signal clean and preventing wasted spend on churned users.

5. Multi-touch B2B or high-consideration funnels. When a user clicks an ad on mobile but converts on desktop 5 days later, CAPI's hashed identifiers stitch the journey together more reliably than cookies alone.

6. Aggregated Event Measurement (AEM) compliance. On iOS, Meta limits advertisers to 8 prioritized events per domain. CAPI lets you send the highest-value events server-side, so you preserve the signal that matters most.

Misconceptions

"CAPI replaces the Pixel." No. Meta explicitly recommends running both. The Pixel catches in-browser signals (like fbp cookie and referrer data) that servers cannot see. CAPI adds reliability and identity resolution. Running only one leaves signal on the table.

"CAPI is a magic fix for iOS." It improves attribution, but it is not perfect. Hashing email only works if the user is logged into Meta with that same email. Match rates typically range from 60–85% depending on data quality. Expect improvement, not omniscience.

"It's plug-and-play." For Shopify, apps like the native Facebook & Instagram channel or third-party tools (Stape, Elevar, Analyzify) handle it. For custom stacks (headless, custom checkout), you need engineering work: server endpoint, SHA-256 hashing, event deduplication with event_id, and rate-limit handling.

"More events = better." Sending low-quality or duplicate events hurts performance. Meta's algorithm learns from clean signals. Sending 10,000 redundant PageView events dilutes the model and can trigger event quality warnings in Events Manager.

"It's a privacy violation." CAPI sends *hashed* first-party data that you already collected with consent. Meta hashes it again on receipt and never sees raw PII. Done correctly, CAPI is GDPR/CCPA-compatible — but you still need a lawful basis and clear consent language.

"One event per conversion is enough." You should send the full funnel — ViewContent, AddToCart, InitiateCheckout, Purchase — so Meta can optimize for upper-funnel signals when lower-funnel volume is thin.

Related Terms

- Meta Pixel — the client-side counterpart to CAPI

- CAPI Gateway — Meta's no-code server-side option

- Aggregated Event Measurement (AEM) — iOS 14.5+ framework limiting events per domain

- Event Match Quality (EMQ) — Meta's 0–10 score for event identity strength

- Deduplication (event_id) — matching Pixel and CAPI events to avoid double-counting

- Server-Side Tagging (SST) — broader category including GTM Server-Side, Stape

- Hashed PII / SHA-256 — the encryption standard for user_data

- fbp / fbc cookies — Meta's first-party identifiers passed via CAPI

- Offline Conversions — CAPI's predecessor for CRM/offline event uploads

- TikTok Events API / Google Enhanced Conversions — equivalent solutions on other platforms

- First-Party Data Strategy — the broader marketing discipline CAPI serves

Bottom line: The Conversions API is no longer optional for serious DTC advertisers. With iOS opt-out rates above 70% and ad blocker usage at 30%+ globally, server-side tracking is the difference between optimizing on real revenue and optimizing on a broken mirror. Set it up once, deduplicate properly, and let Meta's algorithm see what your business actually earns.