Conversions API (CAPI) Meaning: Server-Side Meta Events

What is the Conversions API?

The Conversions API, or CAPI, is Meta's method for receiving conversion events — purchases, leads, registrations — directly from your server instead of from a visitor's browser. You send the same event types the pixel would normally fire, but the request travels from a server you control to Meta's Graph API over HTTPS. Meta then matches that event to a user profile using hashed identifiers such as email or phone, and folds it into the same optimization and reporting systems the pixel already feeds.

CAPI is one implementation of a wider practice: server-side tracking, where the advertiser's own infrastructure, not the user's device, sends the event to Meta. Run the pixel and CAPI together and Meta deduplicates matching events using an event ID you generate yourself, so a single purchase never gets counted twice.

How does CAPI differ from the pixel?

CAPI differs from the pixel primarily in where the event originates and what can silently block it before it reaches Meta. The pixel is JavaScript that runs inside the visitor's browser and reports whatever it can see before a blocker, a privacy setting, or a closed tab interrupts it; for a full breakdown of what that snippet still captures, see what the Facebook pixel tracks now. CAPI, by contrast, runs on infrastructure you control, so nothing on the visitor's device can stop the request from firing.

Neither channel alone tells the full story, which is why Meta scores the combined feed rather than either source in isolation. A pixel-only account and a CAPI-only account can each look healthy on their own dashboards while still under-reporting the same conversions for entirely different reasons.

Why did CAPI become standard after iOS 14?

CAPI became close to mandatory once Apple's App Tracking Transparency framework, launched with iOS 14.5 in April 2021, required an explicit opt-in before any app could track a user across other companies' apps and websites. Adoption of that opt-in landed low: industry estimates through 2021 and 2022 clustered somewhere in the 20% to 40% range of eligible users, though the exact figure for any given account varies enough that it needs checking against your own data rather than assumed from a headline number. Meta's browser-side pixel lost visibility into a large share of iOS conversions almost overnight, and Aggregated Event Measurement arrived as a partial patch that still couldn't recover full signal.

That erosion never fully reversed — it kept compounding as Meta's own measurement systems shifted, and the 2026 attribution change cut reported conversions again for advertisers who hadn't already layered in server-side data. CAPI became the standard response not because it's flawless, but because it's the one lever advertisers control when the browser-side picture degrades.

What is Event Match Quality (EMQ)?

Event Match Quality, or EMQ, is Meta's score — on a 0-to-10 scale — for how confidently it can tie an incoming event to a real user profile. Meta calculates it from the customer information parameters you send with each event: email, phone, first and last name, external ID, IP address, user agent, and the fbc/fbp browser cookies. More matched parameters generally raise the score, and a higher score generally improves how efficiently Meta can optimize delivery around that event.

A higher EMQ score doesn't only sharpen attribution: it strengthens the audiences Meta builds from that same data, including any lookalike audience modeled off the buyers those events represent. Meta doesn't publish an exact score-to-performance curve, so treat published EMQ benchmarks as directional rather than precise until you've tested your own account.

Do affiliates need CAPI, or do network postbacks cover it?

Most affiliates running offers through a network don't need to build their own CAPI integration, and the common advice to just set up CAPI misapplies a merchant-side tool to a publisher-side role. A network's server-to-server postback already reports the sale to Meta, or to the tracking layer feeding Meta, with match data the network controls end to end, because the network, not the affiliate, owns the actual purchase event on its checkout page.

Building a parallel CAPI feed for a page you don't control usually produces duplicate events, fabricated event IDs, or data that contradicts what the network already sent, which muddies optimization rather than improving it. CAPI earns its place when you own the checkout: your own domain, your own order confirmation, your own server. For a pure affiliate without that infrastructure, the postback is the real conversions API, even though Meta doesn't call it that.

What is a CAPI gateway vs a full setup?

A CAPI gateway is a hosted, pre-built bridge that maps your data source to Meta's API without custom code, while a full setup means you write and maintain that connection yourself. Gateways trade a monthly fee and some flexibility for speed: connect a form tool or a checkout platform, map a handful of fields, and events start flowing within a day. A full setup demands developer time to handle hashing, deduplication logic, and Meta's periodic API version changes, but it gives you complete control over what gets sent and when.

Some gateways also bundle event warmup logic that overlaps with older pixel seasoning practices, trickling a run of low-value events through the pipe before real ad spend hits it. That overlap is a convenience, not a substitute for checking the feed yourself: a gateway configured wrong seasons the pixel with garbage data as easily as it seasons it with good data.

• Gateway: fast to launch, recurring cost, limited to the fields the vendor supports.
• Full setup: no vendor lock-in, higher upfront development cost, full control over event timing and parameters.
• Hybrid: some teams start on a gateway, then migrate high-volume events to a custom feed once volume justifies the build.

What are the most common CAPI failures?

