The Conversions API (CAPI) is a direct channel between a developer's CRM and Meta: when a lead from an ad is marked as qualified by the sales team, books a meeting or buys an apartment, the CRM tells Meta. With that signal Meta learns to look for people who resemble real buyers rather than people who simply fill in forms. Phone numbers and names are hashed before sending, so they never reach Meta as plain text.
Key points:
- The pixel sees what happens on the website. What happens on the phone, in the office and at the contract is known only to the CRM; the Conversions API passes that to Meta.
- The event chain for a developer: Lead (enquiry), QualifiedLead (the card moves past "new"), Schedule (meeting), Purchase (sale).
- The ads look for people similar to those who triggered the event they can see. If only Lead is sent, they find people who like filling in forms.
- An apartment sale is rare and slow, so the in-between stages (qualified lead, meeting) matter most for learning.
- Phone and name are hashed. The quality of the signal depends on the team: stages must be updated on time and honestly.
The Conversions API in plain words
Meta's ads learn from two things: what a person does with the ad and what happens afterwards. Meta sees the first part itself: who viewed, who clicked, who filled in the form. The second part, whether that person became a buyer, happens in your sales office, and Meta cannot see it.
The pixel is a small piece of code on your website that reports what happens in the browser (a page view, a form submission) to Meta. But in apartment sales the key events do not happen in the browser: the manager calls, the buyer visits the office, reserves the apartment, signs the contract. Only the CRM knows about that.
The Conversions API is a channel from the CRM's server to Meta's server. When a manager moves a card to the next stage, the CRM sends Meta a short message: this event happened, at this time, with this (hashed) person. Meta matches it to someone who saw the ad and learns which click turned into a buyer.
Why it matters: a developer's audience is large. According to DataReportal's Digital 2026 report, Instagram ads can reach 4.25 million people in Azerbaijan, 54.4% of adults. To find the future apartment buyer in that crowd, the algorithm has to be shown who buys.
Which events a developer sends
A developer's sales chain is long, but you do not need to send every step to Meta. The chain that runs in our CRM has four events:
| What happens in the CRM | Event sent to Meta | Who triggers it | What Meta learns |
|---|---|---|---|
| An enquiry arrives from a form or the website | Lead | Automatic | Who shows interest |
| The manager moves the card past "new" | QualifiedLead | Sales manager | Who is ready for a real conversation |
| A meeting is booked at the office or by video | Schedule | Sales manager | Who is ready to come |
| The deal is closed (won) | Purchase | Sales manager | Who buys |
Lead, Schedule and Purchase are Meta's standard event names. We name the qualified-lead event QualifiedLead ourselves. What matters is not the name but a stable rule: the head of sales should write down once what makes a card leave "new", and the whole team should follow it.
Some developers want to track reservations separately. If a reservation is its own stage in the CRM, it can be sent as its own event too. The key condition is that every stage is one the sales team really uses, not one that exists only on paper.

