Video.delivery

How the player can receive the ad's media, from AdCOM List: Delivery Methods: 1 Streaming, 2 Progressive, 3 Download. Absent means all methods are supported.

Currentinteger arrayOptionalSince 2.0

Field facts

Path: imp.video.delivery
Object: Video
Type: integer array
Requirement: Optional
Added: OpenRTB 2.0
Values: AdCOM list Delivery Methods
Spec section: 3.2.7

How it is used

Buyers compare it with the delivery attribute on each MediaFile in their VAST response. A player that handles only one method should say so, because an absent list tells buyers every method works.

Allowed values

Value	Meaning
`1`	Streaming: The ad's media is delivered by a streaming protocol rather than as a single file.
`2`	Progressive: A single media file downloaded over HTTP and played while it downloads.
`3`	Download: The media file is fully downloaded before playback starts. Added in OpenRTB 2.4.

Example

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

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

Common mistakes

Sending strings such as "streaming" instead of the integer codes.

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	array of teger	No	No
2.1	array of integer, default All m p a C l	No	No
2.2	array of integers, default All	No	No
2.3 to 2.4	integer array	No	No
2.5	integer array	No	No
2.6-202210 to 2.6-202606	integer array	No	No