QualimizeQualimize
FeaturesHow it worksQualified leadsMeta CAPIComparePricingResourcesContact
LoginBook 1:1 Demo
QualimizeQualimize

The CRM for teams running Meta Ads. Capture every lead, record what your sales team finds, and send those outcomes back to Meta.

+91 94997 11011WhatsApp us

Address

Sama Savli Road, Vadodara,
Gujarat, 390008

Product

  • Features
  • Pricing
  • Product tour
  • How it works
  • Qualified leads
  • Meta CAPI
  • For agencies
  • Partner program

Industries

  • All industries
  • Real estate CRM
  • Travel CRM
  • Education CRM
  • Visa consultancy CRM
  • Healthcare CRM
  • Solar CRM
  • Marketing agencies

Compare

  • All comparisons
  • vs Zoho CRM
  • vs LeadSquared
  • vs TeleCRM
  • vs Privyr
  • vs GoHighLevel
  • vs HubSpot
  • vs Salesgem
  • vs FlowZo
  • LeadSquared alternatives
  • GoHighLevel alternatives
  • Privyr alternatives

Company

  • About
  • Contact
  • What's new
  • Pricing
  • Login

Legal

  • Security & data
  • Privacy policy
  • Terms of service
QualimizeQualimize

The CRM for teams running Meta Ads. Capture every lead, record what your sales team finds, and send those outcomes back to Meta.

+91 94997 11011WhatsApp us

Address

Sama Savli Road, Vadodara,
Gujarat, 390008

Product

  • Features
  • Pricing
  • Product tour
  • How it works
  • Qualified leads
  • Meta CAPI
  • For agencies
  • Partner program

Industries

  • All industries
  • Real estate CRM
  • Travel CRM
  • Education CRM
  • Visa consultancy CRM
  • Healthcare CRM
  • Solar CRM
  • Marketing agencies

Compare

  • All comparisons
  • vs Zoho CRM
  • vs LeadSquared
  • vs TeleCRM
  • vs Privyr
  • vs GoHighLevel
  • vs HubSpot
  • vs Salesgem
  • vs FlowZo
  • LeadSquared alternatives
  • GoHighLevel alternatives
  • Privyr alternatives

Company

  • About
  • Contact
  • What's new
  • Pricing
  • Login

Legal

  • Security & data
  • Privacy policy
  • Terms of service

© 2026 Qualimize. All rights reserved.

Better signals in. Better customers out.

Back to blog
Meta CAPI & Tracking

Meta's Conversion Leads Goal Explained: Requirements and When to Switch

What Meta's Conversion Leads performance goal is, the five requirements Meta lists (200 leads a month, daily uploads, a stage within 28 days, a 1% to 40% conversion rate), the payload fields it needs, and when switching makes sense.

Written by Qualimize Team

Founder, Qualimize

Published
November 16, 2026
Last updated
November 16, 2026
Reading time
11 min read
META CAPI & TRACKING4 5REQUIREMENTS METInstant Forms200+ leads/moDaily uploadStage in 28 days

Table of contents

  1. 01 The short answer
  2. 02 What the goal actually does
  3. 03 The five requirements, in Meta's words
  4. 04 What data the integration needs
  5. 05 When switching makes sense
  6. 06 When to stay on standard optimisation
  7. 07 Checking your setup before you switch
  8. 08 What changes for your sales team

Full article

The short answer

Conversion Leads is a performance goal for Meta Instant Form campaigns that optimises for leads likely to reach a sales stage you choose, using lead stage data sent from your CRM. Meta lists five requirements: Instant Form lead ads, at least 200 leads a month, CRM data uploaded at least once a day, a target stage reached within 28 days of the lead, and a stage conversion rate between 1% and 40%. Switch when you meet all five and your problem is lead quality rather than lead volume.

If you do not meet them yet, the standard approach of sending CRM stages as Conversions API events still gives Meta useful feedback. This guide explains both, and the exact data the Conversion Leads integration expects.

What the goal actually does

A normal Instant Form campaign optimises for form submissions. Meta looks for people likely to fill in the form, and it has no idea whether those people ever answer a call. That is why cheap leads so often turn out to be poor leads.

Conversion Leads changes the target. You tell Meta which CRM stage counts as a good outcome, your CRM keeps sending stage updates for each lead, and Meta uses that history to favour people who look like the leads that reached the stage. The campaign still produces Instant Form leads; Meta just chooses whom to show the ad to differently.

Because the goal learns from your own stage data, it can only be as good as that data. A team that updates statuses late, or applies them inconsistently, will teach the system the wrong lesson.

It also changes what a good result looks like. Under standard lead optimisation, success is more leads for less money. Under Conversion Leads, success is more leads reaching your chosen stage for the money spent, even if the raw lead count falls. Agree on that measure with whoever runs your ads before you switch, or the first week's higher cost per lead will be read as failure and the test will be switched off before it has had a chance to learn.

The five requirements, in Meta's words

Meta's Conversion Leads documentation lists the conditions an advertiser should meet. They are worth reading closely, because each one rules out a common type of business.

