Geo.accuracy

The estimated accuracy of lat and lon in meters, as reported by the device. Added in OpenRTB 2.4 and recommended when the coordinates come from location services (type 1).

CurrentintegerOptionalSince 2.4

Field facts

Path: device.geo.accuracy, user.geo.accuracy
Object: Geo
Type: integer
Requirement: Optional
Added: OpenRTB 2.4
Spec section: 3.2.19

How it is used

On iOS and Android it is a radius around the point within which the true position probably lies; check the OS documentation for the exact confidence level. A value of 5000 tells a buyer the point is only good to about five kilometers, however many decimal places the coordinates have.

Example

Where the field sits in a payload, with everything else left out:

{
  "id": "req-1",
  "device": {
    "geo": {
      "accuracy": 20
    }
  }
}

Common mistakes

Sending a fixed value such as 0 or 1 for every request, which claims impossible precision.

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 to 2.6-202606	integer	No	No