Amazon Ads on November 20, 2026 updated "Deal report," a Support Center page that sets out how advertisers buying inventory through publisher deals assemble a report of impressions, costs and conversions for each deal inside its unified reporting system. The page sends readers whose deals are not delivering to a companion page, "Troubleshooting deals," last updated on November 2, 2026, which lists the reasons an ad group attached to a deal may decline to bid and the remedy Amazon pairs with each.
The companion page is the more revealing of the two. Its table runs to 20 rows, from frequency caps and creative lengths to out-of-stock products and Prime Video titles that are not yet available, and it describes a "No bid reasons" view that shows what share of a deal's incoming requests each cause affected - over a date range of no more than 14 days. Three rows are written specifically for private auction and preferred deals, and one is described as most common on programmatic guaranteed deals. Another still refers to an "Amazon DSP or SSP auction," although Amazon retired the Amazon DSP name on September 29.
In Short
Amazon has documented how to build a per-deal performance report in its unified reporting tool and, on a separate page, 20 reasons an ad group attached to a publisher deal might not bid at all. That matters to advertisers and agencies buying streaming TV, video and display through private auctions, preferred deals and guaranteed deals on Amazon's platform, because a deal that sends plenty of requests can still deliver nothing if a setting on the buying side filters every one of them out. When a deal goes quiet, the console shows which reason applied and to what share of requests, but only across 14 days at a time, and nine of Amazon's 20 suggested fixes involve loosening a cap, a threshold, a target or a schedule, or raising a bid or budget.
Two pages, one workflow
Both pages sit in the Support Center under Measure results and then Reports and metrics by product, with the troubleshooting page filed beneath the deal report in the breadcrumb trail. Both carry the Amazon Ads Agent header that Amazon now places on its advertising console. Neither has a change log, so what the November 20 revision altered cannot be read from the page.
The deal report page opens with its purpose: "Use the deal report to review impressions, costs, and performance across your deals." A second line narrows the use - "Check the deal report when you want to confirm that a deal is winning impressions or to compare results across deals" - and a third explains that the report is not a product of its own. "You build a deal report from the Inventory report template in Unified Reporting, and then add deal columns to it," according to Amazon.
That dependency places deal reporting on the new side of a migration Amazon has scheduled. Unified reporting, which opened in beta at unBoxed in November 2025, reached general availability on June 8, 2026. Amazon's migration page has since set December 17 as the date the legacy report pages turn read-only and January 31, 2027 as the date they close, with saved reports and historical data deleted. The deal report page describes only the unified reporting route.
What the deal report contains
The page lists the settings a deal report uses, grouped into filters, dimensions, report period and metrics. It also links to a general guide, "Create a report in Unified reporting," for the mechanics shared by every report type.
| Setting | What the page lists |
|---|---|
| Template | Inventory, with deal columns added under Customize columns |
| Filters | Account, campaign, country, ad product |
| Deal dimensions | Deal ID, deal name, deal type |
| Other dimensions | Portfolio, advertiser, campaign, ad group, ad, flight, supply source, site "and more" |
| Report period presets | Last 7 days, Last 30 days, This month, Last month, This year, or a custom date range |
| Metric groups (9) | Delivery (such as impressions and CPM); costs and fees (such as total cost and third-party fees); reach and impression share; engagement; Amazon retail conversions (such as ROAS and detail page views); Amazon device conversions; Amazon video conversions; off-Amazon conversions; combined conversions |
Five of the nine metric groups are conversion groups, split by where the conversion happens: Amazon's retail store, Amazon devices, Amazon video, off Amazon, and all of them combined. The page links out to three reference pages for definitions - conversion metrics, engagement metrics and traffic metrics, the last covering delivery, cost and fee, reach and impression share.
What the list does not name is as telling. No group mentions bid requests, win rates or the reasons an ad group held back. The deal report answers what a deal delivered and what it earned; the explanation for silence lives elsewhere, in the console's Deals page and in the campaign delivery table, according to the troubleshooting page.
The presets raise a question the page leaves alone. PPC Land reported on November 18 that Amazon's data availability page caps a single daily-granularity pull in unified reporting at 120 days, out of 24 months of history. A "This year" deal report run on November 20 and broken down by day would span 324 days, by PPC Land's calculation. The deal report page does not say how its presets interact with that limit.
The first question: is the deal sending requests?
The troubleshooting page opens with a three-step triage, and the first branch has nothing to do with the buyer's settings. The buyer opens Deals in the campaign manager and checks whether the deal is receiving bid requests, the messages a publisher's systems send each time an impression is up for sale. "If the deal is not receiving any bid requests, contact the supply partner," the page says.
Only when requests are arriving does the problem shift to the buying side. Clicking the deal name shows its details and the ad groups it has been added to, and a "No Bid Reasons" column breaks down why those ad groups held back. A "View reasons" link opens "the ad group settings that correspond to not bidding, and the proportion of bid requests impacted by this reason," according to Amazon.
One row blurs that division. Its label, "Flight dates ended," understates its scope: the row covers a deal that has not started, a deal that has ended, a wrong deal ID, and a deal the publisher has not switched on. Amazon's fix includes a line any trader who has copied a deal ID from an email will recognise: "Make sure that the deal ID matches exactly and there are no swapped digits or trailing spaces." The same row tells buyers to ask the supply partner to confirm the deal is live and sending traffic.
Twenty reasons, in Amazon's words
The table below condenses each row of the troubleshooting page. Row labels are Amazon's; the causes and fixes are paraphrased from the page except where quoted elsewhere in this article.
| Reason (Amazon's label) | Cause, as Amazon describes it | Fix Amazon lists | Deal types named |
|---|---|---|---|
| Campaign frequency cap | The campaign has reached its frequency cap for that user | Increase or remove the campaign cap | None |
| Ad group frequency cap | The ad group has reached its frequency cap for that user | Increase or remove the ad group cap | None |
| Amazon viewability mismatch | The request's estimated viewability score falls short of the ad group's Amazon viewability threshold | Modify or remove the threshold | None |
| Creative size mismatch | No ad in the ad group matches the ad size the request requires | Add ads matching the deal's size and type | None |
| Creative type mismatch | Ad types do not match what the deal requires, or their configuration misses its delivery requirements | Verify ad types and configurations against the deal | None |
| Creative duration mismatch | The ad runs longer than the deal permits | Keep the ad within the deal's maximum duration | PG (most often); PA and PD for comparison |
| Location mismatch | The ad group's geo targeting does not overlap the request's location | Check the geo target; keep targeting broad, not too narrow | None |
| Audience mismatch | The request lacks the behavioral audience and device segments the ad group targets | Relax audience targeting where mismatch is very high and delivery low | PA, PD |
| Bids below deal price or floor during bidding | The ad group's bids sit consistently below the deal price or floor | Raise bids to clear the deal price (PD) or floor (PA) | PA, PD |
| Auction losses | Bids lose to other ad groups competing for the same inventory | Bid higher against ad groups of the same type | PA, PD |
| Flight dates ended | The deal has not started, has ended, has the wrong ID, or is not switched on | Check dates and the deal ID; ask the supply partner to confirm | None |
| Budget exhausted | Four budget conditions (see below) | Keep budget available at both levels; loosen restrictive settings; allocate manually | None |
| Ad groups paused or inactive | The ad group or its campaign is paused | Resume both | None |
| Ad not approved | The ad awaits approval or failed its scan and was rejected | Fix and resubmit, or attach an approved ad | None |
| Outside dayparting hours | Requests arrive outside the targeted daypart hours | Widen the schedule; confirm the time zone setting | None |
| Products out of stock | Every product on every ad is out of stock | Add an in-stock product or attach another ad | None |
| Domain or Brand safety blocked | Blocklists or brand safety filters exclude most or all targeted supply | Review block lists at every level and the brand safety tier | None |
| Deal not in ad group's supply | The deal exists but is not attached to the ad group as a supply source | Add the deal to the ad group's sources | None |
| Learning period (Performance+/Brand+) | New Performance+ and Brand+ ad groups warm up for a few hours before bidding | Activate them a few hours before the flight starts | None |
| Prime Video title not yet available | The title linked to an ad has a future buy, rent or subscription period | Align targeted titles' offer periods with flight dates | None |
The abbreviations PA, PD and PG, which the page never spells out, stand for private auction, preferred deal and programmatic guaranteed, the three deal types Amazon's own streaming TV budget calculator separates into tabs. Sixteen of the 20 rows name no deal type at all.
Settings that take an ad group out of the running
A recurring phrase gives the first group away. Five rows - the two frequency caps, the viewability threshold, creative size and location - end with the words "therefore the ad group is not considered." In each case a control the advertiser set, or an asset the advertiser supplied, removes the ad group before any price is weighed.
The frequency rows are the simplest: "The campaign has already reached its frequency cap for that user, therefore the ad group is not considered." They make no distinction between deal types. The day before the deal report revision, PPC Land reported that Amazon's frequency page for DVA+ treats them differently, fully enforcing caps on private auction and preferred deals while programmatic guaranteed lines from publishers other than Google AdX, Amazon Publisher Direct and Amazon's own properties keep delivering after a cap is reached.
Three rows concern creatives. Size and type mismatches are the familiar kind: the deal asks for a format the ad group does not carry. Duration is where the deal type shows. "An ad that has longer duration than what the deal permits will not bid," the page says. "This happens most often on PG deals." Programmatic guaranteed deals, it explains, are tailored and typically set a specific maximum duration, while the standardised private auction and preferred deals "accommodate a broader range of lines."
The audience row is written for the auction-based deal types only. "For PA and PD deals, the ad group can only bid when the incoming request includes the behavioral audience and device segments it targets," according to Amazon. A deal can therefore be sending a steady stream of requests for segments the ad group does not target, and the ad group will sit them all out. The row is "Not applicable if ad group does not target any behavioral audience or device segments."
Brand safety gets a single row with several sources. An ad group's targeted or excluded blocklists can shut out most or all of its supply, and a brand safety filter can exclude a site, the page says, citing "DoubleVerify or IAS pre-bid filters, targeted content categories, or targeted inventory tiers" as possible causes. Amazon's platform put brand suitability tier settings into open beta on November 18, 2025 and added content exclusion categories covering Twitch and third-party inventory in 43 markets a month later. The fix is to "Review block lists at every level and brand safety tier setting"; it does not say to remove them.
Dayparting carries a quieter trap. An ad group delivers only during its targeted hours, and "the targeted hours are based on the time zone you selected during setup, either the viewer's time zone or the account's time zone," according to Amazon. A schedule built for one time zone and run in the other would miss its intended hours without any error. The simplest cause of all sits near the bottom of the table: a deal that was created but never attached to the ad group as a supply source.
Price and competition
Two rows deal with money, and both apply to private auction and preferred deals. The first covers an ad group whose targeting is correct and which is actively bidding, yet "you may still see no delivery if [the] ad group's bids are consistently below the deal price or deal floor." The fix spells out the difference between the two deal types: bids must clear "the deal price (for PD Deal) or deal floor (for PA Deal)." A preferred deal carries a fixed price; a private auction carries a price floor, below which the publisher will not sell.
The second row describes bids that clear those thresholds and still lose. When targeting is set up correctly and the ad group's "bids are moving to Amazon DSP or SSP auction," delivery can stall if those bids lose to other ad groups competing for the same inventory. The wording implies two contests, one inside Amazon's buying platform and one at the publisher's supply-side platform. The page does not say whether the rival ad groups belong to the same advertiser or to others. Its remedy is direct: "bidding higher would help with delivery."
The name in that row is out of date. Amazon retired the Amazon DSP name on September 29, folding the product into DVA+, yet the troubleshooting page, revised five weeks later, still refers to the old name.
Status, stock and timing
The remaining rows concern whether anything can run at all. Paused campaigns, rejected ads and ended flights need little explanation. Others are specific to Amazon. "Every product (ASIN) on every ad is out of stock" is a reason not to bid, which ties a programmatic deal on an outside publisher to the stock status of products in Amazon's store. Ads that promote a Prime Video title will not bid while the title "has a future buy, rent, or subscription period."
Budget exhaustion gets the longest entry, with four conditions: campaign and ad group budgets both spent; a campaign budget spent while manually set ad group budgets add up to more than it; every ad group budget spent while the campaign budget exceeds their sum; and automated budget allocation moving an ad group's budget to other ad groups in the campaign "due to poor performance." For that last case, the page advises loosening "restrictive settings" on the ad group so it can deliver, or allocating budget to it manually.
That fourth condition is a system decision presented as a delivery problem. PPC Land argued on November 14 that Amazon's defaults increasingly decide how budgets move inside campaigns, and Amazon's DVA+ setup guide, updated on November 13, already warned that budget caps can cause under-delivery by blocking full use of a budget. The troubleshooting page does not say how often the reallocation case arises, or whether the No bid reasons view separates it from the other three budget conditions.
The learning period is the one reason that resolves itself. "New Performance+ and Brand+ ad groups have a warm-up period and take a few hours to learn" before they start bidding, according to Amazon, which suggests activating them a few hours before the flight begins. Brand+ has selected deals automatically by default for new streaming TV prospecting lines since July 2026, so in those ad groups the deal choice and the warm-up both sit with Amazon's models.
The documented path, step by step
According to Amazon, building a deal report takes three steps:
- From the navigation side menu, click Measurement & reporting, then Reporting.
- Click See all templates, then select Inventory.
- Under Customize columns, scroll or search for "deal" to add deal columns to the report.
The first-line check on an under-delivering deal, as the troubleshooting page sets it out, has three steps:
- Go to the campaign manager and select Deals.
- Check whether the deal is receiving bid requests. With no requests, the page says to contact the supply partner; with requests, clicking the deal name shows its details and the ad groups it is added to.
- When requests arrive but the ad group is not bidding, open the No Bid Reasons column and click View reasons to see the corresponding settings and the share of bid requests affected.
Retrieving the reasons for not bidding is documented in six steps:
- Navigate to the Amazon Advertising Console and select Deals.
- Search for the deal name or ID in the quick search field.
- Click the deal name to troubleshoot.
- Review the deal details and associated ad groups, select a date range in the date picker "up to a maximum of 14 days," and click View reasons in the No bid reasons column.
- A window displays the reasons and "the percentage of bid requests for which it is applicable."
- Ad group settings matching a reason can be changed by exiting the window and clicking the ad group name.
Additional delivery metrics by deal take five steps:
- Navigate to the Amazon Advertising Console and select an ad group on the campaign page.
- Find the campaign delivery metrics table at the bottom of the page.
- Click "Breakdown," select "Deals" and click "Apply."
- Click "Columns" above the table, select "Customize columns," choose among the mismatch metrics offered and click "Apply."
- Check the mismatch metrics for the deal's record "to identify possible optimizations and blockers."
Why deals now need a manual
Amazon has spent two years adding deal routes to its buying platform. The company introduced guaranteed deals for Prime Video ads in August 2024, brought Netflix inventory into its buying platform from late 2025, opened inventory management APIs with deal planning endpoints in March 2026, launched automatic deal selection for streaming TV on April 15, 2026 and added publisher-hosted creatives for Google Ad Manager guaranteed deals in 33 markets in August. Each route adds a set of terms - a size, a length, a price, a floor, a flight - that an ad group must match before it can bid.
A mismatch rarely announces itself. A deal that does not fit an ad group produces no error on the campaign; it simply produces no impressions, which is why the No bid reasons view expresses each cause as a share of requests rather than as an error. The troubleshooting page puts that diagnosis in the console, next to the settings it concerns. On November 19, PPC Land reported an exchange in which Amazon's conversational agent told an agency chief executive it could read reporting data but not campaign settings, when asked why three sponsored ads campaigns had stopped serving. That case did not involve deals, but it described the same gap between what a report shows and what explains it.
The remedies themselves lean one way. By PPC Land's count, nine of the 20 fixes loosen a control or raise spending: increasing or removing either frequency cap, modifying or removing the viewability threshold, broadening location targeting, relaxing audience targeting, raising bids in two rows, widening the daypart schedule, and adding budget or loosening restrictions in the budget row. Most of the other 11 repair setup errors, such as attaching the deal, fixing a rejected ad or swapping in an in-stock product. Frequency caps, viewability thresholds and audience targets are usually set on purpose; the page does not discuss what relaxing them does to cost, reach quality or the audience a campaign was built to find.
What the pages leave open
The troubleshooting page does not name the mismatch metrics it tells buyers to add, explain how a request's "estimated viewability score" is calculated, say whether the 14-day window can reach back beyond recent weeks, or give any data on how often each reason occurs. Neither page names markets or explains what changed in its latest revision. The console appears under three names - "campaign manager," "Amazon Advertising Console" and, in the header, Amazon Ads Agent - and the column is written both as "No Bid Reasons" and "No bid reasons," alongside several typing errors, including "viewabilty" in a row label.
Key facts
- Source documents: Amazon Ads Support Center pages "Deal report," "Updated on Nov 20, 2026" (https://advertising.amazon.com/help/GCW4KFW7XYVS2XB9), and "Troubleshooting deals," "Updated on Nov 2, 2026" (https://advertising.amazon.com/help/GVRC8YAHDX7F5M45)
- Location: Support Center > Measure results > Reports and metrics by product > Deal report > Troubleshooting deals
- Console header on both pages: Amazon Ads Agent
- Report template: Inventory, in unified reporting, with deal columns added under Customize columns
- Deal dimensions: deal ID, deal name, deal type
- Filters: account, campaign, country, ad product
- Report period presets: Last 7 days, Last 30 days, This month, Last month, This year, custom range
- Metric groups: nine, including five conversion groups (Amazon retail, Amazon device, Amazon video, off-Amazon, combined)
- No-bid reasons: 20 rows (PPC Land count), shown as a percentage of bid requests; date range up to 14 days
- Deal types named: PA (private auction), PD (preferred deal), PG (programmatic guaranteed)
- Verification vendors named: DoubleVerify, IAS
- Products named: Performance+, Brand+, Prime Video titles, Amazon DSP (in the auction losses row)
- Mismatch metrics path: ad group > campaign delivery metrics table > Breakdown > Deals > Columns > Customize columns
Timeline
- August 1, 2024 - Amazon introduces programmatic guaranteed deals for Prime Video ads
- September 10, 2025 - Netflix and Amazon Ads announce Netflix inventory in Amazon DSP from Q4 2025
- November 10, 2025 - Amazon announces Performance+ and Brand+ enhancements at unBoxed
- November 11, 2025 - Unified reporting opens in beta
- November 18, 2025 - Brand suitability tier settings enter open beta in Amazon DSP
- December 18, 2025 - Amazon DSP adds content exclusion categories for Twitch and third-party inventory in 43 markets
- March 2026 - Inventory management APIs with deal planning endpoints open in beta
- April 15, 2026 - Automatic deal selection for streaming TV launches
- June 8, 2026 - Unified reporting reaches general availability
- July 22, 2026 - Brand+ switches to automatic deal selection by default for streaming TV
- August 10, 2026 - Publisher-hosted creatives arrive for Google Ad Manager guaranteed deals in 33 markets
- September 29, 2026 - Amazon retires the Amazon DSP name in favour of DVA+
- November 2, 2026 - Amazon updates "Troubleshooting deals," listing 20 reasons for not bidding
- November 13, 2026 - Amazon's DVA+ setup guide notes that budget caps can cause under-delivery
- November 14, 2026 - PPC Land analyses how Amazon's defaults shift budget control
- November 17, 2026 - Amazon's streaming TV guide separates private auction, preferred and guaranteed deals in its budget calculator; the data availability page caps daily report pulls at 120 days
- November 18, 2026 - Amazon's ad agent says it cannot see why three campaigns stopped serving
- November 19, 2026 - Amazon's frequency page for DVA+ describes deal-type enforcement of caps
- November 20, 2026 - Amazon updates "Deal report," built on the Inventory template in unified reporting
- December 17, 2026 - Legacy report pages scheduled to become read-only
- January 31, 2027 - Legacy report pages scheduled to close, with saved reports deleted
Related PPC Land coverage
- Amazon's DVA+ frequency caps count Netflix and Prime Video as one - How caps are enforced on private auction, preferred and programmatic guaranteed deals across publishers.
- Amazon limits daily unified reports to 120 days of its 24-month history - The lookback windows and pull limits that apply to every unified report, including deal reports.
- Amazon advertisers will lose unmigrated reports on January 31, 2027 - The migration timeline for the legacy report pages.
- Amazon Ads unified reporting exits beta - and takes two old tools with it - General availability of the reporting system that hosts the deal report.
- Amazon sizes streaming TV budgets as commitment plus up to five fees - The streaming TV guide, its inventory builder deals tab and its minimum deal price field.
- Amazon caps its automated DVA+ campaigns at 20 products - The DVA+ setup guide, with its notes on budget caps, frequency caps and Brand+ and Performance+ ad groups.
- Amazon's ad agent can't see why three campaigns stopped serving - An agency's exchange with Amazon's conversational agent over campaigns that dropped to zero impressions.
- Amazon's $78bn ad machine now sets the defaults agencies buy inside - PPC Land's analysis of how automated defaults move budget decisions to Amazon.
- Amazon kills single-deal STV buying in Brand+ as 10 AI features land - The July 2026 switch to automatic deal selection in Brand+.
- Amazon DSP auto deal selection picks streaming TV inventory by itself - The April 2026 launch of machine-built deal groups for streaming TV.
- Amazon opens DSP inventory management APIs - what changed in March - API access to deals, supplier proposals and inventory groups.
- Amazon DSP gains publisher-hosted creatives for GAM deals in 33 markets - Guaranteed deals through Google Ad Manager with creatives hosted by publishers.
- Netflix becomes available in Amazon DSP starting Q4 2025 - The partnership that brought Netflix guaranteed and private marketplace deals to Amazon's platform.
- Amazon introduces Guaranteed Deals for Prime Video Ads - The 2024 launch of programmatic guaranteed deals on Prime Video.
- Amazon DSP launches brand suitability settings in open beta - The inventory tier settings that can block deal supply.
- Amazon DSP adds content exclusion categories for brand suitability control - Content categories that can exclude Twitch and third-party inventory.
- Amazon calls its ad platform an agent, but the agent is still closed beta - The September 2026 retirement of the Amazon DSP name.
Summary
Who: Amazon Ads, through two Support Center pages, and the advertisers and agencies that buy display, video and streaming TV inventory through private auction, preferred and programmatic guaranteed deals on Amazon's buying platform, along with the supply partners that run those deals.
What: "Deal report" explains how to build a per-deal report from the Inventory template in unified reporting, with deal ID, deal name and deal type dimensions and nine metric groups covering delivery, cost, reach, engagement and five kinds of conversion. "Troubleshooting deals" lists 20 reasons an ad group attached to a deal may not bid, each with a cause and a fix, and documents a No bid reasons view that shows the share of bid requests each reason affected over up to 14 days, plus mismatch metrics in the campaign delivery table.
When: The deal report page was updated on November 20, 2026, and the troubleshooting page on November 2, 2026. Neither page has a change log.
Where: The Amazon Ads Support Center, under Measure results and Reports and metrics by product, describing the Deals page, the campaign delivery table and the Reporting section of the console that now carries the Amazon Ads Agent header. Neither page names markets.
Why: A deal that does not match an ad group's settings produces silence rather than an error. The pages separate supply problems, where no requests arrive, from buying-side filters, prices and statuses that block bids, at a time when more of Amazon's outside inventory is sold through deals and its reporting is moving to a single system before the legacy pages close on January 31, 2027.
Discussion