Amazon Ads deadlines
Marketing Stream V1 and v3 reporting stop on 30 June 2027. Move one pipeline a week, $500 fixed.
On 30 June 2027 Amazon stops delivering Marketing Stream V1 and every v3 reporting endpoint. Each sprint moves one pipeline for one advertiser account, from Stream V1 to V2 or from v3 reports to the new reporting API v1, and your old feed keeps running until the two reconcile.
For agencies, brands and tool builders pulling Amazon Ads data through Stream V1 or v3 reports.
What each $500 sprint covers
- Stream sprint: a written inventory of your current setup: V1 datasets, profiles, regions, and everything that reads from them
- Stream sprint: Amazon's own V2 CloudFormation template deployed in your AWS account: S3 bucket, SQS queue and dead-letter queue, encryption keys and access policies
- Stream sprint: a least-privilege IAM role for the loader, scoped to that bucket, queue and keys
- Stream sprint: the ads-performance-v1 subscription created for your advertiser account, and proved by data landing, not just by an ACTIVE status
- Stream sprint: a loader into BigQuery, Snowflake or Postgres that keeps the latest version of each record, the way Amazon's V2 docs specify
- Stream sprint: the 70 days of history Amazon delivers on subscribe, loaded into that warehouse
- Stream sprint: your V1 pipeline left running, untouched, until V2 is verified
- Stream sprint: a reconciliation report: V1 against V2 for the overlapping hours, per campaign, with every difference written down
- Stream sprint: a no-data alarm, so a subscription that stops delivering is noticed in hours, not weeks
- Stream sprint: a handover note: what runs where, how to add the next account, and when to switch V1 off
- Reporting sprint: every v3 report type you request mapped to reporting API v1 dimensions and metrics, using Amazon's dimensions and metrics libraries
- Reporting sprint: your report job moved from POST /reporting/reports to POST /adsApi/v1/create/reports and POST /adsApi/v1/retrieve/reports, including polling until COMPLETED and downloading the completedReportParts
- Reporting sprint: a parity check of v3 against v1 for the same date range while both still work, with every difference named. Amazon warns that some DSP metrics now use broader definitions and can come back higher
- Reporting sprint: the switch deployed behind a flag, so v3 stays your fallback until you turn it off
What it does not
- Dashboard and report changes (Looker Studio, Sheets, BI). Quoted separately once the reconciliation shows exactly what moves
- More than one advertiser account or more than one pipeline. Each extra account is quoted separately; the destination is reusable
- Moving automation that writes to live campaigns, such as bid rules or dayparting. That moves after the dashboards, as its own piece of work
- Replacements for what V2 doesn't carry: budget-usage, campaign-change and recommendation messages. Amazon points those at other APIs
- Your AWS and warehouse bills, which run in your own accounts. I'll estimate them before we start
- Getting Ads API access in the first place. If you don't have it yet, start with the $50 access session
- History beyond what Amazon keeps: 70 days on a new Stream V2 subscription, and 14 days of hour-level data in reporting API v1
A sprint is one pipeline for one advertiser account. Dashboards and live-campaign automation move afterwards, quoted once the reconciliation shows what changes.
How it works
Four steps, priced before you pay.
Send me your setup
Which feed you run (Stream V1 through Firehose or SQS, or v3 reports), your marketplaces, and your warehouse. I'll confirm it fits one sprint before you pay anything.
Fixed quote, then access
$500 per sprint, fixed, in writing. You grant AWS, Ads API and warehouse access through least-privilege roles I specify, never root keys.
New beside old
I build the new feed next to the old one and land the history Amazon provides. Your current pipeline keeps running exactly as it is.
Reconcile, then you decide
You get the old-versus-new reconciliation. You choose when the old feed goes off, as long as it's before Amazon switches it off on 30 June 2027.
Want to do it yourself first?
What changes in Stream V2, and the V1 setup it replaces, are written up, free.
Questions
What exactly stops working on 30 June 2027?
Amazon's September 2026 deprecation notice gives one hard shutoff date for three things: Marketing Stream Version 1 and all its subscriptions (reporting, messaging and recommendation data delivered to Firehose and SQS), every v3 reporting endpoint and report type available through POST /reporting/reports, and Sponsored Ads v2 reporting. All three keep working until then, in every region. The Exports API for campaign metadata is not affected.
Why migrate now if it all keeps working until June 2027?
Because the honest way to switch is to run old and new side by side and compare them, and that only works while the old one still delivers. Amazon also says some V1 functionality may be limited before the shutoff. A new Stream V2 subscription delivers 70 days of history, so starting early costs you nothing and gives the reconciliation weeks of overlap instead of a rushed final month.
Have you done V2 and reporting API v1 migrations before?
Both became generally available on 30 September 2026, so nobody has a long track record with them yet, and I won't pretend to. What I have done is build and run the V1 Stream pipelines and v3 reporting jobs they replace, for clients in production. That's exactly the code that changes, and it's why your old feed stays on until the new one reconciles.
Is the new reporting API hourly?
It has an hour dimension, but Amazon keeps hour-level data there for only 14 days, and a report can't span more than 14 days of hours. For hourly history you still want Marketing Stream V2, which delivers 70 days when you subscribe and keeps going from there.
Will we lose any history?
Not the history you already hold. Your V1 data stays where it is, and V2 adds 70 days on subscribe. Two limits, both Amazon's: nothing older than 70 days comes from V2, and Amazon says that history may arrive at a coarser grain than hourly, for example daily. Your stored V1 data covers anything older.
We're not on Marketing Stream at all yet. Is this for us?
Yes. Skip V1 entirely and go straight to V2. Everything in the package still applies, except that the reconciliation compares V2 against Amazon's reporting API for a sample of days, because there's no V1 feed to compare with.
We're an agency with many client accounts. How does pricing work?
The fixed price covers one advertiser account and one pipeline. Amazon lets one destination serve every account you subscribe, so later accounts reuse it and are quoted separately. One planning point: Amazon caps an application at five destinations, so a bucket per client stops working at the sixth.
What will V2 cost us to run?
Amazon charges nothing for Marketing Stream. You pay AWS for S3 storage of the files you keep, SQS for delivery notifications, and the two encryption keys Amazon's template creates, which AWS lists at $1 a month each before rotation charges, plus your warehouse. I'll estimate it for your volume before we start.
How do I pay?
PayPal, Wise or direct bank transfer. The written quote says what's due when.
Send me what you have.
Tell me what you run today. If it's bigger than a week, or not a fit, I'll say so before you pay.