Advantage+ shopping campaigns (ASC) and Advantage+ app campaigns (AAC) used to be separate campaign types with their own rules and their own API flag. Meta has replaced them with one setup: you build a normal sales or app campaign, and it counts as Advantage+ when its budget, audience and placement settings meet Meta's conditions. Over 2025 and 2026 Meta closed the legacy types step by step, first for new campaigns, then for edits, and finally for the campaigns still running. This guide covers what the old types were, what replaced them, the timeline Meta published, what happens to existing campaigns, the API changes for developers, and a migration checklist. The facts come from Meta's developer documentation, developer blog and business pages. The checklist is our own practitioner advice and is labelled as such.
What the legacy campaign types were
Meta's developer documentation describes an Advantage+ shopping campaign as one campaign that replaces a portfolio of manual sales campaigns. Each ASC had exactly one ad set, used only the OUTCOME_SALES objective and was marked by smart_promotion_type set to AUTOMATED_SHOPPING_ADS. It allowed up to 150 creative combinations, against 50 for manual campaigns.
ASC also had an optional existing customer budget cap, set with the field existing_customer_budget_percentage. You defined your existing customers as custom audiences, and the field, a value from 0 to 100, limited how much of the budget could go to them. Meta warned that lower values may lead to higher costs per conversion.
An Advantage+ app campaign followed the same pattern for app installs: one campaign, one ad set and several ads, marked by smart_promotion_type set to SMART_APP_PROMOTION and using the APP_INSTALLS objective. Manual app campaigns, by contrast, could hold several ad sets.
What replaced them: one Advantage+ campaign setup
In June 2025 Meta's developer blog announced a streamlined Advantage+ campaign setup for sales and app campaigns. Advertisers no longer pick between an Advantage+ campaign and a manual one at the start. They build one campaign, and Meta reports whether it has reached Advantage+ status. Meta's developer documentation calls the new versions Advantage+ sales campaigns and Advantage+ app campaigns, and applies the same framework to Advantage+ leads campaigns.
The status is read-only. In the API, the campaign field advantage_state_info returns an advantage_state of ADVANTAGE_PLUS_SALES, ADVANTAGE_PLUS_APP, ADVANTAGE_PLUS_LEADS or DISABLED. Meta's documentation says a campaign reaches the Advantage+ state only when three levers are all enabled:
- Budget: Advantage+ campaign budget, set at the campaign level, with a supported bid strategy. Meta lists LOWEST_COST_WITHOUT_CAP (its recommendation), COST_CAP, LOWEST_COST_WITH_BID_CAP and LOWEST_COST_WITH_MIN_ROAS.
- Audience: Advantage+ audience in at least one ad set, or targeting limited to locations, or individual options used as suggestions (Advantage lookalike, Advantage custom audience, Advantage detailed targeting, and age and gender as suggestions).
- Placements: no placement targeting or exclusions at the ad set level, so every placement is eligible. Ad account level placement exclusions are allowed, and Advantage+ placements is the API default.
The documented timeline
Meta published the shutdown in stages across its developer blog and Marketing API changelogs. Two details are worth knowing first. The dates are tied to API versions, and Meta applied the v25.0 restriction to all older versions after a 90-day window. Meta's February 2026 blog post also lists the v25.0 date as 18 February 2025, while the v25.0 changelog gives February 18, 2026, which fits the post's own date.
- May 29, 2025: Meta extends the streamlined Advantage+ setup for sales and app campaigns, starting with selected advertisers. The advantage_state_info field is available from API v23.0.
- October 8, 2025 (v24.0): new ASC and AAC campaigns can no longer be created with the legacy APIs on v24.0. Meta says v23.0 or earlier still worked, and it introduced the migrate_to_advantage_plus option.
- February 18, 2026 (v25.0): creating, duplicating and updating ASC and AAC campaigns is no longer allowed on v25.0 and later.
- May 19, 2026: the same restriction applies to all API versions.
- July 29, 2026 (v26.0): Meta's documentation says all legacy ASC and AAC campaigns are blocked from edits with the release of v26.0. Campaigns that used the existing customer budget cap are paused, and Meta's February 2026 post said all remaining ASC and AAC campaigns would be paused at v26.0.
What happens to existing campaigns, learning and reporting
Meta documented three ways to move a legacy campaign. Migrate only sends migrate_to_advantage_plus to the existing campaign and keeps the same campaign ID. Copy and migrate uses the copies endpoint with the same field and returns a new campaign ID; it works for ASC only, since AAC can be migrated but not copied. In Ads Manager, editing an eligible campaign, for example its name or budget, prompts an upgrade to Advantage+ campaign budget, and publishing that change completes the migration.
There were exceptions. Campaigns using existing_customer_budget_percentage couldn't be migrated through the API and had to be duplicated in Ads Manager or rebuilt by API. Meta also said managed partners could ask their Meta contact for a one-time, account-level migration. Meta's documentation says campaigns with more than 50 ads in an ad set can't be migrated to Advantage+ sales.
Learning: Meta states that migrating, or copying and migrating, forces the campaign into the learning stage, and that there is no workaround. Plan the move as you would a relaunch. Our learning phase guide explains what that costs.
Reporting: after an ASC is converted in Ads Manager, its budget is shown at the campaign level in reporting, and its smart_promotion_type changes from AUTOMATED_SHOPPING_ADS to GUIDED_CREATION with an advantage_state of ADVANTAGE_PLUS_SALES. A copied campaign has a new ID, so its results report under that new ID. Meta's documentation doesn't say more about historical reporting, so don't assume old and new campaigns will be combined in one view.
API changes for developers
If you build campaigns through the Marketing API, these are the documented changes. Meta lists the affected endpoints for the creation block as POST /{ad-account-id}/campaigns and POST /{campaign-id}/copies, and for the edit block as POST /{campaign-id} and POST /{campaign-id}/copies.
- Stop creating campaigns with smart_promotion_type set to AUTOMATED_SHOPPING_ADS or SMART_APP_PROMOTION. Build a standard campaign with the objective you need, campaign budget, Advantage+ audience and no ad set placement restrictions.
- You can't set advantage_state in a POST request, and you can't set smart_promotion_type to GUIDED_CREATION yourself. Check the result with GET on the campaign with fields=name,objective,advantage_state_info. Each sub-state (advantage_budget_state, advantage_audience_state, advantage_placement_state) must be ENABLED.
- Migration calls: POST /{campaign-id}?migrate_to_advantage_plus=true keeps the ID; POST /{campaign-id}/copies?migrate_to_advantage_plus=true returns a copied_campaign_id. From v26.0 Meta says legacy campaigns are blocked from edits.
- existing_customer_budget_percentage is not available in Advantage+ campaigns. Meta's replacement pattern uses two ad sets under one campaign budget: one includes your existing-customer custom audience, with targeting_relaxation_types.custom_audience set to 0 and its spend bounded by daily_min_spend_target and daily_spend_cap; the second is a copy that adds the same audience to excluded_custom_audiences.
- Meta's v26.0 changelog adds changes in the same area: from October 27, 2026 on all versions, the applink_treatment value web_only is deprecated for Web and App campaigns (use automatic or deeplink_with_web_fallback), and poll fields are no longer accepted when creating or updating ads.
Migration checklist (practitioner advice)
The steps below are our own working practice, not Meta guidance. They assume a legacy campaign is still in your account or that you are rebuilding one that was paused.
Run it separately in each ad account, because campaigns belong to a single ad account. Power Ads supplies Meta agency ad accounts at 4% per top-up; we don't build or migrate campaigns, so these steps stay with your team or your tools.
- Inventory first. List every campaign whose smart_promotion_type is AUTOMATED_SHOPPING_ADS or SMART_APP_PROMOTION, and flag the ones that used an existing customer budget cap or have more than 50 ads in an ad set.
- Export reporting for the legacy campaigns before you change anything, with the date range, spend, results and creative-level breakdowns you rely on.
- Decide per campaign: migrate in place if you want to keep the campaign ID, or rebuild if the structure needs changing anyway. Both restart learning, so pick the quieter week.
- Rebuild the existing-customer split on purpose. If the cap mattered to your margins, use the two-ad-set pattern and set the spend bounds from your own customer economics.
- Set the three levers deliberately: campaign budget, Advantage+ audience or suggestions in at least one ad set, and open placements. Then confirm the status in Ads Manager or through advantage_state_info. Our Advantage+ sales campaigns guide covers setup in more depth.
- Update your tools. Remove legacy fields from scripts, templates and bulk-launch sheets, and test on the current API version. For multi-account launches, see our bulk launch guide.
- Annotate your reports with the migration date so a learning-phase dip isn't read as a creative or offer problem.
Common mistakes
Most problems we see come from treating the change as a rename. It is a different campaign model with different switches.
- Assuming Advantage+ status is a setting you choose. It is reported, not set. One ad set with placement exclusions, or ad set budgets instead of a campaign budget, and the campaign is reported as DISABLED, which means Advantage+ off.
- Adding many ad sets to recreate an old manual structure without checking the status afterwards.
- Expecting the existing customer budget cap to carry over. It doesn't exist in Advantage+ campaigns, and an ad account that relied on it needs the two-ad-set replacement or its own rule.
- Migrating everything on one day. Every migration restarts learning, so moving all key campaigns at once makes performance harder to read.
- Leaving old API code running. Calls that create legacy campaigns return errors, edits to them are blocked, and Web and App campaigns with web_only links are blocked from October 27, 2026.
- Reading the product name as the full requirement list. Meta's sales campaign page says its most advanced optimizations need Advantage+ audience, campaign budget, placements and destination, while the API state is built from budget, audience and placements. For app campaigns, our app install playbook covers the wider setup.
Key takeaways
- ASC and AAC are retired. Sales and app campaigns are now one setup that Meta reports as Advantage+ on or off.
- A campaign reaches Advantage+ state when campaign budget, Advantage+ audience and open placements are all enabled; you can't set the state directly.
- Creating or editing legacy campaigns was blocked on v25.0 from February 18, 2026 and on all API versions from May 19, 2026.
- With v26.0 (July 29, 2026) legacy campaigns were blocked from edits, and existing customer budget cap campaigns were paused.
- Migrating restarts learning. Meta says there is no workaround, so stagger moves and export reports first.
FAQ
Can I still create an Advantage+ shopping campaign?
No. Meta's v25.0 changelog says creation, duplication and updates of ASC and AAC campaigns are no longer allowed, on v25.0 and later from February 18, 2026 and on all API versions from May 19, 2026. Build a sales campaign that meets the Advantage+ conditions instead.
What happened to my old ASC campaigns?
Meta's documentation says legacy ASC and AAC campaigns are blocked from edits with v26.0, released July 29, 2026, and that campaigns using the existing customer budget cap are paused. Meta's February 2026 post said all remaining ASC and AAC campaigns would be paused at v26.0. Rebuild them as Advantage+ campaigns.
Does migrating keep my campaign ID and learning?
Migrating in place keeps the campaign ID; copy and migrate creates a new one. In both cases Meta says the campaign is forced into the learning stage, with no workaround.
How do I replace the existing customer budget cap?
It isn't available in Advantage+ campaigns. Meta documents a two-ad-set pattern under one campaign budget: one ad set targets your existing-customer audience with spend limits, and a copy excludes that audience.
How do I check whether a campaign is Advantage+?
In the API, request advantage_state_info on the campaign. An advantage_state of ADVANTAGE_PLUS_SALES, ADVANTAGE_PLUS_APP or ADVANTAGE_PLUS_LEADS means it qualifies; DISABLED means at least one of budget, audience or placements isn't enabled.
Do I need to change my API integration?
Yes, if it still uses smart_promotion_type to create campaigns or edits legacy campaigns. Create standard campaigns with the Advantage+ levers, read advantage_state_info, and remove existing_customer_budget_percentage, web_only link treatment in Web and App campaigns, and poll creative fields.
Sources
- developers.facebook.com/blog/post/2025/06/03/advantage-plus-campaign-experience-for-sales-and-app
- developers.facebook.com/blog/post/2025/10/08/upcoming-asc-and-aac-mapi-deprecation-migration-options-to-advantage-plus
- developers.facebook.com/blog/post/2026/02/13/asc-and-aac-deprecation-mapi-v25
- developers.facebook.com/blog/post/2026/07/29/introducing-graph-api-v26-and-marketing-api-v26
- developers.facebook.com/documentation/ads-commerce/marketing-api/marketing-api-changelog/version25.0
- developers.facebook.com/documentation/ads-commerce/marketing-api/marketing-api-changelog/version26.0
- developers.facebook.com/docs/marketing-api/advantage-campaigns
- developers.facebook.com/documentation/ads-commerce/marketing-api/advantage-shopping-campaigns
- developers.facebook.com/docs/app-ads/advantage-app-campaigns
- facebook.com/business/ads/meta-advantage-plus/sales-campaigns
