Advertiser/Data Provider Integration Guide
This guide covers integration steps for organizations that collect user data and push it to other UID2 participants. Data collectors include advertisers, data on-boarders, measurement providers, identity graph providers, third-party data providers, and any other organizations that send data to other participants.
If you are using an Open Operator service hosted in the Snowflake Data Marketplace, see also Snowflake Integration Guide.
The following diagram outlines the steps that data collectors must complete to map directly identifying information (DII) to UID2 identifiers for audience building and targeting.
DII refers to a user's normalized email address or phone number, or the normalized and SHA-256-hashed email address or phone number.
Refer to the following sections for details about the different parts of the diagram:
- Retrieve a raw UID2 for DII using the identity map endpoints
- Send stored raw UID2s to DSPs to create audiences
- Monitor for salt bucket rotations related to your stored raw UID2s
1: Retrieve a raw UID2 for DII using the identity map endpoint
|1-a||POST /identity/map request||Send a request containing DII to the identity mapping endpoint.|
|1-b||POST /identity/map response||The |
The response returns a user's raw UID2 and the corresponding
For ease of maintenance, a recommended approach is to store a user's raw UID2 and
2: Send stored raw UID2s to DSPs to create audiences
advertising_id (raw UID2) returned in Step 1-b to a DSP while building your audiences. Each DSP has a unique integration process for building audiences; follow the integration guidance provided by the DSP for sending raw UID2s to build an audience.
3: Monitor for salt bucket rotations related to your stored raw UID2s
A raw UID2 is an identifier for a user at a specific moment in time. The raw UID2 for a specific user changes at least once per year, as a result of the salt rotation.
Even though each salt bucket is updated approximately once per year, individual bucket updates are spread over the year. Approximately 1/365th of all salt buckets are rotated daily.
IMPORTANT: To ensure that your integration has the current raw UID2s, check salt bucket rotation for active users every day.
|3-a||POST /identity/buckets||Send a request to the bucket status endpoint for all salt buckets that have changed since a specific timestamp.|
|3-b||POST /identity/buckets||UID2 service: The bucket status endpoint returns a list of |
|3-c||POST /identity/map||Compare the returned |
If you find that the salt bucket was updated for one or more raw UID2s, re-send the DII to the identity mapping service for a new raw UID2.
|3-d||POST /identity/map||Store the new values returned for |
Use an Incremental Process to Continuously Update Raw UID2s
To keep your UID2-based audience information accurate and up to date, follow these integration steps every day:
The response from the UID2 retrieval step contains mapping information. Cache the following:
- The mapping between DII (
identifier), raw UID2 (
advertising_id), and salt bucket (
- The most recent
- The mapping between DII (
Using the results from Step 3, Monitor for salt bucket rotations related to your stored raw UID2s, remap any raw UID2 for which the salt buckets have been rotated by retrieving new raw UID2 for those IDs, following Step 1, Retrieve a raw UID2 for DII using the identity map endpoint.
Then, use the refreshed UID2s to update audiences, following Step 2, send raw UID2 to a DSP.
For a list of frequently asked questions for advertisers and data providers using the UID2 framework, see FAQs for Advertisers and Data Providers.