VASTlint
Back to blog
Wrapper chains/10 min read

Missing VAST Error URIs on a wrapper hide 301, 302, and 303 from the hop that still bills impressions.

VAST expects an Error element on each wrapper so players can beacon timeout, depth, and no-fill failures upstream. A chain without HTTPS Error URIs on hops you control still validates as XML while buyer diagnostics show healthy delivery and seller logs show a serve.

Author

Alex Sekowski

Published

November 17, 2026

Reading time

10 min read

WrappersVASTError codesCTVSSAI

On November 16, 2026, TVREV published Magnite executive Matt McLeggon arguing that streaming ad dollars still have not caught up with streaming audiences. Fill pressure is the seller headline. For buyers, the same week produces a quieter failure mode: wrapper chains that bill impressions on the outer hop while the player never reports error 301, 302, or 303 upstream because nobody trafficked an Error URI on the wrapper that failed.

IAB Tech Lab publishes VAST as the contract between ad servers and players. The Error element is not decorative. It is where the player sends [ERRORCODE] when a wrapper times out, when depth limits bite, or when a chain resolves to empty VAST. Omit Error on a hop you control and the production failure is split: seller analytics show a serve, buyer logs show silence, and the support ticket argues demand quality instead of a broken redirect.

This post is the document check before you blame McLeggon's inventory gap on bid density alone. A wrapper without Error, or with Error on http instead of https, is spec-shaped enough to pass casual review and behavior-shaped enough to hide chain breakage from the ad server that was supposed to learn the hop failed.

What 301, 302, and 303 actually measure

Code 301 means the player could not finish loading a VASTAdTagURI before its timeout. Code 302 means the player hit its wrapper depth limit without reaching an InLine. Code 303 means wrappers resolved but the final document had no ad to play. Each code assumes the player can HTTP GET an Error URL with the macro replaced.

Those codes are not the same as vastlint rule IDs. They are runtime buckets the player chooses after it already attempted the chain. A missing Error element does not prevent the player from failing; it prevents the failure from reaching the ad server that trafficked the outer hop. That is why fill conversations and error-code files disagree even when both sides read accurate instruments.

SSAI and exchange gateways amplify the split. The stitcher impression often fires when the outer wrapper returns, before the inner hop proves playable media. If the inner fetch times out and the outer wrapper had no Error URI, the stitcher log still looks like monetization while the buyer's VAST analytics never receive a 301 beacon. CTV capacity arguments assume someone upstream learns the chain broke. Error URIs are that learning path.

Who can see the failure

The publisher player sees HTTP status, parse results, and its own timeout clock. It only beacons upstream when Error is present and uses HTTPS if the environment requires it. The ad server on the outer wrapper sees Impression pixels it inserted, not the player's internal reason code, unless Error was configured to receive the macro.

The buyer DSP or verification seat sees the tag URL the exchange forwarded, not always every hop the stitcher merged. When diagnostics stop at the first fetch, a missing Error on hop two is invisible until someone inspects the full chain. Magnite's interview is about macro demand; your Monday is often a wrapper someone normalized for latency and stripped Error from because the element looked optional.

Pre-bid filters on the OpenRTB request cannot substitute for this check. A bid can win while the VAST response still lacks Error on the seller wrapper. The rtblint capacity note on CTV fill is about request readability; this failure is response reachability after the win. Both can be true on the same deal.

