Growth Systems Library
Conversion API (CAPI)
The Conversions API (CAPI) is a server-side integration that sends conversion events directly from your server to ad platforms, bypassing browser tracking restrictions — it is the most impactful technical fix available for the signal loss caused by iOS 14 and browser privacy changes.
The Conversions API (CAPI) is a server-to-server integration that sends website event data — purchases, sign-ups, lead form completions, add-to-carts — directly from your server to an ad platform's server, without relying on a browser pixel. Meta's Conversions API, Google's Enhanced Conversions, and TikTok's Events API are the primary implementations. Unlike a browser pixel, CAPI is not affected by ad blockers, iOS tracking restrictions, or cookie deprecation, because it does not pass through the browser at all.
Exactius implements CAPI as a foundational infrastructure requirement in every Growth Operating System deployment — because without reliable conversion signal, platform optimisation algorithms cannot function correctly, and reported attribution metrics are systematically understated.
Following iOS 14.5, the Meta Pixel lost visibility into 30–60% of conversions from Apple device users who did not consent to tracking. This degraded Meta's optimisation algorithm, which relies on conversion signal to identify high-probability purchasers and improve campaign targeting. The result was rising CPAs and declining ROAS for most advertisers who relied solely on the browser pixel. CAPI restores the missing signal by sending conversion data server-side, independent of user consent to browser tracking.
The capital allocation consequence of poor CAPI implementation: the platform's algorithm is optimising on an incomplete signal, which means it is finding the wrong audiences. Bids are calibrated to conversion rates that are lower than actual (because many conversions are invisible to the platform), leading to under-investment in high-performing audience segments. Fixing CAPI is one of the fastest paths to algorithmic performance improvement without changing creative or budget.
CAPI implementation quality metrics: Event Match Quality (EMQ) score on Meta — Meta scores CAPI implementations from 0–10 based on how well the customer information sent with each event matches their user records. Target: 7.0+. Below 6.0 indicates significant matching failures that undermine signal quality. Event deduplication rate — when running CAPI alongside the browser pixel (recommended), deduplication prevents the same conversion from being counted twice. A deduplication rate of 95%+ indicates the implementation is correctly handling overlapping events.
CAPI implementation tiers: Basic — purchase events only, sent server-side with order ID and hashed email. Standard — full e-commerce event set (ViewContent, AddToCart, InitiateCheckout, Purchase) with customer data enrichment (hashed email, phone, name, address). Advanced — all standard events plus custom events, customer LTV data included in purchase events, real-time deduplication with pixel events, and predictive signal enrichment. What breaks CAPI: sending events without customer identifiers (low EMQ); missing deduplication (double-counting inflates attributed conversions); server delays causing events to be attributed to wrong sessions.
CAPI is the highest-ROI technical fix available to most businesses running paid social. Exactius consistently finds that clients with basic pixel-only implementations are recovering only 50–70% of their actual conversion signal on Meta. A properly implemented CAPI typically recovers 15–25% of attributed conversions that the pixel was missing, which improves the platform's optimisation algorithm and often results in 10–20% CPM reduction as the algorithm finds higher-probability conversion audiences more efficiently.
The Growth Operating System, developed by David Manela, treats CAPI implementation quality as a prerequisite for any meaningful Meta campaign optimisation. No creative test, no bid strategy, no budget allocation decision is reliable on top of a broken signal layer. Exactius embeds growth operators who audit CAPI implementation in the first 30 days of every engagement and fix signal quality issues before scaling media spend.
→ Learn more about the Growth Operating System at davidmanela.com/frameworks/growth-operating-system
What is the Meta Conversions API and why do I need it?
The Meta Conversions API (CAPI) is a server-side integration that sends conversion events — purchases, sign-ups, add-to-carts — directly from your server to Meta, without going through the browser. You need it because the Meta Pixel, which runs in the browser, lost visibility into 30–60% of conversions from iOS devices after Apple's App Tracking Transparency update in 2021. Without CAPI, Meta's algorithm is optimising on an incomplete signal — it cannot see a significant share of your actual conversions, which means it cannot correctly identify and target high-probability purchasers. Implementing CAPI recovers the missing signal and restores the algorithm's ability to optimise effectively.
Should you run CAPI alongside the pixel or instead of it?
You should run CAPI alongside the pixel, not instead of it, with proper event deduplication configured. The pixel captures events immediately in the browser with high timestamp accuracy. CAPI captures events server-side with richer customer data (because you have access to your server-side customer record, including email and phone). Running both in parallel gives Meta the most complete signal: browser-speed event timing from the pixel and customer-enriched matching quality from CAPI. Deduplication — using the same event ID for both the pixel and CAPI version of each event — prevents the same conversion from being counted twice. A 95%+ deduplication rate indicates the setup is working correctly.
How do you know if your CAPI implementation is working?
Check your Meta Events Manager for the Event Match Quality (EMQ) score for your CAPI events. An EMQ of 7.0 or above indicates the implementation is working well — Meta can match the customer data you are sending with its user records at a high rate. Below 6.0 indicates significant matching failures. Also check that your deduplication rate in Events Manager is 90%+, which confirms the pixel and CAPI events are being correctly deduplicated. If your CAPI is sending events without customer identifiers (email, phone, name), or if your server is sending events with significant delays, both the EMQ and deduplication rate will suffer.
Exactius Growth
Your growth system is either compounding or degrading.
Book a diagnostic call. We'll identify where your growth system is breaking.
Book a call