Geo object
A Geo object describes a location. Under device.geo it is where the device is now; under user.geo it is the user's home base, such as a registration address, which may be somewhere else. It can hold anything from precise coordinates down to a bare country code, with type recording where the location came from.
How it is used
Every field is optional. Send the most precise data the request's consent and regulatory signals allow and no more, and never dress coarse data up as precise: coordinates belong only when they are as accurate as type and accuracy claim, never the center of a postal code or city. Codes follow specific standards (ISO 3166-1 alpha-3 for country, ISO 3166-2 for region), and mixing in other formats is a frequent source of Geo bugs.
Fields
| Field | Type | Requirement | Since | Status |
|---|---|---|---|---|
accuracy | integer | Optional | 2.4 | Current |
city | string | Optional | 2.0 | Current |
country | string | Optional | 2.0 | Current |
ext | object | Optional | 2.1 | Current |
ipservice | integer | Optional | 2.4 | Current |
lastfix | integer | Optional | 2.4 | Current |
lat | float | Optional | 2.0 | Current |
lon | float | Optional | 2.0 | Current |
metro | string | Optional | 2.0 | Current |
region | string | Optional | 2.0 | Current |
regionfips104 | string | Optional | 2.0 | Current |
type | integer | Optional | 2.0 | Current |
utcoffset | integer | Optional | 2.3 | Current |
zip | string | Optional | 2.0 | Current |
Where it sits
All objects
The field reference index lists every OpenRTB 2.x object.