Meta Ads

Meta Conversions API: Why You Need It and How to Set It Up

9 March 2026 9 min read

If you're running Meta Ads in 2026 without the Conversions API, you're making decisions based on incomplete data. Browser-based tracking through the Meta Pixel has been degraded by iOS privacy changes, ad blockers, and browser restrictions — and the gap between what actually happens on your site and what Meta reports is growing wider every year.

The Conversions API (CAPI) sends conversion data directly from your server to Meta, bypassing browser limitations entirely. It's not a replacement for the pixel — it's a critical complement that ensures Meta's algorithm has the data it needs to optimise your campaigns effectively.

In this guide, we'll explain exactly what the Conversions API does, why it matters for your campaign performance, and how to set it up properly — whether you're using a partner integration or implementing it manually.

What the Conversions API Actually Does

The Meta Pixel works by placing JavaScript on your website that fires when someone takes an action — viewing a page, adding to cart, making a purchase. The problem is that this browser-side tracking is increasingly unreliable:

iOS App Tracking Transparency: A significant percentage of iOS users have opted out of tracking, meaning the pixel can't attribute their actions to your ads
Browser ad blockers: Third-party tracking scripts like the Meta Pixel are blocked by popular browser extensions
Cookie restrictions: Safari and Firefox limit third-party cookies, reducing the pixel's effectiveness
Page load issues: If a user navigates away before the pixel fires, the event is lost

The Conversions API solves this by sending the same event data from your server, which isn't affected by any of these client-side limitations. When you run both the pixel and CAPI simultaneously, Meta uses a deduplication process to ensure events aren't double-counted while capturing the maximum amount of data.

Why CAPI Matters for Campaign Performance

This isn't just a tracking technicality — it directly impacts how well your campaigns perform:

Better Optimisation Signals

Meta's ad delivery algorithm relies on conversion data to find more people likely to take valuable actions. If you're only sending 60–70% of your actual conversions via the pixel, the algorithm is optimising with incomplete information. CAPI fills in the gaps, giving the algorithm a more complete picture of who converts.

More Accurate Reporting

Without CAPI, your conversion tracking understates actual results. This means you might pause campaigns that are actually profitable, or misallocate budget away from your best-performing ad sets. Accurate data leads to better decisions.

Improved Audience Building

Custom audiences built from pixel events are incomplete if the pixel is missing conversions. CAPI ensures your website custom audiences and lookalike audiences are built from more complete data sets.

Future-Proofing

Browser-side tracking will continue to erode as privacy regulations tighten. Server-side tracking through CAPI is the direction the entire industry is moving, and getting it set up now ensures you're not scrambling when the next wave of restrictions hits.

Pro Tip: After implementing CAPI, most advertisers see a 15–30% increase in reported conversions — not because there are more actual conversions, but because they were always happening and simply weren't being tracked. This improved data typically leads to a measurable improvement in campaign efficiency within 2–4 weeks as the algorithm recalibrates.

How to Set Up the Conversions API

There are three main approaches to implementing CAPI, ranging from simple to complex:

Option 1: Partner Integration (Easiest)

If you're on a major e-commerce platform, you can enable CAPI through a native integration with minimal technical work:

Shopify: Shopify's native Facebook & Instagram channel supports CAPI out of the box. Simply connect your Meta Business account and enable data sharing in the channel settings. Set the data sharing level to "Maximum" to send the most comprehensive event data.
WooCommerce: Use Meta's official plugin for WooCommerce, which handles both pixel and CAPI setup
BigCommerce, Magento, WordPress: Meta has partner integrations available for most major platforms

Partner integrations handle deduplication automatically and require no coding. If you're on one of these platforms, this is the recommended approach for our Meta Ads management clients.

Option 2: Meta's Gateway Setup (Moderate)

Meta offers a Conversions API Gateway — a cloud-hosted solution that acts as an intermediary between your website and Meta's servers. It requires some technical configuration but doesn't need custom server-side code:

Set up through Events Manager in your Meta Business Suite
Hosted on your cloud infrastructure (AWS or Google Cloud)
Captures events at the server level and forwards them to Meta
Handles deduplication and data processing automatically

Option 3: Manual Server-Side Implementation (Most Control)

For businesses with custom websites or specific requirements, you can implement CAPI directly by sending events from your server via Meta's API:

Build server-side event tracking that fires when conversions occur in your backend
Send events using Meta's Graph API with the required parameters (event name, event time, user data, custom data)
Implement event deduplication by passing the same event ID in both pixel and CAPI events
Hash user data (email, phone, etc.) using SHA-256 before sending for privacy compliance

