What launched on June 8, 2026?

Unified reporting reached general availability inside Amazon Ads Console. A single report can include campaigns across multiple manager or advertiser accounts, ad products (Sponsored Ads and Amazon DSP), countries, and metrics, replacing the manual reconciliation that ran across two separate report families.

Are any old reports going away?

Yes. ppc.land reports that two legacy Ads Console reports are being retired alongside the unified reporting GA. Any saved report, BI ingestion job, or spreadsheet macro pointed at those legacy schemas will need a one-off rewrite.

What is the fastest migration path before Prime Day?

Rebuild the weekly recurring report on the unified schema first, run it in parallel with the legacy export for two cycles, and compare campaign and ASIN totals before cutting over. Most discrepancies come from attribution window and metric definition differences, not bugs.

Advertising

Amazon Ads unified reporting GA: Sponsored and DSP in one view

On June 8, 2026 Amazon Ads moved unified reporting out of beta and into general availability inside Ads Console, consolidating Sponsored Ads and Amazon DSP data into a single report across multiple manager or advertiser accounts, countries, and ad products. Trade outlet ppc.land confirmed on June 10 that two legacy Ads Console reports are being retired alongside the launch. For brands and agencies that stitch Sponsored and DSP exports every week, the reporting layer just changed and the migration window is short.

MaxCOO at Nova Analytics

Jun 10, 2026 · 4 min read · 808 words

Updated June 10, 2026

Summarize with AI

Claude Gemini ChatGPT

On this page

See your Amazon business clearly.

Try for free

What's happening

On June 8, 2026 Amazon Ads moved unified reporting out of beta and into general availability inside Ads Console. A single report can now pull Sponsored Ads and Amazon DSP data together, across multiple manager or advertiser accounts, countries, ad products, and metrics. PPC trade outlet ppc.land confirmed the launch on June 10 and flagged that two legacy reports are being retired in the process.

For brands and agencies that were stitching Sponsored Ads exports to DSP exports in a spreadsheet every Monday morning, the reporting layer just changed underneath them. The data is the same, but the export shape is new and the old reports go away.

Key Dates & Deadlines

Jun 8, 2026

Unified reporting reaches general availability

Sponsored Ads and DSP data consolidated into one Ads Console report across accounts, countries, and ad products

Jun 10, 2026

Trade press confirms two legacy reports sunset

ppc.land reports the GA launch alongside the retirement of two older Ads Console reporting tools

Next 4 weeks

Migrate weekly and monthly reporting workflows

Rebuild Monday recurring reports and BI dashboards against the unified export before legacy reports are fully removed

Why it matters for Amazon brands

Sponsored Ads and DSP have always lived in two reporting worlds with different metric definitions, attribution windows, and export schemas. Unified reporting removes the manual reconciliation step that consumed a few hours every week on most in-house and agency teams. The trade-off is short-term migration work. Saved report definitions, BI ingestion jobs, and macros built on the legacy schemas will need a one-off rewrite.

The bigger story is operational. Once Sponsored Ads and DSP sit in the same report, the spend question changes from "which channel performed?" to "which ASIN performed across the full funnel?". Brand managers who keep product-level PPC spend next to organic sessions, BSR on their own ASINs, and contribution margin have the most leverage on the new view.

What you should do now

1.
Inventory every saved Ads Console report and downstream consumer
List the Sponsored Ads and DSP exports your team relies on, including the weekly client report, the monthly board pack, the BI pipeline, and the spreadsheet macros. Mark which ones touch the two legacy reports that are sunsetting so you know the migration scope.
2.
Rebuild the weekly recurring report on the unified schema
Recreate the recurring weekly report in unified reporting first, run it in parallel with the legacy export for two cycles, and compare totals at the campaign and ASIN level before cutting over. Differences are usually attribution window or metric definition, not a bug.
3.
Lock metric definitions in the same doc your finance team uses
Unified reporting exposes new column combinations. Pin which spend, sales, and attributed conversion fields feed into ACOS, TACOS, and contribution margin so finance, ops, and the agency stop arguing about why two reports disagree.
4.
Re-baseline ASIN-level performance against organic signals
With Sponsored and DSP in one row per ASIN, this is the cleanest moment of the year to pair ad spend with sessions, unit-session percentage, and winners and losers at the SKU level. It surfaces ASINs where ad spend is propping up a dying organic position before next quarter's plan is locked.

How Nova helps

Nova consolidates sales, sessions, unit-session percentage, BSR on your own ASINs, refunds, and product-level ad spend at the SKU level inside one cockpit, so brand and agency teams already have the cross-channel view that unified reporting is exposing. Coverage spans the 23 Amazon marketplaces Nova supports, and FBM orders blend into the same Seller Cockpit view so the new unified data lands in a dashboard the team is already reading every morning.

Frequently Asked Questions

Common questions about this topic

Unified reporting reached general availability inside Amazon Ads Console. A single report can include campaigns across multiple manager or advertiser accounts, ad products (Sponsored Ads and Amazon DSP), countries, and metrics, replacing the manual reconciliation that ran across two separate report families.
Yes. ppc.land reports that two legacy Ads Console reports are being retired alongside the unified reporting GA. Any saved report, BI ingestion job, or spreadsheet macro pointed at those legacy schemas will need a one-off rewrite.
Rebuild the weekly recurring report on the unified schema first, run it in parallel with the legacy export for two cycles, and compare campaign and ASIN totals before cutting over. Most discrepancies come from attribution window and metric definition differences, not bugs.

Verified Sources

All information verified from official Amazon sources and trusted industry analysts as of publication date.

About the Author

Max

COO at Nova Analytics

Max leads operations at Nova Analytics, helping Amazon sellers optimize their business performance through data-driven insights and strategic automation.

Connect on LinkedIn

See your Amazon business clearly.

Try for free Explore pricing