← All articles

What Is Meta Conversions API (CAPI)? A Plain-English Guide for Advertisers

If you run Meta ads, someone has probably told you to "set up CAPI." Usually right after you complained that Ads Manager shows 12 purchases and your store shows 31.

That advice is right. But most explanations of Conversions API are written either for developers or by people selling you something without explaining it. This one is for advertisers and business owners who want to understand what it actually does before touching anything.

Conversions API in one paragraph

Meta Conversions API (CAPI) is a way to send conversion events — leads, sign-ups, purchases — to Meta from your server, CRM or backend instead of from the visitor's browser. The Meta Pixel watches what happens on a page. Conversions API reports what happened in your business. When both run together, Meta gets a fuller and more reliable picture of who converted after seeing your ads, and it uses that picture to decide who to show your ads to next.

Why the pixel alone stopped being enough

The pixel is a piece of JavaScript. It only works if it loads, runs and is allowed to send data. Today, a lot of things get in the way:

The last two points are the ones people underestimate. For a lead-generation business — clinics, real estate, education, travel, B2B services — the event that matters (a paid deal) lives in a CRM, not on a web page. The pixel physically cannot report it. Conversions API can.

What Meta's Conversions API is meant to do

Meta describes the goal as giving advertisers a more reliable connection between marketing data and ad results. In practice it comes down to three things:

  1. Better measurement. More of your real conversions show up in Ads Manager, so your cost per result is closer to the truth.
  2. Better optimization. Meta's delivery system learns from conversions. If it only sees half of them, it learns from a distorted sample. Feeding it real sales — not just form fills — teaches it to find people who actually buy.
  3. Less dependence on the browser. Your data path no longer breaks every time a browser vendor changes its rules.

How it works, step by step

Here is what happens with a typical lead-gen setup:

  1. A person clicks your ad. Meta adds a click identifier (fbclid) to the landing page URL, and the pixel stores it as the _fbc cookie.
  2. They submit a form. Your site, CRM or integration saves their contact details along with that click ID.
  3. When something important happens — the lead is created, qualified, or pays — your server sends an event to Meta: the event name, the time, and customer information such as email and phone.
  4. Personal data is hashed (SHA-256) before it leaves your server. Meta compares the hashes with its own users and attributes the conversion to the ad that person saw.

Meta calls the share of events it can confidently tie to a person Event Match Quality (EMQ), scored from 0 to 10 in Events Manager. Only matched events are used for attribution and ad optimization; unmatched ones still count for basic reporting. The more identifiers you send — email, phone, name, IP address, user agent, fbc, fbp, external_id — the higher the score tends to be.

Conversions API vs Meta Pixel: do you need both?

Yes, in most cases. They are not competitors. Meta recommends running them together, and the reason is simple: each one sees things the other misses.

Meta Pixel Conversions API
Where it runsVisitor's browserYour server, CRM or integration
Blocked by ad blockersOftenNo
Sees offline sales and CRM stagesNoYes
Sees on-page behavior (views, scrolls, add to cart)YesOnly what you send
SetupPaste a code snippetServer code, a gateway, or a ready integration

When the same event comes from both, Meta needs to know it's one event, not two. That's deduplication: both copies must have the same event_name and the same event_id (or matching external_id and fbp). Get this wrong and your purchases double in Ads Manager — a very common mistake in DIY setups. We'll cover it in detail in a separate article on Conversions API vs Pixel.

Limits worth knowing before you start

Three ways to set up Conversions API

1. Direct integration (developer)

Your developer writes code that calls the Conversions API endpoint, handles hashing, retries and deduplication, and keeps a system user access token safe. Maximum flexibility, but it's real engineering work — and someone has to maintain it when Meta changes API versions.

2. Conversions API Gateway

Meta's own self-serve option. You deploy a gateway into your own cloud account (AWS or Google Cloud), point your pixel at it, and it mirrors browser events to the server side. There's no license fee from Meta, but you pay for the cloud resources. The catch: it's built around website events. It doesn't know when a deal closes in your CRM.

3. A ready-made integration

Platforms like Shopify have built-in CAPI for e-commerce. For lead-gen businesses, the gap has always been the CRM: the sale happens in AmoCRM, Bitrix24, HubSpot, Pipedrive or a Google Sheet, and nothing sends it to Meta.

That's the gap LeadMe was built for. You connect your Meta pixel and your source — a CRM, a form, a spreadsheet — choose which deal stages should become which events (Lead, Qualified Lead, Purchase), and LeadMe sends them through Conversions API with hashing, deduplication and click IDs handled automatically. No servers to rent, no code. It also works with TikTok, Google Ads, Yandex, VK and others, so the same CRM data can feed every ad platform you use.

How to tell it's working

  1. In Events Manager → Test events, send a test event and confirm it arrives with the source "Server."
  2. Check the Overview tab a day later: you should see events labeled as received from both the browser and the server, with deduplication shown for overlapping ones.
  3. Watch Event Match Quality. If it's low, you're probably missing email/phone or click IDs.
  4. Compare Ads Manager with your CRM over a week or two. The numbers won't match perfectly — they never do — but the gap should shrink noticeably.

Short answers to common questions

Is Conversions API free?

Meta doesn't charge for the API itself. You pay for whatever runs it: developer time, cloud hosting for the Gateway, or a subscription to an integration.

Is it the same as "Facebook Conversions API"?

Yes. It's the same product; Facebook's ad platform is now branded Meta. You'll see "CAPI," "Facebook CAPI" and "Meta Conversions API" used interchangeably.

Do I need it if I only get leads, not online sales?

Lead-gen businesses arguably need it more. Without it, Meta optimizes for form fills — including fake numbers and people who never answer the phone. With CRM stages sent through CAPI, it can optimize for leads that turn into paying customers.

Will it break my existing pixel?

No. CAPI runs alongside the pixel. The only thing to get right is deduplication, so the same purchase isn't counted twice.

Next in this series: Conversions API Gateway — what it really costs and when it's not the right choice.