Skip to main content

Integration Samples and Tools

This page lists all official UID2 sample implementations highlighting common integration use cases, along with links to live demo sites, source code, and related documentation. Use this page to quickly identify which sample matches your needs and explore working examples.

All sample sites are available at https://samples.uidapi.com/.

note

The sample implementations on this page demonstrate email-based integrations; however, phone numbers are also supported and follow the same integration patterns, using a different SDK method and requiring an additional normalization step. For a phone number integration example, see the UID2 Hashing Tool.

JavaScript SDK Integrations​

This section summarizes sample integrations using the UID2 SDK for JavaScript directly, without Prebid.js or Google Secure Signals. For integration options by participant type, see Publisher Web Integration Overview or Advertiser/Data Provider Integration Overview.

Client-Side Integration Using UID2 SDK for JavaScript​

This sample is for publishers who prefer a fully client-side integration using the SDK for JavaScript Reference Guide to generate and manage tokens directly in the browser. This approach is ideal for fast prototyping with minimal back-end requirements.

Client-Server Integration Using UID2 SDK for JavaScript​

This sample is for publishers who want more control over UID2 token creation (handled on your servers), while using the SDK for JavaScript on the client side to manage and refresh tokens in the browser.

React Client-Side Integration Using UID2 SDK for JavaScript​

This sample is for publishers with React apps who want to integrate UID2 directly into their component-based architecture using the SDK for JavaScript.

UID2 Server-Only (Server-Side)​

This sample is for publishers who want all UID2 operations to occur on the server side, offering maximum control, security, and flexibility without relying on a client-side SDK.

Prebid.js Integrations​

This section includes sample pages for generating UID2 tokens to be passed by Prebid.js in the RTB bidstream. For details, see UID2 Integration Overview for Prebid.

Client-Side Integration with Prebid.js​

This sample is for publishers who have access to DII on the client side and want to do front-end development only. Prebid.js handles the entire UID2 workflow—token generation, storage, and automatic refresh—with no server-side development required.

Client-Server Integration with Prebid.js​

This sample is for publishers who have access to DII on the server side and can do server-side development. The server generates the initial UID2 token, and Prebid.js continues to manage the token lifecycle—including storage and automatic refresh.

Deferred Client-Side Integration with Prebid.js​

This sample demonstrates how publishers who already have Prebid.js configured can still add the UID2 module using functions provided by Prebid. This allows Prebid.js to handle all UID2 work even when the module wasn't included in the initial configuration.

Prebid.js with Secure Signals​

This sample demonstrates how to configure Prebid.js with both UID2 and Google Secure Signals, enabling the integration between header bidding and Google Ad Manager.

Google Secure Signals Integrations​

This section includes sample pages for passing UID2 identity data to Google's advertising systems through their Secure Signals feature. For details, see Google Ad Manager Secure Signals Integration Guide.

Client-Side Secure Signals​

This sample is for publishers who want a client-side integration with Google Ad Manager Secure Signals. In this integration, the UID2 SDK for JavaScript generates and manages tokens, and the Secure Signals script automatically shares the tokens with Google Ad Manager for ad requests.

Client-Server Secure Signals​

This sample is for publishers who want to generate UID2 tokens on the server side while using the SDK for JavaScript on the client to manage tokens. The Secure Signals script automatically shares the token with Google Ad Manager for ad requests.

Server-Side Secure Signals​

This sample is for publishers who want all UID2 token logic handled server-side. The Secure Signals script reads the token and automatically shares it with Google Ad Manager for ad requests.

React Client-Side Secure Signals​

This sample is for publishers with React apps who want a client-side integration with Google Secure Signals. It uses the UID2 SDK for JavaScript within a React component to generate and manage tokens, while the Secure Signals script automatically shares the token with Google Ad Manager.

Tools​

UID2 Hashing Tool​

This tool is for developers or clients validating data preparation, such as hashing and normalization of emails or phone numbers before token requests. The tool is available at the following links:

note

The sample sites on this page highlight some common integrations, but do not represent all available UID2 integration options. For a summary of all the integration options available, see UID2 Integration Guides: Summary.