The Conversions API, often shortened to CAPI, is a way for your server to send events such as purchases and leads directly to Meta, without relying on the visitor's browser. Because the data goes from your system to Meta's, ad blockers and browser limits cannot stop it.
TL;DR
- CAPI sends events from a server to Meta, instead of from a browser.
- It carries the same kind of events as the pixel: Purchase, Lead, AddToCart and more.
- It helps Meta see sales that the browser hides.
- It can also send events that never happen in a browser, such as a CRM stage change.
- Meta treats server events like pixel events, and removes duplicates when event IDs match.
- It does not fix attribution rules. It gives Meta more data to apply them to.
What does the Conversions API do in plain words?
Think of the pixel as a messenger in the shopper's browser. If the shopper blocks the messenger, the news never arrives. The Conversions API is a direct phone line from your store to Meta. When an order is saved on your server, the server calls Meta and says: this order happened, here is its value, and here is who placed it.
Meta describes the Conversions API as a way to connect your marketing data, such as web events, to Meta systems. Meta says server events are processed like Pixel events, so they feed reporting, audiences and optimization in the same way.
Let Madgicx's AI do the work
Its AI marketer finds what's working and prepares the next move. You approve.
Try for Free ($0 Trial)How does one order travel through the Conversions API?
Here is a made-up order from a store.
| Step | What happens |
|---|---|
| 1 | A shopper clicks a Meta ad and lands on your site. Your site keeps the click ID from the link |
| 2 | The shopper buys a $60 item and enters an email address |
| 3 | Your store saves the order on your server |
| 4 | The server sends a Purchase event to Meta: value $60, currency, the order's event ID, hashed email and the click ID |
| 5 | Meta matches the event to an account and, if an ad earned it inside the attribution window, credits the ad |
| 6 | If the pixel also sent this purchase, Meta sees the same event ID and keeps one copy |
The click ID and customer details are what let Meta match the order to a person. Without them, the event arrives but Meta cannot credit an ad. Meta scores Event Match Quality from 0 to 10 to show how well events match.
What data can it send?
Anything you can describe as an event. For websites, that means standard events and their values. Beyond the website, you can send:
- Orders placed by phone or in a store.
- Lead status changes in a CRM, such as "qualified" or "closed".
- Subscription renewals and other backend events.
This is why the Conversions API suits businesses whose real conversion happens after the web visit. Send the stage that matters to the business, and Meta can optimize toward it.
How is it different from server-side tracking?
They are close relatives. Server-side tracking is the general approach of sending data from a server. The Conversions API is Meta's specific interface for doing that. Other platforms have their own. See server-side tracking for Meta ads for when it helps.
When do you need it?
You need it when the pixel alone loses too many sales. Signs include fewer purchases in Meta than in your store for the same dates, an Event Match Quality score that stays low, and a high share of visitors using blockers or declining consent. You also need it when your key conversion happens off the website. If your account is small and your tracking matches, it can wait. Our comparison of Conversions API versus the pixel shows how to decide.
Where Madgicx fits
Madgicx helps you use the Conversions API without building it. Madgicx Cloud Tracking hosts Meta's Conversions API Gateway and Signals Gateway for you and sends conversions to Meta from the server. That gives Meta's AI more conversions to see and attribute. You choose how it is set up and what it covers.
FAQ
What does CAPI stand for?
CAPI stands for Conversions API. Marketers use it as shorthand, and Meta's own pages write the full name.
Is the Conversions API free?
Meta does not charge for using it. Costs come from setup, hosting or a partner tool you choose.
Does the Conversions API work with Shopify?
Yes, Shopify supports sending server events to Meta, through its data sharing settings. The levels vary, so check what yours sends.
Is the Conversions API the same as the pixel?
No, the pixel runs in the browser and the Conversions API runs on a server. They send the same kinds of events by different routes.
Does the Conversions API need customer data?
It works best with some, such as hashed email or phone, because matching depends on it. Send only data you may legally use.
Related
- Answers: Conversions API vs Meta pixel
- Answers: Setting up the Conversions API, step by step
- Glossary: Conversions API, Server-side tracking glossary entry
Go deeper
Our Conversions API setup guide walks through the options and common errors.
Sources
- About Conversions API, Meta Business Help Center
- Conversions API overview, Meta for Developers
- About event match quality, Meta Business Help Center
