Conversion leads optimization is the qualified leads goal, which Ads Manager calls Maximize number of qualified leads. You set it in a Leads campaign, and it only works if your CRM sends every lead stage back to Meta through the Conversions API, at least once a day, so the system can learn which people turn into real conversations. The setup is five decisions, and the one people skip is the first: writing down what “qualified” means before any data leaves your CRM.
What the goal changes
Meta’s article on performance goals for lead ads describes the difference in one sentence each. Maximize number of leads shows the ad to people in your audience who are most likely to share their contact information. Maximize number of qualified leads shows it to the people most likely to convert after sharing it.
That second instruction is only possible if Meta knows what happened after the submit. It cannot infer it from a form. Each time a lead moves stage, new, contacted, qualified or won, your CRM has to tell Meta, using the lead’s identifier, through the Conversions API.
So the goal does not improve your leads by selecting a better audience in the abstract. It improves them because the audience is now defined by outcomes you reported. If your CRM reports nothing, the goal has nothing to learn from, which is why Meta made the CRM integration a requirement rather than an option: from April 2026 the goal is not available on new campaigns without it, and existing campaigns were affected from August 2026.
What you need before you start
Meta’s integration guide sets the bar in a short list of requirements:
| Requirement | Meta’s guideline |
|---|---|
| Conversions API integration | required, sending lead stages from your CRM |
| Upload frequency | at least once per day |
| Timing of the stage you optimize for | within 28 days of the lead |
| Conversion rate of that stage | between 1% and 40% |
| Matching key | the 15 to 17 digit Meta lead ID, or click ID, phone or email if you do not have it |
| Lead volume | at least 200 leads a month in the integration guide; Meta said on 30 October 2025 that the minimum monthly volume is being removed |
| Time to value | about a month, including two to four weeks of training |
The conversion rate range is the one that surprises people. If the stage you pick happens for one lead in a hundred, or for most of them, it falls outside what the system can learn from. A stage that nearly every lead reaches teaches nothing about who is different.
Step 1: define qualified in a way you can count
Pick one event that stands for a real sales opportunity, and keep the definition fixed for the life of the campaign. Budget confirmed, area served, a booked appointment, a passed phone screening: any of these works, as long as your sales team applies the same rule every time.
Then check the arithmetic. Take last month’s leads, count how many reached that stage, and divide. If the answer sits inside the 1% to 40% band, the stage is usable. If it is far below, pick an earlier stage. If it is far above, pick a later one.
Two things to avoid. Do not change the definition mid-flight, because the system’s history then describes two different events. And do not use a stage that only your best salesperson records, because the count becomes a measure of your team’s discipline rather than of lead quality. Facebook lead quality sets out the three rates that make this decision easier.
Step 2: make sure every lead carries its ID
Before choosing a CRM integration, check one column in your lead records. The join between your CRM and Meta runs on the lead identifier, and Meta’s guide to finding the lead ID lists where each route puts it:
| Route | Meta lead ID stored? |
|---|---|
| Webhook or Graph API | yes, in the lead’s id field |
| Zapier or LeadsBridge | yes, in the id field, if you map it |
| Make | yes, in the Lead ID field, if you map it |
| Salesforce Lead Capture | yes, in the Lead ID field, map it to a custom field |
| HubSpot Lead Sync | no |
| Zoho CRM social integration | no |
| Microsoft Dynamics | no lead ads integration at all |
| Manual file | first column, id, possibly with a label to strip |
If your CRM is in the lower half of that table, you can still run the goal, using email or phone as the key. Expect a worse match rate, and expect duplicates when two people share a number. The clean fix is a route that keeps the lead ID: a webhook you build, or middleware that lets you map the field.
Step 3: build the stage events
The event you send is the stage, with the lead identifier and the time it happened. Two rules make the difference between data Meta can use and data it discounts:
- send the same event names every time, so the system sees a consistent series rather than a handful of one-off names;
- send the stages in order, so a lead that jumps from new to won still reports the stages in between, dated when they happened.
Meta’s own guidance is to upload at least once per day, and near real time is better: a stage sent three days after it happened describes a lead that has already been called.
If you have no engineering time, this is where the CRM integration earns its place. Several CRMs have a native lead ads connection, and Meta keeps a searchable directory of them in the Instant forms section of Meta Business Suite. Setting up the Conversions API covers the event payload, the identifiers and the deduplication rules.
Step 4: pick the goal in the ad set
In Ads Manager, create a campaign on the Leads objective, then open the ad set. In the Conversion section, choose the conversion location the leads come from, Instant Forms or Website, and then set the performance goal to Maximize number of qualified leads.
If the goal is greyed out, the cause is almost always upstream: the pixel or the CRM connection that the ad account expects is missing, or the campaign was duplicated from one that never had it. Rebuilding the ad set from a fresh Leads campaign is faster than hunting for the switch.
Then leave the learning phase alone. Meta’s threshold for exiting it is about 50 optimisation events per ad set per week, and with a qualified-leads goal your optimisation event is now the stage, not the submit. A campaign that produced 50 leads a week may produce far fewer qualified events, so it can sit in learning longer. That is arithmetic, not a fault, and the answer is fewer ad sets rather than more budget.
Step 5: judge it on your own numbers
Meta’s help centre reports 21% lower cost per quality lead for Instant Forms with a CRM integration, compared with the volume goal. That is Meta measuring Meta against its own volume goal, and it belongs in a plan as a reason to test, not as a forecast.
The comparison that matters is your cost per qualified lead before and after, on a stage you defined yourself. Keep three columns per ad and per landing page: leads received, qualified leads, and spend. Then the goal’s effect shows up as a change in the ratio rather than in the lead count.
Two caveats make the comparison honest. The first is the compatibility gap: Meta’s integration guide says the goal is currently compatible only with Instant Forms, while Meta’s help centre says it works with website forms and instant forms too, so check what your account shows before you plan a landing page campaign around it. The second is the training month. Judge the change after the system has had its two to four weeks.
When the goal is not the right answer
If you cannot send stages back yet, Meta’s advice is implicit in the requirement: use Maximize number of leads and do the qualification work yourself. That is not a downgrade. Cutting creatives on cost per qualified lead, computed from your own CRM, gives the same decision without waiting for the system to learn.
The other case is volume. A campaign with 60 leads a month has too little to train the stage model on, whatever Meta’s threshold says. In that range the manual routine is more reliable: contact rate, qualification rate, and the same numbers split by ad and by landing page. All the Meta lead ads questions covers the form side, and the objectives guide shows where this goal sits among the others.