![]() |
RTBKit
0.9
Open-source framework to create real-time ad bidding systems.
|
#include <openrtb.h>
Public Attributes | |
| TaggedFloat | lat |
| Latitude of user (-90 to 90; South negative) | |
| TaggedFloat | lon |
| Longtitude (-180 to 180; west is negative) | |
| TaggedBool | latlonconsent |
| Has user given consent for lat/lon use? (Rubocon extension) | |
| string | country |
| Country code (ISO 3166-1 Alpha-3) | |
| string | region |
| Region code (ISO 3166-2) | |
| string | regionfips104 |
| Region using FIPS 10-4. | |
| string | metro |
| Metropolitan region (Google Metro code) | |
| Utf8String | city |
| City name (UN Code for Trade and Transport Loc) | |
| string | zip |
| Zip or postal code. | |
| string | dma |
| Direct Marketing Association code. | |
| LocationType | type |
| Source of Geo data (table 6.15) | |
3.3.11 Geo Object
The geo object itself and all of its parameters are optional, so default values are not provided. If an optional parameter is not specified, it should be considered unknown.
Note that the Geo Object may appear in one or both the Device Object and the User Object. This is intentional, since the information may be derived from either a device-oriented source (such as IP geo lookup), or by user registration information (for example provided to a publisher through a user registration). If the information is in conflict, it’s up to the bidder to determine which information to use.
1.7.6.1