Meta Conversions API: what it is and why you should use it

For years, measuring the results of Facebook and Instagram ads depended solely on the pixel, a piece of code that runs in each visitor’s browser. Today that system on its own falls short.

What the Conversions API is

The Conversions API (CAPI) lets your server send Meta the important events (purchase, quote request, sign-up) directly, without going through the user’s browser.

The recommended approach is to use both at once: pixel + API. Meta combines them and, through a shared event identifier (event_id), avoids counting the same conversion twice.

Why data is lost with the pixel

• Browsers that block third-party cookies or restrict tracking.
• Ad-blocking extensions.
• Users who reject cookies (as regulations require).
• In-app browsers, such as Facebook’s or Instagram’s, which behave differently.
• Conversions that happen outside the website (for example, payment is confirmed in another system).

When data is missing, Meta’s algorithm learns worse and ads are optimised worse.

What advantages it brings

• More events measured, and more reliably.
• The ability to send conversions that happen on the server: confirmed orders, accepted payments, qualified leads.
• Better match quality by sending hashed contact data (with consent).
• More control: you decide what is sent and when.

What data is sent

A typical event includes: event name, date, source URL, event identifier, and optional “match” data such as email or phone encrypted with a hash. For purchases, the order value and currency.

Respecting privacy and consent

That something can be measured by server does not mean it can be done without permission. In the European Union:

• You should only send advertising data if the user has given consent to marketing cookies.
• Consent must be recordable and revocable.
• Privacy texts should name Meta as a provider.

A correct implementation stores the user’s choice alongside the order and does not send the event when there is no consent.

How to implement it

1. Through your platform’s integration: WooCommerce, Shopify and others have plugins or native connections.
2. Through server-side Google Tag Manager, if you need a lot of flexibility.
3. Through custom development, sending events from your backend to Meta’s API with an access token.

Afterwards, check in Meta’s Events Manager that:

• Events arrive from both “Browser” and “Server”.
• They appear as deduplicated.
• Match quality is reasonable.

Common mistakes

• Sending the same event without an event_id, which duplicates conversions.
• Not sending the value and currency on purchases.
• Sending events without checking consent.
• Setting up the pixel and never testing it with the testing tool.

Measuring well is what makes a campaign improve over time. If you want us to leave it working, let’s talk.