Loading docs...

👋 Need help? Chat with us!

ASC/AAC Migration: Beat the May 19, 2026 Deadline

How to find every Advantage+ Shopping and Advantage+ App campaign in your account before Meta blocks create/update, plus the exact replacement recipe.

Intermediate7 min readUpdated 2026-05-17

Meta is killing the legacy Advantage+ Shopping (ASC) and Advantage+ App (AAC) campaign types. If you have any campaigns using

output

smart_promotion_type: AUTOMATED_SHOPPING_ADS

output

AUTOMATED_APP_ADS

, you have a hard deadline.

What's being killed and when

Date	What stops
2026-05-19	Create/update of ASC and AAC campaigns blocked on every Marketing API version
~2026-09 (v26.0)	Remaining ASC/AAC campaigns are auto-paused by Meta

This is not a soft deprecation. From May 19, every API client — yours, ours, Meta's own tools — will get an error if it tries to create or update a campaign with the legacy

output

smart_promotion_type

flags. Existing live campaigns keep running until the v26 auto-pause sweep in September.

Step 1: Find your legacy campaigns

AdsMAA includes a one-shot scan that walks every connected Meta integration in your org, finds legacy campaigns, and sorts them by last-30-day spend so you can prioritize.

Via the MCP tool

In any MCP-connected AI assistant (Claude Desktop, Cursor, Claude Code):

output
Use meta_scan_legacy_campaigns with lookback_days=30

Via REST API

bash
curl https://api.adsmaa.com/api/v1/mcp/v23/scan-legacy-campaigns?lookback_days=30 \
  -H "X-API-Key: pk_live_..."

What you get back

json
{
  "scanned_at": "2026-05-17T17:50:58.004Z",
  "lookback_days": 30,
  "integrations_scanned": 1,
  "legacy_campaigns_found": 0,
  "total_spend_last_period": 0,
  "deadline": "2026-05-19 — create/update blocked across all MAPI versions",
  "auto_pause": "2026-09 (v26.0) — remaining campaigns auto-paused by Meta",
  "campaigns": [],
  "errors": []
}

output

legacy_campaigns_found > 0

, each item in

output

campaigns

includes the campaign ID, current spend,

output

legacy_type

(ASC or AAC), and

output

recommended_replacement

— the exact MCP tool to use for the new version.

Heads up — if you see an

output

errors

entry with

output

"Invalid OAuth access token"

, that integration's Meta token has expired or was revoked. Reconnect it via the Integrations page before the migration scan can cover it.

Step 2: Replacement recipe

The unified Advantage+ objectives replace both legacy types:

For ASC (Advantage+ Shopping) campaigns

Old	New
Tool	output `live_meta_create_campaign` with output `smart_promotion_type: AUTOMATED_SHOPPING_ADS`
Tool (new)	output `live_meta_create_advantage_sales_campaign` (omit smart_promotion_type entirely)
Objective	OUTCOME_SALES
Default targeting	Advantage+ Audience

For AAC (Advantage+ App) campaigns

Old	New
Tool	output `live_meta_create_campaign` with output `smart_promotion_type: AUTOMATED_APP_ADS`
Tool (new)	output `live_meta_create_advantage_app_campaign`
Objective	OUTCOME_APP_PROMOTION
Default targeting	Advantage+ Audience

Both new tools default to

output

status: PAUSED

— the new campaign won't spend until you flip it.

Step 3: Migrate the audience strategy

If your old ASC campaign had a lookalike-heavy targeting stack, don't recreate it. Meta is steering everyone to Advantage+ Audience, which Meta reports cuts CPA up to 32% in ecommerce benchmarks vs lookalike stacks.

output
Use live_meta_create_advantage_audience_adset with:
  campaign_id = <new campaign ID>
  geo_locations = your hard geo constraints
  age_min / age_max / genders = hard demographic constraints
  suggestions = [{id, name}] interests as SOFT hints

Controls become hard constraints; suggestions are hints Meta may expand beyond. Don't pass

output

lookalike_spec

here — that path is the one being replaced.

Step 4: Verify the migration

Run the new campaign paused for 24h alongside the old one.
Compare Campaign Score —
output
```
live_meta_get_campaign_score
```
on both. The new Advantage+ campaign should score higher because it follows Meta's current playbook.
Activate the new campaign at the same budget as the old one.
Watch 48h of performance. Spend, ROAS, CPA, CPL.
Pause the old ASC/AAC campaign once you're satisfied.
Re-run the scan — confirm
output
```
legacy_campaigns_found: 0
```
.

Common gotchas

