Amazon Ads Unified Reporting: The Old Console Reports End on 31 December, Your Ads Don't

Sponsored Products, Sponsored Brands and Sponsored Display campaigns keep running unchanged: the only thing Amazon is retiring is the old report pages in the Ads Console. Amazon announced on 8 June 2026 that it is sunsetting Sponsored Ads reports and Amazon DSP reports by 31 December 2026, and moving all reporting to Amazon Ads unified reporting.

So if your agency sends Amazon clients a scheduled report straight out of the Ads Console, that report has an end date. Every saved report, every emailed subscription and every spreadsheet that reads those exports will need a new source before the year closes.

The good news is that there is time, and the replacement is better in several ways. The bad news is that Amazon has left three things open: when its migration tool arrives, whether the API changes, and how much the new attribution moves the numbers. This guide sets out what Amazon has confirmed, what it has not, and a checklist for moving client reports without a gap.

What is Amazon Ads unified reporting?

Amazon Ads unified reporting is the single reporting area in the Ads Console that replaces the separate Sponsored Ads and DSP report builders, found under Measurement and Reporting, then Reporting. According to Amazon's unified reporting announcement, one report can now span multiple manager or advertiser accounts, ad products, countries, metrics and dimensions. You can build and schedule a custom report or start from a template gallery.

For agencies, three details matter most. Reports that once took hours now generate in minutes, by Amazon's account. History is longer: up to 15 months of daily or weekly data and up to 6 years of monthly, yearly or summary data. And a client with brands in several marketplaces can finally be reported in one file instead of one export per country. Amazon lists 34 countries.

When do the legacy Sponsored Ads reports stop?

Amazon says Sponsored Ads reports and Amazon DSP reports in Measurement and reporting will be sunset by 31 December 2026. Note the word "by". Amazon has not published a day by day schedule, so a report could stop before New Year's Eve. Treat the start of December as your real deadline, which leaves the December report itself running on the new system with a month of checking behind it.

Year end is also the worst moment for a report to break. Q4 is peak season for most Amazon sellers, and the December report is the one clients compare against last year's holiday sales. If the old report silently stops and nobody notices until January, the most important report of the year goes out late.

Will scheduled reports move on their own?

Not today: Amazon says an automated subscription migration tool "will be available soon" to move existing scheduled reports, and it has not given a date. Until then, Amazon points advertisers to a Help Center guide on creating or recreating reports in unified reporting.

Plan as if the tool will not arrive in time. If it does, use it, then check every migrated report against the original, because a tool that copies a schedule cannot know which columns a client's spreadsheet expects.

Is the Amazon Ads Reporting API affected?

Amazon has not said whether the existing Reporting API v3 is affected by the sunset. The announcement lists three ways to reach unified reporting: the Ads Console (generally available), Amazon Marketing Stream (beta) and a Reporting API (beta). It does not mention v3 at all, and it does not say the API reports you may already pull are retiring.

So do not guess in either direction. If your agency or a tool you use pulls Amazon data through the API, ask the vendor what they plan, and watch the Amazon Ads API release notes. A beta API for unified reporting is a signal of where things are heading, not a deadline for what exists today.

For transparency: AgencyReportr pulls Sponsored Products data by connecting to the Amazon Ads API, not by reading Ads Console report subscriptions, so the console sunset does not by itself change those client reports. We will follow whatever Amazon announces for the API.

Why will the numbers in unified reporting look different?

Unified reporting numbers can differ from legacy reports because Amazon standardized metrics and dimensions across ad products and moved attribution from conversion based to traffic based. That is Amazon's own wording, and the announcement does not spell out how far individual metrics will move.

In practice, that means a sales or orders figure in the new report may not equal the same field in the old one, even for the same campaign and date range. Column names can also change when Amazon standardizes them across Sponsored Products, Sponsored Brands and DSP. Neither is a problem if you spot it first. Both become a problem when a client spots it in a month over month chart and asks why last month's sales "changed".