The 200 leads a month requirement rules out very small campaigns. The daily upload rules out teams that update the CRM once a week. The 28-day window rules out businesses with long sales cycles, unless they pick an earlier stage. The 1% to 40% conversion rate rules out stages that are either too rare (such as final sale for a high-ticket product) or too common (such as Contacted, if nearly everyone is reached).

  • Use Facebook or Instagram Instant Form lead ads; Meta says these are the only lead type compatible with the goal
  • Generate at least 200 leads per month
  • Upload CRM data at least once a day
  • The stage you optimise for happens within 28 days of the lead being generated
  • That stage has a conversion rate between 1% and 40%

What data the integration needs

Meta publishes a payload specification for Conversion Leads events, and it differs from a standard Conversions API setup in a few important ways.

event_name is a free-form field for the stage names you use in your CRM, and Meta asks you to send all stages as they update, including the raw lead stage. event_time is the Unix time the stage was updated, no more than 7 days before the event is sent and after the lead was generated. action_source must be system_generated. Two custom_data fields are required: event_source set to crm, and lead_event_source set to the name of the CRM the data comes from (Meta's examples include HubSpot, SAP and Oracle).

For customer information, Meta lists the lead_id from leadgen_id as optional but in its highest priority group, alongside the click ID and hashed email, and says that if you send a lead_id it must be valid or the event is rejected. You must send at least one customer information parameter.

When switching makes sense

Switch when three things are true at once: you meet all five requirements, your sales team says the main problem is lead quality rather than lead quantity, and your CRM data has been clean and timely for at least a few weeks.

Example: a Jaipur coaching centre gets around 600 Instant Form leads a month across courses. Reps update statuses the same day, and about 15% of leads attend a demo class within two weeks. That stage fits every requirement, so it is a reasonable candidate to test Conversion Leads against.

Example: a Pune developer selling ₹1.2 crore apartments gets 250 leads a month, but bookings happen 45 to 90 days after the lead and fewer than 1% of leads book. The booking stage fails two requirements. An earlier stage, such as site visit done within 28 days, might qualify instead.

When to stay on standard optimisation

Stay where you are if you are below 200 leads a month, if your team cannot commit to updating statuses daily, or if your best stage happens too rarely or too late. Forcing the goal onto thin or late data does not help it learn.

Also stay if most of your leads come from your website rather than Instant Forms. Conversion Leads only works with Instant Form campaigns, so a business whose best leads come through landing pages would be optimising its smaller channel. For those leads, standard Conversions API events with the captured click ID and hashed contact details are the route.

Staying does not mean doing nothing. Sending Contact, Lead, SubmitApplication and Purchase through the Conversions API still lets Meta see which ads produce reached, interested and paying leads, and it lets you report cost per qualified lead by campaign in your own CRM. When your volume and data quality grow, you can revisit Conversion Leads.

When you do switch, run it alongside your existing campaign rather than replacing it outright, and judge it on cost per qualified lead over several weeks, not on cost per lead in the first few days. Fewer, better leads at a higher cost per lead can be a good result.

Checking your setup before you switch

Meta's CRM implementation guide gives a simple sequence: send test events with a test event code and a valid lead_id, confirm they appear in the Test Events tab, then upload for real and confirm the events appear in Events Manager, which Meta says should happen within an hour when uploads are working.

Look for the custom parameters event_source and lead_event_source on the events. Without them, the events are not recognised for Conversion Leads, even if they show up as received. Also check the stage names you send are the same every time; a stage spelled two ways becomes two stages.

Remember the backfill rule while you test. Meta's guide says you can backfill data for up to 7 days in the past and warns against changing event_time values to squeeze in older data, which may cause the backfilled data to be discarded. Start sending live, and let history build forward.

What changes for your sales team

Conversion Leads is usually discussed as an ads setting, but most of the work lands on the sales team. The goal learns from stage updates, so the timing and honesty of those updates become part of your media buying.

Three habits matter. Reps must update status the same day they speak to a lead, because Meta asks for at least daily uploads and an update made a week late teaches the system about last week. Every rep must apply the target stage the same way, because a stage that means site visit done for one rep and site visit promised for another blurs the signal. And leads must not be skipped: a lead that is never updated looks to Meta like a lead that never progressed.

Example: a Pune broker's team of four agrees that the target stage is Site Visit Done, marked only after the visitor has seen the property in person. The manager checks the overdue follow-up list each morning so no lead sits untouched for more than a day. That routine is what makes the data good enough for Conversion Leads to learn from.

If your team cannot keep those habits yet, fix that first. It will improve your reporting and your standard CAPI feedback straight away, and it is the groundwork Conversion Leads needs later.

Comparison tables

Standard CAPI stage events vs the Conversion Leads integration

Standard CAPI stage eventsConversion Leads integration
event_nameMeta standard events (Contact, Lead, SubmitApplication, Purchase)Free-form CRM stage names
action_sourcesystem_generated is typical for CRM eventsMust be system_generated
Required custom_dataNone (value and currency on Purchase)event_source = crm and lead_event_source
Lead IDRecommendedHighest-priority group; must be valid if sent
Volume neededNone to send eventsAt least 200 leads a month
What Meta optimises forYour chosen optimisation eventLeads likely to reach your chosen CRM stage

Quick readiness check

RequirementPass ifCommon reason it fails
Lead typeInstant Form lead adsLeads come from a website form
Volume200+ leads a monthSmall or seasonal campaigns
Upload frequencyAt least dailyStatuses updated weekly or in bulk
Stage timingStage happens within 28 daysLong sales cycle (property, B2B)
Stage rateBetween 1% and 40% of leadsStage too rare, or too common

FAQ

What is the Conversion Leads optimisation goal on Meta?

It is a performance goal for Instant Form lead ad campaigns that optimises for leads likely to reach a CRM stage you choose, instead of simply optimising for form submissions. It learns from lead stage updates your CRM sends to Meta.

What are the requirements for Meta Conversion Leads?

Meta lists five: use Instant Form lead ads, generate at least 200 leads a month, upload CRM data at least once a day, choose a stage that happens within 28 days of the lead, and choose a stage with a conversion rate between 1% and 40%.

What fields does a Conversion Leads event need?

According to Meta's payload specification: event_name (your CRM stage name), event_time (within 7 days), action_source set to system_generated, custom_data.event_source set to crm, custom_data.lead_event_source set to your CRM's name, and at least one customer identifier, with the Meta lead ID, click ID and hashed email in the highest priority group.

Is Conversion Leads better than optimising for leads?

It can be when lead quality is the problem and you meet the requirements, because it targets people likely to reach a real sales stage. Expect fewer leads, possibly at a higher cost per lead. Judge it on cost per qualified lead over several weeks, run alongside your existing campaign.

Can I use Conversion Leads with website form leads?

No. Meta's documentation says Instant Form lead ads are the only lead type compatible with the Conversion Leads goal. For website leads, send CRM stage events through the Conversions API with hashed contact details and the click ID instead.

Where does Qualimize fit?

Qualimize sends CRM stage events to Meta through the Conversions API, with the Meta lead ID, within minutes of a status change. It does not send two CRM fields that Meta's Conversion Leads specification lists, so Qualimize does not claim Conversion Leads support. What it does give you is standard Contact, Lead, SubmitApplication and Purchase feedback, plus cost per qualified lead by campaign. If Conversion Leads is a hard requirement for you today, use a tool that states support for it.

Key takeaways

  • Conversion Leads optimises Instant Form campaigns for leads likely to reach a CRM stage you choose.
  • Meta's requirements: Instant Forms, 200+ leads a month, daily uploads, a stage within 28 days, a 1% to 40% stage rate.
  • The payload needs action_source system_generated plus custom_data event_source and lead_event_source.
  • If you do not qualify yet, standard CAPI stage events still give Meta useful quality feedback.
  • Test it alongside your current campaign and judge it on cost per qualified lead, not cost per lead.

Further reading

  • Meta: Conversion Leads integration
  • Meta: Conversion Leads payload specification
  • Meta: Implementing the CRM integration

Keep reading

  • ProductHow Qualimize sends lead stages to Meta (CAPI)
  • GuideHow to get more qualified leads from Meta Ads
  • GuideHow to Send CRM Lead Stages to Meta, Step by Step
  • GuideWhat the Meta Lead ID Is and Why It Decides Your Match Rate
  • ProductPricing: one plan, every feature
  • CompareCompare CRMs for Meta lead ads
Discuss Qualimize

Keep reading

Related articles

Meta CAPI & Tracking

How to Send CRM Lead Stages to Meta, Step by Step

Qualimize is a CRM for Meta lead ads that has this built in. A status in your workspace can be attached to Contact, Lead, SubmitApplication or Purchase, and the event is sent server-side when a rep changes the status, with the Meta lead ID, hashed contact details and a stable event ID. Failed sends retry automatically and every send is visible in Settings. If you already use a CRM you like, the steps in this guide work with any tool that can call the Conversions API.

Read next
Meta CAPI & Tracking

Which Meta Events to Send for Lead Gen: Contact, Lead, SubmitApplication, Purchase

Qualimize uses exactly this ladder. Each workspace status can be attached to one of four signals: Contact, Lead, SubmitApplication or Purchase, with defaults of Contacted, Pre-Qualified, Qualified and Converted. Purchase carries the deal value and currency when a rep records it. If you need a different event, such as Schedule, you would need another tool or a custom integration.

Read next
Meta CAPI & Tracking

How to Send Purchase Value from Your CRM to Meta

In Qualimize, the status your workspace attaches to the Converted tier sends a Purchase event when a rep moves a lead into it. It carries the deal value and currency when the rep has entered the deal value on the lead (entered by hand), and a nominal value of 1 otherwise, never 0. Qualimize does not pull payment amounts from billing or accounting tools, so the value is only as good as what your team records.

Read next

Build a cleaner Meta Ads sales workflow

Qualimize helps you capture leads, qualify them faster, and connect CRM outcomes back to ad performance.

Book 1:1 Demo
20-minute walkthroughMeta CAPI built-inNo lock-in
See Plans & Pricing