Audio.stitched

Whether the ad is stitched into the audio content (1) or delivered to the player separately (0).

CurrentintegerOptionalSince 2.4

Field facts

Path: imp.audio.stitched
Object: Audio
Type: integer
Requirement: Optional
Added: OpenRTB 2.4
Spec section: 3.2.8

How it is used

Stitching changes who fetches the media and who fires tracking: in a stitched stream the server assembles the audio, so client-side trackers may never run. Since 2.6, Imp.ssai describes the same situation for any media type in more detail, separating stitched assets with client-side tracking (2) from fully server-side delivery (3). Send both and keep them consistent.

Allowed values

0, 1.

Example

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

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

Common mistakes

Sending true or false. It is an integer flag, and booleans trigger openrtb.dialect.bool_for_integer.
Sending 1 here while Imp.ssai is 1, all client-side, which contradicts it.

Version history

Added in OpenRTB 2.4, 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 to 2.6-202606	integer	No	No

Related fields

Other Audio fields

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