Table of contents
Introduction
As of Criteo SDK 4.1.0, publishers have the option to send additional User and Context data as signals that will be used by Criteo to bid.
User Data
User Data are signals that represent non-personal data related to the user in the current session.
Data | Key Constant | Description |
|---|---|---|
Hashed Email | | Hashed the user's email address. This data can be crossed with hashed emails from other sites or apps data with deterministic and cross-device matching |
Developer User ID | | A developer's own persistent unique user identifier. This ID will be used for app-level ad frequency capping. |
Email Hashing Format
Criteo SDK provides a utility class EmailHasher to hash a user's email address based on the format that's accepted by Criteo.
In a case where you'd like to hash the user's email address yourself, please follow the following steps:
Encode in UTF-8
Trim all white spaces
Convert to lowercase
Hash with MD5 & output as ASCII text
Hash with SHA256 and output as ASCII text
Example:
Original Email: john.doe@gmail.com
MD5:
e13743a7f1db7f4246badd6fd6ff54ffSHA256 of MD5:
000e3171a5110c35c69d060112bd0ba55d9631c7c2ec93f1840e4570095b263a
Context Data
Context Data are signals that signify the current context/state of the app that the user interact with.
Data | Key Constant | Description |
|---|---|---|
Content URL | | A web-equivalent URL of the content that the user is currently viewing. The URL will be analyzed server side to extract its category. The category will be used to better blacklist/whitelist campaigns that will be delivered. |