Video.poddur

The total seconds of ad time buyers can fill in a dynamic video ad pod, or in the dynamic portion of a hybrid pod. It describes the whole break, while the duration fields constrain individual slots. Added in 2.6 and recommended.

CurrentintegerRecommendedSince 2.6-202204

Field facts

Path: imp.video.poddur
Object: Video
Type: integer
Requirement: Recommended
Added: OpenRTB 2.6-202204
Spec section: 3.2.7

How it is used

The spec requires it only for the dynamic parts of a pod. A 120 second break with a Video.maxseq of 4 can take four 30 second spots or a mix of shorter and longer ones, within the per-slot limits set by Video.minduration and Video.maxduration or Video.rqddurs. Video.mincpmpersec usually accompanies it to price that time.

Example

Where the field sits in a payload, with everything else left out:

{
  "id": "req-1",
  "imp": [
    {
      "video": {
        "poddur": 120
      }
    }
  ]
}

Common mistakes

Using it for the length of a single slot. That is Video.maxduration; poddur covers the entire break.
Sending a value shorter than Video.minduration, which makes the pod impossible to fill.

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	Recommended	No

Versioned rules that name this field

openrtb.2.6.imp.video_audio.pod_bidding OpenRTB 2.6 added pod-bidding controls for video and audio inventory.