Glossary

What is Conversions API? Definition and how it works

What is Conversions API? Meta's Conversions API, usually called CAPI, is a server-to-server connection that sends conversion events, such as leads, booked calls and purchases, from your website server or CRM directly to Meta. It does not depend on the visitor's browser, so it records events the browser-based Pixel misses.
Quick answer

What is Conversions API?

Conversions API is Meta's server-side tracking method. Instead of relying only on browser code, your server or CRM sends events like Lead, Schedule and Purchase straight to Meta with matching customer data. It recovers events lost to ad blockers and browser privacy limits and lets you send offline outcomes such as booked calls.

How Conversions API works

  1. A visitor converts on your funnel, and the Meta Pixel fires a browser event.
  2. Your server or CRM sends the same event to Meta through the API, with hashed customer details such as email and phone.
  3. Both events carry the same event ID, so Meta deduplicates them and counts the conversion once.
  4. Later outcomes, such as a booked call or closed sale in the CRM pipeline, are sent as additional events.
  5. Meta uses the fuller data to report results and optimize delivery toward people likely to convert.

Pixel vs Conversions API

Meta PixelConversions API
Runs inVisitor's browserYour server or CRM
Affected by ad blockersYesNo
Offline events (calls, sales)NoYes
Setup effortLowModerate

Use both together, with deduplication, rather than choosing one.

Example: 31% more events recovered

On funnels where we added Conversions API alongside the Pixel, Meta recorded 31% more conversion events than with the Pixel alone. Just as important, sending booked calls and closed deals lets the campaign optimize for buyers instead of form fillers, which is how lead funnels keep a low cost per lead while lead quality rises.

The step-by-step setup is in our Conversions API setup guide.

Common mistakes

  • No deduplication. Without a shared event ID, every conversion counts twice.
  • Weak customer matching. Sending events without hashed email or phone lowers match quality.
  • Sending only the Lead event. The value comes from sending deeper events such as Schedule and Purchase.
  • Never checking Events Manager. Match quality and duplicate warnings show problems quickly.

We configure Pixel, CAPI and CRM events together in our Meta Conversions API setup service.

Related terms

Conversions API works alongside the Meta Pixel, reads outcomes from your CRM pipeline and directly affects cost per lead by improving what Meta optimizes for.

Proof from client campaigns

See 275+ results ↗

Glossary

Frequently asked questions.

Do I still need the Meta Pixel if I use Conversions API?

Yes. Meta recommends running both, and we do too. The Pixel captures browser behavior such as page views quickly, while Conversions API fills the gaps and adds offline events. With a shared event ID on both, Meta deduplicates them and counts each conversion once.

Which events should I send through Conversions API?

For lead generation, send Lead when the form is submitted, Schedule when a call is booked, and Purchase or a custom event when a deal closes, with the deal value. For eCommerce, send the full checkout path. Deeper events help Meta find people who buy, not just people who fill in forms.

Is Conversions API hard to set up?

It ranges from simple to technical. Platforms like Shopify and GoHighLevel offer built-in connections for common events. Custom funnels, CRM stage events and deduplication need more work, often through a server-side tag manager or webhooks. Testing in Events Manager before relying on the data is essential.

Does Conversions API lower cost per lead?

It can, indirectly. More complete data gives Meta more signals to optimize on, which often stabilizes performance. The bigger gain comes from sending booked calls and sales, so Meta targets people who become customers. Lead cost may stay similar while cost per booked call or sale falls.

Is Conversions API compliant with privacy rules?

It can be, when customer data is hashed before sending, your privacy policy discloses the tracking, and consent rules for your region are respected. It does not bypass a visitor's choices; it changes where events are sent from. Review your consent setup with your legal adviser.

FTP automation robot

We
build
with
Robots.Let's Talk

Talk with us →

We're a small team of strategists, builders and automation nerds, blending funnels, follow-up and AI calling so your leads turn into booked calls, not cold contacts.