Facebook Lead Ads to Bitrix24 integration: three ways to connect, step by step

Teams usually look for a Facebook Lead Ads to Bitrix24 integration in one situation: the lead is in Ads Manager, and the sales team sees it late or not at all. This guide covers the three ways to connect the two, what a delivery must do, the steps with CAPI Platform (capip.uz), how to check the first leads, and sending Bitrix24 stages back to Meta.

An Instagram lead form needs no separate integration with Bitrix24: Facebook and Instagram show the same form, and a lead takes the same road whichever placement it came from.

What are the ways to send Facebook leads to Bitrix24?

There are three. What is said about other vendors comes from their own pages as of October 2026; the links are at the end.

On price, CAPI Platform is not the cheapest: the builders start lower. The difference is what you build yourself and what arrives ready. Other tools send Bitrix24 stages back to Meta as well: LeadsBridge (Bitrix24 → Conversions API, filtered by deal stage) and Datahash (Bitrix24 deals → Meta Conversion Leads; no price on its site).

What must a good lead delivery do?

Whichever way you choose, test the integration against five requirements. Beside each: how CAPI Platform handles it (more on the lead delivery page).

• No doubles. One Meta lead is one record in Bitrix24. Each Meta lead ID is registered once, and the record carries an origin mark (ORIGINATOR_ID, ORIGIN_ID): a retry finds the first record instead of creating a second.
• No losses. If Bitrix24 does not answer, the lead stays in the queue and is sent again after 1, 5, 15, 60, 180, 720 and 1,440 minutes. A lead that has waited 15 minutes raises a Telegram alert.
• UTM tags and the ad in the record. The record gets UTM tags, and the lead is tied to the exact ad it came from. Without that, nobody can say which creative sold.
• A responsible person. Pipeline, first stage, responsible person and source are chosen per form; the form's answers go into their own Bitrix24 fields.
• Speed. Meta's webhook hands the lead over at once; a check every minute backs it up. The lead appears in Bitrix24 within about a minute.

How do you connect lead forms to Bitrix24 with CAPI Platform?

If we set it up, you provide two things: access to Bitrix24 and to the Meta ad account. If you do it yourself, the order is the same; connection details are on the Bitrix24 integration page.

1. 1

   Connect Bitrix24

   Create an inbound webhook in Bitrix24; it needs one scope, CRM (crm). On the day it is connected, the last 30 days of leads and deals load into the report; they are not sent to Meta.

2. 2

   Connect Meta

   The ad account, the Page and its lead forms are connected. To read leads, the Meta token needs the leads_retrieval permission; for leads to arrive instantly, pages_manage_metadata.

3. 3

   Set the route for each form

   Choose what a request becomes: a lead, or a deal with a contact. Then set the pipeline, first stage, responsible person, source, title template, UTM tags and which answer goes into which Bitrix24 field. Settings can be copied from another form.

4. 4

   Preview before switching on

   “Preview” shows how the form's last 3 real leads would be written with these settings: phones are masked, nothing is saved. “Test” creates one test record without a phone number in Bitrix24, so you can open the card.

5. 5

   Switch the old integration off, then the form on

   First stop this form in Albato or whichever service delivers it now, then switch it on in the platform. Leads are delivered from the moment of switching on. If a lead missed the CRM in between, pick the first such lead — at most 3 days back.

How do you check the first leads?

Once the form is on, check the first 5–10 leads by hand: thousands more will arrive with the same settings.

1. The log. The delivery log holds the last 50 leads; each should read “Delivered”. A lead left with an error is resent with one button.
2. The count. Each form shows two numbers: how many leads Meta has since switching on, and how many reached the CRM. They should match.
3. The card. Open the lead in Bitrix24: title, responsible person, source, UTM fields and the form's answers should all be in place. One person, one record.
4. The time. Compare the time the form was submitted with the time the record was created in Bitrix24: the gap is about a minute.
5. The ad. In the platform's lead list, each lead stands beside the ad it came from.

The second half: how do you send Bitrix24 stages back to Meta?

A lead in Bitrix24 is half the job. So far Meta knows one thing: a form was filled in. One week at a driving school (2–8 October 2026): Meta counted 863 leads; the CRM closed 36 sales that week, and on its own Meta saw none of them — a sale closes in the sales team, not on a website. Meta knows only what it is told: until the CRM’s stages reach it, it keeps looking for people who fill in forms.

The Conversions API fixes that. On CAPI Platform's Funnel page each Bitrix24 stage gets a meaning — a qualified lead or a sale, for example — and the event that goes to Meta. You mark which stage means a qualified lead and which means a sale once.

Product screen · capip.uz

The moment a manager moves a lead into such a stage, the event is queued and sent: Lead, QualifiedLead or Purchase. Meta recognises a lead-form lead by its own lead ID; phone and e-mail go only as SHA-256 hashes, and names are never sent. Purchase carries the deal amount, when there is one, in the ad account's currency. One event name is sent once per lead, and the history loaded on connection is not sent to Meta.

Product screen · capip.uz

To optimise ads for qualified leads, you create a custom conversion from the QualifiedLead event in Ads Manager — covered in a separate article.

Setup takes 3 days: Bitrix24 is connected on day one, stages are tied to signals on day two, a test signal goes out on day three. The price is $159 once, with lead delivery included as a bonus; then $40 a month for the Conversions API, the report, Telegram reports and up to 4,000 leads a month. See pricing.