Wrapper that bills an impression but cannot report 301
xml
<VAST version="4.2">  <Ad id="seller-wrap-902">    <Wrapper>      <AdSystem>SSP Gateway</AdSystem>      <VASTAdTagURI><![CDATA[https://buyer.example/vast?deal=441]]></VASTAdTagURI>      <Impression><![CDATA[https://ssp.example/wrapimp?id=902]]></Impression>      <Creatives/>    </Wrapper>  </Ad></VAST>

This XML is ordinary exchange output. The seller impression is on the wrapper. The buyer inline with MediaFile and quartile trackers lives behind VASTAdTagURI. Without Error, many players still follow the URI, still time out on a slow buyer host, and still emit nothing the SSP ad server can correlate to error 301.

Add Error with [ERRORCODE] on every hop you own before you ask finance why fill rose while completion rates fell. The player replaces the macro with 301, 302, or 303 depending on the failure mode. If Error uses http on a CTV app that blocks mixed content, the beacon fails for a second reason and the ticket becomes SSL hygiene instead of chain depth.

Compare this hop to the inner inline you expect to play. Impression on the wrapper plus Error on the wrapper is valid VAST. Impression on the wrapper plus Error only on the inline is not a substitute when the timeout happens before the inline arrives.

Same wrapper with an HTTPS Error beacon
xml
<VAST version="4.2">  <Ad id="seller-wrap-902">    <Wrapper>      <AdSystem>SSP Gateway</AdSystem>      <VASTAdTagURI><![CDATA[https://buyer.example/vast?deal=441]]></VASTAdTagURI>      <Impression><![CDATA[https://ssp.example/wrapimp?id=902]]></Impression>      <Error><![CDATA[https://ssp.example/vasterror?code=[ERRORCODE]&aid=902]]></Error>      <Creatives/>    </Wrapper>  </Ad></VAST>

Get VAST spec updates, platform guides, and release notes in your inbox.

Signing up means you agree to receive VAST debugging guides and release updates. Privacy.

The only structural change is Error with a macro the player understands. IAB documents Error under Wrapper and InLine; both locations matter because failures happen on different hops. A chain three wrappers deep needs three Error endpoints if each hop is yours to traffic, not one Error copied only to the creative inline at the end.

Video tech FAQs distinguish 301 timeout from 302 depth from 303 no-fill. Your log pipeline should store those as different investigations. A spike in 301 is CDN or buyer latency. A spike in 302 is policy on maximum wrappers. A spike in 303 is demand returning empty VAST. Without Error URIs, you never get the histogram; you get unexplained zeros in quartiles while impressions climb.

OM SDK and verification nodes do not replace Error. Verification scripts measure the session that played. Error reports chain breakage before a creative session exists. The November OM SDK CTV format posts cover pause and overlay measurement; they assume a playable document arrived. Error URIs answer whether the document arrived at all.

Checklist before the next fill review

  • Fetch the live tag URL in the tester. If the first body is a Wrapper, open the inspector and record hop count.
  • On each hop your team controls, confirm Error exists and uses https.
  • Confirm [ERRORCODE] is literal in the URL, not pre-filled with a static digit.
  • Match declared VAST version to player support for wrapper Error placement.
  • Compare seller impression time to buyer error beacons on the same attempt ID when available.
  • When SSAI merges wrappers, verify Error was not dropped in normalization logs.
  • Separate 301 investigations from 303 investigations before retargeting demand.

What to send in the escalation

Send hop number, the wrapper XML or fetched URL, and whether Error was present on that hop. Send player timeout settings when arguing 301. Do not send only the inner inline if the failure happened on VASTAdTagURI fetch.

vastlint checks missing Error on wrappers, http Error URIs, and broken macro tokens on Error URLs. It does not call the player or prove the beacon was received. It gives you a document-level answer when someone insists the tag was green in a schema tool that ignored Error entirely.

Pair validator output with the inspector when the tag is URL-driven. The validator answers pasted XML. The inspector answers which hop dropped Error before the player timed out.

Keep a hop map in the IO when multiple sellers wrap the same buyer URL. Operations teams rotate vendors without retesting Error placement on each new outer host. A green validator result on the buyer attachment does not update when the exchange adds a second wrapper without Error. Re-fetch after any trafficking change that touches the tag URL, not only after creative swaps.

Fill reviews should include error histograms

Seller QBRs that only chart impression growth cannot explain quartile collapse when wrappers fail quietly. Ask for error 301, 302, and 303 counts per wrapper hop before accepting that demand was thin. If the ad server never received those beacons, the histogram is empty by configuration, not by market.

Buyers who pay for verification on the creative still need Error on the chain that delivers the creative. Verification vendors measure playback and IVT on the inline that played or on declared tracking URLs. They do not replace the wrapper Error URI the SSP was responsible for trafficking.

Document the player timeout value used when arguing 301 against a buyer CDN. The IAB spec assigns 301 to player-defined timeouts on VASTAdTagURI fetch. Two environments with different clocks will disagree on whether the hop was slow or dead.

Archive one failing fetch with response headers and time to first byte when opening a 301 ticket against a buyer host. Network teams need that evidence because the VAST document alone cannot prove latency.

Treat empty VAST after wrappers as 303, not as a player bug, until Error beacons confirm the player reached a terminal hop. Confusing the two sends engineers to tune creative codecs when the upstream returned no ad.

Validate Error URIs on the wrapper chain

Paste wrapper XML or fetch the live tag, then walk hops in the inspector when the first response is still a Wrapper.

Open the VAST inspector

Sources

Fill rate versus request readability on the OpenRTB side.

Tracking URL parameters on the same tags after the chain resolves.

Related stories

All posts

Check a tag while you read.

Open a related example, then replace it with your own tag.