Conversions API (CAPI)
Also known as: Meta Conversions API
The Conversions API (CAPI) is Meta's server-to-server connection that lets a store send events such as purchases directly from its server to Meta, alongside or instead of the browser pixel.
Formula
Event sent by pixel (browser) + same event sent by CAPI (server) with the same event_name and event_id → Meta keeps one, discards the duplicateOther platforms offer equivalents, such as TikTok's Events API.
Worked example
Illustration: a store has 100 real purchases in Shopify. Because of ad blockers and browser restrictions, the browser pixel records 80. With CAPI also sending each purchase from the server, the same order ID is used as event_id on both.
- Pixel only: 80 of 100 purchases reach Meta.
- Pixel + CAPI: up to 100 reach Meta; the 80 that arrive twice are deduplicated by event_id.
- Without a shared event_id, those 80 could be counted twice, reporting up to 180 purchases.
CAPI recovers missing events; the event_id is what keeps it from inventing extra ones.
Why it matters for a Shopify store running ads
Browser pixels lose events to ad blockers, cookie restrictions and pages that close before the script fires. Missing purchases mean Meta's algorithm learns from fewer conversions and under-reports results, which makes good campaigns look weak.
CAPI sends the event from your server, so it doesn't depend on the browser. Sending hashed customer details such as email improves match quality. For Shopify stores, CAPI is available through Meta's sales channel or third-party apps; the key is to check deduplication and the value being sent (with or without VAT).
Common mistakes
- Sending pixel and CAPI events without a shared event_id, which double-counts purchases.
- Sending a different purchase value from the server than from the browser.
- Assuming CAPI fixes attribution; it improves data completeness, not how credit is assigned.
FAQ
Do I still need the Meta pixel if I use CAPI?
Meta recommends using both. The pixel captures browser-side signals, CAPI fills the gaps from the server, and deduplication with a shared event_id prevents counting the same event twice.
Does CAPI work with Shopify?
Yes. You can connect it through Meta's Facebook & Instagram sales channel for Shopify or through third-party tracking apps. After setup, check in Events Manager that purchases are received from both sources and deduplicated.
Related terms
- Server-side trackingServer-side tracking is a setup in which conversion and behaviour events are sent to analytics and ad platforms from a server you control, rather than directly from the shopper's browser.
- Attribution windowAn attribution window is the period after someone clicks or views an ad during which an ad platform will credit a purchase to that ad, for example 7 days after a click or 1 day after a view.
- UTM parametersUTM parameters are tags added to the end of a link, such as utm_source and utm_campaign, that tell your analytics which source, medium, campaign and ad sent each visitor and order.
- ROASROAS (return on ad spend) is the revenue attributed to your ads divided by what those ads cost, so a ROAS of 3 means every $1 of ad spend brought in $3 of sales.
Want this number for your own store without a spreadsheet? ProfitFly connects Shopify, Meta and TikTok and shows your real profit every day, free up to 50 orders a month.
Start free