VAST-2.0-wrapper-depth
Wrapper chain depth exceeds the configured maximum
Short answer
VAST wrapper chains must be finite. Most players and SSPs enforce a maximum chain depth (commonly 3–5). Chains that exceed this limit are abandoned, resulting in no-fill. The vastlint default maximum is 5 wrappers.
Why this matters in production
This rule is usually a delivery blocker. Many players, SDKs, and ad servers will discard the response or skip the affected creative once this condition is hit. Structure rules matter because wrapper resolution, creative selection, and event handling all depend on the XML tree appearing in the exact place the spec expects. Affected scope: VAST 2.0 and later (all versions).
How to fix
Reduce the wrapper chain by removing intermediate redirects, or negotiate a more direct tag from your supply partner.
VAST-2.0-wrapper-depth and other issues instantly.Validate a tag →