The most common CAPI failures are duplicate events, weak parameter hashing, missing source fields, and expired access tokens, all of which degrade EMQ or inflate reporting without throwing an obvious error. Because Meta accepts malformed events in many cases without rejecting them outright, a broken integration can run for weeks before anyone notices the reported numbers don't match the ad account.

• Duplicate events: pixel and CAPI both fire the same conversion without a shared event ID, inflating reported totals.
• Unhashed or malformed identifiers: emails and phone numbers sent without proper SHA-256 hashing get silently dropped from matching.
• Missing action_source or event_source_url fields: events that omit these deliver successfully but score as low quality.
• Expired system user token: a lapsed token breaks the whole feed with no alert in the ads interface unless someone checks Events Manager diagnostics directly.
• Event time outside the accepted window: sending event_time too far in the past gets an event rejected or discounted; the exact cutoff has shifted before, so confirm the current window in Meta's documentation rather than assuming last year's rule still holds.

Quick decision checklist

Use this page as a decision aid, not a generic blog post. The practical question is whether the reader needs faster evidence about what is already working in VSL-driven direct response, especially across nutra, supplements, GLP-1, weight loss, blood sugar, and adjacent high-intent health markets.

Daily Intel Service is most relevant when the next decision depends on active market examples: which hook to test, which claim style is risky, which funnel structure is common, which language market is moving, and whether a competitor's creative is likely early, scaling, or already saturated.

• Start with the TL;DR if you need the direct answer.
• Use the table to compare trade-offs quickly.
• Use the FAQ for answer-engine-ready summaries.
• Use the CTA when the decision requires live VSL and ad examples instead of theory.

Daily Intel's coverage advantage

Daily Intel Service is positioned around category-leading variety and actionability: one of the broadest direct-response catalogs of VSLs and ad creatives across blackhat, greyhat, and whitehat advertising patterns, with enough context to understand what the advertiser is doing beyond the visible creative. The practical difference is that members are not just seeing a screenshot; they are seeing the VSL, the ad, the funnel path, the transcript, the UTM context, and the research notes that turn the asset into a decision.

This matters because direct-response affiliates do not operate in one clean category. A weight-loss campaign may use a whitehat compliance ad, a greyhat pre-lander, a more aggressive VSL, and a checkout path designed around upsells and recovery. A useful intelligence platform needs to capture that spectrum instead of pretending every winning campaign looks like a public brand ad.

Blackhat, whitehat, and multilingual signal coverage

Daily Intel tracks patterns across both blackhat-style and whitehat-style campaigns so operators can understand the market without blindly copying risk. Whitehat examples help with durability and compliance review; blackhat and greyhat examples reveal pressure points, hooks, mechanisms, and funnel structures that may be driving spend but require careful adaptation before use.

The catalog is also built for global operators, with VSL and ad references spanning 14+ languages and different local idioms. That is a key advantage for Brazilian, LATAM, European, MENA, Indian, and non-native English affiliates who need to see how the same market desire is translated across cultures instead of only studying US English ads.

How to use the intelligence responsibly

The goal is modeling, not copying. Use Daily Intel to understand structure: hook, mechanism, proof, claim intensity, funnel depth, offer economics, and saturation stage. Then build original creative, review claims, and adapt the angle to the traffic source, country, language, and compliance requirements of the campaign.

A strong workflow compares multiple examples before acting. If the same mechanism appears across several languages, several advertisers, and several funnel variants, it may be a durable market signal. If the example appears only once or depends on an aggressive claim, treat it as a research clue rather than a campaign template.

• Model structure, not protected creative assets.
• Separate whitehat durability from blackhat persuasion pressure.
• Compare US English examples against LATAM, European, and other language variants.
• Use transcripts and funnel notes to build original briefs.
• Keep compliance review separate from market research.

Methodology and source context

Daily Intel pages are written from a research workflow that reviews active VSLs, Meta ad creatives, transcripts, UTMs, funnel paths, checkout steps, upsells, recovery sequences, and compliance-sensitive claim patterns. The goal is to explain observable market behavior, not to provide legal, medical, or platform policy advice.

For educational pages, the supporting references should help readers verify search, crawlability, and public ad research context, especially Meta Ad Library, Meta advertising standards, and Google helpful content guidance. Daily Intel then adds the direct-response interpretation layer so the page explains what the signal means for actual affiliate research decisions.

For deeper evaluation, continue through Direct response glossary hub, Prostate VSL Mechanisms: Flush, Switch and Exotic Herbs, How to Model a Tinnitus VSL Without Copying the Villain, Nail Fungus VSL Angles: 76% of Its Villain Lines Are Fungal, VSLs Scaling in 2026: Live Cross-Niche Winner Index, and What is a VSL?. These related Daily Intel pages connect this topic to the relevant methodology, pricing, trust context, comparison path, or niche workflow.