Gotcha	Fix
output `smart_promotion_type` still passed in your code	The new output `live_meta_create_advantage_sales_campaign` rejects it with a clear error. Just remove the field.
Stale Meta OAuth token	If the scan errors with "Invalid OAuth access token", reconnect the integration via the Integrations page first.
Existing ad sets reference the old campaign ID	Create new ad sets against the new campaign; don't try to move existing ones.
Custom audiences attached to lookalike specs	Recreate the audience as Advantage+ Audience suggestions instead.
App promotion ID format	AAC used output `object_store_url` patterns; the new flow uses output `application_id` on the campaign.

Need help? Drop into the AdsMAA dashboard, run the scan from the MCP page, and your AI assistant can walk you through the migration end-to-end.

Key Takeaways

1Hard deadline: 2026-05-19 — Meta blocks create/update of ASC + AAC campaigns on every API version
2Existing live campaigns keep running until ~Sep 2026 (v26.0) when Meta auto-pauses them
3AdsMAA scans all your connected Meta accounts in one call: meta_scan_legacy_campaigns
4Replacement is unified Advantage+ Sales / App objective + Advantage+ Audience (no smart_promotion_type)
5Migration is non-destructive — run new campaigns in PAUSED state, validate, then cut over

Frequently Asked Questions

How long does the migration take?

For a typical account with 5-20 legacy campaigns: ~30 minutes end-to-end via MCP — scan, create paused replacements, validate Campaign Score, cut over. AdsMAA does the scan and creation; you only confirm budget transitions.

What if I miss the May 19 deadline?

Your existing ASC and AAC campaigns will keep running until ~Sep 2026 (v26.0), but you cannot create new ones or update existing ones via API. Manual changes in Ads Manager may also be blocked. Migrate early to avoid running budgets you cannot adjust.

Does this affect Boost Post campaigns from the Facebook app?

No. Boosted posts use a different code path. This deadline only affects ASC and AAC campaign types created via the Marketing API or Ads Manager.

My scan returned an "Invalid OAuth access token" error. What now?

The stored Meta token for that integration has expired or been revoked. Go to Integrations in the AdsMAA dashboard, click on the affected Meta account, and reconnect. Then re-run the scan.

Will historical spend on old ASC campaigns still appear in reports?

Yes. Historical data is preserved regardless of the campaign type. Only future spend on new campaigns moves to the new objective.

Was this article helpful?

Ask a question

Continue Reading

integrations

Meta Marketing API v23.0: What's New

Everything Meta shipped in Marketing API v22-v25 and how AdsMAA exposes it — Advantage+ Suite, Advantage+ Creative (AI), Threads ads, Business AI, Incremental Attribution, and the legacy surfaces being killed off.

integrations

Meta Ads Integration

Connect your Meta Business account to manage Facebook and Instagram campaigns with AI-powered optimization.

mcp server

MCP Server Overview

Learn how AdsMAA's MCP Server connects your Meta Ads data to AI tools like Claude, Cursor, and VS Code.

Loading docs...

ASC/AAC Migration: Beat the May 19, 2026 Deadline

How to find every Advantage+ Shopping and Advantage+ App campaign in your account before Meta blocks create/update, plus the exact replacement recipe.

Intermediate7 min readUpdated 2026-05-17

Meta is killing the legacy Advantage+ Shopping (ASC) and Advantage+ App (AAC) campaign types. If you have any campaigns using

output

smart_promotion_type: AUTOMATED_SHOPPING_ADS

output

AUTOMATED_APP_ADS

, you have a hard deadline.

What's being killed and when

Date	What stops
2026-05-19	Create/update of ASC and AAC campaigns blocked on every Marketing API version
~2026-09 (v26.0)	Remaining ASC/AAC campaigns are auto-paused by Meta

This is not a soft deprecation. From May 19, every API client — yours, ours, Meta's own tools — will get an error if it tries to create or update a campaign with the legacy

output

smart_promotion_type

flags. Existing live campaigns keep running until the v26 auto-pause sweep in September.

Step 1: Find your legacy campaigns

AdsMAA includes a one-shot scan that walks every connected Meta integration in your org, finds legacy campaigns, and sorts them by last-30-day spend so you can prioritize.

Via the MCP tool

In any MCP-connected AI assistant (Claude Desktop, Cursor, Claude Code):

output
Use meta_scan_legacy_campaigns with lookback_days=30

Via REST API

bash
curl https://api.adsmaa.com/api/v1/mcp/v23/scan-legacy-campaigns?lookback_days=30 \
  -H "X-API-Key: pk_live_..."

What you get back

