Conversions Objective (Legacy)

Meta ran eleven separate campaign objectives, Awareness, Reach, Traffic, several Engagement variants, App Installs, Video Views, Lead Generation, Messages, Conversions, Catalog Sales, and Store Traffic, until the ODAX consolidation folded them into the current six starting in 2022 and finishing as a mandatory migration by 2023. The old Conversions objective, which optimized toward a pixel or Conversions API event like Purchase, Add to Cart, or Lead, did not disappear; it split based on the event category into either Sales for commerce-type events or Leads for form and registration-type events.

Live campaigns were not rebuilt during that migration, they were remapped. Ad sets, budgets, pixel wiring, and audiences carried over untouched; only the objective label shown in Ads Manager and the corresponding value in the Marketing API's objective enum changed, from the old CONVERSIONS string to OUTCOME_SALES or OUTCOME_LEADS. Nothing about how the pixel event itself gets optimized changed underneath that relabeling.

Where the old name still causes real friction is anywhere it is hard-coded: a script or integration built against the legacy Marketing API objective value keeps matching old campaigns and silently misses every campaign created after the migration, since new ones are tagged with the current enum instead. Older training material, agency documents, and screenshots in years-old posts still say Conversions, which reads as a missing feature to anyone newer to the platform rather than what it actually is, a naming change. It is also worth not conflating this with the other retired objective names from the same era, Reach, Video Views, Store Traffic, and Catalog Sales among them; those consolidated into Awareness, Traffic or Engagement, and Sales respectively, and each followed its own mapping logic based on the optimization event rather than a single blanket rule, so a one-to-one translation table is more reliable than assuming every old objective maps the same way.

The other place it bites is historical reporting. Pulling a multi-year performance export grouped by objective and charting it without normalizing legacy and current labels into the same bucket produces a fake discontinuity right at the migration date, spend appearing to fall off one label and appear from nowhere under another, even though the underlying campaigns ran continuously.

A practical way to audit an older account for this is to check campaign creation dates against when the account itself was migrated, since Meta rolled ODAX out account by account through 2022 and into 2023 rather than on one universal day, so two accounts under the same business can have different cutover points. Business Manager access templates and some older reporting integrations, including Looker Studio connectors and Zapier flows built before the transition, may still reference the legacy CONVERSIONS string in their field mappings; it is worth checking those directly against Meta's current Marketing API reference rather than assuming they were updated automatically alongside the ad platform itself.

There is no live decision to make with this term today since it is not selectable when creating a campaign; treat any reference to it as either historical account context or a stale integration that needs its objective-matching logic updated to the current OUTCOME_ enum values.