Audio.rqddurs
The exact audio ad durations the slot accepts, in seconds, aimed at live radio and similar streams where an ad of the wrong length leaves silence or cuts into content. Mutually exclusive with Audio.minduration and Audio.maxduration. Added in 2.6.
Field facts
- Path
imp.audio.rqddurs- Object
- Audio
- Type
- integer array
- Requirement
- Optional
- Added
- OpenRTB 2.6-202204
- Spec section
- 3.2.8
How it is used
Radio breaks are often built from 15, 30, and 60 second units. Listing those lengths keeps out creatives that would leave a gap. Bidders state each creative's length in Bid.dur.
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"imp": [
{
"audio": {
"rqddurs": [
15,
30,
60
]
}
}
]
}Common mistakes
- Sending it together with
Audio.mindurationorAudio.maxduration, which the validator reports asopenrtb.fields.mutually_exclusive. - Sending an empty array, which permits no duration at all.
Version history
Added in OpenRTB 2.6-202204, 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.6-202204 | Added in the first 2.6 release, published without a structured text archive; the 2.6-202210 republication is the first tagged text. | ||
| 2.6-202210 to 2.6-202606 | integer array | No | No |
Versioned rules that name this field
openrtb.2.6.imp.video_audio.rqddursOpenRTB 2.6 added exact-duration requirements for video and audio creatives.
Related fields
Other Audio fields
apibattrcompanionadcompaniontypedeliverydurfloorsextfeedmaxbitratemaxdurationmaxextendedmaxseqmimesminbitratemincpmpersecmindurationnvolpoddurpodidpodseqprotocolssequenceslotinpodstartdelaystitched
For a walkthrough of the whole object, read Audio object guide.