Content.livestream

Whether the content is broadcast on a schedule, where 1 means scheduled or linear viewing and 0 means video on demand or another user-started stream. This meaning dates from 2.6-202606; earlier versions used 1 for live content.

CurrentintOptionalSince 2.0

Field facts

Path: app.content.livestream, dooh.content.livestream, site.content.livestream
Object: Content
Type: int
Requirement: Optional
Added: OpenRTB 2.0
Spec section: 3.2.16

How it is used

From 2.0 through 2.6-202505, 1 meant the content was live, such as a live stream or live blog, and 0 meant it was not. 2.6-202606 kept the name and type, changed the question, and moved the idea of live right now to Content.realtime. A replay airing on a linear channel is now livestream 1 with realtime 0. Sellers that set livestream to 1 for live events should recheck each case against the new definition and add realtime.

Allowed values

0, 1.

Example

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

{
  "id": "req-1",
  "app": {
    "content": {
      "livestream": 1
    }
  }
}

Common mistakes

Keeping the old meaning after moving to 2.6-202606. A live stream the user starts on demand is now 0, not 1.
Sending true or false instead of 1 or 0.

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 to 2.1	integer	No	No
2.2	integer “1	No	No
2.3 to 2.3.1	integer	No	No
2.4	integer	No	No
2.5 to 2.6-202505	integer	No	No
2.6-202606	int	No	No