Campaign Types & Objectives

Conversions vs Sales Objective on Meta: The Renamed Objective

In short: Conversions is the old name. Under Meta's pre-ODAX objective set it was what you selected to optimize toward a pixel event; the consolidation mapped it into Sales or Leads depending on the event, and existing campaigns were migrated. If a guide tells you to pick Conversions for purchases, it means the Sales objective.

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 definition

Sales Objective

Optimizes Meta delivery toward people predicted to purchase or complete another high-value conversion tracked by the pixel or Conversions API.

You choose a conversion location, set a performance goal such as purchases or value, and Meta's delivery system seeks people likely to fire that event. Ecommerce and subscription advertisers default to it. The common mistake is optimizing for an event with too little volume, which starves learning; widen the event, consolidate ad sets, or fix signal quality before blaming creative.

Full definition

Side by side.

The differences that actually change what happens in your account.

	Conversions Objective (Legacy)	Sales Objective
Status	Retired naming from the pre-ODAX objective set.	Current objective in every account.
What it optimized	Any pixel or Conversions API event you selected.	Purchases and other high-value conversions.
Where it maps	Sales for purchases, Leads for contact events.	Not applicable; it is the destination.
API naming	The older CONVERSIONS objective enum.	OUTCOME_SALES.
Where you still see it	Older guides, agency vocabulary, third-party dashboards.	The campaign creation flow.
Practical difference	None in capability; the delivery goal survived the rename.	Conversion location is now an explicit step.

What actually separates them.

The rename consolidated objectives rather than removing a capability, so nothing you could optimize toward under Conversions became impossible.

Conversion location, meaning website, app, Messenger, WhatsApp, or calls, is now an explicit choice inside Sales rather than an implied one.

Whether an old Conversions campaign belongs in Sales or Leads depends on the event: purchases go to Sales, contact events to Leads.

Older API references and third-party tools may still carry the legacy objective name even though the interface does not.

Treating Conversions as a missing feature leads people to hunt for an objective that no longer exists instead of selecting Sales.

Which one should you use?

Use Conversions Objective (Legacy) when

Reading documentation, courses, or agency decks written before the objective consolidation.
Auditing historical campaign data where the old objective label persists.
Working with API integrations or dashboards that still expose legacy enums.
Translating an old playbook into the current campaign flow.

Use Sales Objective when

Building any new campaign whose goal is a purchase or high-value conversion.
The tracked event has a monetary value you may want to optimize on.
You need value bidding or a ROAS goal, which live in the current flow.
Anything happening in the account today, since the legacy name is not selectable.

Common questions.

Did my old Conversions campaigns lose performance in the migration?

The mapping preserved the optimization event and the delivery goal, so the mechanics carried over. What changed around the same period, and gets blamed on the rename, is signal quality: attribution windows, deduplication, and Conversions API coverage all affect results far more than which label the objective carries.

Should I choose Sales or Leads if my old campaign said Conversions?

Follow the event. If it was a purchase or another transaction with value, that is Sales. If it was a form submission, call, or message, that is Leads, which also gives you in-platform capture options the old objective did not surface. The optimization event you pick matters more than the objective name.

Why do some tools still show a Conversions objective?

Reporting tools, exports, and older API integrations often keep legacy enums so historical data stays readable. It is a labeling artifact rather than an available choice, and building new campaigns still means selecting Sales or Leads in the current flow. Check what the campaign optimizes toward rather than trusting the label.

Or stop choosing between them.

AdFlint picks the setting, writes the ads, and keeps optimizing inside the Google and Meta accounts you already own.

Try AdFlint free See how it works

Related comparisons

All comparisons