Platform / Send back / Conversions API
The sale, sent back to Meta.
When a lead becomes a customer, we tell your own Meta dataset — server to server, hashed, once — so Meta learns which people actually buy.
| Event | Sent as | Key | Status | When |
|---|---|---|---|---|
| LFDeal won · $12,000 | Won | lead ID | accepted | 12:17 |
| MRMeeting attended | MeetingAttended | lead ID | accepted | 12:17 |
| JMMeeting attended | MeetingAttended | email · phone | accepted | 12:17 |
| SSQualified lead | LeadQualified | lead ID | retrying · same event ID | 11:17 |
| TKDeal won · no total | — | — | waiting for sale total | — |
| CPQualified lead | — | — | older than 7 days | — |
How it works
Step by step.
What you actually get
Conversions API, in detail.
Your own dataset
Events go to your Meta dataset with your own token. Never a shared one.
Lead ID first
For Instant Form leads we send Meta's own lead ID — the key Meta trusts most.
Hashed before it leaves
Email, phone and country are SHA-256 hashed on our server. Names never leave.
Stable event ID
A retry carries the same ID, so Meta never counts a conversion twice.
Inside Meta's window
Events older than seven days aren't sent — Meta would reject them anyway.
A clear delivery log
Every event shows accepted, retrying or waiting — with the reason, in one list.
Works with
Connect what you already use.
Meta, your website and a CSV from any CRM today. Direct CRM and payment connections are next.
Will this change my ads?
No. We only send outcome events. We never change ads, budgets or audiences.
How often is it sent?
Every hour.
What about my match quality score?
Meta shows it in your own Events Manager — we go through it together after the first events.
The sale, sent back to Meta
on your own data.
Book a 30-minute call — we set it up with you live.
Book demo