Audio.sequence

A legacy number for coordinating delivery of several creatives offered in one request. Present since Audio arrived in 2.4 and deprecated in 2.6 in favor of Audio.slotinpod.

Deprecated since 2.6-202204integerOptionalSince 2.4

Field facts

Path: imp.audio.sequence
Object: Audio
Type: integer
Default: 0 DEPRECATED
Requirement: Optional
Added: OpenRTB 2.4
Deprecated: OpenRTB 2.6-202204
Spec section: 3.2.8

How it is used

2.6 gave it a default of 0 when it marked the field deprecated, and the validator reports it as openrtb.field.deprecated on 2.6. Describe pods with Audio.podid, Audio.podseq, and Audio.slotinpod.

Example

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

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

Common mistakes

Copying sequence numbers 1, 2, 3 into slotinpod, where 2 means first or last rather than second.

Version history

Added in OpenRTB 2.4, 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.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.

Related fields

Other Audio fields

For a walkthrough of the whole object, read Audio object guide.