Size units
Size units say what the width and height of a placement are measured in: device independent pixels, inches or centimeters. AdCOM uses the list in the unit field of its display and video placement objects, where it defaults to 1, so it is an OpenRTB 3.0 signal. OpenRTB 2.x has no unit field: banner, video and creative sizes are always device independent pixels.
Values
| Value | Name | What it means |
|---|---|---|
1 | Device independent pixels (DIPS) | Device independent pixels, the default and the unit OpenRTB 2.x uses everywhere for ad sizes. |
2 | Inches | Inches, for placements described by physical size. |
3 | Centimeters | Centimeters, for placements described by physical size. |
How to use it
Most placements should use 1. Physical units make sense where pixel density varies widely or the physical size matters more than resolution, as with large out-of-home screens. When converting AdCOM placements to OpenRTB 2.x, convert inches and centimeters to device independent pixels first, because 2.x consumers will read any number in Banner.w or Video.w as pixels. The unit applies only to the placement's own size, not to the creative sizes it accepts.
Common mistakes
- Assuming
Device.wuses the same unit. In OpenRTB 2.x, device dimensions are physical screen pixels, while banner and video sizes are device independent pixels. - Sending a physical size without a unit, which a receiver reads as pixels.
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 context types
- 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
All lists are on the enumerated lists index.