Stage-to-event mapping
You define which Bitrix24 stage corresponds to a Lead, Contact or Purchase event in Meta.
Integrations
Bitrix24 Meta Conversions API
Meta knows who filled in a form; it does not know who actually bought. The Conversions API sends that information back and changes what your campaigns optimise for.
At a glance
- Stage-to-event mapping
- Sending sales value
- Four operating modes
- Pixel selection
- Privacy-preserving matching
What Meta does not know
Ad optimisation works from the data Meta holds. If all it holds is form submissions, it optimises for form submissions:
- Meta optimising for "more forms filled in" rather than "more sales"
- Ads that bring cheap but low-quality leads appearing to perform well
- The audience that actually buys never being recognised by Meta
- Cost per lead falling while cost per customer rises
- Lookalike audiences built from the wrong source list
- Budget allocated by form count rather than real return
Scope of the implementation
The setup is less technical than it is a matter of judgement: deciding correctly which stage matches which event.
Sending sales value
On stages that carry an amount the sales value is sent too, so Meta can optimise on value.
Four operating modes
Off (the default), dry run (the payload is built but not sent), test (with a Meta test code) and live.
Pixel selection
Your ad account's pixel is picked from a live list; without ad account permission no pixel appears.
Privacy-preserving matching
Phone numbers and email addresses are not sent to Meta; matching uses Meta's own lead ID.
Event log and manual retry
Every row shows which stage was sent and its trace code. A failed event is retried by hand with one click.
Which stage should you report?
This is the critical decision. Report too early a stage; "first contact made"; and Meta keeps optimising for low-quality leads. Report too late a stage; "treatment completed"; and the event may fall outside Meta's attribution window and never be linked to the ad. The right point is between the two: where purchase intent is clear but the process has not dragged on. The panel shows funnel statistics; how many times each stage is passed per week and how long it takes on average. We make the decision together from that data and Meta's attribution window.
- Too early: Meta keeps optimising for low-quality leads
- Too late: the event may fall outside the attribution window
- Funnel statistics show stage transitions and average duration
- Several events can be reported: a consultation as Contact, the sale as Purchase
Why dry run first?
Meta does not take back a conversion it has received. If you reported the wrong stage, or sent test data live, it cannot be deleted; your ad account's optimisation data is permanently polluted. That is why sending is off by default and the order is deliberate: first dry run (the payload is built and visible in the panel but does not go to Meta), then a test with Meta's test code, and only then live. By the same logic there is no bulk resend button; failed events are retried one at a time, with you looking at them.
- Sending is off by default
- Dry run: the payload is built, visible in the panel, not sent to Meta
- Test mode: verification with Meta's test code
- Live mode: only after your approval
- Bulk resend is deliberately absent
Duplicate conversions and privacy
Two technical details matter. First: every event has a fixed ID, so re-sending an event does not create a second conversion in Meta; even if it is triggered twice by accident, the numbers do not inflate. Second, and decisive for data protection: your customer's phone number and email address are not sent to Meta. Matching runs through the lead ID Meta itself generated. In other words, you do not have to share your customers' contact details with Meta in order to report a conversion.
- Every event has a fixed ID; re-sending does not create a duplicate conversion
- Phone numbers and email addresses are not sent to Meta
- Matching uses Meta's lead ID
- A failed event is not retried automatically; it shows in the log and is retried by hand
- When Bitrix24 converts a lead into a deal, breakdown fields move to the deal and tracking continues
The four operating modes
Setup moves through them in this order; skipping a step can produce results you cannot undo.
| Mode | What happens | When it is used |
|---|---|---|
| Off | Nothing is sent | The default state |
| Dry run | The payload is built and shown in the panel but not sent to Meta | While verifying the stage mapping |
| Test | Sent with Meta's test code | While verifying on Meta's side |
| Live | Conversions are reported for real | After your approval |
How would this work in your process?
In a free 30-minute call we listen to your workflow and map out how this would run in your company.
How we work
Rushing this setup is the most expensive mistake; we follow the order exactly.
- 01
Reading the funnel data
Weekly transitions and average duration per stage are reviewed; the stage to report follows from that.
- 02
Stage-to-event mapping
Which stage matches which Meta event, and whether an amount is sent, are defined.
- 03
Dry run and test
The payload is built and verified in the panel, then sending is tried with Meta's test code.
- 04
Go-live and monitoring
With your approval we switch to live mode and watch the event log and failed sends for the first weeks.
What you end up with
- Stage-to-event mapping and value sending configuration
- A setup verified through dry run and test records
- Live conversion reporting and an event log screen
- A control panel where failed events can be retried by hand
- Real sales conversion reporting per campaign
- A data flow ready for value-based optimisation on Meta's side
Product pages
Technical detail and the live demo are on the product's own site.
FlexInbox | Meta ads and Conversions API
The official account of operating modes, the event log and technical detail.
flexinbox.ioFlexInbox | Bitrix24 integration
Setup on the Bitrix24 side and the Open Channel flow.
flexinbox.ioFlexInbox: interactive demo
A live demo of the real panel with sample data, no sign-up required.
flexinbox.ioFeatures
Related features
The modules we most often roll out alongside this one; they reinforce each other in the same setup.
Campaign ROI
Clicks and open rates don't prove a campaign worked; closed revenue does. We connect your campaigns to CRM data so every lira spent can be matched against the deals it produced.
Sales Reporting
Rebuilding the same spreadsheet every week costs you hours and, worse, decision quality. We connect your CRM data to live dashboards so the report builds itself while you work.
Lead Management
Collecting leads is the easy part. Responding quickly, assigning correctly and following up consistently is where deals are won. We build Bitrix24 around those three things.
Sales Pipeline
When the pipeline is unclear, nobody knows which deals are moving and which are stuck. We design your stages around your real sales process and make the next step visible on every card.
Other integrations
WhatsApp is the primary channel for customer communication in Turkey, yet in most setups it sits outside the CRM. We connect your team's own number to Bitrix24 Open Channels.
Telegram
Stop opening a separate app for customers who write on Telegram. Your team's Telegram accounts connect to Bitrix24 and conversations are written to the same customer record.
AI Assistant
An assistant that gives the first answer to enquiries arriving out of hours, trained on your own price list. When it does not know, it hands off to the Bitrix24 queue rather than inventing an answer.
Frequently Asked Questions
What does the Conversions API actually do?
It tells Meta that a lead genuinely turned into a sale. Without that information Meta optimises the campaign for "more forms filled in". With it, Meta can look for people who resemble buyers rather than people who resemble form-fillers. In practice lead volume may fall while lead quality rises.
Is our customer data sent to Meta?
Phone numbers and email addresses are not sent. Matching runs through the lead ID Meta itself generated, so you do not have to share your customers' contact details with Meta to report a conversion; an important detail under Turkish data protection law.
If we report the wrong stage, can we undo it?
You cannot. Meta does not delete a conversion it has received. That is why setup starts in dry-run mode and why there is deliberately no bulk resend button. We verify the mapping in the panel before going live.
Which stage should we report?
The stage where purchase intent is clear but the process has not dragged on. Report too early and Meta keeps optimising for low-quality leads; report too late and the event may fall outside Meta's attribution window. The panel shows weekly transitions and average duration per stage, and we decide together from that data.
What happens if the same conversion is reported twice?
Every event has a fixed ID, so a repeat send does not create a second conversion in Meta. Even if it is triggered twice by accident, the numbers do not inflate.
Is there a separate charge?
The Conversions API comes inside the Meta ads module and is not charged separately. The module is USD 79 per ad account per month. Meta does not charge separately for conversion reporting.
Let's configure this around your business
Book a free intro call and we'll walk through your process and show which settings fit you.