Amazon opened its buying platform to the fourth generation of the industry standard for video ad serving on September 02, 2026, covering third-party publisher inventory across 34 countries while its own properties stay on the older specification.

Amazon Ads published a launch announcement dated September 02, 2026 confirming that Amazon DSP now supports VAST 4, in versions 4.0 through 4.3, on third-party publisher inventory worldwide. The change is not a migration in the usual sense. Nothing is switched off, no deadline is attached, and advertisers are not asked to rebuild anything. What changed is the answer Amazon's bidder gives when a video player asks what it can handle.

Version negotiation happens at the impression

According to Amazon Ads, the platform reads what the publisher's video player supports for each ad opportunity and responds with the highest compatible version. Publishers still running VAST 2 or VAST 3 continue to be served as before. Publishers that support VAST 4 now receive VAST 4 automatically, without an election on the buyer's side.

That design detail carries more weight than the version number. Runtime negotiation means the transition is distributed across the supply base rather than scheduled by the buying platform, and it means a single campaign can be serving two different specification generations simultaneously depending on which player answered the call. There is no cutover date because there is no cutover.

Eligibility is wide. Managed-service and self-service advertisers using Amazon DSP are covered. Amazon-served campaigns select the optimal version automatically. Advertisers running their own advertiser ad server gain the ability to use VAST 4 tags on third-party inventory, which is the part of the announcement most likely to change day-to-day trafficking practice, since it removes a downgrade step that agencies with their own serving stack had been absorbing.

The exception sits inside the same document

Amazon-operated inventory is excluded. The announcement states that Stores, Fire TV and comparable owned surfaces continue "to only support VAST 2/3 creatives." The company offers no timeline for closing that gap and no explanation for it.

The asymmetry is the most consequential line in a short document. A buyer running one video campaign across Amazon's owned properties and the open web now sits astride two creative standards at once. Creative teams delivering a single master asset to a single demand-side platform will find that asset conditioned differently depending on whether the impression came from Fire TV or from a news publisher in Frankfurt. Measurement teams reconciling that campaign will be reading events produced under two different schemas.

For a company that has spent two years arguing that its authenticated signal set makes cross-channel comparison possible, the persistence of a version split inside its own supply is awkward. It is also, in fairness, common. Owned-and-operated video environments across the industry tend to run bespoke player stacks with long upgrade cycles, and the constraint is engineering rather than strategy.

What VAST 4 actually carries

The Video Ad Serving Template is the XML specification maintained by IAB Tech Lab that tells a player which file to fetch, how long it runs and what to report back. Its version history explains why publishers gate on the fourth generation rather than treating it as cosmetic.

VAST 3.0, released in 2012, introduced ad pods, the sequential set of advertisements delivered into a single break. VAST 4.0 arrived in 2016 and made two structural changes: it separated the high-quality mezzanine source file from the ready-to-serve rendition, and it introduced a registered universal advertisement identifier. VAST 4.1, published in November 2018, added the AdVerification node that carries Open Measurement signals, and folded the separate Digital Audio Ad Serving Template into the same document. VAST 4.2 followed in June 2019 with support for SIMID, the interface that moved interactive playback control from the creative to the player as the replacement for VPAID. VAST 4.3 landed in December 2022, setting five as the recommended ceiling on wrapper redirects, with error code 302 reserved for a breached limit.

Each of those additions solves a problem that only becomes visible at scale. The mezzanine file matters because server-side insertion platforms transcode creatives to match a stream's quality ladder, and a pre-compressed rendition transcodes badly. The universal advertisement identifier matters because frequency capping, competitive separation and creative reconciliation all require a persistent handle on the advertisement itself rather than on the impression. IAB Tech Lab integrated that identifier into the Open Measurement SDK in June 2025, tightening the link between the two.

The retrofit work of recent years underlines how much of the market never moved. IAB Tech Lab published a draft VAST CTV Addendum in April 2024 and released the finished document in July 2024, specifically to backport registered advertisement identifiers, SIMID support and a high-resolution media node into VAST 2 and VAST 3 implementations still carrying traffic. Standards bodies do not spend that effort on versions nobody uses.

Thirty-four markets, including China

The availability map runs to 34 countries. North America accounts for three: the United States, Canada and Mexico. South America contributes Brazil alone. Europe is the largest block at seventeen, covering Germany, Spain, France, Italy, the United Kingdom, Belgium, Switzerland, Poland, Turkey, Austria, the Netherlands, Sweden, Finland, Norway, Ireland, Denmark and Luxembourg. The Middle East adds seven: Saudi Arabia, the United Arab Emirates, Israel, Egypt, Morocco, Bahrain and Kuwait. Asia Pacific closes the list with six, comprising Australia, India, Japan, China, New Zealand and Singapore.

That figure matches the perimeter Amazon used when it converted every Amazon DSP account into a single global advertiser account on July 30, 2026, a migration that also spanned 34 countries. It exceeds the map Amazon used three weeks earlier, when publisher-hosted creatives for Google Ad Manager programmatic guaranteed deals opened in 33 markets with China absent. Video version support arrives with China included. Whether that reflects a different technical dependency or simply a different product team's rollout sequence, the announcement does not say.

Consistency in market lists is not a trivial matter for agencies planning multinational activations. A buyer assembling a pan-European video campaign needs to know whether a capability stops at the same border as the last one, and the recurring mismatch between 33 and 34 forces that check to be repeated each time.

Why publishers gate their inventory

Amazon's stated rationale is that many publishers now require VAST 4 to fully activate their inventory, and that campaigns can consequently reach more premium supply and benefit from improved cross-channel measurement without workflow changes. That is the company's characterisation rather than an independently verified outcome, and no figures accompany it.

