Geo.ipservice
Which IP geolocation provider produced the location when type is 2, as an integer from the AdCOM IP Location Services list: 1 ip2location, 2 Neustar (Quova), 3 MaxMind, 4 NetAcuity (Digital Element). Added in OpenRTB 2.4.
Field facts
- Path
device.geo.ipservice,user.geo.ipservice- Object
- Geo
- Type
- integer
- Requirement
- Optional
- Added
- OpenRTB 2.4
- Values
- AdCOM list IP Location Services
- Spec section
- 3.2.19
How it is used
AdCOM 1.0 extends the list with 511 and 512 for 51Degrees at high and medium confidence. Buyers use the provider to judge how far to trust city and postal code, since IP databases often disagree below the region level.
Allowed values
| Value | Meaning |
|---|---|
1 | ip2location: The IP2Location database. |
2 | Neustar (Quova): Neustar's IP geolocation service, which grew out of the Quova product. |
3 | MaxMind: MaxMind's GeoIP databases and web services. |
4 | NetAcuity (Digital Element): Digital Element's NetAcuity service. |
511 | 51Degrees (High Confidence): A 51Degrees lookup that reported a high confidence level for the result. |
512 | 51Degrees (Medium Confidence): A 51Degrees lookup that reported a medium confidence level, so city and postal data deserve less weight. |
Example
Where the field sits in a payload, with everything else left out:
{
"id": "req-1",
"device": {
"geo": {
"ipservice": 3
}
}
}Version history
Added in OpenRTB 2.4, 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.4 | integer | No | No |
| 2.5 | integer | No | No |
| 2.6-202210 to 2.6-202606 | integer | No | No |