Paid Advertising Intermediate

Conversions API (CAPI)

The Conversions API sends conversion data from your server directly to Meta, bypassing browser restrictions that block or degrade the standard pixel.

The Conversions API is a direct server-to-server integration that sends conversion event data from your website or systems to Meta without relying on the browser.

What Conversions API Means in Marketing

The Meta Pixel fires JavaScript from the user’s browser to send conversion events. That architecture worked well before iOS privacy changes and widespread ad blocking reduced the reliability of browser-based tracking. Today, a significant share of pixel events either do not fire or arrive stripped of the user data needed to match them to Meta profiles.

The Conversions API solves this by moving the event signal from the browser to your server. When a purchase happens, your server sends the event data directly to Meta’s API. Browser restrictions cannot interfere with server-to-server communication.

The two approaches are used together, not as alternatives. The pixel captures events it can reach. The Conversions API captures what the pixel misses. Meta deduplicates the two streams using a shared event ID so conversions are not counted twice.

How Conversions API Works

The technical setup requires server-side engineering. When a user triggers a conversion on your site, your server sends a POST request to Meta’s Conversions API endpoint with the event data. At minimum, the request includes the event name, the timestamp and a unique event ID. For better matching, you also send hashed customer data: email address, phone number and browser information.

Meta uses the customer data to match the event to a profile in its system. Higher match rates mean better attribution. Poor data quality, such as incomplete or unstandardised customer fields, reduces match rates and degrades the accuracy of reporting and optimisation.

The event ID is the deduplication key. You generate the same ID for both the pixel event and the CAPI event. Meta sees both, checks the ID and counts the event once.

Conversions API Example

A fashion retailer in India was running a Meta retargeting campaign and noticed their reported conversions had dropped significantly after Apple’s iOS 14 update. Their pixel events were being blocked for a large segment of their audience. After implementing the Conversions API alongside the pixel, their reported purchase events increased by around 30 percent. The additional signal improved the campaign’s ability to optimise for high-value purchasers and reduced cost per acquisition.

Why Conversions API Matters for Marketers

Meta campaigns optimise based on the signal you feed them. Incomplete event data means the algorithm is making decisions with partial information. CAPI closes that gap. Better signal quality leads to better targeting decisions and more accurate reporting.

For any brand spending meaningfully on Meta, CAPI is not optional. It is the baseline required for accurate measurement and effective campaign optimisation in a post-iOS-14 environment.

Frequently Asked Questions

Why does server-side tracking matter for Meta campaigns?

The Meta Pixel fires from the browser. When users have ad blockers, iOS privacy restrictions or cookies blocked, pixel events either do not fire or fire without enough data. The Conversions API sends the same events from your server, where these restrictions do not apply. The two signals are deduplicated by Meta, so you end up with more complete event data without double-counting.

What is deduplication and why does it matter?

Deduplication is the process by which Meta reconciles events received from both the pixel and the Conversions API to avoid counting the same conversion twice. You assign an event ID to each event and send the same ID from both sources. Meta uses the ID to recognise that both signals refer to the same event and counts it once. Without deduplication logic, CAPI deployments inflate reported conversion numbers.

What data can you send through the Conversions API?

Standard events such as Purchase, Lead, ViewContent, AddToCart and InitiateCheckout, plus custom events. Beyond event type and value, you can pass hashed customer data for matching: email, phone number, name, location and user agent. The more customer data you send with each event, the higher the match rate between your events and Meta user profiles, which improves attribution accuracy.

Consulting & Strategy

Need help putting this concept into practice on your campaigns? Share your current targets and I will suggest the right approach.

Discuss your campaigns