Content.context

The kind of content, as a value from the AdCOM Content Contexts list: 1 video, 2 game, 3 music, 4 application, 5 text, 6 other, 7 unknown.

CurrentintegerOptionalSince 2.0

Field facts

Path: app.content.context, dooh.content.context, site.content.context
Object: Content
Type: integer
Requirement: Optional
Added: OpenRTB 2.0
Values: AdCOM list Content Contexts
Spec section: 3.2.16

How it is used

OpenRTB 2.0 to 2.2 typed it as a string even though the values came from a numbered table; 2.3 made it an integer, and 2.6 moved the list to AdCOM. Use 1 for video and CTV programming, 3 for audio streams, and 5 for articles.

Allowed values

Value	Meaning
`1`	Video: The user is watching video content, on demand or live.
`2`	Game: The user is playing an interactive game.
`3`	Music: The user is listening to audio, such as music or internet radio.
`4`	Application: The user is using an interactive application that is not a game.
`5`	Text: The user is reading a mainly textual document, such as a web page, eBook, or news article.
`6`	Other: The content is known but fits none of the other contexts.
`7`	Unknown: The seller does not know the content context.

Example

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

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

Common mistakes

Sending "1" as a string, a leftover from 2.2-era builders. From 2.3 the field is an integer and strict parsers reject the string.

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	string	No	No
2.2	string et	No	No
2.3 to 2.3.1	integer	No	No
2.4	integer	No	No
2.5	integer	No	No
2.6-202210 to 2.6-202606	integer	No	No