Creative subtypes (audio and video)

Creative Subtypes - Audio/Video is the protocols list: the VAST and DAAST versions a player can parse, each split into an inline entry and a Wrapper entry. Requests carry it in Video.protocols and Audio.protocols, and a bid states the protocol of its own markup in Bid.protocol.

List: Creative Subtypes - Audio/Video16 valuesUsed by imp.audio.protocols, seatbid.bid.protocol, imp.video.protocols

Values

ValueNameWhat it means
1VAST 1.0VAST 1.0 inline documents; the oldest entry and rare in current traffic.
2VAST 2.0VAST 2.0 inline documents, still a common baseline for web players.
3VAST 3.0VAST 3.0 inline documents, which introduced ad pods, skip offsets, and standard error codes.
4VAST 1.0 WrapperVAST 1.0 Wrapper: a VAST 1.0 response that redirects to another VAST document.
5VAST 2.0 WrapperVAST 2.0 Wrapper: a VAST 2.0 response that redirects to another VAST document.
6VAST 3.0 WrapperVAST 3.0 Wrapper: a VAST 3.0 response that redirects to another VAST document.
7VAST 4.0VAST 4.0 inline documents, added to the list in OpenRTB 2.4.
8VAST 4.0 WrapperVAST 4.0 Wrapper, added in OpenRTB 2.4.
9DAAST 1.0DAAST 1.0 inline, the separate audio template; audio support moved into VAST as of 4.1.
10DAAST 1.0 WrapperDAAST 1.0 Wrapper: a DAAST response that redirects to another DAAST document.
11VAST 4.1VAST 4.1 inline documents, the version that brought audio into VAST. An AdCOM addition.
12VAST 4.1 WrapperVAST 4.1 Wrapper. An AdCOM addition.
13VAST 4.2VAST 4.2 inline documents. An AdCOM addition.
14VAST 4.2 WrapperVAST 4.2 Wrapper. An AdCOM addition.
15VAST 4.3VAST 4.3 inline documents, the newest version in the list. An AdCOM addition.
16VAST 4.3 WrapperVAST 4.3 Wrapper. An AdCOM addition.

Fields that use this list

How to use it

List every version the player handles, with inline and wrapper values listed separately, because a player can accept inline documents of a version while refusing redirects. The list grew in steps. OpenRTB 2.0 had 1 to 6 (VAST 1.0, 2.0, and 3.0); OpenRTB 2.4 added VAST 4.0 and DAAST 1.0 as 7 to 10 when it introduced the Audio object; VAST 4.1, 4.2, and 4.3 (11 to 16) exist only in the AdCOM list that OpenRTB 2.6 references. The numbers are not in version order, so never compare them numerically to find the newest version. The single-value Video.protocol was deprecated in OpenRTB 2.3 in favor of the array and is not part of 2.6.

Common mistakes

  • Leaving Video.protocols out. Bidders then guess the VAST version, and a version mismatch is a common reason a won creative never plays.
  • Listing inline values without the matching wrapper values when the player follows wrappers. Buyers that serve through their own ad server then see the placement as ineligible.
  • Comparing values numerically, such as treating 8 as newer than 7 or 9. Value 8 is the VAST 4.0 Wrapper, 9 is DAAST, and VAST 4.1 is 11.
  • Offering only DAAST (9, 10) on a new audio integration. Audio moved into VAST with 4.1, so audio players should list the VAST 4.1 and later values.

Validation

On OpenRTB 2.6 snapshots, RTBlint reports a value outside this list as openrtb.value.invalid. Paste a request into the tester to check the values you send.

Related lists

All lists are on the enumerated lists index.