json
{
  "scanned_at": "2026-05-17T17:50:58.004Z",
  "lookback_days": 30,
  "integrations_scanned": 1,
  "legacy_campaigns_found": 0,
  "total_spend_last_period": 0,
  "deadline": "2026-05-19 — create/update blocked across all MAPI versions",
  "auto_pause": "2026-09 (v26.0) — remaining campaigns auto-paused by Meta",
  "campaigns": [],
  "errors": []
}

output

legacy_campaigns_found > 0

, each item in

output

campaigns

includes the campaign ID, current spend,

output

legacy_type

(ASC or AAC), and

output

recommended_replacement

— the exact MCP tool to use for the new version.

Heads up — if you see an

output

errors

entry with

output

"Invalid OAuth access token"

, that integration's Meta token has expired or was revoked. Reconnect it via the Integrations page before the migration scan can cover it.

Step 2: Replacement recipe

The unified Advantage+ objectives replace both legacy types:

For ASC (Advantage+ Shopping) campaigns

Old	New
Tool	output `live_meta_create_campaign` with output `smart_promotion_type: AUTOMATED_SHOPPING_ADS`
Tool (new)	output `live_meta_create_advantage_sales_campaign` (omit smart_promotion_type entirely)
Objective	OUTCOME_SALES
Default targeting	Advantage+ Audience

For AAC (Advantage+ App) campaigns

Old	New
Tool	output `live_meta_create_campaign` with output `smart_promotion_type: AUTOMATED_APP_ADS`
Tool (new)	output `live_meta_create_advantage_app_campaign`
Objective	OUTCOME_APP_PROMOTION
Default targeting	Advantage+ Audience

Both new tools default to

output

status: PAUSED

— the new campaign won't spend until you flip it.

Step 3: Migrate the audience strategy

output
Use live_meta_create_advantage_audience_adset with:
  campaign_id = <new campaign ID>
  geo_locations = your hard geo constraints
  age_min / age_max / genders = hard demographic constraints
  suggestions = [{id, name}] interests as SOFT hints

Controls become hard constraints; suggestions are hints Meta may expand beyond. Don't pass

output

lookalike_spec

here — that path is the one being replaced.

Step 4: Verify the migration

Run the new campaign paused for 24h alongside the old one.
Compare Campaign Score —
output
```
live_meta_get_campaign_score
```
on both. The new Advantage+ campaign should score higher because it follows Meta's current playbook.
Activate the new campaign at the same budget as the old one.
Watch 48h of performance. Spend, ROAS, CPA, CPL.
Pause the old ASC/AAC campaign once you're satisfied.
Re-run the scan — confirm
output
```
legacy_campaigns_found: 0
```
.

Common gotchas

Gotcha	Fix
output `smart_promotion_type` still passed in your code	The new output `live_meta_create_advantage_sales_campaign` rejects it with a clear error. Just remove the field.
Stale Meta OAuth token	If the scan errors with "Invalid OAuth access token", reconnect the integration via the Integrations page first.
Existing ad sets reference the old campaign ID	Create new ad sets against the new campaign; don't try to move existing ones.
Custom audiences attached to lookalike specs	Recreate the audience as Advantage+ Audience suggestions instead.
App promotion ID format	AAC used output `object_store_url` patterns; the new flow uses output `application_id` on the campaign.

Need help? Drop into the AdsMAA dashboard, run the scan from the MCP page, and your AI assistant can walk you through the migration end-to-end.

Key Takeaways

1Hard deadline: 2026-05-19 — Meta blocks create/update of ASC + AAC campaigns on every API version
2Existing live campaigns keep running until ~Sep 2026 (v26.0) when Meta auto-pauses them
3AdsMAA scans all your connected Meta accounts in one call: meta_scan_legacy_campaigns
4Replacement is unified Advantage+ Sales / App objective + Advantage+ Audience (no smart_promotion_type)
5Migration is non-destructive — run new campaigns in PAUSED state, validate, then cut over

Frequently Asked Questions

How long does the migration take?

What if I miss the May 19 deadline?

Does this affect Boost Post campaigns from the Facebook app?

No. Boosted posts use a different code path. This deadline only affects ASC and AAC campaign types created via the Marketing API or Ads Manager.

My scan returned an "Invalid OAuth access token" error. What now?

The stored Meta token for that integration has expired or been revoked. Go to Integrations in the AdsMAA dashboard, click on the affected Meta account, and reconnect. Then re-run the scan.

Will historical spend on old ASC campaigns still appear in reports?

Yes. Historical data is preserved regardless of the campaign type. Only future spend on new campaigns moves to the new objective.

Was this article helpful?

Ask a question

Continue Reading

integrations