Skip to main content

Integration Samples and Tools

This page lists all official EUID 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 also available at https://samples.integ.euid.eu/.

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 EUID Hashing Tool.

JavaScript SDK Integrations

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

Client-Side Integration Using EUID 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 EUID SDK for JavaScript

This sample is for publishers who want more control over EUID 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 EUID SDK for JavaScript

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

EUID Server-Only (Server-Side)

This sample is for publishers who want all EUID 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 EUID tokens to be passed by Prebid.js in the RTB bidstream. For details, see EUID Integration Overview for Prebid.

Client-Side Integration with Prebid.js

This sample is for publishers who have access to personal data on the client side and want to do front-end development only. Prebid.js handles the entire EUID 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 personal data on the server side and can do server-side development. The server generates the initial EUID 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 EUID module using functions provided by Prebid. This allows Prebid.js to handle all EUID 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 EUID 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 EUID 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 EUID 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 EUID 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 EUID 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 EUID 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

EUID 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 EUID integration options. For a summary of all the integration options available, see EUID Integration Guides: Summary.