Skip to main content

Web Integration Overview

As a publisher, there are many ways that you can integrate with EUID to generate identity tokens to be passed into the RTB bidstream 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 EUID, you'll implement these three key activities:

  1. Generate the EUID token
  2. Refresh the EUID token as needed
  3. Pass the token into the bidstream

There are many ways you can accomplish these key steps. Generally, 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 EUID SDK for JavaScript, client-side, to generate and refresh the token, and Google Ad Manager Secure Signals to pass the token to the bidstream.

Integration SolutionGenerate TokenRefresh TokenPass Token to the Bidstream
Prebid.js client-side (8.42.0 or later)
Prebid.js server-side (7.53.0 or later)
EUID SDK for JavaScript, client-side
EUID SDK for JavaScript, server-side
EUID SDK for Java
EUID SDK for Python
Direct integration (API endpoints)

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

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

Generate the EUID Token

There are two main paths that you can choose to generate an EUID token—you can choose to initiate the EUID token generate request:

Each option has different advantages. We recommend client-side integration using Prebid.js 8.21.0 or later as the easiest and fastest integration option.

note

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

Client-Side Integration Options

Generating the EUID 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 bidstream. If you use Prebid 8.21.0 or later, this is generally 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 EUID token on the client side, via the web page, with corresponding documentation resources.

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

Server-Side Integration Options

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

  • You can keep your personal data 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 EUID token on the server side.

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

Refresh the EUID Token

For security reasons, the EUID 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 EUID token before the current EUID token expires, you'll get a new EUID 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 EUID token.

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

Pass the Token Into the Bidstream

Publishers use EUIDs by encrypting personal data into EUID tokens and then sending the EUID tokens into the bidstream.

The following table shows integration options that support passing EUID token into the bidstream.

OptionDocumentation
Prebid.js client-side implementation (8.21.0 or later)EUID Client-Side Integration Guide for Prebid.js
Prebid.js server-side implementation (7.53.0 or later)EUID Server-Side Integration Guide for Prebid.js
note

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