Audio.podid
A string that groups impressions into one audio ad pod. Every impression in the same request whose audio object carries the same value belongs to the same break. Added in OpenRTB 2.6.
Field facts
- Path
imp.audio.podid- Object
- Audio
- Type
- string
- Requirement
- Optional
- Added
- OpenRTB 2.6-202204
- Spec section
- 3.2.8
How it is used
A podcast mid-roll with two spots can be two impressions sharing one pod ID, each with its own Audio.slotinpod. A dynamic break can instead be a single impression with Audio.poddur and Audio.maxseq.
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"imp": [
{
"audio": {
"podid": "midroll-1"
}
}
]
}Common mistakes
- Sending it as a number instead of a string.
- Giving the spots of one break different values, which tells buyers they belong to separate breaks.
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 | string | 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
apibattrcompanionadcompaniontypedeliverydurfloorsextfeedmaxbitratemaxdurationmaxextendedmaxseqmimesminbitratemincpmpersecmindurationnvolpoddurpodseqprotocolsrqddurssequenceslotinpodstartdelaystitched
For a walkthrough of the whole object, read Audio object guide.