Video.podid

A string that groups impressions into one video ad pod. Every impression in the same request whose video object carries the same value belongs to the same ad break. Added in OpenRTB 2.6.

CurrentstringOptionalSince 2.6-202204

Field facts

Path: imp.video.podid
Object: Video
Type: string
Requirement: Optional
Added: OpenRTB 2.6-202204
Spec section: 3.2.7

How it is used

A structured pod is several impressions, one per slot, sharing a pod ID, each with its own duration constraints and Video.slotinpod. A dynamic pod can be a single impression with Video.poddur and Video.maxseq. The value only needs to be unique within the request, so a readable label such as the break name works.

Example

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

{
  "id": "req-1",
  "imp": [
    {
      "video": {
        "podid": "break-2"
      }
    }
  ]
}

Common mistakes

Sending it as a number. The field is a string, so 2 should be "2".
Giving each slot of one break a different value, which tells buyers the slots belong to separate breaks.
Leaving pod identifiers in imp.video.ext from a pre-2.6 integration, where 2.6 buyers do not look.

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_bidding OpenRTB 2.6 added pod-bidding controls for video and audio inventory.