Digital Audio Ad Serving Template (DAAST) has been deprecated, and is being replaced by VAST. Please use VAST 4.1 or above. For more information please read this blog post.
The Digital Audio Ad Serving Template (DAAST) is the IAB’s first technical solution addressing the fragmented audio advertising market. DAAST provides a common set of specifications for audio ad delivery, execution, and reporting across a wide variety of devices and platforms.
DAAST also paves the way for other streaming formats by addressing various environment needs like mobile and in-car radios where access to a web browser is limited or doesn’t exist which complicates ad and play tracking functionality.
Adoption of DAAST makes it easier for ad servers to reach publisher platforms compliant with the DAAST specification. DAAST offers a compliance program for audio players, which requires support for linear ads and optionally one or more of the following ad formats: Companion ads, Ad pods, and Skippable ads. More details can be found in the Compliance section below.
|Download DAAST 1.1 (PDF)||View the Webinar||Understanding Digital Audio Ad Serving (PDF)||Read the Press Release|
To help the industry adopt the new DAAST specification, several resources have been created:
VAST to DAAST Transition Schema (Excel)
A resource for those updating their VAST implementation to DAAST. This comparison document shows where changes in VAST were made to develop DAAST. A quick comparison should help programmers make a smooth transition.
DAAST XML Schema Definition (XSD) Draft (.zip)
Provided for developers to validate their DAAST tags, this is a draft and candidate for the IAB’s Tech Lab to review. Please notify us with any inconsistencies or issues.
DAAST Ad Categories (Excel)
Alist of ad categories to be referenced in the DAAST required <Categories> element. This list is based on of the Quality Assurance Guidelines Contextual Taxonomy and the OpenRTB Content Codes, but includes additional categories.
General DAAST Audio Player and Ad Server Expectations
The audio player should be able to recognize a DAAST response, parse it, and execute the files provided depending on publisher specifications. The player is responsible for supporting XML conventions, respecting ad server instructions in a DAAST inline or wrapper response, and playing the audio ad as specified within the declared limits of audio player. Ads that fall short of publisher requirements may be ignored.
Audio Ad Server
In order for an audio ad to function in a DAAST-compliant audio player or audio streaming server the ad server must respond to the player’s request for an ad with an XML response formatted according to the DAAST specification. Audio ad servers should also be able to receive process and respond to any player requests for tracking and error details in the DAAST response that the ad server sent.
Minimum Requirements for DAAST Player Compliance
Audio Player Feature support
- XML parsing
- Linear Ads
Companies must disclose their level of support for DAAST, although IAB doesn’t specify how this is done. Additionally, companies should specify whether disclosure is at time of sale or in real-time per bid.
Areas of disclosure include:
- Tracking client-side or server-side
- Caching practices
- Supported Ad Types
DAAST Compliance for IAB Members
Adoption of DAAST improve efficiencies for buyers and sellers of audio advertising. IAB promotes member adoption of DAAST through its compliance program. To be recognized as DAAST compliant, a member company must self-attest to meeting the minimum requirements stated in the technical specification. DAAST compliance is applicable for Audio Players, but audio ad servers must meet certain expectations for their ads to work in a DAAST compliant player. To submit your self-attested compliance, please see IAB’s Compliance Program.
To learn about Technology Compliance Programs for DAAST, please email Compliance@iabtechlab.com.
Developed by the Digital Audio Ad Serving Template Working Group
IAB Tech Lab Contact
Senior Product Manager