Migrate legacy Amazon Sponsored Brands v3 campaigns to the v4 API
domain: advertising.amazon.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Audit all Sponsored Brands campaigns, prioritizing any created before Sponsored Brands v4's rollout, since these are the ones most likely still on legacy structures.
Confirm your integration's Sponsored Brands endpoints and reporting calls point at the v4 API and v4 reporting endpoints rather than v3.
Recreate each legacy campaign under v4 with matching targeting, budgets, and creative, since v3 Sponsored Brands campaigns do not automatically convert to v4.
Validate that migrated v4 campaigns begin appearing in the current Amazon Ads reporting API; legacy v3-structured campaigns stop returning performance data as v3 is deprecated.
Pause or archive the original v3 campaigns only after confirming the v4 replacements are delivering and reporting correctly.
Known gotchas
Legacy Sponsored Brands campaigns left un-migrated stop reporting performance data in the reporting API — this can look like a tracking bug rather than what it actually is, an unmigrated campaign.
Amazon has previously issued alerts about legacy campaigns being unexpectedly rejected — treat migration as time-sensitive rather than optional cleanup.
There is no in-place server-side conversion; migration means creating new v4 campaign objects and redirecting budgets/traffic to them.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?