Video.sequence

A legacy number for coordinating delivery of several creatives offered in one request. Deprecated in OpenRTB 2.6, where the spec points to Video.slotinpod instead.

Deprecated since 2.6-202204integerOptionalSince 2.0

Field facts

Path: imp.video.sequence
Object: Video
Type: integer
Default: 0 DEPRECATED
Requirement: Optional
Added: OpenRTB 2.0
Deprecated: OpenRTB 2.6-202204
Spec section: 3.2.7

How it is used

It has been on Video since 2.0, with a stated default of 1 through 2.2 and of 0 once 2.6 marked it deprecated. Its meaning was loose, so exchanges used it in different ways before 2.6 gave ad pods proper fields. On 2.6 the validator reports it as openrtb.field.deprecated. Describe pod membership and position with Video.podid, Video.podseq, and Video.slotinpod.

Example

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

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

Common mistakes

Reading it as the slot index within a pod on 2.6 traffic instead of using Video.slotinpod.
Copying sequence numbers 1, 2, 3 into slotinpod. That list holds only -1, 0, 1, and 2, and 2 means first or last, not second.

Version history

Added in OpenRTB 2.0, deprecated in 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.0	integer	No	No
2.1 to 2.2	integer, default 1	No	No
2.3 to 2.4	integer	No	No
2.5	integer	No	No
2.6-202210 to 2.6-202606	integer, default 0 DEPRECATED	No	Yes

Versioned rules that name this field

openrtb.2.6.deprecated_fields OpenRTB 2.6 deprecated legacy sequence, device-ID hash, demographic, and single-api fields.