Content.ext
Exchange-specific extensions for the content. The spec defines nothing inside it, so its contents depend on the exchange's own documentation.
Field facts
- Path
app.content.ext,dooh.content.ext,site.content.ext- Object
- Content
- Type
- object
- Requirement
- Optional
- Added
- OpenRTB 2.1
- Spec section
- 3.2.16
How it is used
For identifiers from external content ID systems, use Data.cids on a content Data object (since 2.6-202505) rather than an extension.
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"app": {
"content": {
"ext": {}
}
}
}Version history
Added in OpenRTB 2.1, 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.1 | object | No | No |
| 2.2 | object cu Op be | No | No |
| 2.3 to 2.3.1 | object | No | No |
| 2.4 | object | No | No |
| 2.5 to 2.6-202606 | object | No | No |
Related fields
Other Content fields
albumartistcatcattaxchannelcontentratingcontextdataembeddableepisodefirstbroadcastgenregenresgtaxidisrckeywordskwarraylangblanguagelenlivestreamnetworkprodqproducerqagmediaratingrealtimeseasonseriessourcerelationshiptitleurluserratingvideoquality
For a walkthrough of the whole object, read CTV and ad pods.