VASTlint
DAAST-1.0-inline-category

DAAST-1.0-inline-category

DAAST `<InLine>` must contain `<Category>` (required in DAAST, unlike VAST)

ErrorDAASTIAB DAAST 1.0 §3.1.4.1DAAST 1.0 and 1.1 (all DAAST documents)

Short answer

Unlike VAST, the <Category> element is required in every DAAST <InLine>. It classifies the ad content so audio players can apply content-blocking rules.

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

<InLine>
  <AdSystem>My Ad Server</AdSystem>
  <AdTitle>My Audio Ad</AdTitle>
  <Impression><![CDATA[https://track.example.com/imp]]></Impression>
  <!-- missing Category -->
</InLine>

Valid

<InLine>
  <AdSystem>My Ad Server</AdSystem>
  <AdTitle>My Audio Ad</AdTitle>
  <Category authority="https://iabtechlab.com/IAB_Tech_Lab_Content_Taxonomy">IAB1</Category>
  <Impression><![CDATA[https://track.example.com/imp]]></Impression>
</InLine>
Check your VAST tag for DAAST-1.0-inline-category 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-creativesDAAST `<InLine>` must contain `<Creatives>` with at least one `<Creative>`DAAST-1.0-wrapper-daastadtaguriDAAST `<Wrapper>` must contain `<DAASTAdTagURI>`