The underlying dynamic is verifiable enough. Connected television publishers in particular depend on transcoding pipelines that want a source file, and on verification vendors that read the AdVerification node. IAB Europe's April 2026 programmatic connected television guide set out how server-side insertion moves delivery logic away from the client device and complicates impression measurement, and argued that publishers and technology providers must disclose whether impressions are counted server-side, client-side or through a hybrid method. IAB Australia made a related point in mid-2026, observing that insertion standards govern how advertisements are signalled and stitched rather than how impressions are counted.

Version fragmentation compounds that. A completion rate reported from a VAST 2 wrapper and one reported from a VAST 4 document with a verification node attached are not equally auditable, even when the number is identical. IAB Tech Lab's December 2025 connected television format work went further into the same territory, establishing six new formats and acknowledging that server-side insertion platforms commonly require mezzanine files to produce acceptable quality across playback environments.

Where the version cost shows up most directly is in the ordinary in-stream slot. A pre-roll bought programmatically from a publisher that has upgraded its player but keeps receiving downgraded responses is inventory the publisher may simply withhold, which is the mechanism behind the phrase about fully activating inventory. IAB Spain's April 2026 supply-side platform guide, which measured working media at 41% of programmatic spend, spent part of its length distinguishing the VAST standard from the VAST tag and the VAST document precisely because the three are conflated in commercial conversations.

Where this sits in Amazon's buying stack

The announcement belongs to a sequence rather than standing alone. Amazon has spent roughly a year widening what its demand-side platform can reach and narrowing the number of interfaces required to reach it.

On the supply side, Spotify audio and video inventory entered the platform across nine markets on October 1, 2025. Triton Digital added Amazon DSP as a demand-side partner on its programmatic marketplace on July 15, 2026, opening audio, podcast and streaming inventory across more than 80 countries. Publisher-hosted creatives for Google Ad Manager programmatic guaranteed deals opened on August 10, 2026, letting buyers transact against inventory where the asset never passes through Amazon's systems.

On the workflow side, in-market audience definitions were unified across 32 countries on November 4, 2025. Automatic deal selection for streaming television campaigns launched on April 15, 2026 in the United States. Self-service access to more than 50 third-party measurement products opened across 18 countries on May 15, 2026. Ten capabilities landed across the Brand+ and Performance+ automated products on July 22, 2026, including the removal of the single-deal default from new streaming television lines.

Read together, the pattern is consistent: reduce the number of decisions a buyer must make manually, and increase the amount of inventory reachable from one seat. VAST 4 negotiation fits that shape exactly. It removes a compatibility question the buyer never wanted to answer and adds supply the buyer could not previously address.

What marketers get, and what they do not

The practical gain is access. Publishers that had been declining or degrading Amazon DSP video demand for specification reasons become addressable, and the buyer does nothing to make that happen. For agencies running their own advertiser ad server, VAST 4 tags become usable on third-party inventory, which removes a translation layer and the discrepancy risk that comes with it.

The practical limit is that none of this is quantified. Amazon has not disclosed how much third-party video supply was previously unreachable, how many publishers gate on VAST 4, or what share of impressions will now negotiate up rather than down. Without those figures, the size of the opening is unknowable from the announcement, and buyers will only see it in delivery reports over the coming weeks.

There is also a measurement caveat that cuts against the stated benefit. Improved cross-channel measurement depends on the channels sharing a standard. As long as Stores and Fire TV accept only VAST 2/3 creatives, the cross-channel comparison Amazon markets most heavily runs across the exact seam this release does not close. Interoperability in a supply chain is bounded by its least capable participant, and in this case that participant is Amazon.

Open questions

Three remain unanswered. First, whether Amazon-operated inventory will move to VAST 4 at all, and on what schedule. Second, whether the 34-market map will become the standard perimeter for platform capabilities or will keep drifting against the 33-market lists used elsewhere. Third, how the version split will be represented in reporting, since a buyer reconciling one campaign across two specification generations needs to know which events came from which.

The announcement was published in Amazon's product announcements feed with no named executive, no partner list and no performance claim. It is plumbing, documented as plumbing. The consequences will be visible in delivery data rather than in the document.

Timeline

Summary

Who: Amazon Ads, covering managed-service and self-service advertisers using Amazon DSP, third-party video publishers whose players support the fourth generation of the video ad serving template, and agencies running their own advertiser ad servers.

What: Amazon DSP began supporting VAST versions 4.0 through 4.3 on third-party publisher inventory, negotiating the highest compatible version per ad opportunity based on what the publisher's player reports. Publishers on VAST 2 and VAST 3 continue to be served at those versions. Amazon-operated inventory, including Stores and Fire TV, continues to accept only VAST 2/3 creatives.

When: The launch announcement carries the date September 02, 2026. No transition deadline is attached, and no advertiser action is required.

Where: Thirty-four countries: the United States, Canada and Mexico in North America; Brazil in South America; Germany, Spain, France, Italy, the United Kingdom, Belgium, Switzerland, Poland, Turkey, Austria, the Netherlands, Sweden, Finland, Norway, Ireland, Denmark and Luxembourg in Europe; Saudi Arabia, the United Arab Emirates, Israel, Egypt, Morocco, Bahrain and Kuwait in the Middle East; and Australia, India, Japan, China, New Zealand and Singapore in Asia Pacific.

Why: According to Amazon Ads, many publishers now require the fourth-generation specification to fully activate their inventory, so buyers gain access to supply that was previously degraded or withheld, along with better cross-channel measurement, without changing their workflow. The company supplied no figures for the size of that opening, and the exclusion of its own inventory leaves a version seam inside the same platform.