Conversions vs Leads Objective on Meta: Where Lead Events Went
In short: Under Meta's old objective set, a lead form on your website was optimized through the Conversions objective. The consolidation moved those events into Leads, which also gained in-platform capture through instant forms, Messenger, WhatsApp, and calls. The old label survives in guides and API references, not in the campaign flow.
By the AdFlint research team · Fact-checked against current Google and Meta platform behavior · Last reviewed July 2026
Conversions Objective (Legacy)
Pre-ODAX Meta objective name for optimizing toward pixel events, retired when objectives were consolidated and now covered by sales and leads.
Under Meta's older objective set, Conversions was what you selected to optimize toward a pixel or Conversions API event, sitting alongside Traffic and Engagement. The ODAX consolidation mapped it into Sales or Leads depending on the event, and existing campaigns were migrated. The term still appears in older guides and API references. Treat it as a naming legacy, not a capability missing from current accounts.
Full definitionLeads Objective
Collects contact details on Meta by optimizing toward form submissions, calls, or messages, either on your website or inside Facebook and Instagram.
You choose whether the lead lands on your site, an instant form, Messenger, WhatsApp, or a phone call, then set the optimization event. Service businesses and B2B advertisers use it where there is no online purchase. The mistake is judging it on cost per lead alone; add qualifying questions and feed closed deals back as offline conversions so delivery learns what quality means.
Full definitionSide by side.
The differences that actually change what happens in your account.
| Conversions Objective (Legacy) | Leads Objective | |
|---|---|---|
| Status | Retired pre-ODAX naming. | Current objective for contact capture. |
| Capture options | Website events only, through the pixel. | Instant form, website, Messenger, WhatsApp, or a call. |
| API naming | The older CONVERSIONS objective enum. | OUTCOME_LEADS. |
| Quality feedback | Offline conversions, as today. | Offline conversions, with the loop now explicit in the flow. |
| Where you meet it | Old documentation, dashboards, historical campaign data. | The campaign creation flow. |
| Practical difference | None in optimization; the goal survived the rename. | Conversion location is an explicit step. |
What actually separates them.
The rename consolidated objectives instead of removing capability, so website lead optimization works exactly as it did under Conversions.
What Leads added over the old objective is the explicit choice of where the contact is captured, including capture that never touches your site.
Whether an old Conversions campaign maps to Leads or Sales depends on the event: contact events go to Leads, transactions to Sales.
In-platform capture cannot be reproduced by pointing an old-style pixel campaign at a landing page, because the form lives inside Meta.
Legacy enums persist in exports and third-party tools, which is a labeling artifact rather than an available choice.
Which one should you use?
Use Conversions Objective (Legacy) when
- Reading playbooks, courses, or agency decks written before the consolidation.
- Auditing historical performance where the old objective label appears.
- Maintaining API integrations or dashboards carrying legacy enums.
- Translating an older lead generation setup into the current flow.
Use Leads Objective when
- Building any new campaign whose goal is contact details.
- You want an instant form, a message thread, or a call as the capture point.
- The lead event is tracked on your site and should drive delivery.
- CRM outcomes will be returned so delivery can learn lead quality.
Common questions.
Do I lose website lead optimization by switching to Leads?
No. Choosing the website conversion location inside Leads optimizes toward your tracked lead event exactly as the old Conversions objective did. What you gain is the option of capturing in-platform instead, and a flow that makes the capture point an explicit decision rather than something implied by the pixel event you picked.
An old guide says to use Conversions for lead forms. What now?
Read it as Leads with a website conversion location, and check the rest of the guide's assumptions too. Advice from that era often predates current attribution settings and Conversions API practice, which affect lead campaign results far more than the objective name ever did.
Why does my reporting tool still show Conversions?
Exports and integrations often keep legacy objective enums so historical rows stay readable across the rename. It tells you nothing about how a current campaign is configured. Look at the optimization event and conversion location on the ad set to know what delivery is actually being asked to find.
Or stop choosing between them.
AdFlint picks the setting, writes the ads, and keeps optimizing inside the Google and Meta accounts you already own.
Related comparisons
- Leads Objective vs Sales Objective
- Sales Objective vs Traffic Objective
- Engagement Objective vs Sales Objective
- Awareness Objective vs Sales Objective
- App Promotion Objective vs Sales Objective
- Advantage+ Shopping Campaigns vs Sales Objective
- Manual Sales Campaigns vs Sales Objective
- Conversions Objective (Legacy) vs Sales Objective