The Meta pixel runs in the shopper’s browser, where ad blockers, browser privacy features and pages that fail to load can stop it from firing. The Conversions API sends the same events from a server instead, so Meta receives more complete conversion data. Customer details such as email and phone number are hashed before sending and help Meta match events to people.
Meta recommends running the pixel and CAPI together. To avoid counting the same purchase twice, each event sent through both channels carries the same event name and event ID, and Meta keeps one copy of matching events received within 48 hours. Other ad platforms offer similar server-side connections, such as TikTok’s Events API.
Why it matters for eCommerce
Meta’s bidding learns from the conversions it receives. When purchases go missing, campaigns look less efficient than they are and optimize on less data. A complete, deduplicated event stream gives the algorithm better signals and gives you more trustworthy reporting.
How it works in practice
- On Shopify, the Facebook & Instagram app’s Enhanced and Maximum data-sharing levels use the Conversions API. The Standard level uses the pixel only.
- For custom or headless stores, send events through server-side Google Tag Manager or a partner integration.
- Check Events Manager for event match quality and deduplication warnings after launch.
- Send only the events each visitor’s consent allows.
Common mistakes
- Sending events through both the pixel and CAPI without shared event IDs, which inflates reported conversions.
- Treating CAPI as a way around consent. Server-side events still need a lawful basis.
- Passing order values before discounts or refunds, so value-based bidding chases inflated revenue.