Skip to content
Book a call
Glossary

Conversions API

The Conversions API is Meta's tool for sending events like purchases and leads straight from your server, website platform, app or CRM to Meta. It works alongside the Meta Pixel and is less affected by ad blockers and browser errors.

Also called
CAPI, Meta Conversions API
Category
Meta platform and measurement
Updated

How the Conversions API works

The Meta Pixel is a piece of code that runs in your shopper's browser. When someone buys, the browser reports the purchase to Meta. The Conversions API sends the same kind of event from your side instead: your server, your website platform, your app or your CRM.

Meta says the Conversions API can carry website events, app events, offline conversions and messaging events. Website events sent this way are linked to your Pixel and behave like Pixel events. They can be used for the same optimization, such as maximizing the number or value of conversions, and they show up in Ads Manager and Events Manager.

Setup is lighter than it used to be. Meta's help page says many integrations do not need a developer. Its developer docs say a brand with a Pixel can set up the Conversions API for website events in one click from Events Manager, with no code or setup fees. Custom setups, like sending offline sales from a CRM, take more work.

Why the Conversions API matters for brands advertising on Meta

Meta can only optimize toward the results it hears about. If a purchase never reaches Meta, the system cannot learn from it, and it cannot credit the ad that drove it.

Meta's help page lists the benefits plainly. Conversions API data is less affected than the Pixel by browser loading errors, connectivity issues and ad blockers. Used alongside the Pixel, Meta says it helps the delivery system lower your cost per result. It can also carry customer information that raises the number of matched events, meaning events Meta can tie to an account on its apps. Meta's developer docs add that only matched events can be used for attribution and delivery optimization.

That is why we treat the Conversions API as part of creative testing. When signals go missing, good ads look worse than they are, and the attribution window you report on ends up counting fewer of the sales your ads drove.

How to set up the Conversions API properly

Meta recommends what it calls a redundant setup: run the Conversions API alongside the Pixel and send the same events through both. That gives Meta two chances to receive each purchase.

Two copies of every purchase would double your numbers, so Meta deduplicates them. The method it recommends is to give the browser event and the server event the same event name and the same event ID. Meta keeps the first and discards the matching copy, as long as both arrive within 48 hours. Its developer docs describe a second method using a browser ID or an external ID, which only works when the browser event arrives first.

Two more details matter. Send events as they happen, since Meta says real-time sharing helps campaigns get the best results. Send the customer information you are allowed to share, because it can raise your Event Match Quality in Events Manager. Meta is also clear that the Conversions API is not designed to get around privacy rules such as Apple's App Tracking Transparency framework.

Mistakes we look for in a Conversions API audit

Most tracking problems are quiet. Ads Manager still shows numbers, so nobody notices they are wrong.

The first thing we check is duplication. If the Pixel and the Conversions API both send purchases without matching event IDs, the same sale can be counted twice and results look better than they are. The second is missing purchase details. Meta's Pixel reference lists value and currency as required for the Purchase event, and purchase ROAS is built on purchase conversion value. Without them, ROAS cannot be trusted. The third is thin customer information, which keeps match quality low and leaves events unmatched.

The last is a setup that worked once and was never checked again. Theme changes, new checkout apps and platform updates can break an event that used to fire. Events Manager shows what Meta is receiving, so it is worth a look every time something on the site changes.

How Fifth Dimension handles the Conversions API

We make ads for a living, so it is fair to ask why we care about server events. Every creative decision we make depends on the numbers coming back. If purchases go missing, we could cut ads that were working and scale ads that were not.

Our Meta Ads Management service includes an audit of the Pixel, Conversions API and attribution setup, and we implement fixes that fall within scope. For Herbar, we fixed tracking so Meta received purchase signals, alongside new ads made from creator footage with voiceover from the co-founder. Herbar reached €93K in total business revenue in its record month, May.

Even when a brand hires us only for creative, we ask about tracking early. Creative test results only mean something when the signal behind them is sound.

Sources

  1. Meta Business Help Center: About Conversions API
  2. Meta for Developers: Conversions API
  3. Meta for Developers: Handling Duplicate Pixel and Conversions API Events
  4. Meta for Developers: Conversions API best practices
  5. Meta for Developers: Meta Pixel reference (standard events)
  6. Meta Business Help Center: Purchases ROAS (return on ad spend)

Questions about Conversions API

Do I still need the Meta Pixel if I set up the Conversions API?

Yes. Meta recommends running both and sending the same events through each, then deduplicating them with a shared event name and event ID. Each one covers gaps the other can miss.

Do I need a developer to set up the Conversions API?

Often not. Meta says many integrations do not need a developer, and a brand with a Pixel can set up website events in one click from Events Manager. Custom setups, like sending offline sales from a CRM, usually need more technical help.

Does the Conversions API get around iOS privacy rules?

No. Meta states that the Conversions API is not designed to bypass data-sharing rules such as Apple's App Tracking Transparency framework or Europe's ePrivacy Directive. Its job is to get the data you are allowed to share to Meta more reliably.

Can Fifth Dimension check our Conversions API setup?

Yes. Auditing the Pixel, Conversions API and attribution setup is part of our Meta Ads Management service, and we implement fixes that fall within scope.

Put these ideas to work on your ads

Book a call and we'll look at your product, your current ads and what to test next.