Audio.protocols
The audio creative formats the player accepts, from AdCOM List: Creative Subtypes - Audio/Video, the same list Video uses. Recommended.
Field facts
- Path
imp.audio.protocols- Object
- Audio
- Type
- integer array
- Requirement
- Recommended
- Added
- OpenRTB 2.4
- Values
- AdCOM list Creative Subtypes - Audio/Video
- Spec section
- 3.2.8
How it is used
Under 2.4 and 2.5 the Audio object assumed DAAST, values 9 and 10. DAAST was later merged into VAST 4.1, so a player that parses VAST 4.1 or later should list those versions (11 to 16, inline and wrapper) and add DAAST only if it still parses DAAST documents.
Allowed values
| Value | Meaning |
|---|---|
1 | VAST 1.0: VAST 1.0 inline documents; the oldest entry and rare in current traffic. |
2 | VAST 2.0: VAST 2.0 inline documents, still a common baseline for web players. |
3 | VAST 3.0: VAST 3.0 inline documents, which introduced ad pods, skip offsets, and standard error codes. |
4 | VAST 1.0 Wrapper: VAST 1.0 Wrapper: a VAST 1.0 response that redirects to another VAST document. |
5 | VAST 2.0 Wrapper: VAST 2.0 Wrapper: a VAST 2.0 response that redirects to another VAST document. |
6 | VAST 3.0 Wrapper: VAST 3.0 Wrapper: a VAST 3.0 response that redirects to another VAST document. |
7 | VAST 4.0: VAST 4.0 inline documents, added to the list in OpenRTB 2.4. |
8 | VAST 4.0 Wrapper: VAST 4.0 Wrapper, added in OpenRTB 2.4. |
9 | DAAST 1.0: DAAST 1.0 inline, the separate audio template; audio support moved into VAST as of 4.1. |
10 | DAAST 1.0 Wrapper: DAAST 1.0 Wrapper: a DAAST response that redirects to another DAAST document. |
11 | VAST 4.1: VAST 4.1 inline documents, the version that brought audio into VAST. An AdCOM addition. |
12 | VAST 4.1 Wrapper: VAST 4.1 Wrapper. An AdCOM addition. |
13 | VAST 4.2: VAST 4.2 inline documents. An AdCOM addition. |
14 | VAST 4.2 Wrapper: VAST 4.2 Wrapper. An AdCOM addition. |
15 | VAST 4.3: VAST 4.3 inline documents, the newest version in the list. An AdCOM addition. |
16 | VAST 4.3 Wrapper: VAST 4.3 Wrapper. An AdCOM addition. |
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"imp": [
{
"audio": {
"protocols": [
11,
12,
13,
14
]
}
}
]
}Common mistakes
- Listing only DAAST values, which shuts out buyers that serve audio as VAST 4.1 or later.
- Listing inline versions without their wrapper values, which shuts out bidders that return wrapper tags.
Version history
Added in OpenRTB 2.4, and present in the latest snapshot. The table shows how each version's spec text types the field.
| Versions | Type in the spec | Required | Deprecated |
|---|---|---|---|
| 2.4 | integer array | Recommended | No |
| 2.5 | integer array | Recommended | No |
| 2.6-202210 to 2.6-202606 | integer array | Recommended | No |
Related fields
Other Audio fields
apibattrcompanionadcompaniontypedeliverydurfloorsextfeedmaxbitratemaxdurationmaxextendedmaxseqmimesminbitratemincpmpersecmindurationnvolpoddurpodidpodseqrqddurssequenceslotinpodstartdelaystitched
For a walkthrough of the whole object, read Audio object guide.