Link Search Menu Expand Document

PDF

Device Object

Demand Partners

BidRequest Object


BidRequest.device

Each BidRequest object may contain a Device object, which provides details about the end-user’s computing environment. The Device object can contain an Extensions object (see below) and can reference the Geo object.

Field nameData typeDescriptionSent?
uastringThe HTTP user agent, which typically indicates the user’s browser. For example, “Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_2; en-us)”Sometimes
geogeo objectAn object containing properties that describe the geographic location of the user as derived from the device.Sometimes
dntintegerThe “do not track” flag. This flag indicates whether the user’s web browser is set for private browsing.
   • 0 = False
   • 1 = True (Browser is set for private browsing.)
Sometimes
lmtintegerThe “limit tracking” flag. If the user’s mobile device is set for private browsing, the LMT (limit tracking) flag is passed.
   • 0 = False
   • 1 = True (The user does not want to be tracked.)
Sometimes
ipstringThe ipv4 address closest to the user’s device. For example, 238.122.7.1Sometimes
ipv6stringThe IP address closest to device as IPv6.Sometimes
devicetypeintegerThe detected device category for the user’s device as defined in the IAB’s OpenRTB 2.5 specification.

Note: OpenX OpenRTB uses a devicetype value of 1001 to indicate text (SMS).
Sometimes
makestringThe make for the user’s device. For example, AppleSometimes
modelstringThe model for the user’s device. For example, iPhoneSometimes
osstringThe operating system for the user’s device. For example, iOSSometimes
osvstringThe version number for the user’s operating system. For example, 3.1.2Sometimes
hwvstringThe device’s hardware version. For example, 5S (for iPhone 5S)Sometimes
hintegerThe physical height of the device’s screen, in pixels.Sometimes
wintegerThe physical width of the device’s screen, in pixels.Sometimes
languagestringA single two-letter code ISO 639-1 for the user’s preferred browsing language on their device. For example, enSometimes
carrierstringThe carrier or ISP using exchange-curated string names. Should be published to bidders a priori. For example, VERIZONSometimes
mccmncstringThe mobile carrier for the user’s device as the concatenated MCC-MNC code. Refer to Mobile country code for additional examples.

Note: The dash between the MCC and MNC parts is required to remove parsing ambiguity. For example, 310-005 (Identifies Verizon Wireless CDMA in the USA.)
Sometimes
connectiontypeintegerThe detected data connection type for the user’s device as defined in the IAB’s OpenRTB 2.5 specification. For example, 2Sometimes
ifastringThe ID for advertisers (also referred to as “IDFA”). This is the ID sanctioned for advertiser use in the clear (not hashed).Sometimes
didsha1stringThe SHA-1 hash identifier for the user’s device, such as the UDID for an iOS device. For example, 2b6f0cc904d137be2e1730235f5664094b831186Sometimes
dpidsha1stringThe SHA-1 hash of the Android ID for the end-user’s mobile device.Sometimes
dpidmd5stringThe MD5 hash of the Android ID for the end-user’s mobile device.Sometimes
macsha1stringThe SHA-1 hash of the device’s MAC address.Sometimes
macmd5stringThe MD5 hash of the device’s MAC address.Sometimes
extextension objectAn object containing properties that describe custom fields related to this device.Sometimes

For additional details, see:


BidRequest.device.ext

To provide additional details about the end-user’s device, the Device object may include an Extensions object.

Field nameData typeDescriptionSent?
languagearray of stringsAn array of two-letter codes for the user’s preferred browsing languages on their device, listed in order of the user’s language preferences in the browser.Always