The Complete Meta Pixel & CAPI Setup Guide for 2025
iOS changes killed the basic Meta Pixel. Here's how to set up Conversions API alongside your Pixel to recover lost signal and improve campaign performance.
The Meta Pixel was once the backbone of Facebook and Instagram advertising. Then Apple introduced App Tracking Transparency in iOS 14.5, and everything changed. Cookie-based tracking became unreliable. Conversions disappeared from the platform. ROAS calculations became guesswork.
The answer isn't to abandon Meta advertising, it's to upgrade your tracking infrastructure. Here's how to set up both the Meta Pixel and Conversions API (CAPI) correctly for 2025.
Why the Pixel Alone Is No Longer Enough
The standard Meta Pixel fires from the user's browser. When a user has iOS privacy restrictions, an ad blocker, or a privacy-focused browser, the Pixel signal is either blocked or degraded. Studies suggest that in privacy-regulated markets, client-side Pixel tracking underreports conversions by 30–60%. You're bidding blind.
What Is the Conversions API?
The Conversions API (CAPI) sends conversion data directly from your server to Meta, bypassing the browser entirely. This means no ad blockers, no iOS limitations, and significantly more complete data. When combined with the browser Pixel (using event deduplication to prevent double-counting), you get the most complete picture of your campaign performance possible.
Setting Up the Meta Pixel
1. Create Your Pixel in Meta Events Manager
Go to Meta Business Suite → Events Manager → Connect Data Sources → Web. Create a new Pixel and give it a clear name tied to your business. Never share one Pixel across multiple unrelated businesses or domains.
2. Install via Google Tag Manager
Use the Meta Pixel base code as a Custom HTML tag in GTM, firing on All Pages. Then create individual GTM triggers for each key conversion event: lead form submissions, purchases, book-a-call completions. This keeps your Pixel setup modular and auditable.
3. Enable Advanced Matching
Advanced Matching sends hashed customer data (email, phone, name) alongside conversion events. This dramatically improves match rates, often by 20–40%, and helps Meta attribute conversions that the Pixel would otherwise miss. Enable it in your Pixel settings and pass available customer data at the point of conversion.
Setting Up Conversions API
Option A: Partner Integration (Fastest)
If you're on Shopify, WooCommerce, or another supported platform, Meta has native CAPI integrations. These are the fastest to implement and handle deduplication automatically.
Option B: Gateway via GTM Server-Side (Recommended)
For custom setups, implement CAPI through a server-side GTM container. This gives you full control, works across any platform, and allows you to enrich events with first-party data before sending to Meta. It requires more technical setup but is the most robust long-term solution.
Deduplication: The Critical Step Most Businesses Skip
When running both Pixel and CAPI, the same conversion will be detected by both. Without deduplication, Meta will count it twice, inflating your conversion numbers and distorting your optimisation signals. Always pass matching event_id values from both the browser Pixel and CAPI for the same event. Meta uses this to deduplicate correctly.
Verify in Events Manager
After setup, use Meta's Test Events tool in Events Manager to confirm events are firing correctly from both browser and server. Check the Event Match Quality score, aim for 7.0 or above. Lower scores indicate gaps in your customer data matching that will hurt your campaign performance.
