Facebook Pixel has been the backbone of Meta ad tracking since 2015. But in 2026, Pixel alone is no longer enough. iOS 14+ App Tracking Transparency, browser restrictions on third-party cookies, and ITP (Intelligent Tracking Prevention) in Safari have reduced Pixel accuracy by 30 to 50% for many advertisers (Meta Business Help Center, 2025). The solution is Conversions API (CAPI) — server-side tracking that sends conversion data directly from your server to Meta. This guide shows you how to implement both and why you need both.
What Meta Pixel is and how it works
Meta Pixel (formerly Facebook Pixel) is a JavaScript code snippet you install on your website. When a user visits a page, the browser loads the pixel, and it sends data back to Meta about the user's actions — page views, button clicks, form submissions, purchases, and other events.
Pixel data is used for three purposes: conversion tracking (measuring ad results), audience building (creating custom audiences based on website behavior), and ad optimization (giving Meta's algorithm conversion signals so it can find more users likely to convert).
The pixel works by setting a cookie in the user's browser and matching it with Meta profiles. The problem is that this client-side approach is vulnerable to cookie restrictions, ad blockers, and browser privacy settings. For a comprehensive understanding of Meta advertising, see our Meta Ads guide.
Pixel installation methods
There are three main methods for installing Meta Pixel: direct code installation, Google Tag Manager (GTM), and CMS plugins. Choice of method depends on technical expertise and platform.
Direct code installation gives full control. Add the Pixel base code in the head tag on all pages, then add event code on relevant pages. GTM installation is the most flexible method for most businesses — you add the Pixel via a GTM tag and can easily manage events without editing website code directly.
CMS plugins (Shopify, WooCommerce, WordPress, etc.) provide the easiest installation but least control. Most plugins now also support Conversions API integration. For Shopify, Meta's official Facebook channel is the recommended method, and it configures both Pixel and CAPI automatically.
Standard events, custom events, and custom conversions
Meta has defined 17 standard events covering the most common actions: PageView, ViewContent, AddToCart, InitiateCheckout, Purchase, Lead, CompleteRegistration, Contact, Search, and more. Standard events give Meta the most data to optimize against because they are predefined and used across millions of advertisers.
Custom events are used for actions not covered by standard events. You define the event name yourself, for example "BookingComplete" or "QuoteRequested." Custom events can be used for audiences but have limited support for ad optimization compared to standard events. Custom conversions let you create conversion rules based on URL or event parameters without changing code.
The recommendation is to use standard events wherever possible. Even if "Lead" is not a perfect description of your conversion, it is better to use "Lead" than a custom event because Meta optimizes more effectively against standard events. Use custom events only for actions that truly have no standard event counterpart.
- PageView: Automatic on all pages with Pixel installed
- ViewContent: When user views a product or service page
- AddToCart: When user adds to cart
- InitiateCheckout: When user starts checkout
- Purchase: When purchase is completed (with value)
- Lead: When user submits a form or requests contact
The iOS 14+ problem and why Pixel alone is not enough
In April 2021, Apple rolled out App Tracking Transparency (ATT) with iOS 14.5. Users now had to give explicit consent to tracking across apps and websites. The results were dramatic: According to Flurry Analytics (2022), only 25% of iOS users chose to allow tracking. In 2026, this has stabilized at around 30% opt-in globally.
The consequences for Meta advertising are significant: Conversion tracking became inaccurate (up to 50% underreporting for iOS users), remarketing audiences shrank, and Meta's optimization algorithm received fewer signals to work with. Additionally, Safari ITP limits cookies to 7-day lifetime, Firefox blocks third-party cookies by default, and Chrome is planning restrictions in Privacy Sandbox.
Meta itself reports that advertisers using only Pixel (without CAPI) in 2026 can lose up to 40% of their conversion data (Meta Business Help Center, 2025). Conversions API is Meta's answer to these challenges — and it is no longer optional for serious advertising.
What Conversions API is and why it is essential
Conversions API (CAPI) sends conversion data from your server directly to Meta's servers — without going through the user's browser. This means CAPI is not affected by cookie restrictions, ad blockers, or iOS ATT settings.
Technically, it works like this: When a conversion occurs (for example a purchase transaction), your server sends an API request to Meta's Conversions API endpoint with event data (event type, user data such as email and phone, and transaction data). Meta matches this data with Meta profiles using hashed user information.
CAPI does not replace Pixel — the two work together. Pixel captures data client-side (in the browser), CAPI captures data server-side. Both are sent to Meta, which deduplicates the events to avoid double counting. This redundant approach ensures you capture maximum conversion data regardless of the user's privacy settings. Also read our GA4 guide for cross-platform tracking setup.
CAPI implementation methods
There are three main methods for implementing CAPI: direct API integration, GTM server-side tagging, and partner integrations.
Direct API integration gives the most control and flexibility. You write code that sends POST requests to Meta's API on conversion events. This requires developer resources but provides the best data quality and most flexibility for customization. GTM server-side tagging is a good alternative for businesses already using GTM. You set up a server-side GTM container (typically hosted in Google Cloud) and configure a Facebook CAPI tag that sends data directly from the server.
Partner integrations are the easiest method for CMS users. Shopify, WooCommerce, Magento, and other platforms have built-in CAPI integrations. For Shopify: Go to Sales Channels, select Facebook, and activate CAPI under Data Sharing Settings. Select Maximum data sharing to activate both Pixel and CAPI. For most businesses without their own development department, partner integrations are the most cost-effective choice.
Event Match Quality (EMQ) and optimization
Event Match Quality (EMQ) is a 1 to 10 scale showing how well Meta can match server-side events with Meta profiles. Higher EMQ means more conversions can be attributed to specific users, which improves reporting and optimization.
EMQ is primarily affected by the quality of user data you send with CAPI events. The more identifiers you include, the better the match. Meta recommends sending: email address (hashed), phone number (hashed), first name and last name (hashed), city, postal code, country, external ID, and client IP address.
For most e-commerce businesses sending email, phone, and name with Purchase events, EMQ typically falls between 6 and 8. For Lead events with only email, EMQ may be 3 to 5. Check EMQ in Events Manager under Diagnostics and then Event Match Quality. Focus on improving EMQ for your most important conversion events first.
- EMQ 1-3: Poor — likely missing user data in the CAPI call
- EMQ 4-6: Average — improvement potential by sending more identifiers
- EMQ 7-8: Good — most events matched with Meta profiles
- EMQ 9-10: Excellent — optimal data quality
Deduplication between Pixel and CAPI
When you use both Pixel and CAPI, you send the same event twice — once from the browser (Pixel) and once from the server (CAPI). Without deduplication, Meta will count each event double, which destroys reporting.
Deduplication works by sending the same event_id with both events. When Meta receives two events with the same event_name and event_id, it keeps the one that arrived first and discards the duplicate. Implementation requires generating a unique ID (for example a UUID) for each event and sending it with both the Pixel call and the CAPI call.
Typical implementation errors include: Not sending event_id at all (results in double counting), using a fixed ID instead of a unique ID per event (results in only the first event being registered), and sending different event_names in Pixel and CAPI (Meta is case-sensitive on event names).
Aggregated Event Measurement and testing
Aggregated Event Measurement (AEM) is Meta's framework for respecting iOS ATT restrictions while still enabling conversion tracking. Under AEM, you can prioritize up to 8 conversion events per domain, ranked by importance.
Choose and rank your 8 events carefully: Purchase should typically be number 1, then Lead or CompleteRegistration, InitiateCheckout, AddToCart, and ViewContent. The order means that if a user completes multiple events, Meta reports only the highest-ranked event for ad optimization for iOS users.
For testing and debugging, use two tools in Events Manager: the Test Events tool and the Diagnostics tab. Test Events lets you send test events and verify they register correctly. Diagnostics shows errors, warnings, and suggestions for improvement. Check Diagnostics weekly to catch issues early. Our glossary defines pixel, conversion tracking, and server-side tracking.
Common setup mistakes
Mistake 1: Implementing only Pixel without CAPI. You lose 30 to 50% of conversion data. Mistake 2: Implementing CAPI without deduplication. You double-count all conversions. Both mistakes produce completely wrong reporting and destroy ad optimization.
Mistake 3: Sending too little user data with CAPI. Without email, phone, or name, the EMQ is so low that CAPI barely provides value. Mistake 4: Not verifying the domain in Business Manager. Domain verification is required for AEM and affects which events you can optimize against.
Mistake 5: Using ViewContent as the primary optimization event. ViewContent is too far up the funnel — Meta finds users who view pages, not users who buy. Optimize against Purchase or Lead for best results. Mistake 6: Not testing after implementation. Use Meta Pixel Helper (Chrome extension) and Events Manager Test Events to verify everything works. Visit our PPC services page for help with tracking setup.
Sources and further reading
This article draws on the following sources:
- Meta Business Help Center — Conversions API Documentation (2025)
- Meta — Event Match Quality Best Practices (2025)
- Flurry Analytics — iOS ATT Opt-In Rates Report (2022, updated 2025)
- Meta — Aggregated Event Measurement Framework (2025)
- Google — Server-Side GTM with Facebook CAPI Setup Guide (2025)
