A complete guide to setting up Facebook Conversions API in 2026 for server-side tracking, covering Shopify, WordPress, and Google Tag Manager methods, plus how to improve your Event Match Quality score.
If you're relying only on the Meta Pixel to track conversions, you're missing data, and not a small amount of it. Browser-based tracking alone no longer captures enough conversions for Meta's algorithm to optimize properly, since a purchase event fired from a customer's browser can be blocked by iOS privacy rules, ad blockers, or cookie consent restrictions before it ever reaches Meta. The Conversions API, commonly called CAPI, fixes this by sending the same event data directly from your server instead of relying on the browser alone.
Think of the Pixel and CAPI as two separate paths carrying the same information to Meta. The Pixel fires from the customer's browser at the moment of an action, add to cart, purchase, form submission. CAPI sends that same event from your own server, independent of whatever privacy restriction or blocker might be interfering with the browser-based version. Meta recommends running both simultaneously, using a shared event ID to deduplicate any event that both paths successfully deliver, so you get maximum coverage without double-counting.
The real-world impact is measurable. Industry reporting consistently cites CAPI recovering roughly 15 to 35 percent of conversion data that Pixel-only tracking misses, particularly on iOS traffic, which has been the hardest-hit segment since Apple's 2021 tracking changes.
CAPI supplements your Pixel, it doesn't replace it. Before setting up server-side tracking, confirm your Pixel is already installed and firing correctly using the Test Events tool in Events Manager. If your browser-based tracking isn't solid, adding a server-side layer on top of a broken foundation just compounds the confusion when you're trying to diagnose data problems later.
Which path makes sense depends heavily on your platform and technical comfort level.
In your Shopify admin, go to Settings, then Apps and Sales Channels, and open the Facebook and Instagram sales channel. Inside its settings, find the Facebook Conversion API section and set tracking to "Maximum," which sends both browser-side Pixel events and server-side CAPI events together with automatic deduplication. This is the fastest path to a working setup, typically under 30 minutes, and Shopify handles most of the technical complexity for you.
Install the official Facebook for WooCommerce plugin, which includes native CAPI support. In the plugin's settings, locate the Conversion API section, generate or enter your access token from Events Manager, and enable server-side tracking alongside your existing Pixel.
For businesses wanting more control over exactly what data gets sent, a server-side GTM container is a more advanced but more flexible path. This involves creating a server-side container separate from your standard web container, adding a Meta CAPI tag inside it, and configuring triggers that define when each event should fire. This method is worth considering once your tracking needs outgrow what a partner integration's predefined events can handle, custom events or specific customer data points partner integrations don't support by default.
Once CAPI is sending data, Meta assigns an Event Match Quality score, a 1 to 10 rating showing how well your server events can be matched to actual Facebook user accounts. A higher score means better attribution and stronger optimization signals for your campaigns. To improve this score, send as many matching parameters as your platform allows: email, phone number, first-party browser identifiers (fbp and fbc), IP address, and user agent. In Events Manager, go to your Pixel's Settings, then Advanced Matching, and enable all available automatic matching options.
In Events Manager, select your Pixel and open the Test Events tool. Trigger a real test action on your site, an add to cart, a purchase. You should see the same event appear as both a browser event and a server event, correctly matched together rather than counted twice. If Meta shows the event names differing between the browser and server versions, standardize them, since mismatched event names prevent proper deduplication and inflate your reported conversion counts.
Yes. Meta explicitly recommends running both together. The Pixel and CAPI cover different failure modes, and deduplication via a shared event ID means running both doesn't inflate your numbers, it closes the gaps either method misses on its own.
Setting up CAPI itself is free through Meta. Partner integrations like Shopify's native Facebook and Instagram channel are included at no extra cost. More advanced server-side GTM setups may involve hosting costs for the server container, depending on your traffic volume and hosting provider.
Watch your Event Match Quality score in Events Manager, since it directly reflects how well your setup is performing, and compare your reported conversion volume before and after implementation. A meaningful increase in matched conversions, particularly from iOS traffic, indicates the server-side layer is genuinely recovering data your Pixel alone was missing.
With browser and server-side tracking both in place, the next infrastructure piece worth adding is Google Tag Manager, which gives you one central place to manage every tracking tag rather than editing each platform's settings separately. This connects to our guide on setting up the Meta Pixel and our broader tracking verification guide. If you'd rather have your full ad tracking stack set up and verified by someone who does this daily, that's exactly what our paid media team handles as part of a free Growth Gap Analysis.
How We Work
