25 Sep – 8 Oct 2026
Driving school
All 1,790 Meta leads from 5 lead forms reached the CRM.
- leads delivered to the CRM
- 1,790
- lead forms
- 5
- in the queue
- 0
- errors
- 0
Lead delivery
Facebook lead ads to your CRM: with the ad, without duplicates
CAPI Platform (capip.uz) delivers every Facebook and Instagram lead-form lead into Bitrix24, amoCRM (Kommo) or its own capiCRM with name, phone, all answers, UTM tags and the exact ad. Leads arrive through Meta’s webhook, backed by a check every minute. From the moment a form is switched on, each lead is written once; if the CRM does not answer, delivery retries at intervals from 1 minute to 24 hours.
- Meta’s webhook plus a check every minute: a lead is in the CRM in about a minute
- Each form has its own switch, and leads go only from the moment it is on
- One Meta lead is one CRM record, even after a retry
- Answers, UTM tags and the ad’s name sit in the record itself
- Meta leads delivered to the CRMtwo projects, as of 8 Oct 2026
- 2,103
- leads losta measurement for these dates, not a guarantee
- 0
- leads left with an error
- 0
How it works
How does a lead get from the form to the CRM?
It is set up once: by us within the 3-day set-up, or by you. The steps are the same.
- 1
Meta and the CRM are connected
The project gets its Meta ad account, its Page and its CRM: Bitrix24, amoCRM or capiCRM. The platform reads the Page’s list of lead forms by itself.
- 2
Each form gets its route
You choose what a lead becomes in the CRM: a lead, or a deal with a contact; which pipeline, stage, responsible person, source and title. The form’s answers are mapped to CRM fields.
- 3
It is checked before it is switched on
“Preview” shows how the form’s last 3 real leads would land in the CRM with these settings: nothing is written and phones are masked. “Test” creates one test record in the CRM, with no phone.
- 4
The form is switched on
From this moment the form’s new leads go to the CRM. Earlier leads are not sent again.
- 5
A lead comes in and is written to the CRM
Meta’s webhook reports the lead at once; as a backup the platform checks Meta for new leads every minute. The lead is written to the CRM and, if you want, a notice goes to a Telegram chat too.
What is in the record
What does the sales manager see in the CRM?
Opening the lead, a manager sees who left the request, what they answered and which ad they came from.
| What | Where it goes in the CRM | Settings |
|---|---|---|
| Name, phone, e-mail | The CRM’s own contact fields | Automatic. If the form asks for two phones, the one the person typed is the main one |
| Answers to the form’s questions | The comment, as question and answer | Any answer can also go into a CRM field of its own |
| Title | The name of the lead or deal | Built from parts: name, phone, form, campaign, ad set, ad, answers. Default: “Name · Form name” |
| The ad | The comment: form, campaign, ad set, ad name and the Meta lead ID | Automatic |
| UTM tags | The CRM’s UTM fields | Default: utm_source=facebook, utm_medium=lead_form, utm_campaign is the campaign name, utm_content the ad ID, utm_term the ad set name |
| Pipeline, stage, responsible person, source | The record’s own fields | Set per form |
| A fixed value | The CRM field you choose | A course or a branch, say, whatever the person answered |
The title and UTM tags are set for Bitrix24 and amoCRM; in capiCRM the source, form and ad show on the lead’s card itself. When a deal is chosen and the CRM already has a contact with that phone or e-mail, the deal is attached to it; otherwise a new contact is created.
Attribution
A lead arrives with its ad, and the report starts there
Every lead from a Meta lead form is taken together with its Meta lead ID and its ad ID. So in the report it is counted for that exact creative, and when it becomes a qualified lead or a sale in the CRM, the Conversions API signal goes to Meta for that same lead.
- Per creative: spend, leads, qualified leads and sales in one row
- Repeat requests from one person are merged by phone in the report
- A Bitrix24 Lead → Deal counts as one lead
A familiar case
The leads are in Ads Manager, not in the CRM
An integration stops without a word, and the sales team is the one to notice, a day later.
The chat is an illustration. In CAPI Platform, a lead that has not reached the CRM in 15 minutes raises a message in the Telegram chat that has alerts switched on; so does a form Meta stops letting the platform read. When Meta access has an end date, a warning comes 7 days before it. While a problem lasts it is repeated once a day, and you are told when it is fixed.
Sales team
- Head of salesHardly any leads in the CRM today. Did the ads stop?
- No, Ads Manager shows leads coming in. I’ll check the integration.
- Found it: the token expired yesterday. No lead has reached the CRM since.
- Head of salesSomeone who left a request a day ago won’t pick up the phone now.
Safeguards
What keeps a lead from being lost or delivered twice?
Two ways in
Meta’s webhook hands the lead over at once. If it never arrives, the check every minute picks the lead up in about a minute.
A switch for every form
You choose which forms the platform delivers. Leads of a form that is off are not sent.
One lead, one record
Each Meta lead ID is recorded once. A Bitrix24 record carries an origin ID: a retry finds the record already made and does not create a second one.
7 retries
If the CRM does not answer, the lead waits in the queue and is sent again after 1, 5, 15, 60, 180, 720 and 1,440 minutes.
A message about a stuck lead
A lead that waits 15 minutes for the CRM raises an alert in Telegram. It is repeated once a day while the problem lasts, and once more when it is fixed.
Learn moreA count against Meta, and a log
Beside each form: how many leads Meta has since it was switched on and how many reached the CRM. The log keeps the last 50 leads; one button resends a failed one.
Measured
2,103 leads in two projects: all reached the CRM
This is a measurement for the stated dates, not a guarantee. The projects are named only by their trade.
5–8 Oct 2026
Learning centre
All 313 Meta leads that came in after the forms were switched on were delivered to the CRM.
- leads delivered to the CRM
- 313
- lost
- 0
- errors
- 0
Moving over
How do you move from Albato or another connector without duplicates?
When two integrations deliver the same form, every lead lands in the CRM twice. So the order matters.
- 1
Set the form up on the platform, but leave it off
Choose the pipeline, stage, responsible person, title and fields. In “Preview”, check how the last 3 real leads would land in the CRM.
- 2
Switch this form off in the old integration
Stop the automation in Albato or in the other service. From that minute nobody delivers this form’s leads.
- 3
Switch the form on here and pick the first lead
“New leads only” starts from this moment. Or pick the first lead that did not reach the CRM after the old integration stopped: it and every later one are delivered, the earlier ones are not. You can go back 3 days at most.
- 4
Check the log
The first leads should read “Delivered”, with one record each in the CRM.
For the other ways to connect lead forms to Bitrix24, see the article on Facebook lead ads and Bitrix24.
Website forms
Which request reaches which CRM?
Lead-form leads reach all three CRMs. Requests from website forms reach Bitrix24 and capiCRM only: the site posts the request to the platform, in capiCRM it becomes a lead at once, and into Bitrix24 it is written through the same queue as Meta leads, with the retries and the Telegram alert.
| Where the request comes from | Bitrix24 | amoCRM | capiCRM |
|---|---|---|---|
| Facebook and Instagram lead form | Yes | Yes | Yes |
| Form on a website | Yes | No | Yes |
| What a lead-form request becomes | A lead, or a deal with a contact | A deal with a contact | A lead or a deal |
| Responsible person | The one you choose, or the CRM’s rule | The one you choose, or the CRM’s rule | The one you choose, or in turn |
The tracking code for a website keeps UTM tags and fbclid in the visitor’s browser for 90 days and adds them to the form as hidden fields; it reads no personal data. When the UTM tags of the visitor’s link name the ad, a website request arrives with its ad too.
Price
What does lead delivery cost?
It is not sold separately: it comes as a bonus inside the set-up price, then runs inside the monthly fee.
- oncethe CRM and Meta connected in 3 days; lead delivery included as a bonus
- $159
- a monthCAPI, the report, Telegram reports, lead delivery
- $40
- leads a monththe limit for lead delivery
- 4,000
All the terms are on the pricing page. If you expect more than 4,000 leads a month, write to us before the set-up.
More pages about leads
Bitrix24 integration
Lead → Deal mode, stages and the signals that go to Meta.
amoCRM integration
From the lead form to the deal: pipeline stages go back to Meta as signals.
capiCRM
No CRM yet? Leads land in the platform’s own CRM.
Telegram reports
A notice of each new lead, scheduled reports and alerts when something breaks.
Questions and answers
How fast does a lead reach the CRM?
At once when Meta’s webhook works. If the webhook does not arrive, the platform checks Meta for new leads every minute, so the lead is in the CRM in about a minute.
Which CRMs do Facebook and Instagram leads go to?
Lead-form leads go to Bitrix24, amoCRM (Kommo) and capiCRM. Requests from website forms go to Bitrix24 and capiCRM only; website requests are not sent to amoCRM. One project connects one CRM.
Are leads that came in before the form was switched on delivered too?
No. Leads are delivered only from the moment the form is switched on. The exception is a move from another integration: when switching on, you can pick one of the leads of the last 3 days as the starting point.
Can Albato or another integration keep running alongside?
Not for the same form: if both deliver it, every lead lands in the CRM twice. Switch the form off in the old integration first, then on in the platform. Different forms can be delivered by different services.
Is a lead lost if the CRM is down or the token has expired?
The lead stays in the queue and is sent again after 1, 5, 15, 60, 180, 720 and 1,440 minutes. A lead that waits 15 minutes raises an alert in Telegram. If it still has not reached the CRM after every attempt, it stays in the log as “Failed” and can be resent by hand within 7 days.
If one person submits the form twice, do both requests arrive?
Yes. Meta gives each submission its own lead ID and the platform delivers each one once; a repeat request is not dropped. When a deal is chosen, the second deal is attached to the same contact. In the report, one person’s requests are merged by phone.
Does the platform keep the leads’ data?
The form’s answers are kept encrypted for 7 days for retries, then erased. With Bitrix24 or amoCRM, a phone and an e-mail stay on the platform only as a hash and a partly masked number; capiCRM’s contacts are kept encrypted. If new-lead notices are on, the answers also go to the Telegram chat you connected. More in the privacy policy.
What does lead delivery cost, and is there a limit?
It has no price of its own: it is a bonus inside the one-time $159 set-up, then runs inside the $40 a month. The limit is 4,000 leads a month. The terms are on the pricing page.
Shall we connect your lead forms to the CRM?
Sign up and open your project yourself, or leave a request and we connect the CRM and Meta in 3 days.