Once a Taxonomy is uploaded and active, DataX allows the upload of user/audience data against its segments, attributes, scores, campaigns (or anything that can have user-level data associated with it) – generically referred to as a taxonomy-element in this section.
Important
Any international identifiers require prior written approval. Before sending Yahoo hashed IP addresses, or any other identifier type not already covered by your agreement with Yahoo, relating to users located outside the United States, contact your Yahoo business development representative. You may send this data only after Yahoo confirms in writing that your agreement covers the identifier type and region and enables your account for it. Data sent without that confirmation is not authorized and may be rejected or deleted. Do not send raw (unhashed) IP addresses.
A User can be identified by one of the following types of identifiers:
EMAIL. Must be SHA256 hashed, also known as hems.
Phone. Must be SHA256 hashed.
PXID.
IXID. IXID are encrypted cookies.
Mobile IDs. Mobile IDs are also known as maids.
IDFA (iOS ID for Advertisers)
GPADVID (Google Play Advertising ID)
IP Address.
The IP Address must be SHA256 hashed and be one of the following versions: IPv4 or IPv6. IPv6 addresses must be normalized according to RFC 5952 normalization rules.
IP addresses from the following countries are allowed:
United States
United Kingdom
Australia
Canada
IP addresses from any other country are not allowed and are dropped from the upload.
DataX can be customized to represent data keyed by either a taxonomy-element or a user-identifier in order to provide the flexibility of choosing a representation that works best for your data and backend systems. User Data is modeled as the following set of resource collectors in DataX:
/audience - This is the most generic and recommended form of representing user data. It allows the upload a list of segment qualifications and/or attribute values against a user identifier. Data is represented as a set of JSON records. A single upload will usually contain data for more than just one user, but DataX does not require that the same set of attribute and segment qualifications be specified for every user. Each user record is handled independently.
/audience/segment - This is a more specialized and alternate way of uploading a list of users against a segment (taxonomy-element of type “SEGMENT”)
/audience/attribute - Similar to /audience/segment, this is a more specialized and alternate way of uploading a list of users and their values for a certain attribute, e.g., a score (“taxonomy-element of type “ATTRIBUTE”)
/audience/opt-out - Use this to opt out user(s) completely.
Though the limit on payload size of uploads is reasonably high, it is strongly recommended that data be uploaded in frequent mini-batches of incremental updates to optimize reach.