Conversions API

The Conversions API is the connection that sends events such as purchases straight from the advertiser’s server to Meta. It fills in the events the browser-based Meta Pixel misses because of ad blockers and browser restrictions. The two are used together, and each event carries a shared ID so that it is not counted twice.

Also called
CAPI
In Turkish
Conversions API

Why it matters

When data from the browser is incomplete, Meta cannot see part of the sales and optimises with less data. Sending from the server closes that gap. If the same event arrives by both routes without a shared ID, the sale is counted twice and ROAS looks higher than it is.

Example

Say a shop has 100 real orders but the Pixel reports 80 from the browser. Adding server-side sending fills in the missing 20. Without a shared ID the same orders arrive twice and the dashboard shows 180 sales. With the ID, the count stays at 100.

The definitions are general information. If you think one is incomplete or wrong, write to us and we will reply within one working day. Get in touch

From our journal

From what we have written on Advertising; they show how the term turns up in the work.

Tell us about
your project.

Fill in the form or write to us directly, and we will agree on a day to talk.

Your first meeting is with Deniz Sezer, founder of Detmore.

First meeting free · Reply within one working day · Written proposal in 2 to 3 days · NDA ready

What do you need? pick as many as you like

Name, email and phone are required.

Contact

We reply within one working day.