Conversions API
Conversions API is a server-to-server interface that lets advertisers send conversion and event data directly to ad platforms, reducing dependence on browser-side tracking.
Also known as: conversion API, server-side conversion tracking, CAPI
Conversions API, commonly abbreviated CAPI, is the general name for server-to-server interfaces that ad platforms expose so advertisers can send conversion and event data directly from their servers rather than relying on the browser pixel. Meta's Conversions API is the most well-known example; Google, TikTok, LinkedIn, and most major platforms offer equivalent capabilities under various names.
What The Conversions API Means
Conversions API is the server-side counterpart to the traditional pixel. Where a pixel relies on JavaScript running in the user's browser to fire events back to the ad platform, CAPI sends those events from the advertiser's own server through an authenticated API call. The scope typically covers form submissions, purchases, lead-quality signals, custom conversion events, and offline conversions imported from CRM systems. CAPI does not replace the pixel in most setups; it complements the pixel to provide a more complete and resilient view of what happened, especially as browsers tighten restrictions on third-party tracking.
How The Conversions API Works
In practice, Conversions API is implemented by capturing the conversion event server-side — when a lead form processes successfully, when a purchase completes, when a CRM stage advances — and sending an authenticated payload to the ad platform's API with the event details, the user identifiers available, and a deduplication key that matches the pixel event if one also fired. The ad platform reconciles pixel and CAPI signals using the dedup key and uses the combined data for attribution and optimization. Setup typically involves a tag manager, a server-side container, or a direct integration from the marketing automation platform or CRM.
Common Pitfalls and Misconceptions
The most common Conversions API mistake is implementing it without a deduplication strategy, which inflates event counts when both the pixel and CAPI report the same conversion. Teams also under-invest in user identifier quality — CAPI requires hashed email, phone, or other identifiers to match users, and weak identifiers degrade the matching that makes the API valuable. Another trap is treating CAPI as a one-time setup. Ad platforms iterate on event taxonomies, identifier requirements, and API versions, and an implementation set up two years ago is probably leaving signal on the table. Privacy posture is also routinely misjudged: CAPI does not exempt the advertiser from consent obligations, and pushing conversion data server-side without honoring consent is a regulatory risk.
Conversions API in Practice
A mature Conversions API implementation pairs server-side event sending with disciplined consent enforcement and identifier hygiene. The teams that get the most value run regular event-quality reviews against the ad platform's diagnostics, confirm dedup is working, and review identifier match rates to spot where the CRM or marketing automation can contribute better data. They also keep CAPI in step with the broader server-side tracking story, often co-locating it with their own server-side container so the same event firing logic powers analytics, attribution, and ad platforms consistently. CAPI is best treated as one component of a server-side measurement strategy, not a standalone feature toggled on in the ad platform's settings.
Frequently asked questions
-
How is a conversions API different from a tracking pixel?
A tracking pixel runs in the user's browser and can be blocked by ad blockers or browser restrictions. A conversions API sends data server-to-server, bypassing the browser. The API captures conversions the pixel may miss, and the two are often used together.
-
Why use a conversions API at all?
Browser-based tracking has become less reliable due to ad blockers, cookie deprecation, and tracking prevention. A conversions API restores some measurement accuracy by sending conversion data directly from servers, helping ad platforms optimize and report correctly.
-
What is event deduplication in this context?
When both a pixel and a conversions API report the same conversion, the ad platform needs to recognize them as one event. Deduplication, typically using a shared event identifier, prevents the conversion from being counted twice.
-
Does a conversions API affect privacy compliance?
Yes. Sending user data to an ad platform server-side still requires a lawful basis and valid consent. The conversions API changes the technical method of sharing data but does not remove privacy obligations.
-
Do all ad platforms offer a conversions API?
Most major advertising platforms now offer a server-side conversions interface, though they use different names and have different requirements. Implementation details, supported events, and matching methods vary by platform.
-
What user identifiers should be sent through a conversions API?
Most ad platforms accept hashed identifiers like email, phone, and external user IDs, which they match against their own data. Sending high-quality, hashed identifiers improves attribution and audience matching. The platforms publish exact hashing requirements that must be followed for the match to work.
-
Does using a conversions API improve campaign performance?
It can, because better conversion data improves the ad platform's optimization signal. Many advertisers see measurable lifts after implementing CAPI, especially in iOS-heavy or privacy-restricted audiences. The size of the lift depends on how much the pixel was missing before, which varies by industry and audience.