How to Set Up Facebook Conversion API: Step-by-Step Guide

Last updated: March 2026 | Reading time: 12 minutes

If you’re running Facebook Ads in 2026 and still relying only on the Facebook Pixel, you’re flying blind. Between iOS privacy updates, browser tracking restrictions, and ad blockers, the Pixel alone misses 20–35% of conversion events. That’s money you’re spending with no data to show for it.

The Facebook Conversion API (CAPI) fixes this by sending conversion data directly from your server to Meta — bypassing browsers entirely. It’s not optional anymore. It’s the baseline for any serious advertiser.

This guide walks you through exactly how to set up Facebook Conversion API, whether you’re on Shopify, WordPress, or a custom stack.

What Is the Facebook Conversion API?

The Facebook Conversion API is a server-side tracking tool that sends web events (purchases, leads, add-to-carts) directly from your server to Meta’s servers. Unlike the Pixel, which runs in the visitor’s browser, CAPI operates independently of cookies, ad blockers, or browser privacy settings.

Think of it this way: the Pixel watches what happens in the browser. CAPI reports what actually happened on your server. When you run both together, Meta gets a more complete picture of your funnel — and your campaigns optimize faster.

Why CAPI Matters in 2026

Three things have changed the tracking landscape permanently:

iOS 14.5+ and App Tracking Transparency. Apple’s ATT framework lets users opt out of cross-app tracking. Over 80% of iOS users have opted out. Without CAPI, you lose most of your iOS conversion data.

Browser privacy features. Safari’s Intelligent Tracking Prevention, Firefox’s Enhanced Tracking Protection, and Chrome’s phase-out of third-party cookies all limit how long the Pixel cookie survives. First-party cookies set by the Pixel now expire in 7 days on Safari — meaning any conversion that happens after a week is invisible.

Ad blockers. Roughly 30% of desktop users run ad blockers that prevent the Pixel from firing at all. CAPI bypasses this completely since the data never touches the browser.

Meta’s Andromeda algorithm. The biggest reason CAPI matters in 2026 isn’t just privacy — it’s performance. Meta’s Andromeda update uses machine learning that’s 10,000x more powerful than its predecessor. But machine learning is only as good as the data it receives. If your tracking sends incomplete or inaccurate conversion signals, Andromeda optimizes on bad data. CAPI ensures Meta gets the cleanest, most complete conversion data possible — which directly translates to better ad performance and lower CPAs.

The advertisers seeing the best results post-Andromeda are the ones with clean tracking stacks. We’ve seen clients reduce cost per acquisition by 30–45% simply by fixing their CAPI implementation — before making any changes to creative or targeting. The algorithm can only optimize what it can measure.

How CAPI and the Pixel Work Together

The Facebook Pixel fires in the user’s browser — it tracks page views, button clicks, and conversions through JavaScript. This works well on desktop Chrome but breaks down when browsers block third-party cookies, ad blockers strip tracking scripts, or users browse in private/incognito mode.

CAPI bypasses all of these limitations. It sends event data directly from your server to Meta’s servers, completely independent of the browser. When a customer completes a purchase on your site, your server sends that event to Meta’s API with the customer’s hashed email and phone number. Meta matches it to a Facebook user and attributes the conversion — regardless of what the browser allowed or blocked.

Running both simultaneously gives you redundant tracking. If the Pixel misses an event (blocked by Safari ITP, for example), CAPI catches it. If CAPI has a server delay, the Pixel captures it in real time. Meta deduplicates the overlapping events automatically using event IDs, so you get the most complete and accurate conversion data possible.

Before You Start: What You Need

Before setting up CAPI, make sure you have a Facebook Business Manager account with admin access, a Facebook Pixel already installed on your site (CAPI works alongside the Pixel, not instead of it), an Events Manager access token (we’ll generate this during setup), and admin access to your website’s backend or hosting.

Method 1: Shopify (Easiest — 10 Minutes)

Shopify has native CAPI integration built in. If you’re on Shopify, this is the fastest route.

Step 1: Go to your Shopify admin → Settings → Customer events.

Step 2: Connect your Meta account. Click “Add custom pixel” or find the Facebook & Instagram sales channel.

Step 3: In the Facebook & Instagram app, go to Settings → Data sharing. Set the data sharing level to “Maximum.” This enables both the Pixel and CAPI simultaneously.

Step 4: Verify in Events Manager. Go to Meta Events Manager → select your Pixel → click “Test Events.” You should see events coming through both “Browser” and “Server” channels.

Shopify Troubleshooting

