Leave a live Advantage+ Shopping campaign alone when it is still delivering and you only need it to keep spending. Migrate—or rebuild in the unified Advantage+ Sales structure—when you must create new campaigns, change structure, restore new-customer budget controls, or regain editable API access. Meta has moved Sales, App, and Leads automation into one Advantage+ campaign experience, and the old ASC creation path is no longer the supported way to build new work.
This article gives ecommerce and performance marketers a Transition Ladder, a Fit Scorecard, and a worked example so you can choose leave-running versus migrate without treating every Ads Manager prompt as an emergency.
Key takeaways
-
Meta renamed Advantage+ Shopping to Advantage+ Sales and documents a unified campaign experience built on Advantage+ audience, Advantage+ campaign budget, and Advantage+ placements.
-
Marketing API changelogs state that creating, duplicating, and updating legacy ASC and AAC campaigns is no longer allowed on modern API versions, with the v25.0 restriction applying to all versions as of May 19, 2026.
-
Meta says matching settings in the new structure should perform similarly—but migrate or copy actions force the learning stage, with no documented workaround.
-
Campaigns that relied on existing_customer_budget_percentage need a special path: Ads Manager duplication or a rebuilt new-versus-existing ad-set design, not a casual API toggle.
What changed—and what still matters for business operators
For years, many ecommerce advertisers treated Advantage+ Shopping Campaigns (ASC) as a separate “always-on sales” product. Meta’s product pages now describe Advantage+ sales campaigns as the renamed successor, and developer documentation frames ASC and Advantage+ App Campaigns as legacy workflows being replaced by a streamlined Advantage+ campaign experience for Sales, App, and Leads.
In Meta’s Advantage+ Campaign Experience documentation, a campaign reaches an Advantage+ state when it uses Advantage+ audience, Advantage+ campaign budget, and Advantage+ placements. Placement automation is the default in the API, so the practical operator checklist is usually: campaign-level budget on, Advantage+ audience on, and avoid unnecessary hard placement exclusions unless policy requires them.
Advantage+ audience still respects non-negotiable constraints such as location, minimum age, language, and custom audience exclusions. That matters because “leave automation on” does not mean “remove every business constraint.”
If you are choosing where paid media sits inside a broader growth plan, keep this article focused on Meta structure. For the earlier channel-priority decision between Google and Meta, see Google Ads or Meta first.
The ASC Transition Ladder
Name your current stage before you accept any upgrade prompt. The goal is controlled editability—not migrating every campaign on the same afternoon.
|
Level |
Operating pattern |
When it fits |
Primary risk |
|
L0 — Ignore the rename |
Keep using legacy ASC create/update paths for new work |
Almost never after the API freeze |
Blocked creates/updates; partner scripts fail; delayed rebuilds |
|
L1 — Inventory live ASC objects |
List campaign IDs, smart_promotion_type, ECBP usage, ad counts, and who edits them |
Any account with historical ASC/AAC objects |
Hidden exceptions (ECBP, 50+ ads) surface only after an urgent edit fails |
|
L2 — Leave-running with a create-new rule |
Stable live ASC keeps spending; every new sales launch uses Advantage+ Sales structure |
Performance is acceptable and no structural edit is required this week |
Accidentally editing the live ASC and resetting learning without a plan |
|
L3 — Controlled migrate or copy-migrate |
Use Ads Manager upgrade prompts or documented migrate/copy paths when still available; expect learning reset |
You need editability, reporting consistency, or Advantage+ Sales features such as multiple ad sets |
Short-term CPA noise while the campaign re-enters learning |
|
L4 — Rebuild for exceptions |
Ads Manager duplicate for ECBP campaigns, or recreate new-versus-existing spend with hard custom-audience constraints |
ECBP campaigns, oversized ad sets, or API migration paths already closed |
Paused or uneditable objects if the rebuild is delayed past platform cutovers Meta documents for v26.0 |
Most healthy accounts should leave L0 immediately, complete L1 this week, operate at L2 by default, and move to L3 or L4 only when an edit, rebuild, or exception forces the change.
Advantage+ Transition Fit Scorecard
Score each factor 0 or 2. Higher totals favor planned migration or rebuild now. Lower totals favor leave-running with a create-new rule.
|
Factor |
Score 2 when |
Score 0 when |
|
1. Structural edit needed soon |
You must change budget topology, conversion location, creative packaging, or reporting shape inside the live ASC |
You only need the campaign to keep spending unchanged |
|
2. New campaign demand |
You will launch a new sales, app, or leads automation campaign in the next sprint |
No new Meta automation launches are planned |
|
3. ECBP or new-customer split dependency |
The campaign uses existing_customer_budget_percentage or a hard new-customer spend ceiling you still need |
No existing-customer budget percentage is in use |
|
4. Ad-set scale / duplication limits |
The ASC ad set holds more than 50 ads, or duplication already fails |
Creative volume is modest and duplication still works in Ads Manager |
|
5. Learning-reset tolerance |
You can fund a learning window without breaking contribution margin |
Any CPA spike this week would halt paid acquisition |
|
6. Measurement readiness |
Pixel plus Conversions API events reconcile to orders or qualified CRM outcomes |
Purchase or lead quality is still disputed between Ads Manager and backend systems |
|
7. Need for expanded Sales features |
You need capabilities Meta documents as expanded in Advantage+ Sales, such as additional conversion locations or more than one ad set per campaign |
Single-ad-set ASC already matches the commercial setup you want |
|
Total |
Recommended move |
|
0–4 |
Stay at L2. Inventory the account, freeze casual edits on live ASC, and create any new work in Advantage+ Sales structure. |
|
6–10 |
Plan L3 on a named campaign with a learning buffer. Do not migrate the entire account in one day. |
|
12–14 |
Treat migration or rebuild as operationally required. Use L4 immediately for ECBP or duplication-blocked campaigns. |
How to migrate without treating every prompt as a panic
Meta’s October 8, 2025 developer post described three transition methods for eligible campaigns: copy-and-migrate into a new campaign ID, migrate-only while keeping the same campaign ID, and Ads Manager migration when an edit prompts an upgrade to Advantage+ campaign budget. Meta also documented exclusions: campaigns using existing_customer_budget_percentage needed Ads Manager duplication, and ASC ad sets with more than 50 ads could remain editable after v25.0 but could not be duplicated.
Meta’s Advantage+ Campaign Experience FAQ is explicit on learning: migrating or copying with migrate_to_advantage_plus forces the learning stage for both migrate-only and copy-migrate actions, with no workaround. That is the main commercial tradeoff. If the live ASC is the only profitable paid acquisition engine this month, leave it running and launch the next test as a separate Advantage+ Sales campaign instead of converting the only winner mid-peak.
Meta also states that if you keep the same settings after moving into the new Advantage+ experience, the campaign should perform similarly to the previous setup. Read that as “do not change five levers at once.” Migration plus a creative overhaul plus a conversion-event change is three experiments stacked into one outage.
-
Export or screenshot current ASC settings: objective, budget location, optimization event, geographic constraints, exclusions, catalog usage, and creative count.
-
Confirm whether existing_customer_budget_percentage is present. If yes, skip casual API migration fantasies and open Ads Manager for the duplicate path Meta documents.
-
For eligible standard ASC objects, choose migrate-only when reporting continuity on the same campaign ID matters, or copy-migrate when you want a parallel contest against the live original.
-
If API migration fields are no longer available in your account, use the Ads Manager edit prompt Meta documents: edit an eligible campaign, accept Advantage+ campaign budget when prompted, and publish deliberately.
-
Keep settings matched during the learning window. Change creative packages or event definitions only after delivery stabilizes enough to read.
For new campaigns, Meta advises creating Advantage+ sales campaigns with advantage_state set to ADVANTAGE_PLUS_SALES rather than smart_promotion_type=AUTOMATED_SHOPPING_ADS. That is the durable create path for digital advertising services teams managing Meta accounts after the ASC API freeze.
Worked example: DTC brand with one profitable ASC
Hypothetical example: a direct-to-consumer skincare brand runs one ASC that produces most Meta revenue. The team wants a cleaner new-customer split and hears that Shopping was renamed to Sales. Scorecard result:
-
Structural edit needed soon: 2 — finance wants a hard existing-customer ceiling again
-
New campaign demand: 2 — Black Friday creative needs a separate launch vehicle
-
ECBP dependency: 2 — the live ASC still uses existing_customer_budget_percentage
-
Ad-set scale limits: 0 — fewer than 50 ads
-
Learning-reset tolerance: 0 — the team cannot absorb a mid-peak CPA spike
-
Measurement readiness: 2 — purchases reconcile
-
Expanded Sales features: 2 — they want more than one ad set for new-versus-existing routing
Total: 10. That is not “migrate the profitable ASC tonight.” It is L4 planning: leave the live ASC running through peak if it is still editable enough to spend, duplicate or rebuild the ECBP logic in Ads Manager on a schedule Meta’s docs support, and launch Black Friday creative in a new Advantage+ Sales campaign. Meta documents that existing_customer_budget_percentage is not available for new Advantage+ campaigns and that ASC campaigns using it can be migrated through Ads Manager duplication, with a documented rebuild pattern that splits existing and new customers across ad sets using non-relaxed custom audience constraints under a campaign budget.
Mistakes, limitations, and exceptions
-
Treating the rename as a performance emergency. Meta’s FAQ says matched settings should perform similarly; the emergency is usually editability and unsupported legacy fields.
-
Migrating every campaign the same day. Learning resets are documented; stagger non-critical objects.
-
Assuming API migrate_to_advantage_plus remains available forever. Meta’s Advantage+ Campaign Experience documentation states that with Marketing API v26.0, legacy ASC/AAC campaigns are blocked from edits and can no longer use that migration field. Confirm the live state of each campaign in Ads Manager before you plan around an API path that may already be closed.
-
Confusing Advantage+ audience expansion with unconstrained targeting. Location, minimum age, language, and custom audience exclusions remain non-negotiable constraints in Meta’s Advantage+ audience documentation.
-
Using this Meta structure decision as a substitute for Google versus Meta channel choice or for bid-signal tools such as seasonality adjustments. Those are separate decisions.
Recommended next steps
-
Complete an L1 inventory of every ASC/AAC object this week, marking ECBP usage and ad counts.
-
Set an account rule: no new AUTOMATED_SHOPPING_ADS creates; new sales automation launches as Advantage+ Sales.
-
Score each live ASC with the Fit Scorecard before accepting upgrade prompts.
-
If you need a migration window, schedule it away from peak demand and keep settings matched while learning resets.
-
If Meta is only one part of acquisition, review whether Search or Performance Max should absorb brand defense while Meta rebuilds—without mixing that into the migration day itself.
If you want help inventorying ASC exceptions and sequencing Advantage+ Sales rebuilds without resetting your only profitable campaign mid-peak, book a growth strategy session with Oasbit.
Sources
-
Meta for Developers — Upcoming ASC and AAC MAPI deprecation, Migration Options to Advantage+
-
Meta for Developers — Advantage+ Campaign Experience for Sales, App, and Leads
-
Meta for Developers — Graph API / Marketing API version 25.0 changelog
-
Meta for Business — Advantage+ shopping / sales campaigns product page
-
Meta for Business — Meta Advantage+ explained in two minutes




