Conversions Objective vs Manual Sales Campaigns on Meta
In short: A manual sales campaign is the closest current equivalent to what advertisers built under the old Conversions objective: full ad set control, pointed at a tracked purchase event. The objective was renamed into Sales during the consolidation, and the manual setup survived intact as the alternative to Advantage+ automation.
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 definitionManual Sales Campaigns
Keeps ad set control over audiences, placements, and budgets on a Meta purchase campaign instead of handing delivery to Advantage+ automation.
You build ad sets with detailed, custom, or lookalike audiences, choose placements, set budgets at ad set or campaign level, and optimize toward a purchase event. Advertisers use it to isolate retargeting, enforce exclusions, or test a hypothesis automation would hide. The mistake is over-segmenting: many small ad sets split conversion data, stall in learning, and bid against each other for the same people.
Full definitionSide by side.
The differences that actually change what happens in your account.
| Conversions Objective (Legacy) | Manual Sales Campaigns | |
|---|---|---|
| Status | Retired objective naming. | A current way of configuring the Sales objective. |
| Control level | Full ad set control, as it was then. | Full ad set control, as it is now. |
| Optimization event | Any pixel event you selected. | A purchase or high-value conversion, plus upstream options. |
| Automated alternative | Little existed at the time. | Advantage+ automation inside the same objective. |
| API naming | The older CONVERSIONS objective enum. | OUTCOME_SALES, configured manually. |
| What actually changed | The label, and where conversion location is chosen. | The amount of automation you can opt into. |
What actually separates them.
The manual setup is not new; what changed is that it now has an automated sibling inside the same objective and a different name above it.
Conversion location is an explicit step in the current flow, where the old objective inferred it from the pixel event you chose.
An old Conversions campaign optimizing a lead event maps to Leads rather than Sales, so not every legacy campaign becomes a manual sales campaign.
Signal practice has moved further than naming: Conversions API coverage and deduplication affect results more than anything the rename touched.
Legacy enums linger in exports and third-party tools, which is why old and new campaigns can appear side by side under different labels.
Which one should you use?
Use Conversions Objective (Legacy) when
- Reading pre-consolidation guides or agency playbooks.
- Auditing historical campaigns where the legacy label appears in reporting.
- Maintaining API integrations or dashboards exposing the old enum.
- Translating an older account structure into the current objectives.
Use Manual Sales Campaigns when
- Building a purchase campaign today that needs exclusions or segmentation.
- Retargeting deserves its own budget and message.
- A test requires one variable isolated with ad set level reporting.
- Conversion volume is thin and you would rather aim spend at a known audience.
Common questions.
Is a manual sales campaign just the old Conversions objective renamed?
Close, but two things moved. The objective became Sales, and conversion location became an explicit choice covering website, app, and messaging surfaces. The manual configuration itself, meaning your own ad sets, audiences, and budgets, is unchanged. What is genuinely new is the automated alternative sitting next to it.
Do old structure recommendations still apply?
The good ones do. Consolidating ad sets so conversion events pool, avoiding overlapping audiences, and optimizing on the deepest reliably reported event were all correct then and remain correct. Advice about specific objective names, attribution defaults, or pixel-only tracking deserves a check against current practice before you copy it.
Should I rebuild legacy campaigns from scratch?
Only if their structure is the problem. Migrated campaigns kept their optimization event and their history, and rebuilding discards accumulated learning for a label change. Rebuild when you are consolidating over-segmented ad sets or fixing signal quality, which are the things that actually move results.
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