The Meta Conversions API is a way for your website, app or CRM to send customer actions, such as leads and purchases, directly from your server to Meta, instead of relying only on the browser-based Pixel. It matters because browsers, ad blockers and privacy settings can stop the Pixel from reporting some events, which leaves Meta with an incomplete view of your results and weakens optimisation. This guide explains how the Conversions API works, how it differs from the Pixel, the main ways to set it up for Shopify, WordPress and custom sites, how deduplication prevents double counting, and how to check data quality.
What is the Meta Conversions API?
The Conversions API, often shortened to CAPI, lets your server send events to Meta using a direct connection. An event might be a lead form submission, a purchase, or a stage in your CRM such as 'qualified'. Each event can carry details like the event name, time, a hashed email or phone number, a browser ID and, for purchases, the value and currency.
Meta uses these signals to attribute conversions to ads and to train its delivery system on who is likely to convert. Because the data comes from your server, it is less affected by browser restrictions. It does not replace consent or privacy rules; you still need to collect and use customer data lawfully, and describe it in your privacy policy.
In practice, this means that a lead who fills your form after seeing an Instagram ad on their phone can still be reported to Meta even if the browser blocked the Pixel. For advertisers in India, where many people browse on Android phones with different browsers and settings, that gap can be meaningful, so it is worth checking how many of your events arrive from each source.
Why is the Pixel alone no longer enough?
The Pixel runs in the visitor's browser, and a growing share of browsers and devices restrict that. Ad blockers, tracking prevention in Safari and other browsers, shorter cookie lifetimes and users who decline consent can all stop an event from being recorded. The result is under-reported conversions, which makes campaigns look worse than they are and gives the algorithm less to learn from.
Sending the same event through both the Pixel and the Conversions API recovers a good part of what is lost. We cannot promise a fixed uplift, because it depends on your audience, device mix and consent rate, but Meta's own recommendation is to use both together. For stores and lead generators that depend on Meta, this is now standard practice rather than an advanced extra.

How do the Pixel and Conversions API work together?
Think of them as two reporters covering the same event. The Pixel reports what happened in the browser, and the Conversions API reports what your server knows. When both send the same event, Meta needs to know they are one action and not two. That is done through deduplication, using a matching event name and a shared event ID.
If the IDs match, Meta keeps one and discards the other. If they do not, you may see inflated conversion numbers that confuse reporting and mislead bidding. Events that only the server can know, such as a sale confirmed offline or a lead marked qualified in the CRM, can be sent through the API alone because the Pixel never saw them. Our conversion tracking setup guide covers the general tracking structure.
What a good event usually includes:
What are the ways to set up the Conversions API?
There are four common routes. First, a partner integration: platforms such as Shopify and some WordPress plugins offer a built-in Meta connection that sends server events with a few clicks. Second, the Conversions API Gateway, a hosted option that Meta provides to reduce developer work. Third, server-side Google Tag Manager, which routes events from a web container to a server container you host. Fourth, a direct integration by a developer.
Choose by your platform and resources. A small Shopify store can use the native Meta channel and check data quality. A lead generation site on WordPress might use a reliable plugin or a server-side Tag Manager setup. A business with a CRM and offline sales is better served by a direct or CRM-based integration. Hosting costs, maintenance and consent handling all differ, so compare them before committing.
How do you set up CAPI for a Shopify or WooCommerce store?
On Shopify, connect your Meta Business assets through the Facebook and Instagram sales channel, choose the maximum data sharing option your privacy policy allows, and confirm that your Pixel is selected. Shopify then sends standard commerce events from the server. Check in Events Manager that purchase events appear under both 'Browser' and 'Server' with deduplication working.
On WooCommerce, use Meta's official plugin or a reputable server-side tracking plugin, and test purchases thoroughly because themes and checkout plugins can interfere. Cash on delivery orders deserve a special mention for Indian stores: decide whether the purchase event fires when the order is placed or when delivery is confirmed, and keep that rule consistent so reporting stays comparable. Whichever platform you use, test with a small real order, compare Events Manager with your orders list, and keep an eye on Pixel and server event counts so that neither drifts away. Read our Shopify vs WooCommerce comparison if you are still choosing a platform.
FAQs: How do you set up CAPI for a Shopify or WooCommerce store?
Will CAPI double my reported sales?
Not if deduplication is set up properly. When the Pixel and server send the same event with a matching event ID and name, Meta counts it once. Duplicate counts usually point to missing or mismatched IDs.
Does CAPI work without the Pixel?
It can, but it is better with both. Without the Pixel you lose browser signals that help matching, so most advertisers run them together.

How do you set up CAPI for a lead generation website?
When a visitor submits a form, send a Lead event from the browser through the Pixel and, with the same event ID, from your server. Include the hashed email and phone number from the form so Meta can match the event to a user. Pass the click ID parameter and browser ID cookie where available, as they significantly improve matching.
Then go beyond the form. If your sales team marks leads as qualified or won in a CRM, send those stages back as custom events or through Meta's conversion leads approach. Optimising for qualified leads rather than raw form fills helps Meta find more people like those who actually become customers. Pair this with fast follow-up described in our Facebook lead ads guide.
What is Event Match Quality and how do you improve it?
Event Match Quality is a score in Events Manager that shows how well the customer information you send can be matched to Meta accounts. Higher scores usually mean better attribution and optimisation. It rises when you send more reliable identifiers: email, phone number, first and last name, city, the click ID and the browser ID.
Make sure data is formatted properly before hashing, with lower case emails, phone numbers in international format and no stray spaces. Do not send information that you have no right to share, and never include sensitive health or financial details. Check the Diagnostics tab regularly, because it lists missing parameters, duplicate events and delays, and tells you what to fix first.
Remember that match quality is only one part of the story. A high score on events that do not reflect real business value will not help much. Prioritise the events that sit closest to revenue, such as purchases and qualified leads, and make sure those carry the best data. Then look at how quickly events arrive, since delays of many hours can reduce their usefulness for optimisation.
Quick data quality checks:
Final thoughts
The Meta Conversions API gives your campaigns a more complete record of what your ads achieve. Use it alongside the Pixel, share event IDs for deduplication, send quality customer data lawfully and review diagnostics every month. If you would like help checking your Meta tracking, book a free marketing audit with Go Beyond Driven, or see our Meta ads agency in Mumbai page.



