Display context types
Display context types describe the kind of content around a native or display placement: content, social, or product, each with finer subtypes. In AdCOM the list feeds the display placement's context field, which is an OpenRTB 3.0 signal. OpenRTB 2.x carries the same idea inside the Native 1.2 request JSON in imp.native.request, split across context and contextsubtype.
Values
| Value | Name | What it means |
|---|---|---|
10 | Content-centric | The placement sits in content such as a newsfeed, article, or image or video gallery. |
11 | Article content | Mostly article content, which may include images within the article. |
12 | Video content | Mostly video content. |
13 | Audio content | Mostly audio content. |
14 | Image content | Mostly image content. |
15 | User-generated content | Mostly user-generated content, such as forums and comment threads. |
20 | Social-centric | The placement sits in a social setting such as a social feed, email or chat. |
21 | Mostly email content. | |
22 | Chat or instant messaging | Mostly chat or instant messaging content. |
30 | Product context | The placement sits among product listings, details, recommendations or reviews. |
31 | App store or marketplace | An app store or marketplace. |
32 | Product reviews | Mostly product reviews, possibly with products also on sale. |
500+ | Vendor-specific codes | Vendor-specific contexts agreed between the parties. |
How to use it
The list has two levels grouped by tens. 10, 20 and 30 are the general contexts, and the values after each (11 to 15, 21 and 22, 31 and 32) refine it. Send the most specific value you know. Native 1.2 uses the same subtype numbers in contextsubtype but numbers its top-level context field 1, 2 and 3, so translating between the two needs a small mapping. This is a separate list from the content contexts used in Content.context, which describe the medium (video, game, music and so on).
Common mistakes
- Sending 10, 20 or 30 in a Native 1.2
contextfield. That field takes 1, 2 or 3; the two-digit values go incontextsubtype. - Confusing this list with the content contexts list used by
Content.context. - Sending a subtype from one group with a context from another, such as
context1 withcontextsubtype21.
Validation
On OpenRTB 2.6 snapshots, RTBlint reports a value outside this list as openrtb.value.invalid. Paste a request into the tester to check the values you send.
Related lists
- Display placement types
- Creative subtypes for display
- Native data asset types
- Native image asset types
- Event types
- Event tracking methods
- Click types
- Audit status codes
- Size units
All lists are on the enumerated lists index.