Skip to main content

Conversions API: send the sale back to Facebook

updated 4 min read

founder

Start free

Facebook knows who clicked your ad, but not who paid. That gap raises the price of the advertising.

Why the pixel is not enough

The pixel works in the browser: someone opened the page, pressed a button, filled in a form. That is where its field of view ends.

The real sale happens somewhere else — after the operator calls, when the deal is closed in the CRM, or when the CPA network confirms the order. None of that happens in the browser, so the pixel never sees it.

The result is that Facebook learns to “collect leads”, not to “make sales”. The algorithm looks for people inclined to fill in a form, not people inclined to pay. The difference is large and it shows up in the budget.

An event sent from the server side

The Conversions API closes that gap: the event is sent from the server, not from the browser. Yuboraman knows the lead status has changed, so it can tell Meta about it itself.

An event goes out as soon as the status is written — usually within seconds. Anything that failed to go for some reason is resent by a backup sweep every ten minutes, up to 1000 events per request. So once a deal is closed in the CRM, Facebook knows almost at once, a few minutes later at worst.

Four events

The path of a lead is split into four steps, and each one goes out as a separate event:

  • Lead — a form on your website was filled in (not duplicated with the pixel event)
  • CRMLead — the lead first reached the CRM or the CPA network
  • QualifiedLead — the lead passed qualification
  • Purchase — the sale was completed

These steps show Meta the quality of the lead. Send only Purchase and the algorithm loses the intermediate signals; send only Lead and it learns nothing about quality. If you want, the negative outcome goes too — a disqualified lead (DisqualifiedLead) and a returned order (OrderReturned); that is switched on separately.

Match quality

How useful a server event is depends on which person Meta can tie it to. Meta gives a 0–10 score for that called Event Match Quality (EMQ). The CAPI section in Yuboraman shows it for each event — with the keys that matched and the ones Meta did not see.

A low score means the event was sent but Meta could not tie it to anyone — so there is little use in it. Watching the score matters, otherwise the CAPI looks like it is working while there is no result.

Where the status comes from

The system learns that a lead has become a sale from several sources. Working with amoCRM, Kommo and Bitrix24, the deal status comes from the CRM; in Google Sheets it is read from the status column. In teams that work through Telegram, the operator presses “✅ Sotildi” (sold) or “⭐ Sifatli lid” (qualified lead) in the lead message — these buttons are switched on in the integration settings.

With the Uzbek CPA networks — 100k.uz, sotuvchi.com — the order status comes from the network itself: Yuboraman sees that the network confirmed or delivered the order and sends the event on that basis.

What changes

Once Facebook starts seeing the customers who paid, the criterion for finding similar people changes too. The advertising starts looking for the lead that turns into a sale, not the cheap lead.

It does not happen overnight — the algorithm needs events to learn from, and events come with sales. But if the data is never sent, the learning does not begin at all.

Related pages

Read next

Do not keep your leads waiting

Sign up and turn on your first integration. No code needed, and up to 1000 leads a month are free.