Conversions API without a website: CAPI for lead forms and a CRM

Guides to the Conversions API tend to start from a website: Pixel, server, cookies. Many businesses have none: the ad opens a lead form, the request lands in a CRM, a manager closes the sale by phone. The Conversions API without a website is for exactly that case. Below: how CAPI for CRM lead ads works, what Meta asks for, the steps and the timing.

Does the Conversions API work without a website?

It does. The Conversions API does two jobs. CAPI for a website repeats through a server the events a Pixel sees, so it needs a site. CAPI for CRM sends an outcome that never happens on a site: a lead turned out qualified, a deal closed as a sale. A business on lead forms needs the second, and that one needs no site. More: what the Conversions API is.

How does Meta recognise the lead?

The key is the Meta lead ID. A lead form (Meta’s name: instant form) is filled in inside Facebook or Instagram, and Meta gives each submission a 15–17 digit number. Meta’s developer documentation says to store this ID for CRM events and, without it, to send a click ID, phone or e-mail. A website’s _fbp and _fbc cookies do not exist here and are not needed.

So the first condition: the lead must reach the CRM with its ID. In CAPI Platform lead delivery does that: the form’s lead is written into Bitrix24, amoCRM or capiCRM with name, phone and answers, tied to its ad. At the driving school, 1,790 leads from 5 lead forms reached the CRM between 25 September and 8 October 2026: queue 0, errors 0 — a measurement for those dates, not a guarantee.

Another service may deliver the leads instead: the platform then matches a CRM record to its form lead by the Meta lead ID or, failing that, by hashed phone or e-mail among form leads of the previous 72 hours.

What goes to Meta: the Meta lead ID, SHA-256 hashes of phone and e-mail, the event name and time; for a sale, amount and currency. A name is never sent. The event follows the shape of Meta’s CRM integration: action_source: system_generated, event_source: crm.

What is the signal: which CRM stage goes to Meta?

The signal is a stage change in the CRM. On the Funnel page each stage gets a meaning: new lead, qualified lead, sale or junk lead. When a lead enters a marked stage, the CRM’s webhook tells the platform, which sends the event to Meta at once.

Product screen · capip.uz

The lead form alone gives Meta only a lead count. A driving school, 2–8 October 2026: Meta counted 863 leads; that week the CRM recorded 335 qualified leads (39%) and 36 sales. Only the CRM knows which leads were good and who paid — the signal carries that to Meta.

Which stage to pick? Meta’s developer documentation gives a guide: 1–40% of leads should reach the stage, within 28 days. A stage every lead passes (“Contacted”) does not tell good leads from bad; one that fewer than one in a hundred reach gives too few examples.

What does Meta require and what does it recommend?

Meta’s developer documentation calls optimising a lead-form campaign on CRM events Conversion Leads; its newer “Conversions API for CRM” page speaks of the “maximize number of qualified leads” goal. Neither page asks for a website: the optimisation is described for instant forms.

The set-up covers the technical rows: CAPI Platform sends an event the moment a stage changes, and takes the lead ID from the form. Volume and the choice of stage stay with the business.

What result has Meta itself reported?

In a test Meta has published, campaigns that used the Conversions API for CRM and optimised for the number of qualified leads on instant forms had a 19% lower cost per quality lead on average. It was a budget-controlled A/B test: 567 advertisers, 13–27 January 2025. Source: Meta — Conversions API for CRM.

Instant forms are exactly the no-website case. But the figure was measured on other advertisers: it is neither a CAPI Platform result nor a guarantee. Nor is sending the signal enough: the campaign has to be optimised for qualified leads, not for lead count.

How do you set up the Conversions API without a website?

No developer is needed — only access to the CRM and the Meta ad account. In CAPI Platform the order is:

1. 1

   Connect Meta

   Enter a System User token and the Dataset (Pixel) ID. The platform checks the token’s permissions on the spot; reading lead forms needs leads_retrieval.

2. 2

   Connect the CRM

   Bitrix24 needs an inbound webhook URL, amoCRM a long-lived token. With no CRM, use the platform’s own, capiCRM. The last 30 days of history load into the report; old leads are not sent to Meta.

3. 3

   Switch on the lead forms

   For each form, choose the pipeline and stage its leads land in. Delivery starts from the moment of switching on. Turn the previous integration off, or each lead lands twice.

4. 4

   Tie stages to signals

   On the Funnel page, mark which stage is a new lead, which a qualified lead and which a sale. Lead, QualifiedLead and Purchase follow from that.

5. 5

   Send a test event

   The “Send a test event” button sends Meta one harmless event and shows that the token, dataset and path work. A Test event code field serves checks in Events Manager.

6. 6

   Teach the campaign quality

   In Ads Manager, create a custom conversion from the QualifiedLead event and optimise the lead-form campaign for it. Without that the signal reaches Meta while the campaign still chases lead count.

Every signal stays in the log with its time, event and status. A failed one is retried at intervals from 1 minute to 24 hours.

Product screen · capip.uz

When will CAPI show a result, and how do you measure it?

So judge no earlier than a month in, and by cost per qualified lead, not cost per lead.

Cost per lead may rise — that is not a bad sign. In that week a creative with 79 leads at $0.87 brought no sales, while one with 77 leads at $1.28 brought 5.

CAPI does not fix CRM discipline: if managers do not move leads through the stages, there is no signal. A lead with no phone, e-mail, Meta lead ID or fbclid is skipped, and the log shows why.