Event Deduplication: Getting It Right

When you're running both the pixel and CAPI (which you should be), deduplication prevents double-counting. Here's how it works:

Assign a unique event ID to each conversion event on the client side
Pass that same event ID in both the pixel event and the CAPI event
Meta matches events by event ID and event name, keeping only one record
If an event only comes through one channel (pixel or CAPI), it's counted as-is

Without proper deduplication, your conversion counts will be inflated, leading to inaccurate CPA and ROAS figures. This is the most common implementation mistake we see.

Testing Your Implementation

After setup, verify everything is working correctly:

Events Manager: Check the "Overview" tab to see events arriving from both Browser and Server sources
Test Events tool: Use Meta's Test Events feature to send test conversions and verify they're received
Event Match Quality score: Aim for a score of 6.0 or higher — this indicates you're sending enough user data parameters for effective matching
Deduplication rate: In Events Manager, check that deduplicated events roughly match your actual conversion volume

Improving Event Match Quality

Event Match Quality (EMQ) measures how effectively Meta can match your server events to Meta user profiles. A higher score means better attribution and optimisation. To improve your EMQ:

Send multiple user data parameters: Email, phone number, first name, last name, city, state, country, and zip code all help with matching
Hash all personal data: Use SHA-256 hashing before sending — Meta will reject unhashed personal data
Include the fbclid and fbc parameters: Pass the Facebook click ID from the URL and the fbc cookie for direct click attribution
Send the fbp parameter: The Facebook browser ID cookie helps match server events to pixel events
Use external IDs: Your internal user or order IDs help with cross-device matching

Pro Tip: The single biggest EMQ improvement comes from sending hashed email addresses with your CAPI events. If you can only send one user data parameter, make it email — it has the highest match rate because most people use the same email for their Meta account and online purchases.

Common CAPI Mistakes and How to Avoid Them

Implementing CAPI without the pixel: You should run both simultaneously. CAPI supplements the pixel, it doesn't replace it
Skipping deduplication: Always pass matching event IDs between pixel and CAPI events
Sending unhashed user data: This violates Meta's data processing terms and your events will be rejected
Not monitoring EMQ scores: Check your Event Match Quality monthly and work to improve scores below 6.0
Ignoring event delay: Server events should be sent within an hour of the actual event for optimal processing

CAPI and Your Retargeting Strategy

One of the biggest benefits of CAPI is improving your retargeting audiences. With more complete data flowing in, your website custom audiences grow larger and more accurate. This means your retargeting campaigns reach more of the people who actually visited your site, leading to better performance and more conversions.

Frequently Asked Questions

Is the Conversions API free to use?

The API itself is free — Meta doesn't charge for sending events via CAPI. However, there may be costs associated with the infrastructure needed to send server-side events. Partner integrations (Shopify, WooCommerce) include CAPI at no extra cost. The Gateway solution requires cloud hosting (typically £20–50/month). Manual implementations require development time but no ongoing Meta fees.

Will CAPI fix my iOS tracking issues completely?

CAPI significantly improves tracking for iOS users who opted out of app tracking, but it doesn't achieve 100% recovery. Server-side events can match users based on hashed email, phone, or other identifiers — but only if that data is available at the time of conversion. For anonymous browsing sessions where no identifiable data is collected, tracking gaps remain. Expect to recover 50–80% of previously lost iOS conversions with a well-implemented CAPI setup.

Do I still need the Meta Pixel if I have CAPI?

Yes, absolutely. The pixel and CAPI work together as complementary tracking systems. The pixel handles real-time browser events efficiently and provides the fbp and fbc parameters that improve CAPI's matching accuracy. CAPI catches events the pixel misses. Running both with proper deduplication gives you the most complete data possible.

How long does it take to see results after implementing CAPI?

You'll see improved reporting data almost immediately as more events flow in. The performance improvements from better optimisation signals typically take 2–4 weeks to materialise as Meta's algorithm adjusts to the richer data. Most advertisers see meaningful improvements in CPA and ROAS within the first month after proper CAPI implementation.

Implementing the Conversions API is one of the highest-impact, lowest-effort improvements you can make to your Meta Ads setup. At Spires Digital, CAPI implementation is included in our onboarding process for every Meta Ads management client, ensuring your campaigns are built on a foundation of accurate, complete data from day one. Book a call through our Calendly link to discuss your tracking setup and how we can help you close the data gap.