Skip to content

Latest commit

 

History

History
109 lines (75 loc) · 5.95 KB

overview-publishers.md

File metadata and controls

109 lines (75 loc) · 5.95 KB
title Publishers
description Information summary for publishers.
hide_table_of_contents false
use_banner true
banner_title EUID overview for publishers
banner_description Maintain audience targeting in the ever-changing advertising industry for better impression monetization and more relevance.
banner_icon publishers
banner_text_color white
banner_text_color_dark black
banner_background_color #035959
banner_background_color_dark #DCDEE1
displayed_sidebar sidebarPublishers

import Link from '@docusaurus/Link'; import SnptIntegratingWithSSO from '../snippets/_snpt-integrating-with-sso.mdx'; import SnptPrivateOperatorOption from '../snippets/_snpt-private-operator-option.mdx'; import SnptPublisherImplementationResources from '../snippets/_snpt-publisher-implementation-resources.mdx';

As a publisher, you can benefit from the cross-device presence of European Unified ID (EUID) and take advantage of a consistent identity fabric on all your inventory.

Learn about benefits, workflow, documentation, and other resources for publishers adopting EUID, as well as instructions for getting started.

Benefits of EUID for publishers

Here are just some of the intended benefits for publishers integrating with EUID:

  • Addressable audience targeting on desktop, mobile, and CTV with a single identifier.
  • Frequency management across devices.
  • More relevant content recommendations.
  • The ability to provide personalized ad experiences with relevant content.
  • The ability to offer opt-out, with the goal of improving consumer privacy controls.

Workflow for publishers

The following steps provide a high-level outline of the workflow intended for organizations that propagate EUID tokens to the bidstream via SSPs—for example, identity providers, publishers, and SSO providers. Publishers can choose to work with an SSO provider or an independent ID provider that is interoperable with EUID and can handle the EUID integration on behalf of publishers.

  1. A user visits a publisher website, mobile app, or CTV app.

  2. The publisher provides transparency around its data practices and asks the user to provide an email address or phone number, by login, SSO login, or other means, and consent to the use of their email address or phone number for EUID.

  1. Once the user has provided an email address or phone number, and consented, the publisher sends it to the EUID Operator via an SDK or direct API integration.
:::tip
A publisher can authorize an SSO provider or identity provider to pass <Link href="../ref-info/glossary-uid#gl-personal-data">personal data</Link> on their behalf.
:::
  1. The EUID Operator:

    • Takes the email or phone number.
    • Performs the salt, hash, and encryption process.
    • Returns the EUID token.
  2. The publisher stores the EUID token to share with SSPs during real-time bidding.

    • Server-side: The publisher stores the token in a mapping table, DMP, data lake, or other server-side application.
    • Client-side: The publisher stores the token in a client-side app or in the user’s browser as a first-party cookie.
  3. The publisher retrieves the EUID token from storage.

  4. The publisher sends the EUID token to the SSP.

  5. The SSP puts the bid request, with the EUID token, into the bidstream.

Publisher workflow

Integrating with single sign-on (SSO)

Private Operator option

Getting started

To get started, follow these steps:

  1. Request access to EUID by filling out the form on the Request access page.

  2. Identify the properties that you want to integrate with EUID.

  3. Sign the EUID contract.

  4. Determine whether you want a client-side, client-server, or server-side integration, and tell your EUID contact.

    For more information about these options, see Integration approaches.

  5. Receive the EUID credentials.

  6. Build your integration to EUID via an SDK or direct integration with the EUID APIs, using the applicable implementation resources.

    :::note Be sure to encrypt request messages to EUID. For details, see Encrypting requests and decrypting responses. :::

  7. Test:

    • Confirm that EUID tokens are being generated and passed correctly within the bid request.
    • Troubleshoot as needed, and work with SSPs to properly pass EUID tokens in bid requests.
  8. Go live.

Implementation resources

FAQs for publishers

For a list of frequently asked questions for publishers using the EUID framework, see FAQs for publishers.