BidRequest.device
A Device object describing the device that will show the ad: user agent, IP address, device type, operating system, identifiers, and location. Recommended.
Field facts
- Path
device- Object
- BidRequest
- Type
- object
- Requirement
- Recommended
- Added
- OpenRTB 2.0
- Spec section
- 3.2.1
How it is used
Most pricing and fraud checks start here. Buyers read device type, connection, and geo for targeting, and the IP address and user agent for invalid traffic filtering. Privacy signals in BidRequest.regs and Device.lmt decide which identifiers may be present.
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"device": {
"ua": "Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Mobile/15E148",
"ip": "203.0.113.44",
"devicetype": 4,
"os": "iOS"
}
}Common mistakes
- Sending a server's IP or a placeholder user agent on server-to-server traffic, which makes real users look like data center traffic.
- Forwarding
Device.ifaon requests whereRegs.coppais 1.
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 to 2.2 | object | Recommended | No |
| 2.3 to 2.6-202606 | object | Recommended | No |
Related fields
Other BidRequest fields
For a walkthrough of the whole object, read Bid request anatomy.