Video.w
Width of the video player in device-independent pixels. Recommended, together with Video.h.
Field facts
- Path
imp.video.w- Object
- Video
- Type
- integer
- Requirement
- Recommended
- Added
- OpenRTB 2.0
- Spec section
- 3.2.7
How it is used
Buyers use player size to choose a rendition and to judge how prominent the ad will be, so a small outstream player and a full-screen CTV app price differently. On CTV, send the resolution the app renders at, commonly 1920 by 1080. If a web player turns floating or sticky, later ad requests should carry the new, smaller size. Specs before 2.4 said pixels; 2.4 and later say device-independent pixels.
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"imp": [
{
"video": {
"w": 1920
}
}
]
}Common mistakes
- Sending the creative's size or the screen's physical pixel width instead of the player's size.
- Sending 0 as a placeholder when the size is unknown, which describes an invisible player. Leave the field out instead.
- Quoting the number, as in "640", which is an
openrtb.type.mismatch.
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 | integer, default - field highl infor | Recommended | No |
| 2.1 to 2.2 | integer | Recommended | No |
| 2.3 to 2.4 | integer | Recommended | No |
| 2.5 to 2.6-202606 | integer | Recommended | No |
Related fields
Other Video fields
apibattrboxingallowedcompanionadcompaniontypedeliverydurfloorsexthlinearitymaxbitratemaxdurationmaxextendedmaxseqmimesminbitratemincpmpersecmindurationplacementplaybackendplaybackmethodplcmtpoddedupepoddurpodidpodseqposprotocolprotocolsrqddurssequenceskipskipafterskipminslotinpodstartdelay
For a walkthrough of the whole object, read Video object guide.