Skip to content

What is Conversions API (CAPI)?

The Conversions API (CAPI) is Meta's server-to-server interface for sending conversion events to Facebook from your backend, instead of from the browser via the Pixel. CAPI events are not affected by ad blockers, Safari ITP or iOS App Tracking Transparency, which is why merchants use it to recover the 20-40% of conversions the browser pixel loses.

Definition

Meta exposes the Conversions API as a REST endpoint that accepts events with customer parameters (email, phone, external_id, click IDs), an event_id for deduplication against the pixel, and standard fields like value, currency and content IDs. Events are sent from your server using a long-lived access token tied to a Pixel/Dataset. The same API powers Meta's Server-Side App Events and the Conversions API for Business Messaging. CAPI does not replace the pixel - best practice is to fire both with the same event_id, so Meta deduplicates and gets full coverage. AxiTrace, Shopify's native CAPI integration, Stape's GTM container, and direct backend code are all ways to send CAPI.

Why it matters

The browser pixel is blocked or degraded for a large share of traffic - ad blockers (10-30% of users), Safari Intelligent Tracking Prevention (cookie deletion), iOS App Tracking Transparency (in-app browsers), and consent banners that delay or block firing. CAPI bypasses all of that because the event originates server-side, after the order is confirmed. The downstream wins are: higher Event Match Quality (more parameters, hashed first-party), better Smart Audience training, and accurate ROAS reporting in Ads Manager.

Check it on your site

Our free Meta Pixel and CAPI checker loads your store in a real browser and shows whether the pixel loads once, whether PageView and ViewContent fire with the right parameters, and whether each browser event carries an event_id that a Conversions API copy can be matched against.

Run the Meta Pixel and CAPI checker

Sending the same order to more than Meta? The AxiTrace Conversion API sends it to Meta and 8 more platforms from one install, deduplicated against each pixel.

Frequently asked questions

Do I need both the Pixel and the Conversions API?

Yes. Meta recommends running both with a shared event_id for deduplication. The pixel still provides browser-side signals (page views, button clicks, retargeting) that the server cannot easily produce. CAPI fills the gaps the pixel misses. Together they reach close to 100% event coverage.

Does CAPI work on Shopify Checkout Extensibility?

Yes. Because CAPI events fire from your server (or a connected app), they are unaffected by the checkout.liquid deprecation. Most merchants who lost Purchase tracking during the Shopify checkout migration solved it by moving to CAPI.

Ready to track conversions
accurately?

Join e-commerce teams who stopped guessing and started measuring. Free plan, no credit card, setup in minutes.

10,000 free visits/month · All 9 ad platforms · Full dashboard