Audio.maxduration
The longest audio ad the slot accepts, in seconds. Recommended, and since 2.6 mutually exclusive with Audio.rqddurs.
Field facts
- Path
imp.audio.maxduration- Object
- Audio
- Type
- integer
- Requirement
- Recommended
- Added
- OpenRTB 2.4
- Spec section
- 3.2.8
How it is used
Bidders drop creatives longer than this before pricing. In a pod it limits each spot, while Audio.poddur limits the whole break.
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"imp": [
{
"audio": {
"maxduration": 30
}
}
]
}Common mistakes
- Sending it together with
Audio.rqddurs, reported asopenrtb.fields.mutually_exclusive. - Setting it below
Audio.minduration, which leaves no length that fits.
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 | Recommended | No |
| 2.5 to 2.6-202606 | integer | Recommended | No |
Related fields
Other Audio fields
apibattrcompanionadcompaniontypedeliverydurfloorsextfeedmaxbitratemaxextendedmaxseqmimesminbitratemincpmpersecmindurationnvolpoddurpodidpodseqprotocolsrqddurssequenceslotinpodstartdelaystitched
For a walkthrough of the whole object, read Audio object guide.