DAAST-1.0-wrapper-daastadtaguri
DAAST-1.0-wrapper-daastadtaguri
DAAST `<Wrapper>` must contain `<DAASTAdTagURI>`
ErrorDAASTIAB DAAST 1.0 §3.3.1.1DAAST 1.0 and 1.1 (all DAAST documents)
Short answer
<DAASTAdTagURI> is the URL the player must fetch to retrieve the next DAAST response. Without it the wrapper cannot be resolved and the ad break will be empty.
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. DAAST rules validate the structural and semantic requirements specific to digital audio ad serving. Audio-specific fields like Category, AdInteractions, and audio MediaFile attributes are required by the spec and are absent from standard VAST validation. Affected scope: DAAST 1.0 and 1.1 (all DAAST documents).
Invalid
<Wrapper>
<AdSystem>My DSP</AdSystem>
<!-- <VASTAdTagURI> is wrong here — DAAST uses <DAASTAdTagURI> -->
<VASTAdTagURI><![CDATA[https://dsp.example.com/daast.xml]]></VASTAdTagURI>
</Wrapper>Valid
<Wrapper>
<AdSystem>My DSP</AdSystem>
<DAASTAdTagURI><![CDATA[https://dsp.example.com/daast.xml]]></DAASTAdTagURI>
</Wrapper>Check your VAST tag for
DAAST-1.0-wrapper-daastadtaguri and other issues instantly.Open the VAST tag validator →Other DAAST rules
DAAST-1.0-root-versionRoot `<DAAST>` element must have a version attributeDAAST-1.0-root-version-value`<DAAST>` version attribute must be a recognised version string (`1.0` or `1.1`)DAAST-1.0-root-has-ad-or-error`<DAAST>` must contain at least one `<Ad>` or `<Error>`DAAST-1.0-ad-has-inline-or-wrapperEach DAAST `<Ad>` must contain exactly one `<InLine>` or `<Wrapper>`DAAST-1.0-inline-adtitleDAAST `<InLine>` must contain `<AdTitle>`DAAST-1.0-inline-impressionDAAST `<InLine>` must contain at least one `<Impression>`DAAST-1.0-inline-categoryDAAST `<InLine>` must contain `<Category>` (required in DAAST, unlike VAST)DAAST-1.0-inline-creativesDAAST `<InLine>` must contain `<Creatives>` with at least one `<Creative>`