Where do newer formats like prompts fit?

Prompts are the newest example of a reporting gap to check. Amazon's prompts announcement (10 March 2026) made prompts, which Amazon calls an AI-powered enhancement to existing campaigns, generally available to US Sponsored Products and Sponsored Brands advertisers on 25 March 2026, billed under existing cost per click settings. Amazon describes a prompts report created from the Sponsored Products report category, with impressions, clicks, spend, sales, ACOS, ROAS and 7-day orders and units.

Neither announcement says how that prompts report maps into unified reporting. If a client spends on prompts, rebuild that view early and confirm the same fields exist, rather than discovering in January that one line of the report has nowhere to come from.

How do you move client reports to Amazon Ads unified reporting?

The safest way to move client reports to Amazon Ads unified reporting is to inventory every legacy report, rebuild it, remap its columns and run both versions side by side for one full month. In order:

1. Inventory scheduled reports. List every saved report and subscription across every client account: report type, ad product, date range, recipients and where the file ends up (an inbox, a shared drive, a spreadsheet, a dashboard).
2. Rebuild in unified reporting. Start from the template gallery where one fits, then match the original's ad products, accounts, countries and time grain. Where one client had five country exports, try one multi-country report.
3. Remap the columns. Write down old column name, new column name and any formula, macro or chart that reads it. Spreadsheets break on renamed headers long before anyone looks at the numbers.
4. Run one month side by side. Pull the same month from both systems and compare spend, clicks, sales, orders, ACOS and ROAS at campaign level. Record each gap and its likely cause, usually the attribution change.
5. Switch, then retire. Point every recipient and downstream sheet at the new report, and only then delete the legacy subscription, so nothing goes quiet.

Finish November with every client on the new reports, and December runs on a setup that has already been checked once.

What should you tell clients?

Tell clients early, in one short note, that Amazon is replacing its report system by 31 December and that some figures may shift slightly because Amazon changed how it attributes sales. Something like: "Amazon is replacing its old report pages this year; your campaigns are not affected. We have rebuilt your reports on the new system and compared both for October. Sales differ by about X percent because Amazon now credits sales differently; trends are unchanged." A client who hears that from you first reads it as competence. A client who finds it themselves reads it as an error.

Keep the report itself focused on what clients actually use. Our guide to client reports people read covers the layout, and the PPC report template shows the same structure for paid search. If you would rather not rebuild exports every time Amazon changes its console, an Amazon PPC reporting tool that connects to the API can send white-label client reports on a schedule instead.

Amazon Ads unified reporting FAQ

When do Amazon's legacy Sponsored Ads reports stop?

Amazon says it is sunsetting Sponsored Ads reports and Amazon DSP reports by 31 December 2026. Unified reporting, the replacement in the Ads Console, became generally available on 8 June 2026.

Will my scheduled Amazon Ads reports move over automatically?

Not yet. Amazon says an automated subscription migration tool will be available soon, but it has not given a date. Plan to rebuild the reports clients depend on yourself, and treat the tool as a bonus if it arrives in time.

Does the change affect the Amazon Ads Reporting API v3?

Amazon has not said. The unified reporting announcement lists a Reporting API for unified reporting in beta, but it does not say whether existing Reporting API v3 reports change or retire. Watch the Amazon Ads API release notes before assuming either way.

Will unified reporting numbers match the old Sponsored Ads reports?

Not necessarily. Amazon says unified reporting standardizes metrics and dimensions and moves attribution from conversion based to traffic based. Run one month of both reports side by side and note any gap before clients see it.

Is Amazon retiring Sponsored Products or Sponsored Ads?

No. Sponsored Products, Sponsored Brands and Sponsored Display keep running unchanged. Amazon is retiring only the old Sponsored Ads and Amazon DSP report pages in the Ads Console, by 31 December 2026, and replacing them with unified reporting.