Content.embeddable
Whether the content can be embedded elsewhere, such as through an embeddable video player, where 1 means yes and 0 means no. Added in OpenRTB 2.1.
Field facts
- Path
app.content.embeddable,dooh.content.embeddable,site.content.embeddable- Object
- Content
- Type
- integer
- Requirement
- Optional
- Added
- OpenRTB 2.1
- Spec section
- 3.2.16
Allowed values
0, 1.
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"app": {
"content": {
"embeddable": 1
}
}
}Common mistakes
- Sending true or false instead of 1 or 0. Serializers built on the protobuf schema produce booleans here.
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 | integer | No | No |
| 2.2 | integer em th be | No | No |
| 2.3 to 2.3.1 | integer | No | No |
| 2.4 | integer | No | No |
| 2.5 to 2.6-202606 | integer | No | No |
Related fields
Other Content fields
albumartistcatcattaxchannelcontentratingcontextdataepisodeextfirstbroadcastgenregenresgtaxidisrckeywordskwarraylangblanguagelenlivestreamnetworkprodqproducerqagmediaratingrealtimeseasonseriessourcerelationshiptitleurluserratingvideoquality
For a walkthrough of the whole object, read CTV and ad pods.