What Does Advantage+ Audience Control, and What Does It Ignore?
The expanded audience treats most of your targeting as a starting point. Meta names four constraints it keeps: location, minimum age, language and custom audience exclusions. Its Marketing API page says the setting lets Meta "expand the eligible audience pool the delivery system can search, subject to your non-negotiable constraints", and that "These constraints include location constraints, minimum age, language, and custom audience exclusions" (Advantage+ audience, Meta for Developers).
Age works differently from what many advertisers expect. The same page says that with Advantage+ audience on, "you can pass age_min values ranging between 18 and 25 only", "you cannot set age_max values" and "age_max is fixed at 65". So a buyer profile of 35 to 55 cannot be enforced as a hard limit.
| Setting | With Advantage+ audience | Source |
|---|---|---|
| Location | Honoured as a constraint | Meta Marketing API page linked above |
| Minimum age | Honoured, but only 18 to 25 | Meta Marketing API page linked above |
| Maximum age | Cannot be set, fixed at 65 | Meta Marketing API page linked above |
| Language | Honoured as a constraint | Meta Marketing API page linked above |
| Custom audience exclusions | Honoured as a constraint | Meta Marketing API page linked above |
| Detailed targeting and lookalikes | Not listed as a constraint | Meta Marketing API page linked above |
Meta treats the constraints above as limits. Other targeting inputs guide delivery but are not listed as limits, so assume delivery can go beyond them.
That is the design, and it explains most Facebook ads low quality leads complaints. If the campaign rewards any form fill, a wider pool means more cheap fills from people who were never your buyer.
Advantage+ Audience vs Original Audience: When Should You Switch Back?
Switch an ad set back to original audience when you need a hard maximum age or a hard detailed-targeting limit, for example a regulated offer with a strict age band. Otherwise, try two changes first. Raise the minimum age as far as 25 if your buyer is older. Then add a custom audience exclusion built from known junk leads and existing customers. Neither change is a promise of better results. Both narrow who delivery may reach, and both are limits Meta says it keeps. If junk clusters in one placement, it may also be worth reading how to exclude Audience Network on lead campaigns.
Low-Intent People or Bots: How to Tell Which Advantage+ Audience Bad Leads You Have
Sort your bad leads before you fix anything, because low-intent people and bots need different fixes. The table below is our own triage checklist, built from signals you can observe in your CRM and reports. It is not data, and no single row proves anything on its own.
| Signal | Low-intent human | Bot or scripted | Mistaken tap |
|---|---|---|---|
| Contact details valid | Usually yes | Often fake, malformed or random | Yes, often pre-filled |
| Answers the phone | Sometimes, then shows no interest | Never, or the number is not real | Sometimes, does not remember the ad |
| Duplicate phone or email across leads | Rare | Common, often in bursts | Rare |
| Disposable email domains | Rare | Common | Rare |
| Answer to a custom question | Real but vague or off-target | Nonsense, copied or identical across leads | Blank-looking or default choices |
| Time from click to submit (landing-page forms only) | Normal reading time | Implausibly fast or perfectly regular | Fast, then abandons follow-up |
| Placement concentration | Spread across placements | Concentrated in one placement or app | Concentrated in low-attention placements |
| Geography outside your area | Occasional | Clusters from places you do not serve | Occasional |
Read the table as a pattern match. If the details are real but nobody buys, you have a signal problem, and the next three sections fix it. If the details are fake, repeated, or arrive in bursts, you have a traffic problem, the same pattern behind fake leads in Google Ads. It needs protection on your site and stricter checks in your CRM.
Mixed accounts are normal. A campaign can produce both kinds in the same week, so tag each bad lead with a reason in your CRM rather than one generic "junk" label. Those tags become the evidence for every decision that follows.
Which Meta Lead Quality Signals Can You See in Ads Manager and Your CRM?
Ads Manager shows you cost and volume. Your CRM shows you quality. You need both, compared weekly.
In Ads Manager, start with results and cost per result by ad set. Then break results down. Meta's Insights API documents breakdowns for age, region, the platform an ad ran on, which includes Audience Network, and the position within it, such as Facebook desktop Feed or Instagram Mobile Feed (Breakdowns, Meta for Developers). Breakdowns tell you where cheap leads come from. They cannot tell you which of those leads were any good.
For campaigns that send people to a website form, compare link clicks with landing page views first. A wide gap points to clicks that never loaded your page, and we cover that test in link clicks vs landing page views.
In your CRM, track four rates per campaign and ad set:
- Contact rate: the share of leads you reach by phone or email.
- Qualified rate: the share sales accepts as real prospects.
- Duplicate rate: the share that repeats an existing phone or email.
- Time to first contact: how long leads wait, because slow follow-up makes good leads look bad.
Then track one gap: Meta-reported leads against CRM-accepted leads, each week. There is no good universal ratio. Compare against your own baseline, and look for ad sets where the gap widens after a change.
How to Set Up the Conversion Leads Performance Goal
The conversion leads performance goal lets Meta judge lead quality from what happens to a lead in your CRM, not just from the form fill. Your CRM sends those outcomes through the Conversions API (CAPI). If you are working out how to improve Meta lead quality when leads are real but low-intent, this is the main fix, as long as your account qualifies.
Meta's developer pages disagree on whether the conversion leads performance goal supports Website Forms: the main integration page says Instant Forms only, while its FAQ lists both (checked 9 November 2026). The main page says: "The Conversion Leads performance goal is currently only compatible with Facebook/Instagram's Lead Ads (Instant Forms)" (Conversions API for CRM integration, Meta for Developers). The FAQ says to "Use native lead ads (Instant Forms or Website Forms)" (Conversions API FAQ, Meta for Developers). So check whether the goal appears for your campaign in Ads Manager.
The main page then lists four fit checks. You should:
- "Generate at least 200 leads per month"
- Upload CRM data at least once per day.
- Make sure "The lead stage you want to optimize for occurs within 28 days after you generate the leads"
- Make sure "The lead stage you want to optimize for has a conversion rate between 1% and 40%."
The setup runs in this order:
- 1. Connect the CRM. Your CRM must already download leads from Meta. Then connect it back to Meta through the Conversions API CRM integration, by your own code or a partner connector.
- 2. Let Meta validate the data. Meta validates your uploaded data, which takes about 1 to 2 days, before you configure the funnel.
- 3. Configure the sales funnel. Order your stages and remove ones that do not signal a quality lead.
- 4. Pick the optimization target. Meta's funnel page says to "select the earliest lead stage to optimize for" (Configure your sales funnel, Meta for Developers).
- 5. Turn on the goal. Meta says you may "enable the Conversion Leads optimization in the Optimization and Delivery menu of Ads Manager" (Follow-up steps, Meta for Developers).
Set expectations on timing, because Meta gives two figures. The follow-up steps page describes "a 2-4 week learning phase before the model finishes training with your data". The FAQ says there is "a training period of 1-2 months before your integration is added to the production model". The figures differ, so plan for the longer one. Both pages warn against changing pixels. The follow-up page says: "Changing pixels restarts the training process."
What If You Are Under 200 Leads a Month?
Our view: do not wait idle. Fix data quality first, so every lead in your CRM carries a stage and a reason tag. Start sending stages to Meta anyway, so the integration is built and tested when volume arrives. Meanwhile, tighten the limits Meta keeps from the first section: minimum age and custom audience exclusions. Meta's pages do not say what the goal does below the threshold, so we make no claim about it.
Send CRM Lead Stages Back Through the Conversions API
Meta says it optimizes for the stage you select and all down-funnel stages, so it needs to receive every stage, not just the form fill. The Meta Conversions API carries those CRM events back to the ad account.
Meta's payload specification says to "send all stages as they are updated, including the initial lead stage" (Payload specification, Meta for Developers). The event_name field is free form, so it can match your CRM stage names. The FAQ adds a floor: at least two stages, and "use at least three stages if possible".
The same specification fixes several values:
| Field | Where it sits | Value Meta requires |
|---|---|---|
| event_name | Top level | Your CRM stage name |
| event_time | Top level | Unix seconds when the stage changed. Up to 7 days before you send, and after the lead was created |
| action_source | Top level | system_generated |
| lead_id | Inside user_data | The 15 to 17 digit Meta lead ID from the leadgen_id webhook field |
| event_source | Inside custom_data | crm |
| lead_event_source | Inside custom_data | The name of your CRM |
On the funnel side, Meta's wording is: "The system optimizes for all down-funnel stages as well." It also says the system "may adjust and optimize for a different lead stage than the one you selected" if that performs better. So the earliest stage that signals quality is the safer target, as long as it meets the 28-day and 1% to 40% rules.
Example: One Lead Through Three CRM Stages
This is an illustrative example, not a real lead. A lead arrives from an Instant Form on day 1 and your CRM records the stage Lead. You send that event the same day. On day 4, sales speaks to the person and moves them to Qualified. On day 10, the deal closes and the stage becomes Closed won. Each change is its own event, sent within a day.
Here is the Qualified event, with placeholder values and the nesting copied from Meta's example payload. Meta receives this object inside the data array of the request.
{
"event_name": "Qualified",
"event_time": 1793000000,
"user_data": {
"lead_id": 1111111111111111
},
"action_source": "system_generated",
"custom_data": {
"lead_event_source": "YourCRM",
"event_source": "crm"
}
}
If you optimize for Qualified, the junk leads that never reach that stage stop counting as wins. Meta says it optimizes for the stage you select and all down-funnel stages, so Qualified and Closed won are the events that shape delivery.
Web conversions are a separate stream. See fraud-filtered CAPI conversions for pixel and server events.
What ClickFortify Covers on the Landing-Page Path, and What It Cannot See
ClickFortify scores sessions that reach your site on 100+ device, network and behavior data points and flags suspicious conversions. With the CAPI proxy on, flagged events are dropped or tagged before Meta receives them. It cannot see Instant Form submissions, and Meta does not let advertisers exclude IP addresses, so the levers are the ones above.
For the form itself, Meta's higher-intent form adds a step where people review and confirm their answers before submitting (Create lead ads, Meta for Developers). We cover form-level fixes for fake leads on Meta lead ads. If you also run Advantage+ sales campaigns, that page explains how protection works for them.
A word on our limits as writers. We did not test this in an ad account. Everything here about Meta's behavior comes from Meta's documentation, and Meta's own pages disagree on website forms and on learning time. The conversion leads performance goal works best with volume, and Meta's fit guidelines start at 200 leads a month.
ClickFortify has a 7-day free trial, and no credit card is required.
