The Meta Conversions API, often called CAPI, is a way to send what customers do (a purchase, a lead, a booking) from your server or CRM straight to Meta. The Meta Pixel reports from the visitor's browser; the Conversions API reports from your side. Meta describes it as a connection between an advertiser's marketing data and its systems, covering website, app, messaging and offline events.
Why it matters for your business
Meta's ad system learns from the results you send back. If it cannot see which people bought or enquired, it optimises toward whoever clicks, and your costs drift up.
Browser tracking misses events: ad blockers, privacy settings and pages that close before the pixel fires all lose data. A server connection fills many of those gaps. It can also send events that never happen in a browser at all, such as a lead marked "won" in your CRM or a sale closed on WhatsApp.
Meta recommends running the Conversions API alongside the pixel, which it calls a redundant setup. The two must be deduplicated so one sale is not counted twice.
An example
This is an illustrative example. A Dubai interior design studio runs lead ads that send people to a form on its website. The pixel records 100 form submissions in a month, but the studio's CRM shows 120, and only 15 of those became paying clients.
With the Conversions API, the website server sends every form submission, each with the same event ID the pixel uses. When a lead becomes a client, the CRM sends a second event. Meta now sees all the leads and, more usefully, which kinds of people turn into clients.
How to use it
- Keep the pixel and add the Conversions API, rather than replacing one with the other.
- Send the same event name and a matching event ID from both. Meta deduplicates on event ID and event name, for events received within 48 hours of each other.
- Send customer details only as Meta's documentation requires, hashed, and only with proper consent under the privacy rules that apply to you.
- Test events in Events Manager before spending money.
- Track the events that matter, like qualified leads and purchases with values, not every page view.
For how these signals shape delivery, read how the Meta ads algorithm works. Our Meta ads management sets up and tests the pixel and Conversions API before any budget goes live.
Frequently asked questions
Do I still need the Meta Pixel if I use the Conversions API?
Meta recommends using both. The pixel captures browser activity, the Conversions API adds server and CRM events, and deduplication stops double counting.
Is the Conversions API hard to set up?
Meta offers a quicker setup path for websites that already have a pixel, and many e-commerce platforms, Shopify among them, offer built-in integrations. Custom sites and CRM events need developer work.
Does the Conversions API get around privacy rules?
No. It changes how data reaches Meta, not what you are allowed to share. You still need valid consent and a clear privacy policy where the law requires them.
Last reviewed 22 Oct 2026 by the Astrafolio team.