Imp.video

A Video object, present when the impression is offered as video. It carries the player size, accepted durations, VAST protocols, placement type, and ad pod details a buyer needs to return markup that will play.

CurrentobjectOptionalSince 2.0

Field facts

Path: imp.video
Object: Imp
Type: object
Requirement: Optional
Added: OpenRTB 2.0
Spec section: 3.2.4

How it is used

Video has been on the Imp since OpenRTB 2.0, and 2.1 made clear that one Imp may offer banner and video together. For CTV and other instream inventory the Video object holds most of the 2.6 pod fields, while Imp.rwdd and Imp.ssai stay on the Imp itself.

Example

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

{
  "id": "req-1",
  "imp": [
    {
      "video": {
        "mimes": [
          "video/mp4"
        ],
        "protocols": [
          2,
          3,
          7
        ],
        "w": 1920,
        "h": 1080,
        "plcmt": 1
      }
    }
  ]
}

Common mistakes

Placing Imp-level 2.6 signals such as ssai or rwdd inside the video object hides them from buyers, who read them at imp.ssai and imp.rwdd.

Version history

Added in OpenRTB 2.0, 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.0	object	No	No
2.1	object, default - an impres Video Obj	No	No
2.2	object	No	No
2.3 to 2.4	object	No	No
2.5 to 2.6-202606	object	No	No

Versioned rules that name this field

openrtb.2.0.imp.video OpenRTB 2.0 unified display, mobile, and video bidding around the shared Video object and VAST ad-unit support.
openrtb.2.1.imp.video.behavior OpenRTB 2.1 clarified VAST video support in RTB transactions, including mixed banner-or-video impressions.

Related fields

Other Imp fields

For a walkthrough of the whole object, read Bid request anatomy.