Audio.maxseq
The most ads that can play in an audio ad pod. Audio has carried this field since the object arrived in 2.4; 2.6 kept it and added the other pod fields around it.
Field facts
- Path
imp.audio.maxseq- Object
- Audio
- Type
- integer
- Requirement
- Optional
- Added
- OpenRTB 2.4
- Spec section
- 3.2.8
How it is used
In 2.6 it pairs with Audio.poddur to describe a dynamic pod: the length of the break and the most spots that can fill it. Unlike the Video field of the same name, which 2.6 added and marked recommended, the Audio entry keeps its original wording and no recommendation.
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"imp": [
{
"audio": {
"maxseq": 3
}
}
]
}Common mistakes
- Stripping it from 2.4 or 2.5 audio requests on the assumption that it is a 2.6 pod field. It is valid on Audio in both.
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 | No | No |
| 2.5 to 2.6-202606 | integer | No | No |
Versioned rules that name this field
openrtb.2.6.imp.video_audio.pod_biddingOpenRTB 2.6 added pod-bidding controls for video and audio inventory.
Related fields
Other Audio fields
apibattrcompanionadcompaniontypedeliverydurfloorsextfeedmaxbitratemaxdurationmaxextendedmimesminbitratemincpmpersecmindurationnvolpoddurpodidpodseqprotocolsrqddurssequenceslotinpodstartdelaystitched
For a walkthrough of the whole object, read Audio object guide.