Unreal Engine 5, real time: an enquiry from the apartment picker on the website lands in the CRM with the apartment number and the ad source. That is the first link in the chain.
We can show in a meeting how to connect this chain to enquiries from a 3D model, using your project's own stages.
Why sending outcomes changes who Meta finds
Meta shows your ads to people similar to those who triggered the event you optimise for. If a campaign is optimised for Lead only, the algorithm finds people who are inclined to fill in forms, and it does that well: lots of leads at a low cost. The trouble is that not everyone who fills in a form buys an apartment.
When the CRM sends outcomes back, Meta sees the difference: which of the form-fillers became qualified, came to a meeting, bought. That is a far more precise example for telling the ads "bring me more people like these". What the sales side has to do to turn a lead into a buyer is in our article on Meta ads for developers.
Real estate has one peculiarity: sales are rare and late. The person who buys an apartment saw the ad weeks, sometimes months, earlier. A few sales a month are usually too few for the algorithm to learn from, so the in-between stages do the main work. Qualified leads and meetings happen more often and are closer to a purchase than a Lead. Purchase is there for reporting and audiences: only it shows which part of the advertising brings real sales.
We wrote separately about the role of the signal after Meta's recent changes (Andromeda, Advantage+) in Meta ad changes in 2026.
Privacy: what hashed data means
The CRM does not send the buyer's phone number and name to Meta as plain text. Before sending they are hashed: a one-way mathematical transformation turns the number into a long string of characters. The same number always gives the same string, but the number cannot be recovered from the string. Meta does its matching on these strings.
That is why the way the phone number is written matters. The same number written as "050 ..." and as "+99450..." gives two different hashes. The CRM has to bring numbers to one format before hashing (with the country code, no spaces), otherwise matching fails and the event is wasted.
What is sent: the event name, the time and the hashed contact details. The apartment price, the contract terms or the buyer's documents do not need to be sent for the chain to work.
The legal side: have your lawyer check the consent text for processing buyers' data for advertising (in the form and on the website). This article is not legal advice.
What you need: a setup checklist
| What you need | Why | Who is responsible |
|---|---|---|
| A Meta business portfolio, an ad account and a pixel (dataset) | Events must go to where the ads learn | Marketing |
| A page, an Instagram account and a pixel that can be linked | If they sit in different portfolios, linking a form lead to an event gets harder | Marketing |
| Clear stages in the CRM | "New", "qualified", "meeting", "sale" must mean the same thing to everyone | Head of sales |
| A source on every card | Ad, campaign, form or website; from the website, also the apartment number | Automatic |
| One phone format | Different spellings give different hashes | Technical side |
| A test | Check in Events Manager that test events arrive | Technical side |
| Updating stages on time | A card moved late is a late and weak signal | Managers |
The hardest part of this list is not the technology but the last row. If managers do not move cards on time, even a perfectly built API sends Meta an empty chain.
Common mistakes
- Only Lead is sent. The algorithm learns who fills in forms, not who buys. Add at least QualifiedLead.
- Every card is marked "qualified" at once. The signal becomes false and the ads go back to bringing everyone. Write the rule down and stick to it.
- The same event arrives from both the pixel and the API. Both must be sent with the same event ID, or Meta counts it twice.
- Deals are closed in Excel, not in the CRM. Then Purchase is never sent and you do not know whether the ads bring sales.
- Reports look only at cost per lead. Cost per lead can fall while cost per qualified lead rises; track both side by side.
If the ads bring no leads at all, the problem lies elsewhere; we collected the reasons in Meta ads bring no leads.
How it works at Advertol
In Baku, Advertol runs Meta ads for developers, and our own CRM, AVA, sends each lead's outcome back to Meta through the Conversions API. The chain is: an enquiry from a form or the website goes as Lead; when the team moves the card past "new", QualifiedLead; when a meeting is booked, Schedule; when the deal is won, Purchase. Phone numbers and names are hashed before sending.
In projects where we build a 3D Master Plan in Unreal Engine 5, an enquiry from the apartment picker on the website lands in the CRM with the apartment number and the ad source, so the manager knows before the call which apartment the buyer looked at. For the model itself, see what a 3D master plan is.
In the meeting we look at your ad account and the state of the pixel, the stages in your CRM and where deals are closed, then tell you which events are worth sending. You can book a 15-minute call on the 3D Master Plan meeting page.
Frequently asked questions
What is the Conversions API?
The Conversions API is Meta's server-to-server channel: your system (website or CRM) sends an event straight to Meta. For a developer it is the way to tell the ads what happens on the phone, in the office and at the contract. Unlike the pixel, it does not depend on the browser.
Do you still need the Conversions API if you have a pixel?
Yes, if the sale is closed outside the website. The pixel only sees what happens in the browser, while in apartment sales the key stages happen on the phone and in the office. The pixel and the Conversions API work together; if the same event comes from both, send it with the same ID.
Does the Conversions API send the buyer's phone number to Meta in plain text?
No. The phone and name are hashed before sending, turned into a string of characters that cannot be decoded. Have your lawyer check the consent text and how the data is processed.
Can you set up the Conversions API with an off-the-shelf CRM?
Some off-the-shelf CRMs have a Meta integration; where there is none, the connection is built through the API. The real question is not the integration but whether the CRM has clear stages and the team updates them on time. No stage, no event to send.
When does the Conversions API lower advertising costs?
We do not promise a time frame or a percentage, because the result depends on the number of events and the discipline of the sales team. So first of all, track the cost per qualified lead and per meeting in the CRM. When stages are updated honestly, Meta learns from the right example.
