Device§3.2.18 · Bid Request

This object provides information pertaining to the device through which the user is interacting. Device information includes its hardware, platform, location, and carrier data. The device can refer to a mobile handset, a desktop computer, set top box, or other digital device.

Attribute	Type	Description
geo	object	Location of the device assumed to be the user’s current location defined by a `Geo` object (Section 3.2.19).
dnt	integer	Standard “Do Not Track” flag as set in the header by the browser, where 0 = tracking is unrestricted, 1 = do not track.
lmt	integer	“Limit Ad Tracking” signal commercially endorsed (e.g., iOS, Android), where 0 = tracking is unrestricted, 1 = tracking must be limited per commercial guidelines.
ua	string	Browser user agent string. This field represents a raw user agent string from the browser. For backwards compatibility, exchanges are recommended to always populate `ua` with the User-Agent string, when available from the end user’s device, even if an alternative representation, such as the User-Agent Client-Hints, is available and is used to populate `sua`. No inferred or approximated user agents are expected in this field. If a client supports User-Agent Client Hints, and `sua` field is present, bidders are recommended to rely on `sua` for detecting device type, browser type and version and other purposes that rely on the user agent information, and ignore `ua` field. This is because the `ua` may contain a frozen or reduced user agent string.
sua	object	Structured user agent information defined by a `UserAgent` object (see Section 3.2.29). If both `ua` and `sua` are present in the bid request, `sua` should be considered the more accurate representation of the device attributes. This is because the `ua` may contain a frozen or reduced user agent string.
ip	string	IPv4 address closest to device.
ipv6	string	IP address closest to device as IPv6.
devicetype	integer	The general type of device. Refer to List: Device Types in AdCOM 1.0. Enum Device Types · 8 values 1Mobile/Tablet - General 2Personal Computer 3Connected TV 4Phone 5Tablet 6Connected Device 7Set Top Box 8OOH Device
make	string	Device make (e.g., “Apple”).
model	string	Device model (e.g., “iPhone”).
os	string	Device operating system (e.g., “iOS”).
osv	string	Device operating system version (e.g., “3.1.2”).
hwv	string	Hardware version of the device (e.g., “5S” for iPhone 5S).
h	integer	Physical height of the screen in pixels.
w	integer	Physical width of the screen in pixels.
ppi	integer	Screen size as pixels per linear inch.
pxratio	float	The ratio of physical pixels to device-independent pixels (DIPS).
js	integer	Support for JavaScript, where 0 = no, 1 = yes.
geofetch	integer	Indicates if the geolocation API will be available to JavaScript code running in the banner, where 0 = no, 1 = yes.
flashver	string	Version of Flash supported by the browser.
language	string	Browser language using ISO-639-1-alpha-2. Only one of `language` or `langb` should be present.
langb	string	Browser language using IETF BCP 47. Only one of `language` or `langb` should be present.
carrier	string	Carrier or ISP (e.g., “VERIZON”) using exchange curated string names which should be published to bidders a priori.
mccmnc	string	Mobile carrier as the concatenated MCC-MNC code (e.g., “310-005” identifies Verizon Wireless CDMA in the USA). Refer to https://en.wikipedia.org/wiki/Mobile_country_code for further examples. Note that the dash between the MCC and MNC parts is required to remove parsing ambiguity. The MCC-MNC values represent the SIM installed on the device and do not change when a device is roaming. Roaming may be inferred by a combination of the MCC-MNC, geo, IP and other data signals.
connectiontype	integer	Network connection type. Refer to List: Connection Types in AdCOM 1.0. Enum Connection Types · 7 values 1Ethernet; Wired Connection 2WIFI 3Cellular Network - Unknown Generation 4Cellular Network - 2G 5Cellular Network - 3G 6Cellular Network - 4G 7Cellular Network - 5G
ifa	string	ID sanctioned for advertiser use in the clear (i.e., not hashed) Unless prior arrangements have been made between the buyer and the seller directly, the value in this field is expected to be an ID derived from a call to an advertising API provided by the device’s Operating System.
didsha1 deprecated · 2.6	string	Deprecated as of OpenRTB 2.6.
didmd5 deprecated · 2.6	string	Deprecated as of OpenRTB 2.6.
dpidsha1 deprecated · 2.6	string	Deprecated as of OpenRTB 2.6.
dpidmd5 deprecated · 2.6	string	Deprecated as of OpenRTB 2.6.
macsha1 deprecated · 2.6	string	Deprecated as of OpenRTB 2.6.
macmd5 deprecated · 2.6	string	Deprecated as of OpenRTB 2.6.
ext	object	Placeholder for exchange-specific extensions to OpenRTB.

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