Qualified
It passes every test and describes the buyer. Optimise for it and keep demos and opportunities for reporting.
Guide · Meta Ads lead quality
Meta Conversion Leads optimisation: sending CRM stages through the Conversions API
Conversion Leads is Meta’s version of optimising to the earliest signal that predicts value. Meta forces the choice: the stage must happen within 28 days and be reached by 1–40% of leads. In a 90-day B2B cycle you have to pick a proxy, and it has to reflect buyer quality, not sales activity.
Short answer
Conversion Leads is a performance goal for Meta lead ads that optimises delivery towards people likely to reach a later stage in your sales process, not just submit a form. You send lead stage updates from your CRM to Meta through the Conversions API, matched by Meta’s lead ID, so the system learns which leads mattered.
How it works: lead ID, CRM stage, Conversions API, delivery
- A lead arrives through a Meta Instant Form and carries a Meta lead ID.
- The lead lands in your CRM with that lead ID stored against the record.
- Sales updates the stage: qualified, meeting held, opportunity, lost.
- The stage is sent to Meta through the Conversions API at least daily, matched by lead ID.
- Delivery adjusts towards people who resemble leads that reached the stage you optimise for.
The standard Leads goal, by contrast, optimises for form submissions. Both use the same forms; only Conversion Leads learns from what happened after the form. Meta describes the goals in about performance goals for lead ads.
Eligibility
What are the requirements for the Conversions API for CRM?
Short answer
Meta’s developer documentation asks for at least 200 leads a month from Instant Forms. The stage you optimise for should be reached by 1–40% of leads within 28 days of lead creation. You also need to upload stage data at least daily and keep Meta’s lead ID in your CRM.
| Requirement | What it means | How to check yours |
|---|---|---|
| 200+ leads a month | Enough form volume to learn from | Leads per month from Instant Forms, by account |
| Stage reached by 1–40% of leads | The stage separates good leads from the rest | Stage count divided by lead count for recent months |
| Stage within 28 days | Outcomes arrive while they can still steer delivery | Median days from lead to stage |
| Daily uploads | Fresh signals | Integration schedule and last upload time |
| Lead ID stored | Meta can match the stage to the lead | Share of CRM leads with a Meta lead ID |
Migration
Is the Offline Conversions API still available?
Short answer
Meta calls it its legacy API for offline events, and points offline and CRM uploads to the Conversions API using datasets. If an older integration uploaded offline event sets, check that it has moved to the Conversions API and that events are still being accepted in Events Manager.
Meta documents offline events through the Conversions API in its developer documentation. The usual symptoms of an unmigrated integration are an event set that stopped receiving events and a Conversion Leads goal that can’t find recent stage data.
Original framework
Which CRM stage should a B2B company send to Meta?
Short answer
Send the deepest stage that most qualifying leads reach within 28 days, that 1–40% of leads reach, and that reflects buyer fit rather than sales activity. For long cycles that is usually a defined “qualified” stage, not “contacted”, which measures rep effort, or “closed-won”, which arrives too late.
| # | Test | Pass when |
|---|---|---|
| 1 | Timing | Most leads that reach the stage do so within 28 days |
| 2 | Rate | Between 1% and 40% of leads reach it |
| 3 | Volume | The account produces 200+ Instant Form leads a month |
| 4 | Buyer fit | The stage describes the buyer (size, need, authority), not what a rep did |
| 5 | Consistency | A written definition applied the same way by every rep and market |
| 6 | Prediction | In a past cohort, leads at this stage became opportunities more often |
Pick the deepest stage that passes all six. The cross-platform argument is in the signal gap.
Worked numbers
An Indian B2B SaaS company with 500 Instant Form leads a month
₹4,00,000 a month on Meta lead ads, so ₹800 per lead.
| Stage | Share of leads | Per month | Median days | Result |
|---|---|---|---|---|
| Contacted | 70% | 350 | 1 | Fails: above 40%, and it measures rep effort |
| Qualified (fits target size and need) | 20% | 100 | 6 | Passes all six: cost per qualified lead ₹4,000 |
| Demo held | 9% | 45 | 19 | Borderline: a large share of demos arrive after 28 days |
| Opportunity | 3% | 15 | 41 | Fails timing |
Qualified rate and cost per qualified lead
Compare equal periods after the goal has had time to learn. Don’t judge on cost per lead, which may rise.
Two other accounts
A UAE industrial trader with 120 leads a month is below the threshold. A US consultancy with 300 leads and 18% booking a consultation within 10 days passes.
Setting it up
- Get leads into the CRM with the lead ID. Use Meta’s CRM integrations or a connector so every Instant Form lead arrives with its lead ID (Meta Business Help).
- Define the stage field. Write down what each stage means and who sets it.
- Send stages daily. Use a direct Conversions API integration or a connector that supports the Conversions API for CRM.
- Create the campaign. In Ads Manager, use the Leads objective with an Instant Form and choose the Conversion Leads performance goal.
- Verify receipt. Check Events Manager for stage events and match rates before judging delivery.
If you have fewer than 200 leads a month
- Use a higher-intent form with one qualifying question, so the leads you do get are better.
- Consolidate campaigns to pool leads rather than splitting them across many small ad sets.
- Record stages by lead ID now, even in a spreadsheet, so history exists when volume grows.
- Judge cost per qualified lead manually each month, and revisit eligibility.
For form design, see junk leads from Instant Forms, and check whether Meta fits your funnel with the Meta B2B fit and signal check.
Failure modes
Why Conversion Leads underperforms
| Failure | What happens | Fix |
|---|---|---|
| Lead IDs missing | Stages can’t match to leads | Fix the lead retrieval integration first |
| Stage defined by rep activity | Meta learns who reps called, not who buys | Use a buyer-fit stage |
| Weekly batch uploads | Signals arrive late and in bursts | Upload at least daily |
| Definitions drift by rep or market | The same lead is qualified in one place and not another | Written definitions and a monthly spot check |
| Switching goals mid-learning | Delivery never stabilises | Hold edits until results settle |
| Blaming the goal for a form or creative problem | The wrong fix | Check form friction and message match too |
Conversion Leads doesn’t decide what to change
Sending stages back helps Meta’s delivery. Someone still has to decide which creative, form, audience and budget changes to make, and whether Meta deserves more budget than Google or LinkedIn. That is the job of lead quality optimisation. Zephra sends CRM lead stages to Meta through the Conversions API, where configured, and labels each finding: act, review, investigate or wait (how it works).
Google and LinkedIn equivalents
- Google Ads: enhanced conversions for leads with qualified and converted lead goals, uploaded within 63 days. See offline conversion import.
- LinkedIn Ads: qualified-lead events through the LinkedIn Conversions API, shared within 30 days for qualified leads optimisation. See LinkedIn Ads for B2B.
India, UAE and US notes
- India: leads qualified over WhatsApp must be written back to the CRM record with the lead ID, or Meta never sees them. The DPDP Act requires notice and consent for sharing lead data.
- UAE: lower lead volumes are common, so the below-threshold path often applies. The UAE PDPL governs lead data outside DIFC and ADGM.
- US: honour state privacy opt-outs before sending lead data, and keep follow-up calls and texts TCPA-compliant.
What to measure next
- Share of leads with a stored lead ID.
- Upload freshness: hours since the last stage upload.
- Qualified rate and cost per qualified lead.
- Median days to the chosen stage, and its later opportunity rate.
Questions, answered
Conversion Leads FAQ
01Can Conversion Leads work with website leads?
Meta’s documentation for the Conversions API for CRM covers Instant Form leads for Conversion Leads optimisation. Website leads can still send events through the Conversions API, but check Meta’s current documentation, because supported lead sources can change.
02What if more than 40% of leads reach my stage?
The stage doesn’t separate good leads from the rest. Choose a deeper stage that fewer leads reach, as long as it still happens within 28 days.
03Do I need a CRM?
You need somewhere that stores each lead’s Meta lead ID and sends stage updates at least daily. A spreadsheet can hold the history, but daily sending normally needs an integration or connector.
04Does Conversion Leads fix junk leads on its own?
No. It changes who Meta shows ads to, but form friction, qualifying questions and message still decide who submits. Pair it with a higher-intent form.
05Is the Conversions API for CRM free?
Meta doesn’t charge for the Conversions API itself. Connectors, CRM add-ons or development time may cost money.
06How long before results change?
Meta needs time to learn from the stage data, so allow at least a few weeks and avoid other edits meanwhile. Judge on qualified rate and cost per qualified lead, not cost per lead.
Your account
Check whether your Meta account and lead data are ready.
The free assessment covers measurement gaps across Meta, Google and LinkedIn in 10–15 minutes, with no CRM required and no campaign changes.