Skip to content
BENIBIX Learn

Conversions API

Marketing🛠️ MarTech, Data & AIData Collection

Also known as CAPI, Conversion API, Server-Side Conversion API

Your server sends each sale straight to the ad platform. No pixel in the browser is needed.

Think of it like

It is like calling the shop to say the parcel came. The shop hears it from you, not a stranger.

Example

A furniture shop sends each order to Meta and Google from its own server. Sales that a blocked pixel used to miss now count toward its ads.

Why it matters

Ad platforms learn who to show ads to from conversions. More of them arriving means better ads.

Definition

A conversions API is a door on an ad platform's server for receiving sales and sign-ups. Your own server sends each sale to it, not a pixel. It usually sends a hashed email or phone number, so the platform can match the buyer. Many teams run it beside the pixel. A shared event ID stops a sale from counting twice. It helps ads learn from sales that browsers would have hidden.
The line from your server to the ad platform is the conversions API. No browser sits on it.

Common mistake

Running it beside the pixel without a shared event ID. Each sale then counts twice.

Key takeaways

  1. 1
    Server to server. No browser in the middle.
  2. 2
    Matched by hash. Hashed emails find the buyer.
  3. 3
    No doubles. One event ID per sale.