Skip to main content

Web Integration Overview

As a publisher, there are many ways that you can integrate with UID2 to generate identity tokens to be passed into the RTB bid stream in the context of your web pages.

On this page, you'll find a high-level overview of integration steps and integration options, with links to additional information for each option.

Key Integration Steps

At a high level, to integrate with UID2, you'll implement these three key activities:

  1. Generate the UID2 token
  2. Refresh the UID2 token as needed
  3. Pass the UID2 token into the bid stream

There are many ways you can accomplish these key steps. The simplest and fastest implementation is a full client-side implementation using Prebid.js 8.21.0 or later.

Integration Options Summary

The following table summarizes the solutions available for each integration step.

To accomplish all steps, you can combine solutions. For example, you could use the UID2 SDK for JavaScript, client-side, to generate and refresh the token, and Google Ad Manager Secure Signals to pass the token to the bid stream.

Integration SolutionGenerate TokenRefresh TokenPass Token to the Bid Stream
Prebid.js client-side (8.21.0 or later)
Prebid.js server-side (7.53.0 or later)
UID2 SDK for JavaScript, client-side
UID2 SDK for JavaScript, server-side
UID2 SDK for Java
UID2 SDK for Python
Direct integration (API endpoints)
Google Ad Manager Secure Signals

To choose your implementation and get started, follow these steps:

  1. Review the summary of options to generate a UID2 token:
  2. Review the options to refresh the UID2 token.
  3. Review the options to pass the token into the bid stream.
  4. Choose the option that's best for you, and then click through to the implementation documentation.

Generate the UID2 Token

There are two main paths that you can choose to generate a UID2 token: you can choose to initiate the UID2 token generate request on the client side (in the user's browser) or on the server side.

Each option has different advantages. Client-side integration is easy and fast; integration using Prebid.js 8.21.0 or later is the easiest and fastest integration option.

note

For all integration options, you can choose to store the UID2 token in local storage or cookie storage.

Client-Side Integration Options

Generating the UID2 token on the client side has the following advantages:

  • The code runs on the client side, on the consumer's web page, and no server-side coding is required.
  • There is a Prebid integration that handles all functions for you—token generation, token refresh, and passing the token into the bid stream. If you use Prebid 8.21.0 or later, this is the simplest and fastest implementation option.

If you choose a client-side integration, you'll need to provide a list of your top-level domains, for security purposes, as part of account setup. For details, see Client-Side Implementation for Publishers on the Account Setup page.

The following table summarizes the options for publishers who want to generate the UID2 token on the client side, via the web page, with corresponding documentation resources.

OptionDocumentation
Prebid.js client-side implementation (8.21.0 or later)UID2 Client-Side Integration Guide for Prebid.js
UID2 SDK for JavaScript, client-side implementationClient-Side Integration Guide for JavaScript

Server-Side Integration Options

Generating the UID2 token on the server side has the following advantages:

  • You can keep your directly identifying information (DII) entirely on the server side.
  • If your development resources are back-end developers, you might prefer a server-side integration.
  • For server-side Prebid integration, there is no requirement to update to the latest Prebid version, as long as your version is 7.53.0 or later.

The following table summarizes the options for publishers who want to generate the UID2 token on the server side.

OptionDocumentation
UID2 SDK for JavaScript, server-side implementationServer-Side Integration Guide for JavaScript
UID2 SDK for Java- Publisher Integration Guide, Server-Only
- UID2 SDK for Java
UID2 SDK for Python- Publisher Integration Guide, Server-Only
- UID2 SDK for Python
Direct integration (API endpoints)Publisher Integration Guide, Server-Only

Refresh the UID2 Token

For security reasons, the UID2 token has a limited life, but there is a built-in mechanism to refresh the token so that you can still use it.

When you get the token, it comes with a refresh token and a time stamp indicating how long the token is valid for. As long as you use the refresh token to generate a new UID2 token before the current UID2 token expires, you'll get a new UID2 token and an updated refresh token each time. You can continue to refresh to keep the information valid.

The following table shows the integration options that support refreshing the UID2 token.

OptionDocumentation
Prebid.js client-side implementation (8.21.0 or later)UID2 Client-Side Integration Guide for Prebid.js
Prebid.js server-side implementation (7.53.0 or later)UID2 Server-Side Integration Guide for Prebid.js
UID2 SDK for JavaScript, client-side implementationClient-Side Integration Guide for JavaScript
UID2 SDK for JavaScript, server-side implementationServer-Side Integration Guide for JavaScript
UID2 SDK for Java- Publisher Integration Guide, Server-Only
- UID2 SDK for Java
UID2 SDK for Python- Publisher Integration Guide, Server-Only
- UID2 SDK for Python
Direct integration (API endpoints)Publisher Integration Guide, Server-Only

Pass the UID2 Token Into the Bid Stream

Publishers use UID2s by encrypting DII (email addresses or phone numbers) into UID2 tokens and then sending the UID2 tokens into the bid stream.

The following table shows integration options that support passing UID2 token into the bid stream.

OptionDocumentation
Prebid.js client-side implementation (8.21.0 or later)UID2 Client-Side Integration Guide for Prebid.js
Prebid.js server-side implementation (7.53.0 or later)UID2 Server-Side Integration Guide for Prebid.js
Google Ad Manager Secure SignalsGoogle Ad Manager Secure Signals Integration Guide
note

As long as you generate the token and keep it refreshed, you can also use other options for passing the UID2 token into the bid stream.