Detailed definition
The Pixel collects data in the browser (cookie-based); since iOS 14.5, App Tracking Transparency (ATT) and cookie restrictions can leave gaps in that measurement, and how much is lost varies by site and audience. CAPI sends conversion events from the server, which reduces the effect of browser restrictions; user consent and good event matching are still required. Set-up routes include Stape, server-side Google Tag Manager and Shopify's Meta integration. When the Pixel and CAPI run together, deduplication (event_id) is essential so the same event is not counted twice.
Examples
- A purchase blocked in the browser may not appear in the Pixel; when the same event is passed from the server to Meta via CAPI, it can be included in measurement.
Related terms
Would you like support with this?
If you would like to discuss how CAPI (Conversions API) applies to your business, we can arrange a short initial call. The first 30-minute call is free.
Book a free initial call → +90 543 930 12 72