pub struct User {
pub id: Option<String>,
pub buyeruid: Option<String>,
pub yob: Option<i32>,
pub gender: Option<Gender>,
pub keywords: Option<String>,
pub customdata: Option<String>,
pub geo: Option<Geo>,
pub data: Option<Vec<Data>>,
pub ext: Option<Map<String, Value>>,
}
Expand description
3.2.20 Object: User
This object contains information known or derived about the human user of the device (i.e., the audience for advertising). The user id is an exchange artifact and may be subject to rotation or other privacy policies. However, this user ID must be stable long enough to serve reasonably as the basis for frequency capping and retargeting.
Fields§
§id: Option<String>
string; recommended Exchange-specific ID for the user. At least one of id or buyeruid is recommended.
buyeruid: Option<String>
string; recommended Buyer-specific ID for the user as mapped by the exchange for the buyer. At least one of buyeruid or id is recommended.
yob: Option<i32>
integer Year of birth as a 4-digit integer.
gender: Option<Gender>
string Gender, where “M” = male, “F” = female, “O” = known to be other (i.e., omitted is unknown).
keywords: Option<String>
string Comma separated list of keywords, interests, or intent.
customdata: Option<String>
string Optional feature to pass bidder data that was set in the exchange’s cookie. The string must be in base85 cookie safe characters and be in any format. Proper JSON encoding must be used to include “escaped” quotation marks.
geo: Option<Geo>
object Location of the user’s home base defined by a Geo object (Section 3.2.19). This is not necessarily their current location.
data: Option<Vec<Data>>
object array Additional user data. Each Data object (Section 3.2.21) represents a different data source.
ext: Option<Map<String, Value>>
object Placeholder for exchange-specific extensions to OpenRTB.