If CAPI events aren’t showing up: your Facebook & Instagram app may need updating; data sharing must be “Maximum” not “Standard”; and complete domain verification in Facebook Business Manager.

Method 2: WordPress / WooCommerce

For WordPress sites, you have two options: a plugin-based setup or server-side Google Tag Manager.

Option A: Plugin Setup (Recommended)

Step 1: Generate a CAPI access token in Meta Events Manager → Pixel → Settings → Conversions API.

Step 2: Install PixelYourSite or Facebook for WordPress plugin. Enter your Pixel ID and CAPI access token.

Step 3: Enable server-side events for PageView, ViewContent, AddToCart, InitiateCheckout, Purchase, and Lead.

Step 4: Enable event deduplication. Verify in Events Manager that each event shows as “Browser and Server” not counted twice.

Option B: Server-Side Google Tag Manager

This is the approach we use for most clients at Adverge Media because it gives full control over what data gets sent and when. Set up a server-side GTM container on Google Cloud or AWS, create a Facebook CAPI tag using Meta’s official template, map your events, and pass hashed user data to improve Event Match Quality.

Event Match Quality: The Metric That Matters

Your EMQ score (1–10) tells you how well Meta can match server events to Facebook users. Sending hashed emails has the biggest impact. Include fbp and fbc parameters, client IP address, and user agent. Target: EMQ of 6.0 or higher. Most well-configured setups land between 7–9.

An EMQ of 6.0 or above is the target. Below that, Meta can’t reliably match your conversion events to the users who triggered them, which means the algorithm is partially blind when optimizing your campaigns. We’ve seen accounts jump from EMQ 4.2 to EMQ 8.5 just by passing additional customer parameters — and campaign performance improved within 48 hours.

The parameters that have the biggest impact on EMQ, in order of importance: email address (hashed), phone number (hashed with country code), first and last name, city and state, zip code, and external ID. You don’t need all of them, but sending at least email + phone + name typically gets you above 7.0. For e-commerce stores, the checkout and purchase events usually have all this data available — make sure your CAPI setup passes it.

You can check your EMQ score in Meta Events Manager → select your Pixel → click on any event → look for the Event Match Quality indicator. Meta shows you exactly which parameters you’re sending and which ones are missing. Use this as your checklist for improving match quality.

Deduplication: Don’t Skip This

Both your Pixel event and CAPI event must include an identical event_id for the same action. When Meta sees two events with the same event_id, it keeps one and discards the duplicate.

Without deduplication, your conversion count inflates, your CPA looks artificially low, and Meta’s algorithm optimizes on garbage data. We’ve seen accounts where reported conversions were 40% higher than actual — all because deduplication wasn’t configured.

Testing Your CAPI Setup

Before you trust your data, run these checks: use Meta’s Test Events tool to confirm events appear with “Server” as a connection method. After 24–48 hours, check Events Overview — each event should show both “Browser” and “Server” contributions. Verify your EMQ score is 6 or higher. And watch for duplicate events — if conversions doubled after enabling CAPI, deduplication isn’t working.

Advanced CAPI Configuration

Once your basic CAPI setup is working, there are several optimizations that separate good tracking from great tracking. These aren’t required for a functional setup, but they can significantly improve your data quality and campaign performance.

Custom events and custom parameters. Beyond standard events (Purchase, Lead, AddToCart), you can send custom events that match your specific funnel. For SaaS businesses, events like TrialStarted, PlanUpgraded, or FeatureActivated give Meta more granular signals. For service businesses, events like AppointmentBooked or QuoteRequested help the algorithm find people who take meaningful actions — not just page viewers.

Value-based optimization. If you’re passing purchase values through CAPI, you can optimize campaigns for value rather than volume. This tells Meta’s algorithm to find customers who spend more, not just customers who buy. For e-commerce brands with a wide AOV range, this is a game-changer — we’ve seen clients shift their average order value up 15–25% by switching from purchase-count optimization to value optimization.

Offline conversions. For businesses with an offline sales component — phone calls that lead to sales, in-store visits, consultations that close later — CAPI supports offline event uploads. You can send conversion data back to Meta days or weeks after the initial ad click, giving the algorithm a complete picture of which ads actually drive revenue. This is particularly powerful for high-ticket services like solar, dental, and real estate.

Multi-domain tracking. If your funnel spans multiple domains (landing page on one domain, checkout on another), CAPI handles this better than browser-side Pixel alone. Server-side events aren’t affected by cross-domain cookie restrictions, so your attribution stays intact even when users move between domains during the purchase process.

