Video.maxseq

The most ads the seller will place in a dynamic video ad pod, where the number of slots is not fixed in advance. Added to Video in OpenRTB 2.6 and recommended.

CurrentintegerRecommendedSince 2.6-202204

Field facts

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

How it is used

Send it with Video.poddur on the impression that represents a dynamic pod, or the dynamic part of a hybrid pod. Together they tell a bidder how many creatives, and of what lengths, can fit in the break. Structured pods, where each slot is its own impression, do not need it. The Audio object has carried a field of the same name since 2.4.

Example

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

{
  "id": "req-1",
  "imp": [
    {
      "video": {
        "maxseq": 4
      }
    }
  ]
}

Common mistakes

Sending it without Video.poddur, which leaves the length of the break unknown.
Sending imp.video.maxseq on a 2.5 request because Audio had it. On Video it does not exist before 2.6, and the validator reports openrtb.field.not_yet_available.

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.