UserAgent§3.2.29 · Bid Request
Structured user agent information, which can be used when a client supports User-Agent Client Hints. If both device.ua and device.sua are present in the bid request, device.sua should be considered the more accurate representation of the device attributes. This is because the device.ua may contain a frozen or reduced user agent string due to deprecation of user agent strings by browsers.
| Attribute | Type | Description |
|---|---|---|
| browsers | brandversion[] | Each BrandVersion object (see Section 3.2.30) identifies a browser or similar software component. Implementers should send brands and versions derived from the Sec-CH-UA-Full-Version-List header\*. |
| platform | brandversion | A BrandVersion object (see Section 3.2.30) that identifies the user agent’s execution platform / OS. Implementers should send a brand derived from the Sec-CH-UA-Platform header, and version derived from the Sec-CH-UA-Platform-Version header\*. |
| mobile | integer | 1 if the agent prefers a “mobile” version of the content, if available, i.e. optimized for small screens or touch input. 0 if the agent prefers the “desktop” or “full” content. Implementers should derive this value from the Sec-CH-UA-Mobile header\*. |
| architecture | string | Device’s major binary architecture, e.g. “x86” or “arm”. Implementers should retrieve this value from the Sec-CH-UA-Arch header\*. |
| bitness | string | Device’s bitness, e.g. “64” for 64-bit architecture. Implementers should retrieve this value from the Sec-CH-UA-Bitness header\*. |
| model | string | Device model. Implementers should retrieve this value from the Sec-CH-UA-Model header\*. |
| source default 0 | integer | The source of data used to create this object, List: User-Agent Source in AdCOM 1.0 |
| ext | object | Placeholder for vendor specific extensions to this object. |
Field descriptions are published in the official IAB Tech Lab OpenRTB 2.6 spec (CC-BY 3.0) · enumeration values sourced from AdCOM 1.0 · first-draft proofreading