Video.linearity

Whether the expected VAST response must be linear (1, an ad that plays in sequence with the content) or non-linear (2, typically an overlay shown over it). Absent means either is acceptable.

CurrentintegerOptionalSince 2.0

Field facts

Path: imp.video.linearity
Object: Video
Type: integer
Requirement: Optional
Added: OpenRTB 2.0
Values: AdCOM list Linearity Modes
Spec section: 3.2.7

How it is used

It describes the creative format, not the placement context: an outstream player still asks for linear video. Whether the ad is instream is a Video.plcmt question, and the current spec says so in this field's description. Linearity was required in OpenRTB 2.0 and 2.1 and has been optional since 2.2.

Allowed values

Value	Meaning
`1`	Linear: Linear: the ad takes over the player for its duration, as in pre-, mid-, post-roll, and outstream video.
`2`	Non-Linear (i.e., Overlay): Non-linear: an overlay or similar unit shown over or around content while it keeps playing.

Example

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

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

Common mistakes

Using linearity 1 to mean instream inventory.
Sending 0 for unknown. The list defines only 1 and 2, so omit the field instead of sending a value that triggers openrtb.value.invalid.

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	integer, default - impre See T a lis	Yes	No
2.1	integer	Yes	No
2.2	integer	No	No
2.3 to 2.4	integer	No	No
2.5	integer	No	No
2.6-202210 to 2.6-202606	integer	No	No