Amazon Ads today updated its Support Center page "Understand frequency in DVA+ campaigns," and the page describes a single counter that tracks each user's impressions across every publisher a campaign buys. An ad served on Netflix counts against the same limit as one served on Prime Video or Fire TV, according to Amazon, and the counting starts without any new setting, opt-in or targeting change.
The same page records where that limit stops short. Programmatic guaranteed deals from publishers other than Google AdX, Amazon Publisher Direct and Amazon's own properties keep delivering after the cap is reached, as do Amazon Audience Guaranteed campaigns, while Twitch share of voice lines and ads on Fire tablets and Kindle devices fall outside caps altogether. It also sets out three formulas for measuring what a cap saved, and limits each advertiser account to two advertiser-level frequency groups.
In Short
Amazon's help page says a frequency cap in DVA+, its tool for buying display, video and streaming TV ads, counts impressions from every publisher a campaign buys, so an ad seen on Netflix uses up the same allowance as one seen on Prime Video. That matters to brands buying streaming TV across several services, because the cap can only stop bids DVA+ controls: guaranteed deals with Netflix and most other outside publishers keep delivering after the limit is reached. In practice, those guaranteed impressions spend the allowance and push the stopping onto other ad lines in the same campaign, Fire tablet, Kindle and Twitch share of voice ads are not capped at all, and the page's printed formulas for savings mix units.
One counter across publishers
The page, dated "Updated on Nov 19, 2026," sits in the Support Center under Bidding and budget, below a header that reads Amazon Ads Agent, the name Amazon now gives its advertising console. Its contents are listed as five sections: what frequency is, how to manage it, cross-publisher frequency capping, measurement and limitations. The cross-publisher section carries the rule that changes how a multi-publisher streaming campaign behaves.
"Frequency caps apply across multiple publishers and supply sources," according to Amazon. "When your campaign or frequency group targets supply from more than 1 publisher, a single unified counter tracks impressions per user across all sources. This means an impression on 1 publisher counts toward the same cap as an impression on another."
Frequency capping has long existed inside Amazon's buying platform at the level of a line, a campaign or a group of campaigns. What the page spells out is that the counter does not reset at the boundary of a publisher. Under a heading "How it works," it lists four points, quoted here in full:
- "If you set a frequency cap of 5 per week on a campaign targeting Prime Video, Netflix, and Fire TV, all impressions across those publishers count toward the single shared cap."
- "When a user reaches the cap, additional impressions are suppressed regardless of which publisher would serve the next ad."
- "Budget is not reduced. Suppressed impressions are redistributed to reach additional unique users."
- "No new settings, opt-in, or targeting changes are required. Cross-publisher capping activates automatically."
The last point means there is no switch. A campaign or frequency group buying from more than one publisher is counted as one pool from the moment it does so. The page does not say when the behavior began, whether any campaign can be excluded from it, or whether redistributing suppressed impressions to "additional unique users" changes the prices a campaign pays.
Where the cap holds and where it does not
A shared counter is only as strong as the ability to stop the next ad. Here the page draws a line by deal type, under the heading "Enforcement by deal type":
- "Private auction (PA) and preferred deals (PD): Fully enforced. DVA+ suppresses bids once the cap is reached."
- "Programmatic guaranteed (PG) deals: Impressions count toward the frequency cap, but delivery cannot be suppressed on the PG line. PG impressions that consume the cap will initiate enforcement on other non-PG lines in the same campaign or frequency group."
The distinction follows from how the deals work. Private auctions, Amazon's name for what much of the industry calls a private marketplace, and preferred deals leave the buyer free to decline an impression, so DVA+ can simply withhold the bid. Programmatic guaranteed deals reserve a fixed volume at an agreed price, and the page states that delivery on such a line "cannot be suppressed." Those impressions are still counted. Once they use up a user's allowance, the stopping is done elsewhere, on whichever non-guaranteed line in the same campaign or frequency group would serve next.
Amazon's worked example, set in a blue box on the page, makes the mechanics concrete:
"Example: You run a single campaign with both Netflix and Prime Video ad groups and set a campaign-level frequency cap of 5 per week. A user receives 3 impressions on Netflix (PG deal) and 1 on Prime Video. When Prime Video attempts to serve a 5th impression, the cap is enforced and the bid is suppressed. The 3 Netflix PG impressions counted toward the cap but couldn't themselves be suppressed because Netflix PG does not support bid suppression."
The arithmetic in the example is off by one. Three Netflix impressions and one Prime Video impression make four, so under a cap of five per week a fifth impression would still fall within the limit; as printed, the example stops the fifth, which is how a cap of four would behave. The point the example is built to show is unaffected: the Netflix guaranteed impressions consumed most of the allowance, and the suppression landed on Prime Video, Amazon's own service.
The example concerns Netflix programmatic guaranteed buying only. When Netflix inventory became available in Amazon DSP from the fourth quarter of 2025, PPC Land reported that the arrangement covered both programmatic guaranteed and private marketplace buying across 11 countries. Under the page's own deal-type rules, a Netflix purchase made through a private auction would be "fully enforced"; the page does not say so for Netflix specifically.
The following table records the enforcement rules as the page states them, combining the cross-publisher section with the limitations list.
| Inventory or campaign type | Counts toward caps | Delivery stops at the cap | Page wording |
|---|---|---|---|
| Private auction (PA) | Yes | Yes | "Fully enforced. DVA+ suppresses bids once the cap is reached." |
| Preferred deals (PD) | Yes | Yes | "Fully enforced." |
| PG deals from Google AdX, Amazon Publisher Direct (APD) and Amazon O&O | Yes | Not listed as a limitation | Named as the exceptions in limitation 1 |
| PG deals from other sources (Netflix in Amazon's example) | Yes | No | "impression delivery won't stop when frequency caps are met" |
| Amazon Audience Guaranteed (AAG) campaigns and ad groups | Yes | No | "impression delivery won't stop for AAG campaigns when frequency caps are met" |
| Share of Voice (SOV) ad lines on Twitch | Not supported | Not applicable | "aren't supported by frequency caps or groups" |
| Fire tablet and Kindle ads | Not supported | Not applicable | "currently not supported by frequency caps or groups" |
Two statements on guaranteed deals
The cross-publisher section and the limitations list do not describe guaranteed deals in quite the same way. The enforcement section treats programmatic guaranteed deals as a single class whose delivery "cannot be suppressed on the PG line." The limitations list, lower on the same page, carves out three sources:
"Programmatic Guaranteed (PG) deals besides Google AdX, Amazon Publisher Direct (APD), and Amazon O&O deals: Impressions from PG deals other than these sources count towards the frequency caps, but impression delivery won't stop when frequency caps are met."
Read together, the limitations list implies that guaranteed deals through Google AdX, Amazon Publisher Direct and Amazon's owned and operated properties do stop at the cap, while the enforcement section's general rule does not mention the exception. The limitations wording is consistent with an earlier Amazon announcement. A launch note dated June 7, 2024 introduced frequency groups and frequency caps at the order and line item level for video programmatic guaranteed deals from Google AdX and Amazon Publisher Direct, across 34 markets for self-service Amazon DSP users, and said customers could see whether a given deal supported capping. Today's page adds "Amazon O&O deals" to that list without defining the term.
The Google route has grown since. In August, Amazon DSP gained publisher-hosted creatives for Google Ad Manager programmatic guaranteed deals in 33 markets, an option Amazon said would give access to inventory from broadcasters, news platforms and major publishers.
How frequency is managed, according to the page
The page does not present a click path; it describes the structure of the controls and points to two linked help topics, "set a frequency cap" and "create a frequency group." According to Amazon, the arrangement works as follows.
- Two instruments. "You can set a frequency cap or create a frequency group. (a frequency group is a frequency cap applied to multiple campaigns)."
- Three levels, three intervals. "You can set frequency caps or groups at daily, hourly, or 10-minute intervals at the campaign, ad group, or advertiser account level."
- Grouping by attribute. Amazon suggests "using frequency groups across multiple campaigns with similar attributes (like products from the same business line)."
- A ceiling on account-level groups. "An advertiser account can be in a maximum of 2 Advertiser-level frequency groups."
- Where groups are not recommended. Campaigns whose ad groups "are experiencing delivery issues or have experienced delivery issues in the past," and ad groups "with narrow targeting audiences. For example, geo=NYC and demo= M 21 to 24." The page's preferred alternative is campaigns with broad audiences, "for example, geo=US or demo= Age 18 to 54."
- Cross-publisher counting. Applied automatically whenever a campaign or frequency group buys from more than one publisher.
- Reporting. Results appear in "frequency cap insights," which the page says are available on the ad group, campaign and frequency group pages of an account.
The page illustrates the levels with a toothpaste company. Its table, reproduced below, assigns the frequency cap setting to the advertiser account, ad group and campaign levels, and the frequency group setting to multiple campaigns.
| Level | Setting | Goal, as described by Amazon |
|---|---|---|
| Advertiser account | Frequency cap | Control reach and frequency for specific brands or across brands within a portfolio |
| Ad group | Frequency cap | Control how often individual whitening toothpaste products are shown |
| Campaign | Frequency cap | Control how often whitening toothpaste ads are shown in a particular Streaming TV (STV) campaign |
| Multiple campaigns | Frequency group | Control how often ads are shown across all of the company's whitening toothpaste campaigns |
Two details sit awkwardly with the rest of the page. The listed intervals are daily, hourly and 10-minute, yet both worked examples use a cap of five "per week," and the page does not explain how a weekly window is expressed in those units. The table also labels the advertiser account setting a frequency cap, while the limitations list speaks of "Advertiser-level frequency groups."
Three DVA+ pages, three views of frequency
Today's page is the third DVA+ help document in a week to deal with frequency, and each covers a different slice. The general setup guide, updated on November 13, was covered by PPC Land the following day; the streaming TV guide followed on November 17 and was covered by PPC Land the same day.
| Item | "Create a DVA+ campaign" (updated November 13, as reported by PPC Land) | "Create a DVA+ advanced campaign for Streaming TV" (updated November 17, as reported by PPC Land) | "Understand frequency in DVA+ campaigns" (updated today) |
|---|---|---|---|
| Caps per ad group | Up to 3 | Not stated | Not stated |
| Unit counted | User or household | Not stated | "per user" |
| Default cap | Applied if none is set; value not given | Not stated | Not stated |
| Levels | Ad group (with frequency groups across campaigns) | Not stated | Campaign, ad group, advertiser account |
| Intervals | Not stated | Not stated | Daily, hourly, 10-minute |
| Frequency as a goal | Not stated | Frequency KPI with a target of 2 to 5 exposures per week | Not mentioned |
| Cross-publisher counting | Not mentioned | Not mentioned | Automatic, one counter per user |
| Account-level groups | Not mentioned | Not mentioned | Maximum of 2 per advertiser account |
None of the three documents explains how a frequency target of two to five weekly exposures interacts with a cap, or whether the "per user" counter on today's page also covers caps set at household level.
Measuring what the cap saved
The measurement section introduces three formulas behind the frequency cap insights. They are reproduced here exactly as printed.
| Metric | Formula as printed | Purpose as printed |
|---|---|---|
| Incremental reach | "Impressions saved and reinvested x average impression frequency" | "calculate how many more unique users saw ads as a result of using frequency caps compared to not using them" |
| Impressions saved and reinvested | "Bid requests that were ignored because of the frequency cap" x Win rate | "calculate the estimated number of impressions that would have been shown to the same users beyond the advertiser set frequency cap" |
| Budget saved and reinvested | "Impressions saved and reinvested x CPM" | "calculate the estimated amount of budget that would have been spent on showing ads to the same users beyond the advertiser-set frequency cap if frequency capping wasn't used" |
The win rate, according to the page, "can be calculated by dividing the number of impressions by total bid requests." The logic of the second formula is plain: DVA+ ignored a number of bid requests because a user had reached the cap, and multiplying them by the campaign's usual win rate estimates how many of those requests would have turned into impressions.
The other two formulas, as printed, produce figures that do not fit the units they describe. A worked example with hypothetical inputs shows the difference; the figures are PPC Land calculations, not Amazon's. Suppose 200,000 bid requests were ignored and the campaign wins 10% of the requests it bids on. Impressions saved and reinvested come to 20,000. With an average impression frequency of four, the printed formula gives an incremental reach of 80,000 unique users, four times the number of extra impressions, which is impossible because each additional user needs at least one impression. Dividing instead of multiplying gives 5,000 users. For budget, a CPM is a price per thousand impressions: at a $30 CPM, the printed formula returns 600,000, while the same 20,000 impressions cost $600.
The printed formulas may be shorthand for calculations the insights panel performs correctly. The page does not show the panel's output, and it does not say.
The full limitations list
Rule wording matters for anyone reconciling delivery against a cap, so the seven limitations are recorded here verbatim. The list opens with "Frequency caps and groups aren't available for all types of DVA+ campaigns."
- "Programmatic Guaranteed (PG) deals besides Google AdX, Amazon Publisher Direct (APD), and Amazon O&O deals: Impressions from PG deals other than these sources count towards the frequency caps, but impression delivery won't stop when frequency caps are met."
- "Amazon Audience Guaranteed (AAG) campaigns and ad groups: Impressions from AAG campaigns count towards frequency caps and groups, but impression delivery won't stop for AAG campaigns when frequency caps are met." A sub-point adds: "Minute-level frequency caps aren't supported for AAG campaigns at the campaign level, but existing frequency cap options remain available at the ad group level."
- "Share of Voice (SOV) ad lines running on Twitch aren't supported by frequency caps or groups."
- "Fire tablet and Kindle ads are currently not supported by frequency caps or groups."
- "An advertiser account can be in a maximum of 2 Advertiser-level frequency groups."
- "We don't recommend Frequency Groups for campaigns with ad groups that are experiencing delivery issues or have experienced delivery issues in the past."
- "We don't recommend Frequency Groups for ad groups with narrow targeting audiences."
Two of the exclusions concern Amazon's own devices and services. Fire tablet and Kindle ads, and share of voice lines on Twitch, sit outside the counter entirely, so exposure through them is neither counted nor capped. The AAG sub-point also implies that minute-level caps exist at the campaign level for other campaign types, which matches the 10-minute interval in the page's main text.
Three years of frequency tools
Amazon has built its frequency controls in steps. Frequency groups, which apply one cap across several orders, launched in October 2023; when Amazon added cross-campaign reach measurement for frequency groups in December 2024, it cited internal data showing an average 6% increase in unique reach and a case in which three brands' orders overlapped by 34%. At unBoxed in October 2024, Amazon DSP said frequency groups could manage caps across campaigns, channels and devices, and reported up to 26% of budgets saved from duplicate impressions and up to 21% incremental reach. The same event brought Optimal Frequency in Amazon Marketing Cloud, which recommends a daily cap from conversion data and can create or update caps in the DSP.
Reporting followed. Cross-account reach and frequency reporting arrived on April 2, 2026, with frequency group measurement at manager account and cross-manager account levels and exclusive reach rates for streaming TV supply sources. Then came the product rename. When Amazon put its DVA+ campaign builder into a US closed beta on September 29, frequency caps were among the manual controls kept behind "DVA+ with advanced settings," while the default flow handed targeting, bidding and inventory to automation.
Today's page differs from those announcements in kind. It is not a feature launch with figures attached but a statement of rules, and its most consequential rule concerns outside inventory that Amazon cannot throttle.
Why the Netflix example matters
Netflix expanded its programmatic routes through 2026: in March it added Amazon Audiences for programmatic buys through Amazon DSP, and its May 2026 upfront listed Amazon DSP among five programmatic partners.
Yahoo made the case against guaranteed buying in October. In a post covered by PPC Land on November 11, it argued that caps set inside each publisher's system cannot see exposures elsewhere, and cited an Omnicom Media Intelligence paper from April 2026 in which more than 60% of consumers reported seeing the same ad several times in one streaming session. Amazon's page addresses part of that problem from the buyer's side: guaranteed impressions are counted in a central counter even when they cannot be stopped, and the stopping moves to inventory DVA+ does control.
The arrangement has a cost side. In a campaign mixing a large guaranteed commitment with auction lines, the guaranteed impressions are delivered in full and the auction lines absorb the suppression. The page states that budget "is not reduced" and suppressed impressions are "redistributed to reach additional unique users"; it does not say what happens when a campaign's remaining auction lines have no additional users to reach.
The definition of an impression is also moving. From January 1, 2027, DVA display ads on the Amazon Store will count an impression only once the ad appears on screen, a change Amazon expects to cut counts by about 63% on average. Today's page does not say whether frequency counters follow the same definition.
What the page leaves open
The page gives no date for when cross-publisher counting began, no change log, no list of markets, and no definition of "Amazon O&O" or Amazon Audience Guaranteed. It does not say whether open auction supply follows the private auction rule, how a weekly cap fits the daily, hourly and 10-minute intervals, whether the per-user counter applies to household-level caps or to the default cap described in the November 13 guide, or whether frequency cap insights calculate reach and budget as the printed formulas read.
Key facts
- Source document: "Understand frequency in DVA+ campaigns," Amazon Ads Support Center, under Support Center > Bidding and budget; page header reads Amazon Ads Agent
- Update date: "Updated on Nov 19, 2026"
- Source URL: not shown in the printed page
- Product: DVA+ (Display, Video, and Audio), the successor name to Amazon DSP
- Instruments: frequency cap; frequency group ("a frequency cap applied to multiple campaigns")
- Levels: campaign, ad group, advertiser account
- Intervals: daily, hourly, 10-minute
- Cross-publisher capping: "a single unified counter tracks impressions per user across all sources"; "No new settings, opt-in, or targeting changes are required"
- Fully enforced: private auction (PA) and preferred deals (PD)
- Counted but not stopped: PG deals other than Google AdX, Amazon Publisher Direct (APD) and Amazon O&O; Amazon Audience Guaranteed (AAG) campaigns and ad groups
- Not supported: Share of Voice (SOV) ad lines on Twitch; Fire tablet and Kindle ads
- Account limit: maximum of 2 advertiser-level frequency groups per advertiser account
- AAG: minute-level caps not supported at campaign level; ad group options remain
- Measurement: frequency cap insights on ad group, campaign and frequency group pages; formulas for incremental reach, impressions saved and reinvested, budget saved and reinvested
- Related Amazon launch note: frequency caps for video PG deals from Google AdX and Amazon Publisher Direct, dated June 7, 2024, 34 markets
Timeline
- October 2023 - Amazon DSP launches frequency groups, one cap across several orders
- June 7, 2024 - Amazon extends frequency groups and caps to video programmatic guaranteed deals from Google AdX and Amazon Publisher Direct in 34 markets
- October 15, 2024 - At unBoxed, Amazon DSP reports frequency groups saved up to 26% of budgets from duplicate impressions
- October 15, 2024 - Amazon Marketing Cloud adds Optimal Frequency, which can create caps in Amazon DSP
- December 23, 2024 - Amazon adds cross-campaign reach measurement for frequency groups
- September 10, 2025 - Netflix and Amazon Ads announce Netflix inventory in Amazon DSP from Q4 2025 in 11 countries
- March 4, 2026 - Netflix adds Amazon Audiences for programmatic buys through Amazon DSP
- April 2, 2026 - Cross-account reach and frequency reporting, with frequency group measurement at manager account level
- May 13, 2026 - Netflix upfront lists Amazon DSP among its programmatic partners
- August 10, 2026 - Amazon DSP gains publisher-hosted creatives for Google Ad Manager PG deals in 33 markets
- September 29, 2026 - DVA+ builder enters US closed beta, with frequency caps under advanced settings
- October 22, 2026 - Yahoo argues publisher-side caps cannot see exposures elsewhere
- November 13, 2026 - DVA+ setup guide documents up to 3 caps per ad group and a default cap
- November 17, 2026 - Streaming TV guide adds a frequency KPI of 2 to 5 exposures per week
- November 19, 2026 - Amazon updates "Understand frequency in DVA+ campaigns" with cross-publisher capping, deal-type enforcement, measurement formulas and seven limitations
- January 1, 2027 - DVA display impressions on the Amazon Store scheduled to count only once on screen
Related PPC Land coverage
- Amazon caps its automated DVA+ campaigns at 20 products - The November 13 DVA+ setup guide, including up to three frequency caps per ad group and a default cap.
- Amazon sizes streaming TV budgets as commitment plus up to five fees - The streaming TV guide with a frequency KPI of two to five weekly exposures and separate campaigns for PG share of voice deals.
- Amazon Ads puts 4-step DVA+ campaign builder in US closed beta - The September launch that placed frequency caps among the advanced settings.
- New Amazon frequency capping feature adds cross-campaign reach measurement - Reach and frequency reporting for frequency groups from December 2024.
- Amazon DSP unveils next-gen ad tech for precise reach and performance - The unBoxed 2024 announcements, including frequency groups across channels and devices.
- Amazon Marketing Cloud unveils optimal frequency for ad campaign optimization - The AMC tool that recommends a daily cap and writes caps to Amazon DSP.
- Amazon cross-account reach reporting lands after months of buildup - Deduplicated reach across accounts and frequency group measurement at manager account level.
- Netflix becomes available in Amazon DSP starting Q4 2025 - The partnership behind the Netflix example, covering PG and private marketplace buying in 11 countries.
- Netflix Ads gets Amazon audiences, Yahoo signals, and its own conversion API - Amazon Audiences for programmatic Netflix buys from March 2026.
- Amazon DSP gains publisher-hosted creatives for GAM deals in 33 markets - The Google Ad Manager programmatic guaranteed route that sits among the capped exceptions.
- Yahoo says CTV advertiser reached 60% more homes for 32% less spend - Yahoo's case that guaranteed deals leave frequency control in publisher silos.
- Amazon drops off-screen ads from impression counts, expects 63% fewer - The January 2027 change to how DVA display impressions on the Amazon Store are counted.
Summary
Who: Amazon Ads, through its Support Center page for DVA+, the buying platform formerly called Amazon DSP. The rules affect advertisers and agencies buying display, video and streaming TV across several publishers, including Netflix, Prime Video and Fire TV.
What: The page "Understand frequency in DVA+ campaigns" states that a single counter tracks each user's impressions across all publishers in a campaign or frequency group, automatically and without opt-in. Private auction and preferred deals are fully enforced; programmatic guaranteed deals outside Google AdX, Amazon Publisher Direct and Amazon O&O, and Amazon Audience Guaranteed campaigns, count toward caps but keep delivering; Twitch share of voice lines and Fire tablet and Kindle ads are not supported. The page also sets caps at campaign, ad group and advertiser account level in daily, hourly or 10-minute intervals, limits accounts to two advertiser-level frequency groups, and prints three formulas for measuring savings, two of which do not fit their stated units as written.
When: The page was updated today. It does not say when cross-publisher counting began.
Where: The Amazon Ads Support Center, under Bidding and budget, within the Amazon Ads Agent console. The page names no markets.
Why: Streaming campaigns increasingly buy the same viewers through several publishers and deal types. A shared counter limits repetition across them, but guaranteed impressions that cannot be suppressed push the stopping onto other lines, which shapes how campaigns that mix guaranteed and auction inventory spend their budgets and how the reported savings are read.
Discussion