Common Mistakes to Avoid

Disabling the Pixel after enabling CAPI. They work together — the Pixel captures events CAPI might miss and vice versa. Not hashing user data. Meta requires SHA-256 hashing for personal data before sending. Ignoring Event Match Quality. If your EMQ is below 6, the data isn’t useful for optimization. Using test data in production. Remove the test_event_code parameter before going live.

Forgetting to test after platform updates. Shopify, WordPress, and Meta all push regular updates that can break CAPI connections. Every time you update your e-commerce platform, CMS, or tracking plugins, re-test your CAPI events. Set a monthly calendar reminder to check Events Manager and verify that server-side events are still flowing correctly. One broken update can silently kill your tracking for weeks.

Not passing enough customer parameters. CAPI works best when you send hashed customer data — email, phone, name, address — along with your events. Many setups only pass the event name and value, which gives you a low Event Match Quality score and limits Meta’s ability to attribute conversions. Check your EMQ for every event type and add missing parameters.

Ignoring the Diagnostics tab. Meta Events Manager has a Diagnostics section that flags issues with your event setup in real time — duplicate events, missing parameters, configuration errors, and data freshness problems. Checking this weekly takes 2 minutes and prevents small issues from becoming big performance problems.

Setting up CAPI only for Purchase events. Many advertisers configure CAPI for purchases only, ignoring upper-funnel events like ViewContent, AddToCart, and InitiateCheckout. Meta’s algorithm uses the entire funnel to build audience models and optimize delivery. Sending only purchase events starves the algorithm of the behavioral data it needs to find your best prospects.

When to Hire an Expert

CAPI setup ranges from straightforward (Shopify) to complex (custom GTM server-side + API). If you’re running $5K+/month in ad spend and need server-side GTM, have a custom checkout, or your EMQ is stuck below 6 — it’s worth bringing in a specialist.

At Adverge Media, we handle CAPI implementation as part of our full tracking infrastructure — Pixel configuration, server-side GTM, and GA4 integration. If your tracking isn’t right, your campaigns can’t optimize properly.

Frequently Asked Questions

Does CAPI replace the Facebook Pixel? No. CAPI and the Pixel work together — they’re complementary, not competing systems. The Pixel captures browser-side events; CAPI captures server-side events. Running both gives Meta the most complete data and the best event matching. Disabling the Pixel after setting up CAPI is a common mistake that actually hurts performance.

Will CAPI fix my iOS tracking issues? CAPI significantly improves tracking for iOS users who opted out of App Tracking Transparency. While it can’t override Apple’s privacy choices, server-side events bypass many of the browser restrictions that limit Pixel tracking. Most advertisers see a 20–40% improvement in reported conversions after implementing CAPI correctly.

How much does CAPI setup cost? Shopify CAPI is free — it’s built into the platform. WordPress plugin-based setups typically cost $0–$100/year for a premium plugin license. Server-side GTM requires a cloud server (Google Cloud, AWS, or Stape.io), which runs $10–$50/month depending on traffic volume. Professional setup from an agency or consultant typically costs $500–$2,000 as a one-time project, depending on complexity.

How do I know if CAPI is working correctly? Check three things in Meta Events Manager: 1) Events show ‘Browser and Server’ as the connection method, not just ‘Browser.’ 2) Your Event Match Quality score is 6.0 or above. 3) Deduplication is working — your total event count shouldn’t roughly double after enabling CAPI. Use the Test Events tool to send live test conversions and verify they appear with server-side attribution.

Related Reading

If you’re evaluating whether to manage Facebook Ads in-house or hire an agency to handle CAPI and campaign management together, read our complete guide to hiring a Facebook Ads agency in 2026.

For a deeper understanding of how Meta’s algorithm changes affect your ad performance and tracking strategy, see Facebook Ads After Andromeda: What Changed and How to Win in 2026.

And if you’re deciding where to allocate your ad budget alongside CAPI improvements, our Facebook Ads vs Google Ads comparison breaks down which platform fits your business.

Running Facebook Ads for a medspa or aesthetic practice? Our Facebook Ads for medspas guide covers how CAPI fits into the medspa tracking stack alongside call tracking and offline conversions.

Ready to Fix Your Tracking?

If your Facebook Ads data feels unreliable — conversions don’t match actual sales, ROAS looks inconsistent, or you’re not sure your tracking captures everything — the problem is almost always a Pixel-only setup without CAPI.

Book a free 15-minute audit call and we’ll review your current tracking setup, identify what’s missing, and give you a clear action plan.