Audio.delivery
How the audio media can be delivered, from AdCOM List: Delivery Methods: 1 Streaming, 2 Progressive, 3 Download. Absent means all methods are supported.
Field facts
- Path
imp.audio.delivery- Object
- Audio
- Type
- integer array
- Requirement
- Optional
- Added
- OpenRTB 2.4
- Values
- AdCOM list Delivery Methods
- Spec section
- 3.2.8
How it is used
Match it to how the ad's media file is fetched. When the ad is stitched into the content server-side, the stitcher fetches the file, so list what the stitcher accepts.
Allowed values
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"imp": [
{
"audio": {
"delivery": [
1
]
}
}
]
}Common mistakes
- Sending strings such as "streaming" instead of the integer codes.
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 | No | No |
| 2.5 | integer array | No | No |
| 2.6-202210 to 2.6-202606 | integer array | No | No |
Related fields
Other Audio fields
apibattrcompanionadcompaniontypedurfloorsextfeedmaxbitratemaxdurationmaxextendedmaxseqmimesminbitratemincpmpersecmindurationnvolpoddurpodidpodseqprotocolsrqddurssequenceslotinpodstartdelaystitched
For a walkthrough of the whole object, read Audio object guide.