In 2021, Apple's iOS 14 update changed everything for Meta advertisers. App Tracking Transparency (ATT) meant millions of iPhone users could opt out of cross-app tracking — and most did. The result: Meta lost visibility into a significant portion of purchase events, causing reported ROAS to drop and making optimisation harder. Four years later, the fix is clear: dual-firing Pixel and CAPI together.
What is the Meta Pixel?
The Meta Pixel is a piece of JavaScript code installed on your website. When someone visits your site, adds to cart, or completes a purchase, the Pixel fires an event back to Meta. This data is what Meta uses to optimise your campaigns and report conversions. The problem: it relies on browser-based tracking, which iOS 14+ partially blocks.
What is the Conversions API (CAPI)?
The Conversions API is a server-side tracking solution. Instead of tracking from the browser (which can be blocked), CAPI sends event data directly from your server to Meta. It's not affected by iOS restrictions, browser privacy settings, or ad blockers. It sees conversions the Pixel misses.
Why You Need Both — Dual-Firing
Neither solution alone is complete. Pixel tracking is browser-based and gets blocked. CAPI-only misses some browser events. Running both simultaneously — dual-firing — gives you maximum coverage. Every purchase gets captured from at least one source, giving Meta the most complete data possible to optimise your campaigns.
Impact of dual-firing: Brands that implement Pixel + CAPI dual-firing typically see 15–30% more reported conversions compared to Pixel-only setups. Better data = better algorithm optimisation = better ROAS.
How to Set Up CAPI
The setup method depends on your e-commerce platform:
- Shopify: Meta's native Shopify integration handles CAPI automatically. Enable it in your Facebook channel settings.
- WooCommerce: Use the official Meta Pixel plugin with CAPI support, or implement via Google Tag Manager with server-side container.
- Custom platforms: Requires developer implementation via Meta's Conversions API directly.
Event Match Quality — Why It Matters
CAPI's effectiveness depends on how well your customer data matches Meta's records. The more customer information you pass with each event (email, phone, name, city), the higher your Event Match Quality score — and the more accurately Meta attributes conversions to your ads. Always pass as many customer parameters as legally permissible under your privacy policy.
Deduplication — Avoiding Double-Counting
When running Pixel and CAPI together, the same purchase event may be sent twice — once from the browser, once from the server. Meta deduplicates these using an event ID. Make sure your implementation passes the same event ID from both sources so Meta counts each purchase once.
Is Your Meta Tracking Losing Conversions?
We audit tracking setups for D2C brands and implement dual-firing Pixel + CAPI correctly. Get a free tracking audit.
Get a Free Tracking AuditThe Bottom Line
If you're running Meta Ads without CAPI, you're flying partially blind. You're missing purchase data, your algorithm is under-optimised, and your reported ROAS is likely lower than reality. Implementing Pixel + CAPI dual-firing is one of the highest-leverage technical changes a D2C brand can make — and it doesn't require changing a single campaign.