From ce9ec36b76b6d5ce92420970017a592321380117 Mon Sep 17 00:00:00 2001 From: genwhittTTD Date: Fri, 21 Feb 2025 17:48:12 -0500 Subject: [PATCH 1/6] initial carve up of home page --- docs/intro.md | 92 +------------------- docs/{ => ref-info}/images/UID2Workflows.svg | 0 docs/{ => ref-info}/images/source/source.txt | 0 docs/ref-info/uid-infrastructure.md | 73 ++++++++++++++++ docs/ref-info/uid-principles.md | 39 +++++++++ sidebars.js | 15 +++- 6 files changed, 129 insertions(+), 90 deletions(-) rename docs/{ => ref-info}/images/UID2Workflows.svg (100%) rename docs/{ => ref-info}/images/source/source.txt (100%) create mode 100644 docs/ref-info/uid-infrastructure.md create mode 100644 docs/ref-info/uid-principles.md diff --git a/docs/intro.md b/docs/intro.md index e504519e7..b28665ea7 100644 --- a/docs/intro.md +++ b/docs/intro.md @@ -16,99 +16,13 @@ UID2 is a framework that enables deterministic identity for advertising opportun The term "UID2" can refer to either the framework or an actual identifier. Unless otherwise indicated, this page provides an overview of the UID2 framework. ::: -### Guiding Principles +## Guiding Principles -The UID2 framework has the following principles as its foundation: - -- **First-party relationships**: UID2 enables advertisers to activate their first-party data on publisher websites across the open internet. - -- **Non-proprietary (universal) standard**: All [participants](#participants) in the advertising ecosystem who execute an appropriate participation agreement can access UID2. - -- **Open source**: The source code for the UID2 [components](#components) is publicly available. - -- **Interoperable**: The framework allows other identity solutions (commercial and proprietary) to integrate and provide UID2 tokens with their offerings. - -- **Secure and encrypted data**: UID2 leverages multiple layers of security to help protect user and other participant data. - -- **Consumer control**: Consumers can opt out of UID2 at any time through the [Transparency and Control Portal](https://www.transparentadvertising.com/). - -### Technical Design Principles - -The UID2 framework is built on the following technical principles: - -- **Distributed integration**: Multiple certified integration paths provide options for publishers, advertisers, and third-party data providers to manage and exchange UID2 tokens. - -- **Decentralized storage**: The framework does not have centralized storage for personal data (DII) mappings. All participants maintain only their own data. - -- **Lean infrastructure**: The UID2 system is light and inexpensive to operate. - -- **Internet scale**: The UID2 infrastructure can scale to address the continuously increasing needs of [participants](#participants) and to meet the performance demands of specific geographic regions. - -- **Self-reliant**: UID2 does not rely on external services for the processing of real-time bidding (RTB) data. +For details, see [UID2 Guiding Principles](ref-info/uid-principles.md). ## Elements of the UID2 Infrastructure -The following sections explain and illustrate the key elements of the UID2 framework infrastructure: - -- [UID2 Identifier Types](#uid2-identifier-types) -- [Components](#components) -- [Participants](#participants) -- [Workflows](#workflows) - -### UID2 Identifier Types - -UID2 is a deterministic ID that is based on directly identifying information (DII), such as email address or phone number. There are two types of UID2s: raw UID2s and UID2 tokens (also known as advertising tokens). The following table explains each type. - -| ID Type | Shared in Bidstream? | Description | -| :--- | :--- | :--- | -| **Raw UID2** | No | An unencrypted alphanumeric identifier created through the UID2 APIs or SDKs with the user's verifiable personal data, such as a hashed or unhashed email address or a phone number, as input.
To avoid revealing the source data, the input value is hashed if it was not already hashed, and then hashed again using a secret salt value to create the raw UID2. The process that creates the raw UID2 is designed to create a secure, opaque value that can be stored by advertisers, third-party data providers, and demand-side platforms (DSPs).
Raw UID2s are case sensitive.
Example: A request for the raw UID2 for the fictitious email address `user@example.com` resulted in this value: `E2dxEv3oMBzNHPw5iUVmwH2Hv+60D4AXYe+2ge9U0No=`. | -| **UID2 Token (Advertising Token)** | Yes | An encrypted form of a raw UID2. UID2 tokens are generated from hashed or unhashed email addresses or phone numbers that are converted to raw UID2s and then encrypted to help ensure protection in the bidstream.
UID2 tokens are designed to be used by publishers or publisher service providers. Supply-side platforms (SSPs) pass UID2 tokens in the bidstream and DSPs decrypt them at bid request time.
UID2 tokens are case sensitive.
Example: A request for a UID2 token for the fictitious email address `user@example.com` resulted in this value: `A4AAAAs6ZBcEbwAPoFhVV7CNW5W-4R-9TKDNL4RS0ctkw1U-IkNOXSnWczvwOMgCQaXHPf3Gd1o1W6IBmlZBFIloM67XOsOgwP5jUrQrclGkq1zBJJUJmOFTe6sJJA7pM1GP9gLd-hz5did6baZvcKd8DXkUYM-WALRZFnzHivu_1YEsC_CeXNdMexKDN7EwSQ6L5eZvOd1F1RkF_nLy_J0twg`. | - -:::note -For the fictitious email address `user@example.com` used in these examples, the corresponding refresh token was: `AAAABrexFHvQVhNJqu+y/ua7rsgShF8e9NUXUJOZFmeFRD8TAsJadaLfOlLkwC5iSxcOKWFD9YwMBzbbcPa92CInba+bcPTaAFNmM2ZpIHgGy6lDcNPzvEnPQh/5fyZ3MD44SX/tHyIXa0R2OBAOLBA1A81r3jefhSsxZdyyBF58KtnaX6UbaeOEaguOfMnJdmhaPeWKj33v7vGfROWtxDWmi6wvGL5lHTX9H6iIZ9i1WSsemYPUgmoDOQeT7nzllJK968OECFj5LkCazDN3pCrYSeuJby9o0fMuSZNxzp6EVzi6XVED4ETtzpcaY0AArzzdh0IXV9MgH8jyg7bJSUWXQG+8kMPZzwbs9EB+7ddAUOLZL/GBna8Hm3Im03EjN3sJ`. -::: - -### Components - -The UID2 framework consists of the following components, all of which are currently managed by The Trade Desk. - -| Component | Description | -| :--- | :--- | -| **Core Service** | A centralized service that manages access to salts, encryption keys, and other relevant data in the UID2 ecosystem. | -| **Operator Service** | A service that enables the management and storage of encryption keys and salts from the UID2 Core Service, hashing of users' personal data, encryption of raw UID2s, and decryption of UID2 tokens. There can be multiple instances of the service (public or private) operated by multiple [participants](#participants), known as operators.
Public Operators run publicly available instances of the Operator Service and make them available to all relevant UID2 participants. There might also be Private Operators that run private instances of the Operator Service exclusively for their own use. All instances are designed with protections to keep critical UID2 data secure and interoperable, regardless of who operates the service. | -| **Opt-Out Service** | A global service that manages and stores user opt-out requests and disseminates them to publishers, operator service instances, and DSPs. | -| **Transparency and Control Portal** | A user-facing website, [https://www.transparentadvertising.com/](https://www.transparentadvertising.com/), that allows consumers to opt out of UID2 at any time. | - -### Participants - -With its transparent and interoperable approach, UID2 provides a collaborative framework for many participants across the advertising ecosystem—advertisers, publishers, DSPs, SSPs, single sign-on (SSO) providers, customer data platforms (CDPs), consent management providers (CMPs), identity providers, third-party data providers, and measurement providers. - -The following table lists the key participants and their roles in the UID2 [workflows](#workflows). - -| Participant | Role Description | -| :--- | :--- | -| **Core Administrator** | An organization (currently, The Trade Desk) that manages the UID2 Core Service and other [components](#components). For example, it distributes encryption keys and salts to UID2 operators and sends user opt-out requests to operators and DSPs. | -| **Operators** | Organizations that run the Operator Service (via the UID2 APIs). Operators periodically receive and store up-to-date encryption keys and salts from the UID2 Core Service, salt and hash directly identifying information (DII) to return raw UID2s, encrypt raw UID2s to generate UID2 tokens, and distribute UID2 token decryption keys.
Public Operators (Open Operators) run public instances of the Operator Service. For example, The Trade Desk currently serves as a Public Operator for the UID2 framework, available to all participants. If other Public Operators are available, a participant can choose which operator to work with.
Any participant can also choose to become a Private Operator to generate and manage UID2s. | -| **DSPs** | DSPs integrate with the UID2 system to receive UID2s from advertisers (as first-party data) and third-party data providers (as third-party data) and leverage them to inform bidding on UID2s in the bidstream. | -| **Data Providers** | Organizations that collect user data and push it to other UID2 participants—for example, advertisers, identity graph providers, and third-party data providers. | -| **Advertisers** | Organizations that buy impressions across a range of publisher sites and use DSPs to decide which ad impressions to purchase and how much to bid on them. | -| **Publishers** | Organizations that propagate UID2 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 UID2. Independent ID providers can handle the UID2 integration on behalf of publishers. | -| **Consumers** | Users who have had a UID2 token or raw UID2 created from their email address or phone number. Consumers can opt out of UID2 in the [Transparency and Control Portal](https://www.transparentadvertising.com/). | - -### Workflows - -The following table lists four key workflows in the UID2 framework with links to their high-level overviews. It also provides links to the respective integration guides, which include diagrams, integration steps, FAQs, and other relevant information for each workflow. - -| Workflow | Intended Primary Participants | Integration Guides | -| :--- |:--- |:--- | -| [Workflow for DSPs](overviews/overview-dsps.md#workflow-for-dsps) (Buy-Side) | DSPs who transact on UID2 tokens in the bidstream. | See [DSP Integrations](guides/summary-guides#dsp-integrations) | -| [Workflow for Advertisers](overviews/overview-advertisers.md#workflow-for-advertisers) and [Workflow for Data Providers](overviews/overview-data-providers.md#workflow-for-data-providers) | Organizations that collect user data and push it to DSPs. | See [Advertiser/Data Provider Integrations](guides/summary-guides#advertiserdata-provider-integrations) | -| [Workflow for Publishers](overviews/overview-publishers.md#workflow-for-publishers) | Organizations that propagate UID2 tokens to the bidstream via SSPs.
NOTE: Publishers can choose to integrate using Prebid, leverage the SDK for JavaScript, or complete their own server-side integration without using an SDK. | See [Publisher Integrations](guides/summary-guides#publisher-integrations) | -| [Opt-Out Workflow](getting-started/gs-opt-out.md#opt-out-workflow) | Consumers who engage with publishers or their SSO providers and other identity providers. | N/A | - -The following diagram summarizes all four workflows. For each workflow, the [participants](#participants), [components](#components), [UID2 identifier types](#uid2-identifier-types), and numbered steps are color-coded. - -![The UID2 Ecosystem](images/UID2Workflows.svg) +For details, see [UID2 Infrastructure](ref-info/uid-infrastructure.md). ## FAQs diff --git a/docs/images/UID2Workflows.svg b/docs/ref-info/images/UID2Workflows.svg similarity index 100% rename from docs/images/UID2Workflows.svg rename to docs/ref-info/images/UID2Workflows.svg diff --git a/docs/images/source/source.txt b/docs/ref-info/images/source/source.txt similarity index 100% rename from docs/images/source/source.txt rename to docs/ref-info/images/source/source.txt diff --git a/docs/ref-info/uid-infrastructure.md b/docs/ref-info/uid-infrastructure.md new file mode 100644 index 000000000..edc5feda3 --- /dev/null +++ b/docs/ref-info/uid-infrastructure.md @@ -0,0 +1,73 @@ +--- +title: UID2 Infrastructure +description: Summary of key elements in the UID2 infrastructure, including identifier types, components, participants, and workflows. +hide_table_of_contents: false +sidebar_position: 01 +displayed_sidebar: docs +--- + +import Link from '@docusaurus/Link'; + +# UID2 Infrastructure + +The following sections explain and illustrate the key elements of the UID2 framework infrastructure: + +- [UID2 Identifier Types](#uid2-identifier-types) +- [Components](#components) +- [Participants](#participants) +- [Workflows](#workflows) + +### Identifier Types + +UID2 is a deterministic ID that is based on directly identifying information (DII), such as email address or phone number. There are two types of UID2s: raw UID2s and UID2 tokens (also known as advertising tokens). The following table explains each type. + +| ID Type | Shared in Bidstream? | Description | +| :--- | :--- | :--- | +| **Raw UID2** | No | An unencrypted alphanumeric identifier created through the UID2 APIs or SDKs with the user's verifiable personal data, such as a hashed or unhashed email address or a phone number, as input.
To avoid revealing the source data, the input value is hashed if it was not already hashed, and then hashed again using a secret salt value to create the raw UID2. The process that creates the raw UID2 is designed to create a secure, opaque value that can be stored by advertisers, third-party data providers, and demand-side platforms (DSPs).
Raw UID2s are case sensitive.
Example: A request for the raw UID2 for the fictitious email address `user@example.com` resulted in this value: `E2dxEv3oMBzNHPw5iUVmwH2Hv+60D4AXYe+2ge9U0No=`. | +| **UID2 Token (Advertising Token)** | Yes | An encrypted form of a raw UID2. UID2 tokens are generated from hashed or unhashed email addresses or phone numbers that are converted to raw UID2s and then encrypted to help ensure protection in the bidstream.
UID2 tokens are designed to be used by publishers or publisher service providers. Supply-side platforms (SSPs) pass UID2 tokens in the bidstream and DSPs decrypt them at bid request time.
UID2 tokens are case sensitive.
Example: A request for a UID2 token for the fictitious email address `user@example.com` resulted in this value: `A4AAAAs6ZBcEbwAPoFhVV7CNW5W-4R-9TKDNL4RS0ctkw1U-IkNOXSnWczvwOMgCQaXHPf3Gd1o1W6IBmlZBFIloM67XOsOgwP5jUrQrclGkq1zBJJUJmOFTe6sJJA7pM1GP9gLd-hz5did6baZvcKd8DXkUYM-WALRZFnzHivu_1YEsC_CeXNdMexKDN7EwSQ6L5eZvOd1F1RkF_nLy_J0twg`. | + +:::note +For the fictitious email address `user@example.com` used in these examples, the corresponding refresh token was: `AAAABrexFHvQVhNJqu+y/ua7rsgShF8e9NUXUJOZFmeFRD8TAsJadaLfOlLkwC5iSxcOKWFD9YwMBzbbcPa92CInba+bcPTaAFNmM2ZpIHgGy6lDcNPzvEnPQh/5fyZ3MD44SX/tHyIXa0R2OBAOLBA1A81r3jefhSsxZdyyBF58KtnaX6UbaeOEaguOfMnJdmhaPeWKj33v7vGfROWtxDWmi6wvGL5lHTX9H6iIZ9i1WSsemYPUgmoDOQeT7nzllJK968OECFj5LkCazDN3pCrYSeuJby9o0fMuSZNxzp6EVzi6XVED4ETtzpcaY0AArzzdh0IXV9MgH8jyg7bJSUWXQG+8kMPZzwbs9EB+7ddAUOLZL/GBna8Hm3Im03EjN3sJ`. +::: + +### UID2 Components + +The UID2 framework consists of the following components, all of which are currently managed by The Trade Desk. + +| Component | Description | +| :--- | :--- | +| **Core Service** | A centralized service that manages access to salts, encryption keys, and other relevant data in the UID2 ecosystem. | +| **Operator Service** | A service that enables the management and storage of encryption keys and salts from the UID2 Core Service, hashing of users' personal data, encryption of raw UID2s, and decryption of UID2 tokens. There can be multiple instances of the service (public or private) operated by multiple [participants](#participants), known as operators.
Public Operators run publicly available instances of the Operator Service and make them available to all relevant UID2 participants. There might also be Private Operators that run private instances of the Operator Service exclusively for their own use. All instances are designed with protections to keep critical UID2 data secure and interoperable, regardless of who operates the service. | +| **Opt-Out Service** | A global service that manages and stores user opt-out requests and disseminates them to publishers, operator service instances, and DSPs. | +| **Transparency and Control Portal** | A user-facing website, [https://www.transparentadvertising.com/](https://www.transparentadvertising.com/), that allows consumers to opt out of UID2 at any time. | + +### Participants + +With its transparent and interoperable approach, UID2 provides a collaborative framework for many participants across the advertising ecosystem—advertisers, publishers, DSPs, SSPs, single sign-on (SSO) providers, customer data platforms (CDPs), consent management providers (CMPs), identity providers, third-party data providers, and measurement providers. + +The following table lists the key participants and their roles in the UID2 [workflows](#workflows). + +| Participant | Role Description | +| :--- | :--- | +| **Core Administrator** | An organization (currently, The Trade Desk) that manages the UID2 Core Service and other [components](#components). For example, it distributes encryption keys and salts to UID2 operators and sends user opt-out requests to operators and DSPs. | +| **Operators** | Organizations that run the Operator Service (via the UID2 APIs). Operators periodically receive and store up-to-date encryption keys and salts from the UID2 Core Service, salt and hash directly identifying information (DII) to return raw UID2s, encrypt raw UID2s to generate UID2 tokens, and distribute UID2 token decryption keys.
Public Operators (Open Operators) run public instances of the Operator Service. For example, The Trade Desk currently serves as a Public Operator for the UID2 framework, available to all participants. If other Public Operators are available, a participant can choose which operator to work with.
Any participant can also choose to become a Private Operator to generate and manage UID2s. | +| **DSPs** | DSPs integrate with the UID2 system to receive UID2s from advertisers (as first-party data) and third-party data providers (as third-party data) and leverage them to inform bidding on UID2s in the bidstream. | +| **Data Providers** | Organizations that collect user data and push it to other UID2 participants—for example, advertisers, identity graph providers, and third-party data providers. | +| **Advertisers** | Organizations that buy impressions across a range of publisher sites and use DSPs to decide which ad impressions to purchase and how much to bid on them. | +| **Publishers** | Organizations that propagate UID2 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 UID2. Independent ID providers can handle the UID2 integration on behalf of publishers. | +| **Consumers** | Users who have had a UID2 token or raw UID2 created from their email address or phone number. Consumers can opt out of UID2 in the [Transparency and Control Portal](https://www.transparentadvertising.com/). | + +### Workflows + +The following table lists four key workflows in the UID2 framework with links to their high-level overviews. It also provides links to the respective integration guides, which include diagrams, integration steps, FAQs, and other relevant information for each workflow. + +| Workflow | Intended Primary Participants | Integration Guides | +| :--- |:--- |:--- | +| [Workflow for DSPs](overviews/overview-dsps.md#workflow-for-dsps) (Buy-Side) | DSPs who transact on UID2 tokens in the bidstream. | See [DSP Integrations](guides/summary-guides#dsp-integrations) | +| [Workflow for Advertisers](overviews/overview-advertisers.md#workflow-for-advertisers) and [Workflow for Data Providers](overviews/overview-data-providers.md#workflow-for-data-providers) | Organizations that collect user data and push it to DSPs. | See [Advertiser/Data Provider Integrations](guides/summary-guides#advertiserdata-provider-integrations) | +| [Workflow for Publishers](overviews/overview-publishers.md#workflow-for-publishers) | Organizations that propagate UID2 tokens to the bidstream via SSPs.
NOTE: Publishers can choose to integrate using Prebid, leverage the SDK for JavaScript, or complete their own server-side integration without using an SDK. | See [Publisher Integrations](guides/summary-guides#publisher-integrations) | +| [Opt-Out Workflow](getting-started/gs-opt-out.md#opt-out-workflow) | Consumers who engage with publishers or their SSO providers and other identity providers. | N/A | + +The following diagram summarizes all four workflows. For each workflow, the [participants](#participants), [components](#components), [UID2 identifier types](#uid2-identifier-types), and numbered steps are color-coded. + +![The UID2 Ecosystem](images/UID2Workflows.svg) diff --git a/docs/ref-info/uid-principles.md b/docs/ref-info/uid-principles.md new file mode 100644 index 000000000..01e66e950 --- /dev/null +++ b/docs/ref-info/uid-principles.md @@ -0,0 +1,39 @@ +--- +title: UID2 Guiding Principles +description: Summary of the guiding principles of UID2. +hide_table_of_contents: false +sidebar_position: 01 +displayed_sidebar: docs +--- + +import Link from '@docusaurus/Link'; + +# UID2 Guiding Principles + +The UID2 framework has the following principles as its foundation: + +- **First-party relationships**: UID2 enables advertisers to activate their first-party data on publisher websites across the open internet. + +- **Non-proprietary (universal) standard**: All [participants](#participants) in the advertising ecosystem who execute an appropriate participation agreement can access UID2. + +- **Open source**: The source code for the UID2 [components](#components) is publicly available. + +- **Interoperable**: The framework allows other identity solutions (commercial and proprietary) to integrate and provide UID2 tokens with their offerings. + +- **Secure and encrypted data**: UID2 leverages multiple layers of security to help protect user and other participant data. + +- **Consumer control**: Consumers can opt out of UID2 at any time through the [Transparency and Control Portal](https://www.transparentadvertising.com/). + +## Technical Design Principles + +The UID2 framework is built on the following technical principles: + +- **Distributed integration**: Multiple certified integration paths provide options for publishers, advertisers, and third-party data providers to manage and exchange UID2 tokens. + +- **Decentralized storage**: The framework does not have centralized storage for personal data (DII) mappings. All participants maintain only their own data. + +- **Lean infrastructure**: The UID2 system is light and inexpensive to operate. + +- **Internet scale**: The UID2 infrastructure can scale to address the continuously increasing needs of [participants](#participants) and to meet the performance demands of specific geographic regions. + +- **Self-reliant**: UID2 does not rely on external services for the processing of real-time bidding (RTB) data. diff --git a/sidebars.js b/sidebars.js index 360fe4246..0dd3ce9c5 100644 --- a/sidebars.js +++ b/sidebars.js @@ -20,7 +20,20 @@ function removeItems(sidebar, ...remove) { const fullSidebar = [ - 'intro', + { + type: 'category', + label: 'Overview', + link: { + type: 'doc', + id: 'intro', + }, + collapsed: false, + collapsed: true, + items: [ + 'ref-info/uid-principles', + 'ref-info/uid-infrastructure', + ], + }, { type: 'category', From 7b34b8b512fcd32730818c745dd0756c7e5ee8a4 Mon Sep 17 00:00:00 2001 From: genwhittTTD Date: Thu, 27 Feb 2025 11:33:44 -0500 Subject: [PATCH 2/6] partial work --- docs/intro.md | 6 ++- docs/overviews/participants-overview.md | 59 +++++++++++++++++++++++++ docs/ref-info/uid-infrastructure.md | 19 +------- sidebars.js | 4 +- 4 files changed, 67 insertions(+), 21 deletions(-) create mode 100644 docs/overviews/participants-overview.md diff --git a/docs/intro.md b/docs/intro.md index b28665ea7..ec08a51ec 100644 --- a/docs/intro.md +++ b/docs/intro.md @@ -10,7 +10,7 @@ import Link from '@docusaurus/Link'; # Unified ID 2.0 Overview -UID2 is a framework that enables deterministic identity for advertising opportunities on the open internet for many [participants](#participants) across the advertising ecosystem. The UID2 framework enables publisher websites, mobile apps, and Connected TV (CTV) apps to monetize through programmatic workflows. Built as an open-source, standalone solution with its own unique namespace, the framework offers privacy controls designed to help participants meet local market requirements. +UID2 is a framework that enables deterministic identity for advertising opportunities on the open internet for many [participants](#participants) across the advertising ecosystem. The UID2 framework enables publisher websites, mobile apps, and Connected TV (CTV) apps to monetize through programmatic workflows. Built as an open-source, standalone solution with its own unique namespace, the framework offers privacy controls designed to help participants meet local market requirements. :::note The term "UID2" can refer to either the framework or an actual identifier. Unless otherwise indicated, this page provides an overview of the UID2 framework. @@ -24,6 +24,10 @@ For details, see [UID2 Guiding Principles](ref-info/uid-principles.md). For details, see [UID2 Infrastructure](ref-info/uid-infrastructure.md). +## Components + +For details, see [xxx](ref-info/uid-infrastructure.md). + ## FAQs See [Frequently Asked Questions](getting-started/gs-faqs.md). diff --git a/docs/overviews/participants-overview.md b/docs/overviews/participants-overview.md new file mode 100644 index 000000000..4d0a063fd --- /dev/null +++ b/docs/overviews/participants-overview.md @@ -0,0 +1,59 @@ +--- +title: Overview of UID2 Participants +description: An overview of different types of UID2 participants. +hide_table_of_contents: false +sidebar_position: 06 +displayed_sidebar: docs +--- + +import Link from '@docusaurus/Link'; + +# Overview of UID2 Participants + +With its transparent and interoperable approach, UID2 provides a collaborative framework for many participants across the advertising ecosystem—advertisers, publishers, DSPs, SSPs, single sign-on (SSO) providers, customer data platforms (CDPs), consent management providers (CMPs), identity providers, third-party data providers, and measurement providers. + +The following tables list the key participants and their roles in the UID2 [workflows](../ref-info/uid-infrastructure.md#workflows). They are grouped into three categories: + +- [UID2 Component Services](#uid2-component-services) +- [UID2 External Participants](#uid2-external-participants) +- [UID2 Consumers](#uid2-consumers) + +## UID2 Component Services + +The following table summarizes information about key participant components of the UID2 service. + +For a diagram of how the different services work together, see [UID2 Workflows](../ref-info/uid-infrastructure.md#workflows). + +| Participant | Role Description | +| :--- | :--- | +| **Core Administrator** | An organization (currently, The Trade Desk) that manages the UID2 Core Service and other [components](#components). For example, it distributes encryption keys and salts to UID2 operators and sends user opt-out requests to operators and DSPs. | +| **Operators** | Organizations that run the Operator Service (via the UID2 APIs). Operators periodically receive and store up-to-date encryption keys and salts from the UID2 Core Service, salt and hash directly identifying information (DII) to return raw UID2s, encrypt raw UID2s to generate UID2 tokens, and distribute UID2 token decryption keys.
Public Operators (Open Operators) run public instances of the Operator Service. For example, The Trade Desk currently serves as a Public Operator for the UID2 framework, available to all participants. If other Public Operators are available, a participant can choose which operator to work with.
Any participant can also choose to become a Private Operator to generate and manage UID2s. | + +## UID2 External Participants + +The following table summarizes the main types of external participant partners for UID2. + +| Participant | Role Description | Link to Overview Page | +| :--- | :--- | :--- | +| **Publishers** | Organizations that propagate UID2 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 UID2. Independent ID providers can handle the UID2 integration on behalf of publishers. | [UID2 Overview for Publishers](overview-publishers.md) | +| **Advertisers** | Organizations that buy impressions across a range of publisher sites and use DSPs to decide which ad impressions to purchase and how much to bid on them. | [UID2 Overview for Advertisers](overview-advertisers.md) | +| **DSPs** | DSPs integrate with the UID2 system to receive UID2s from advertisers (as first-party data) and third-party data providers (as third-party data) and leverage them to inform bidding on UID2s in the bidstream. | [UID2 Overview for DSPs](overview-dsps.md) | +| **Data Providers** | Organizations that collect user data and push it to other UID2 participants—for example, advertisers, identity graph providers, and third-party data providers. | [UID2 Overview for Data Providers](overview-data-providers.md) | + +## UID2 Consumers + +A UID2 consumer is a user who has had a UID2 token or raw UID2 created from an email address or phone number. + +UID2 leverages multiple layers of security to help protect user and other participant data. UID2 is a privacy-compliant identifier. With UID2, consumers can enjoy more personalized advertising without compromising privacy. + +Consumers can opt out of UID2 in the [Transparency and Control Portal](https://www.transparentadvertising.com/). + + diff --git a/docs/ref-info/uid-infrastructure.md b/docs/ref-info/uid-infrastructure.md index edc5feda3..29bec74db 100644 --- a/docs/ref-info/uid-infrastructure.md +++ b/docs/ref-info/uid-infrastructure.md @@ -13,8 +13,7 @@ import Link from '@docusaurus/Link'; The following sections explain and illustrate the key elements of the UID2 framework infrastructure: - [UID2 Identifier Types](#uid2-identifier-types) -- [Components](#components) -- [Participants](#participants) +- [UID2 Components](#uid2-components) - [Workflows](#workflows) ### Identifier Types @@ -41,22 +40,6 @@ The UID2 framework consists of the following components, all of which are curren | **Opt-Out Service** | A global service that manages and stores user opt-out requests and disseminates them to publishers, operator service instances, and DSPs. | | **Transparency and Control Portal** | A user-facing website, [https://www.transparentadvertising.com/](https://www.transparentadvertising.com/), that allows consumers to opt out of UID2 at any time. | -### Participants - -With its transparent and interoperable approach, UID2 provides a collaborative framework for many participants across the advertising ecosystem—advertisers, publishers, DSPs, SSPs, single sign-on (SSO) providers, customer data platforms (CDPs), consent management providers (CMPs), identity providers, third-party data providers, and measurement providers. - -The following table lists the key participants and their roles in the UID2 [workflows](#workflows). - -| Participant | Role Description | -| :--- | :--- | -| **Core Administrator** | An organization (currently, The Trade Desk) that manages the UID2 Core Service and other [components](#components). For example, it distributes encryption keys and salts to UID2 operators and sends user opt-out requests to operators and DSPs. | -| **Operators** | Organizations that run the Operator Service (via the UID2 APIs). Operators periodically receive and store up-to-date encryption keys and salts from the UID2 Core Service, salt and hash directly identifying information (DII) to return raw UID2s, encrypt raw UID2s to generate UID2 tokens, and distribute UID2 token decryption keys.
Public Operators (Open Operators) run public instances of the Operator Service. For example, The Trade Desk currently serves as a Public Operator for the UID2 framework, available to all participants. If other Public Operators are available, a participant can choose which operator to work with.
Any participant can also choose to become a Private Operator to generate and manage UID2s. | -| **DSPs** | DSPs integrate with the UID2 system to receive UID2s from advertisers (as first-party data) and third-party data providers (as third-party data) and leverage them to inform bidding on UID2s in the bidstream. | -| **Data Providers** | Organizations that collect user data and push it to other UID2 participants—for example, advertisers, identity graph providers, and third-party data providers. | -| **Advertisers** | Organizations that buy impressions across a range of publisher sites and use DSPs to decide which ad impressions to purchase and how much to bid on them. | -| **Publishers** | Organizations that propagate UID2 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 UID2. Independent ID providers can handle the UID2 integration on behalf of publishers. | -| **Consumers** | Users who have had a UID2 token or raw UID2 created from their email address or phone number. Consumers can opt out of UID2 in the [Transparency and Control Portal](https://www.transparentadvertising.com/). | - ### Workflows The following table lists four key workflows in the UID2 framework with links to their high-level overviews. It also provides links to the respective integration guides, which include diagrams, integration steps, FAQs, and other relevant information for each workflow. diff --git a/sidebars.js b/sidebars.js index 0dd3ce9c5..381c3581f 100644 --- a/sidebars.js +++ b/sidebars.js @@ -28,7 +28,6 @@ const fullSidebar = [ id: 'intro', }, collapsed: false, - collapsed: true, items: [ 'ref-info/uid-principles', 'ref-info/uid-infrastructure', @@ -39,7 +38,8 @@ const fullSidebar = [ type: 'category', label: 'UID2 Participants', link: { - type: 'generated-index', + type: 'doc', + id: 'overviews/participants-overview', }, collapsed: true, items: [ From 4802b49827c38003a5f8af9d95d8352f1ea3d8c1 Mon Sep 17 00:00:00 2001 From: genwhittTTD Date: Mon, 17 Mar 2025 15:33:13 -0400 Subject: [PATCH 3/6] mods, fix links --- docs/getting-started/gs-credentials.md | 2 +- docs/getting-started/gs-opt-out.md | 2 +- docs/intro.md | 32 +++++++++- docs/overviews/overview-advertisers.md | 2 +- docs/overviews/overview-data-providers.md | 2 +- docs/overviews/participants-overview.md | 8 +-- docs/ref-info/glossary-uid.md | 24 ++++---- docs/ref-info/ref-how-uid-is-created.md | 2 +- docs/ref-info/uid-infrastructure.md | 22 +++---- docs/ref-info/uid-principles.md | 39 ------------ docs/ref-info/updates-doc.md | 2 +- .../current/getting-started/gs-credentials.md | 2 +- .../current/getting-started/gs-opt-out.md | 2 +- .../current/intro.md | 31 ++++------ .../current/overviews/overview-advertisers.md | 2 +- .../overviews/overview-data-providers.md | 2 +- .../overviews/participants-overview.md | 59 +++++++++++++++++++ .../current/ref-info/glossary-uid.md | 24 ++++---- .../{ => ref-info}/images/UID2Workflows.svg | 0 .../{ => ref-info}/images/source/source.txt | 0 .../ref-info/ref-how-uid-is-created.md | 2 +- .../current/ref-info/uid-infrastructure.md | 56 ++++++++++++++++++ .../current/ref-info/updates-doc.md | 2 +- sidebars.js | 1 - 24 files changed, 207 insertions(+), 113 deletions(-) delete mode 100644 docs/ref-info/uid-principles.md create mode 100644 i18n/ja/docusaurus-plugin-content-docs/current/overviews/participants-overview.md rename i18n/ja/docusaurus-plugin-content-docs/current/{ => ref-info}/images/UID2Workflows.svg (100%) rename i18n/ja/docusaurus-plugin-content-docs/current/{ => ref-info}/images/source/source.txt (100%) create mode 100644 i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-infrastructure.md diff --git a/docs/getting-started/gs-credentials.md b/docs/getting-started/gs-credentials.md index d870a8251..c703d163a 100644 --- a/docs/getting-started/gs-credentials.md +++ b/docs/getting-started/gs-credentials.md @@ -9,7 +9,7 @@ import Link from '@docusaurus/Link'; # UID2 Credentials -Each UID2 participant needs at least one set of unique credentials. The set of credentials you need is determined by how you are participating in UID2, as shown in the following table. +Each UID2 participant needs at least one set of unique credentials. The set of credentials you need is determined by how you are participating in UID2, as shown in the following table. | Audience | Credentials | Integration | | :--- | :--- | :--- | diff --git a/docs/getting-started/gs-opt-out.md b/docs/getting-started/gs-opt-out.md index 388d27008..93f78fbc0 100644 --- a/docs/getting-started/gs-opt-out.md +++ b/docs/getting-started/gs-opt-out.md @@ -9,7 +9,7 @@ import Link from '@docusaurus/Link'; # User Opt-Out -Many different publishers and advertisers use UID2. Different publishers might have different opt-out processes for their individual sites; however, UID2 as a whole has very specific opt-out processes that all UID2 [participants](../ref-info/glossary-uid.md#gl-participant) are expected to honor. +Many different publishers and advertisers use UID2. Different publishers might have different opt-out processes for their individual sites; however, UID2 as a whole has very specific opt-out processes that all UID2 [participants](overviews/participants-overview.md#uid2-external-participants) are expected to honor. ## How Users Can Opt Out of UID2 diff --git a/docs/intro.md b/docs/intro.md index ec08a51ec..3fe05adcf 100644 --- a/docs/intro.md +++ b/docs/intro.md @@ -10,7 +10,7 @@ import Link from '@docusaurus/Link'; # Unified ID 2.0 Overview -UID2 is a framework that enables deterministic identity for advertising opportunities on the open internet for many [participants](#participants) across the advertising ecosystem. The UID2 framework enables publisher websites, mobile apps, and Connected TV (CTV) apps to monetize through programmatic workflows. Built as an open-source, standalone solution with its own unique namespace, the framework offers privacy controls designed to help participants meet local market requirements. +UID2 is a framework that enables deterministic identity for advertising opportunities on the open internet for many [participants](overviews/participants-overview.md#uid2-external-participants) across the advertising ecosystem. The UID2 framework enables publisher websites, mobile apps, and Connected TV (CTV) apps to monetize through programmatic workflows. Built as an open-source, standalone solution with its own unique namespace, the framework offers privacy controls designed to help participants meet local market requirements. :::note The term "UID2" can refer to either the framework or an actual identifier. Unless otherwise indicated, this page provides an overview of the UID2 framework. @@ -18,7 +18,33 @@ The term "UID2" can refer to either the framework or an actual identifier. Unles ## Guiding Principles -For details, see [UID2 Guiding Principles](ref-info/uid-principles.md). +The UID2 framework has the following principles as its foundation: + +- **First-party relationships**: UID2 enables advertisers to activate their first-party data on publisher websites across the open internet. + +- **Non-proprietary (universal) standard**: All [participants](overviews/participants-overview.md#uid2-external-participants) in the advertising ecosystem who execute an appropriate participation agreement can access UID2. + +- **Open source**: The source code for the [UID2 Component Services](overviews/participants-overview.md#uid2-component-services) is publicly available. + +- **Interoperable**: The framework allows other identity solutions (commercial and proprietary) to integrate and provide UID2 tokens with their offerings. + +- **Secure and encrypted data**: UID2 leverages multiple layers of security to help protect user and other participant data. + +- **Consumer control**: Consumers can opt out of UID2 at any time through the [Transparency and Control Portal](https://www.transparentadvertising.com/). + +### Technical Design Principles + +The UID2 framework is built on the following technical principles: + +- **Distributed integration**: Multiple certified integration paths provide options for publishers, advertisers, and third-party data providers to manage and exchange UID2 tokens. + +- **Decentralized storage**: The framework does not have centralized storage for personal data (DII) mappings. All participants maintain only their own data. + +- **Lean infrastructure**: The UID2 system is light and inexpensive to operate. + +- **Internet scale**: The UID2 infrastructure can scale to address the continuously increasing needs of [participants](overviews/participants-overview.md#uid2-external-participants) and to meet the performance demands of specific geographic regions. + +- **Self-reliant**: UID2 does not rely on external services for the processing of real-time bidding (RTB) data. ## Elements of the UID2 Infrastructure @@ -26,7 +52,7 @@ For details, see [UID2 Infrastructure](ref-info/uid-infrastructure.md). ## Components -For details, see [xxx](ref-info/uid-infrastructure.md). +For details, see [UID2 Component Services](overviews/participants-overview.md#uid2-component-services). ## FAQs diff --git a/docs/overviews/overview-advertisers.md b/docs/overviews/overview-advertisers.md index b460d8a81..12d7561ca 100644 --- a/docs/overviews/overview-advertisers.md +++ b/docs/overviews/overview-advertisers.md @@ -58,7 +58,7 @@ To get started, follow these steps: 1. Request access to UID2 by filling out the form on the [Request Access](/request-access) page. Someone will contact you to discuss your needs and advise on appropriate next steps. -1. Decide on your [participant](../intro.md#participants) role or roles. +1. Decide on your [participant](../overviews/participants-overview.md#uid2-external-participants) role or roles. 1. Decide which implementation option you want to use. 1. Receive your credentials (see [UID2 Credentials](../getting-started/gs-credentials.md)) and follow the instructions in the implementation guide for the option you chose. diff --git a/docs/overviews/overview-data-providers.md b/docs/overviews/overview-data-providers.md index 6bc7b6e39..f330c5348 100644 --- a/docs/overviews/overview-data-providers.md +++ b/docs/overviews/overview-data-providers.md @@ -63,7 +63,7 @@ To get started, follow these steps: 1. Request access to UID2 by filling out the form on the [Request Access](/request-access) page. Someone will contact you to discuss your needs and advise on appropriate next steps. -1. Decide on your [participant](../intro.md#participants) role or roles. +1. Decide on your [participant](../overviews/participants-overview.md#uid2-external-participants) role or roles. 1. Decide which implementation option you want to use. 1. Receive your credentials (see [UID2 Credentials](../getting-started/gs-credentials.md)) and follow the instructions in the implementation guide for the option you chose. diff --git a/docs/overviews/participants-overview.md b/docs/overviews/participants-overview.md index 4d0a063fd..79d0eeadb 100644 --- a/docs/overviews/participants-overview.md +++ b/docs/overviews/participants-overview.md @@ -26,8 +26,8 @@ For a diagram of how the different services work together, see [UID2 Workflows]( | Participant | Role Description | | :--- | :--- | -| **Core Administrator** | An organization (currently, The Trade Desk) that manages the UID2 Core Service and other [components](#components). For example, it distributes encryption keys and salts to UID2 operators and sends user opt-out requests to operators and DSPs. | -| **Operators** | Organizations that run the Operator Service (via the UID2 APIs). Operators periodically receive and store up-to-date encryption keys and salts from the UID2 Core Service, salt and hash directly identifying information (DII) to return raw UID2s, encrypt raw UID2s to generate UID2 tokens, and distribute UID2 token decryption keys.
Public Operators (Open Operators) run public instances of the Operator Service. For example, The Trade Desk currently serves as a Public Operator for the UID2 framework, available to all participants. If other Public Operators are available, a participant can choose which operator to work with.
Any participant can also choose to become a Private Operator to generate and manage UID2s. | +| **Core Administrator** | An organization (currently, The Trade Desk) that manages the UID2 Core Service and other component services. For example, it distributes encryption keys and salts to UID2 operators and sends user opt-out requests to operators and DSPs. | +| **Operators** | Organizations that run the Operator Service (via the UID2 APIs). Operators periodically receive and store up-to-date encryption keys and salts from the UID2 Core Service, salt and hash directly identifying information (DII) to return raw UID2s, encrypt raw UID2s to generate UID2 tokens, and distribute UID2 token decryption keys.
Public Operators (Open Operators) run public instances of the Operator Service. For example, The Trade Desk currently serves as a Public Operator for the UID2 framework, available to all participants. If other Public Operators are available, a participant can choose which operator to work with.
Any participant can also choose to become a Private Operator to generate and manage UID2s. | ## UID2 External Participants @@ -50,8 +50,8 @@ Consumers can opt out of UID2 in the [Transparency and Control Portal](https://w -### UID2 Identifier Types + ### Components -UID2 フレームワークは以下のコンポーネントで構成されており、現在、すべて The Trade Desk が管理しています。 - -| Component | Description | -| :--- | :--- | -| **Core Service** |salts、暗号化キー、および UID2 エコシステムの他の関連データへのアクセスを管理する一元的なサービスです。 | -| **Operator Service** | UID2 Core Service からの暗号鍵とソルトの管理・保管、ユーザーの個人情報のハッシュ化、raw UID2 の暗号化、UID2 Token の復号を可能にするサービスです。
Public Operators は、Operator Service のパブリックインスタンスを実行し、関連するすべての UID2 参加者が利用できるようにします。また、オペレーターサービスのプライベートなインスタンスを自分たちだけのために実行する Private Operators も存在します。どのインスタンスも、誰がサービスを運営するかに関わらず、重要な UID2 データを安全に保ち、相互運用できるように保護設計されています。 | -| **Opt-Out Service** | ユーザーのオプトアウトリクエストを管理・保存し、パブリッシャー、オペレーターのサービスインスタンス、DSP に配信するグローバルサービスです。 | -| **Transparency and Control Portal** | ユーザー向けウェブサイト [https://www.transparentadvertising.com/](https://www.transparentadvertising.com/) では、消費者がいつでも UID2 からの脱退を選択できるようになっています。 | +詳細については、[UID2 Component Services](overviews/participants-overview.md#uid2-component-services) -### Participants + ## FAQs diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/overviews/overview-advertisers.md b/i18n/ja/docusaurus-plugin-content-docs/current/overviews/overview-advertisers.md index 02fe56b05..3bed8079d 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/overviews/overview-advertisers.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/overviews/overview-advertisers.md @@ -58,7 +58,7 @@ UID2 のドキュメント一式に左サイドバーからアクセスしたい 1. [アクセスリクエスト](/request-access)ページにあるフォームに記入して、UID2へのアクセスをリクエストします。 担当者が連絡し、ニーズを伺い、適切なステップをアドバイスします。 -1. [参加者](../intro.md#participants) の役割を決めます。 +1. [参加者](../overviews/participants-overview.md#uid2-external-participants) の役割を決めます。 1. どの実装オプションを使用するかを決めます。 1. 認証情報を受け取り ([UID2 Credentials](../getting-started/gs-credentials.md) を参照)、選択したオプションのインテグレーションガイドの指示に従います。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/overviews/overview-data-providers.md b/i18n/ja/docusaurus-plugin-content-docs/current/overviews/overview-data-providers.md index 4607d0c5a..1d50bfc6d 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/overviews/overview-data-providers.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/overviews/overview-data-providers.md @@ -63,7 +63,7 @@ UID2 を使用することで、データプロバイダーとして得られる 1. [アクセスリクエスト](/request-access)ページにあるフォームに記入して、UID2へのアクセスをリクエストします。 担当者が連絡し、ニーズを伺い、適切なステップをアドバイスします。 -1. [参加者](../intro.md#participants) の役割を決めます。 +1. [参加者](../overviews/participants-overview.md#uid2-external-participants) の役割を決めます。 1. どの実装オプションを使用するかを決めます。 1. 認証情報を受け取り ([UID2 Credentials](../getting-started/gs-credentials.md) を参照)、選択したオプションのインテグレーションガイドの指示に従います。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/overviews/participants-overview.md b/i18n/ja/docusaurus-plugin-content-docs/current/overviews/participants-overview.md new file mode 100644 index 000000000..79d0eeadb --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/overviews/participants-overview.md @@ -0,0 +1,59 @@ +--- +title: Overview of UID2 Participants +description: An overview of different types of UID2 participants. +hide_table_of_contents: false +sidebar_position: 06 +displayed_sidebar: docs +--- + +import Link from '@docusaurus/Link'; + +# Overview of UID2 Participants + +With its transparent and interoperable approach, UID2 provides a collaborative framework for many participants across the advertising ecosystem—advertisers, publishers, DSPs, SSPs, single sign-on (SSO) providers, customer data platforms (CDPs), consent management providers (CMPs), identity providers, third-party data providers, and measurement providers. + +The following tables list the key participants and their roles in the UID2 [workflows](../ref-info/uid-infrastructure.md#workflows). They are grouped into three categories: + +- [UID2 Component Services](#uid2-component-services) +- [UID2 External Participants](#uid2-external-participants) +- [UID2 Consumers](#uid2-consumers) + +## UID2 Component Services + +The following table summarizes information about key participant components of the UID2 service. + +For a diagram of how the different services work together, see [UID2 Workflows](../ref-info/uid-infrastructure.md#workflows). + +| Participant | Role Description | +| :--- | :--- | +| **Core Administrator** | An organization (currently, The Trade Desk) that manages the UID2 Core Service and other component services. For example, it distributes encryption keys and salts to UID2 operators and sends user opt-out requests to operators and DSPs. | +| **Operators** | Organizations that run the Operator Service (via the UID2 APIs). Operators periodically receive and store up-to-date encryption keys and salts from the UID2 Core Service, salt and hash directly identifying information (DII) to return raw UID2s, encrypt raw UID2s to generate UID2 tokens, and distribute UID2 token decryption keys.
Public Operators (Open Operators) run public instances of the Operator Service. For example, The Trade Desk currently serves as a Public Operator for the UID2 framework, available to all participants. If other Public Operators are available, a participant can choose which operator to work with.
Any participant can also choose to become a Private Operator to generate and manage UID2s. | + +## UID2 External Participants + +The following table summarizes the main types of external participant partners for UID2. + +| Participant | Role Description | Link to Overview Page | +| :--- | :--- | :--- | +| **Publishers** | Organizations that propagate UID2 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 UID2. Independent ID providers can handle the UID2 integration on behalf of publishers. | [UID2 Overview for Publishers](overview-publishers.md) | +| **Advertisers** | Organizations that buy impressions across a range of publisher sites and use DSPs to decide which ad impressions to purchase and how much to bid on them. | [UID2 Overview for Advertisers](overview-advertisers.md) | +| **DSPs** | DSPs integrate with the UID2 system to receive UID2s from advertisers (as first-party data) and third-party data providers (as third-party data) and leverage them to inform bidding on UID2s in the bidstream. | [UID2 Overview for DSPs](overview-dsps.md) | +| **Data Providers** | Organizations that collect user data and push it to other UID2 participants—for example, advertisers, identity graph providers, and third-party data providers. | [UID2 Overview for Data Providers](overview-data-providers.md) | + +## UID2 Consumers + +A UID2 consumer is a user who has had a UID2 token or raw UID2 created from an email address or phone number. + +UID2 leverages multiple layers of security to help protect user and other participant data. UID2 is a privacy-compliant identifier. With UID2, consumers can enjoy more personalized advertising without compromising privacy. + +Consumers can opt out of UID2 in the [Transparency and Control Portal](https://www.transparentadvertising.com/). + + diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/glossary-uid.md b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/glossary-uid.md index 02e106f3c..2cfb4866e 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/glossary-uid.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/glossary-uid.md @@ -129,7 +129,7 @@ import Link from '@docusaurus/Link';
Advertising token は UID2 token の別名です。.
API key
-
UID2 参加者 はそれぞれ、API Key (Client Key) と、そのキーに関連付けられた Client Secret (APIシークレット) と呼ばれる秘密の値を持っています。Client Secretは、参加者と UID Service だけが知っています。
+
UID2 参加者 はそれぞれ、API Key (Client Key) と、そのキーに関連付けられた Client Secret (APIシークレット) と呼ばれる秘密の値を持っています。Client Secretは、参加者と UID Service だけが知っています。
詳細は UID2 Credentials を参照してください。
API secret
@@ -169,7 +169,7 @@ import Link from '@docusaurus/Link';
詳細は　Subscription ID and Public Key を参照してください。
Client secret
-
各 UID2 参加者は、API Key (Client Key) と、そのキーに関連付けられた秘密値 (Client secret (API シークレット)) を持っています。Client secretは、参加者と UID2 Service だけが知っています。
+
各 UID2 参加者は、API Key (Client Key) と、そのキーに関連付けられた秘密値 (Client secret (API シークレット)) を持っています。Client secretは、参加者と UID2 Service だけが知っています。
詳細は、UID2 Credentials を参照してください。
Client-server integration
@@ -205,7 +205,7 @@ import Link from '@docusaurus/Link';
Core Service
UID2 Core Serviceは、UID2 エコシステムの salts、暗号化キー、その他の関連データへのアクセスを管理する一元的なサービスです。
-
すべてのUID2 Service の概要については、Components を参照してください。
+
すべてのUID2 Service の概要については、UID2 Component Services を参照してください。
@@ -215,7 +215,7 @@ import Link from '@docusaurus/Link';
Data provider
UID2 のコンテキストでは、データプロバイダーは、データパートナー、測定パートナー、オフライン測定プロバイダーなど、広告に関連するデータおよび測定サービスを提供する事業社を指します。
-
詳細は participant (Data Providers) を参照してください。
+
詳細は participant (Data Providers) を参照してください。
Demand-side platform (DSP)
デマンドサイドプラットフォーム (DSP)は、広告主、ブランド、メディアエージェンシーなど、デジタル広告を購入したい企業にサービスを提供するプラットフォームです。
@@ -341,7 +341,7 @@ import Link from '@docusaurus/Link';
Operator とは、UID2の Operator Service を運営する組織や団体のことです。UID2 Operatorは、UID2 エコシステムの API サーバーです。
Operators は、UID2 Core Service から 暗号化キー と ソルト を受け取り、個人に関するデータ (DII) をソルト化およびハッシュ化して raw UID2 を返し、raw UID2 を暗号化して UID2 Token を生成生成するなど、複数の機能を実行します。
参加者は、UID2 API にアクセスし、プライベートインフラ内で raw UID2 と UID2 Token を生成するために、Private Operator になることも選択できます。
-
詳細は participants と The UID2 Operator を参照してください。
+
詳細は participants と The UID2 Operator を参照してください。
Operator key
各 UID2 Private Operator は、Private Operator Service が Core Service とOpt-Out Service に接続し、その上でいくつかのエンドポイントを呼び出すことを可能にする Operator key を持っています。
@@ -349,7 +349,7 @@ import Link from '@docusaurus/Link';
Operator Service
Operator のすべての機能を可能にするサービスです
-
すべての UID2 Service の概要については、Components を参照してください。
+
すべての UID2 Service の概要については、UID2 Component Services を参照してください。
Opt-Out
UID2 エコシステムに参加しているエンドユーザーは、Transparency and Control Portal にアクセスすることで、いつでもオプトアウトすることができます。
@@ -357,7 +357,7 @@ import Link from '@docusaurus/Link';
Opt-Out Service
Opt-Out Service は、ユーザーのオプトアウト要求を管理・保存するグローバルな UID2 Service です。
-
すべての UID2 Service の概要については、Components を参照してください。
+
すべての UID2 Service の概要については、UID2 Component Services を参照してください。
@@ -367,7 +367,7 @@ import Link from '@docusaurus/Link';
Participant
UID2 において重要な役割を果たすエンティティです。参加者には以下が含まれます: Core Administrator、Operator、DSP、データプロバイダー、広告主、パブリッシャー、消費者。
-
詳細は、参加者 を参照してください。
+
詳細は、参加者 を参照してください。
Private Operator
Private operator は、Operator Service のプライベートインスタンスを実行する事業社です。Private Operator は、安全な環境で独自のリソース (ハードウェアなど) を使用して、自身のために UID2 を生成および管理します。
@@ -392,7 +392,7 @@ import Link from '@docusaurus/Link';
Raw UID2
UID2 API または SDK を通じて、ユーザーの directly identifying information (メールアドレスまたは電話番号) を入力として作成される、暗号化されていない英数字の識別子。raw UID2 を暗号化して UID2 Token を作成します。raw UID2 は一意な値であり、同じ UID2 は2つとありません。raw UID2 とそれに関連付けられた UID2 Token は、大文字と小文字を区別します。
-
詳細は UID2 Identifier Types を参照してください。
+
詳細は UID2 Identifier Types を参照してください。
Refresh Token
Refresh tokenは、UID2 Tokenとともに発行される不透明な文字列です。UID2 token の有効期限を更新するために使用されます。
@@ -485,13 +485,13 @@ import Link from '@docusaurus/Link';
UID2 と EUID の間には多くの類似点がありますが、両者は完全に別物であり、トークンに互換性はありません。
UID2 framework
-
Unified ID 2.0 (UID2) フレームワークは、広告エコシステム全体の多くの 参加者 に対して、オープンインターネット上の広告機会に対する決定論的な ID を提供します。これにより、パブリッシャーウェブサイト、モバイルアプリ、Connected TV (CTV) アプリがプログラマティックワークフローを通じて収益化できます。独自の名前空間を持つオープンソースのスタンドアロンソリューションとして構築されたフレームワークは、参加者が地域の要件を満たすのに役立つプライバシーコントロールを提供します。
+
Unified ID 2.0 (UID2) フレームワークは、広告エコシステム全体の多くの 参加者 に対して、オープンインターネット上の広告機会に対する決定論的な ID を提供します。これにより、パブリッシャーウェブサイト、モバイルアプリ、Connected TV (CTV) アプリがプログラマティックワークフローを通じて収益化できます。独自の名前空間を持つオープンソースのスタンドアロンソリューションとして構築されたフレームワークは、参加者が地域の要件を満たすのに役立つプライバシーコントロールを提供します。
UID2 は北米、アジアの一部、およびその他の地域で運営されています。
UID2とEUIDの間には多くの類似点がありますが、両者は完全に別物であり、トークンに互換性はありません。
UID2 identifier
Unified ID 2.0 (UID2)識別子には、raw UID2s と UID2 tokens (Advertising token とも呼ばれるます) の2種類があります。
-
詳細は UID2 Identifier Types を参照してください。
+
詳細は UID2 Identifier Types を参照してください。
UID2 Portal
UID2 Portal は、UID2 参加者が自分のアカウントを管理するための独立したユーザーインターフェースです。
@@ -507,7 +507,7 @@ import Link from '@docusaurus/Link';
トークンの値は不透明です。文字列のフォーマットや長さについて、推測してはなりません。
トークンの寿命は限られていますが、refresh token を使ってバックグラウンドでリフレッシュすることができます。
パブリッシャーは、ビッドストリームに UID2 Token を送信します。
-
詳細は UID2 Identifier Types と UID2 Tokens: Key Information を参照してください。
+
詳細は UID2 Identifier Types と UID2 Tokens: Key Information を参照してください。
Unified ID 2.0 (UID2)
"UID2" という用語は、UID2 framework、UID2 service、raw UID2、またはUID2 token (Advertising Token) を意味でも使われます。
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/images/UID2Workflows.svg b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/images/UID2Workflows.svg similarity index 100% rename from i18n/ja/docusaurus-plugin-content-docs/current/images/UID2Workflows.svg rename to i18n/ja/docusaurus-plugin-content-docs/current/ref-info/images/UID2Workflows.svg diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/images/source/source.txt b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/images/source/source.txt similarity index 100% rename from i18n/ja/docusaurus-plugin-content-docs/current/images/source/source.txt rename to i18n/ja/docusaurus-plugin-content-docs/current/ref-info/images/source/source.txt diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/ref-how-uid-is-created.md b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/ref-how-uid-is-created.md index b466b1a56..cc67d8925 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/ref-how-uid-is-created.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/ref-how-uid-is-created.md @@ -18,7 +18,7 @@ When a publisher sends a user's DII Some preliminary steps are taken by the publisher, but most of the processing steps are done by the UID2 Operator. It's very important that the publisher steps are performed in the correct sequence: -- When steps are performed in sequence, the resulting value can be recognized as related to other [UID2 identifiers](../intro.md#uid2-identifier-types) generated from online activity by the same individual: the underlying [raw UID2](../ref-info/glossary-uid.md#gl-raw-uid2) matches the raw UID2s generated by other UID2 participants from the same DII, and therefore the token is suitable for targeted advertising. +- When steps are performed in sequence, the resulting value can be recognized as related to other [UID2 identifiers](uid-infrastructure.md#uid2-identifier-types) generated from online activity by the same individual: the underlying [raw UID2](../ref-info/glossary-uid.md#gl-raw-uid2) matches the raw UID2s generated by other UID2 participants from the same DII, and therefore the token is suitable for targeted advertising. - If steps are taken out of sequence, the resulting value cannot be related to other UID2 identifiers generated from online activity by the same individual, and therefore the token is not suitable for targeted advertising. For a summary, see [Steps to Create a UID2 Token](#steps-to-create-a-uid2-token). For an example in diagram form, see [Creating a UID2 Token—Example](#creating-a-uid2-tokenexample). diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-infrastructure.md b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-infrastructure.md new file mode 100644 index 000000000..4f5be9d84 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-infrastructure.md @@ -0,0 +1,56 @@ +--- +title: UID2 Infrastructure +description: Summary of key elements in the UID2 infrastructure, including identifier types, components, participants, and workflows. +hide_table_of_contents: false +sidebar_position: 01 +displayed_sidebar: docs +--- + +import Link from '@docusaurus/Link'; + +# UID2 Infrastructure + +The following sections explain and illustrate the key elements of the UID2 framework infrastructure: + +- [UID2 Identifier Types](#uid2-identifier-types) +- [UID2 Components](#uid2-components) +- [Workflows](#workflows) + +### UID2 Identifier Types + +UID2 is a deterministic ID that is based on directly identifying information (DII), such as email address or phone number. There are two types of UID2s: raw UID2s and UID2 tokens (also known as advertising tokens). The following table explains each type. + +| ID Type | Shared in Bidstream? | Description | +| :--- | :--- | :--- | +| **Raw UID2** | No | An unencrypted alphanumeric identifier created through the UID2 APIs or SDKs with the user's verifiable personal data, such as a hashed or unhashed email address or a phone number, as input.
To avoid revealing the source data, the input value is hashed if it was not already hashed, and then hashed again using a secret salt value to create the raw UID2. The process that creates the raw UID2 is designed to create a secure, opaque value that can be stored by advertisers, third-party data providers, and demand-side platforms (DSPs).
Raw UID2s are case sensitive.
Example: A request for the raw UID2 for the fictitious email address `user@example.com` resulted in this value: `E2dxEv3oMBzNHPw5iUVmwH2Hv+60D4AXYe+2ge9U0No=`. | +| **UID2 Token (Advertising Token)** | Yes | An encrypted form of a raw UID2. UID2 tokens are generated from hashed or unhashed email addresses or phone numbers that are converted to raw UID2s and then encrypted to help ensure protection in the bidstream.
UID2 tokens are designed to be used by publishers or publisher service providers. Supply-side platforms (SSPs) pass UID2 tokens in the bidstream and DSPs decrypt them at bid request time.
UID2 tokens are case sensitive.
Example: A request for a UID2 token for the fictitious email address `user@example.com` resulted in this value: `A4AAAAs6ZBcEbwAPoFhVV7CNW5W-4R-9TKDNL4RS0ctkw1U-IkNOXSnWczvwOMgCQaXHPf3Gd1o1W6IBmlZBFIloM67XOsOgwP5jUrQrclGkq1zBJJUJmOFTe6sJJA7pM1GP9gLd-hz5did6baZvcKd8DXkUYM-WALRZFnzHivu_1YEsC_CeXNdMexKDN7EwSQ6L5eZvOd1F1RkF_nLy_J0twg`. | + +:::note +For the fictitious email address `user@example.com` used in these examples, the corresponding refresh token was: `AAAABrexFHvQVhNJqu+y/ua7rsgShF8e9NUXUJOZFmeFRD8TAsJadaLfOlLkwC5iSxcOKWFD9YwMBzbbcPa92CInba+bcPTaAFNmM2ZpIHgGy6lDcNPzvEnPQh/5fyZ3MD44SX/tHyIXa0R2OBAOLBA1A81r3jefhSsxZdyyBF58KtnaX6UbaeOEaguOfMnJdmhaPeWKj33v7vGfROWtxDWmi6wvGL5lHTX9H6iIZ9i1WSsemYPUgmoDOQeT7nzllJK968OECFj5LkCazDN3pCrYSeuJby9o0fMuSZNxzp6EVzi6XVED4ETtzpcaY0AArzzdh0IXV9MgH8jyg7bJSUWXQG+8kMPZzwbs9EB+7ddAUOLZL/GBna8Hm3Im03EjN3sJ`. +::: + +### UID2 Components + +The UID2 framework consists of the following components, all of which are currently managed by The Trade Desk. + +| Component | Description | +| :--- | :--- | +| **Core Service** | A centralized service that manages access to salts, encryption keys, and other relevant data in the UID2 ecosystem. | +| **Operator Service** | A service that enables the management and storage of encryption keys and salts from the UID2 Core Service, hashing of users' personal data, encryption of raw UID2s, and decryption of UID2 tokens. There can be multiple instances of the service (public or private) operated by multiple [participants](../overviews/participants-overview.md#uid2-component-services), known as operators.
Public Operators run publicly available instances of the Operator Service and make them available to all relevant UID2 participants. There might also be Private Operators that run private instances of the Operator Service exclusively for their own use. All instances are designed with protections to keep critical UID2 data secure and interoperable, regardless of who operates the service. | +| **Opt-Out Service** | A global service that manages and stores user opt-out requests and disseminates them to publishers, operator service instances, and DSPs. | +| **Transparency and Control Portal** | A user-facing website, [https://www.transparentadvertising.com/](https://www.transparentadvertising.com/), that allows consumers to opt out of UID2 at any time. | + +### Workflows + +The following table lists four key workflows in the UID2 framework with links to their high-level overviews. It also provides links to the respective integration guides, which include diagrams, integration steps, FAQs, and other relevant information for each workflow. + +| Workflow | Intended Primary Participants | Integration Guides | +| :--- |:--- |:--- | +| [Workflow for DSPs](../overviews/overview-dsps.md#workflow-for-dsps) (Buy-Side) | DSPs who transact on UID2 tokens in the bidstream. | See [DSP Integrations](../guides/summary-guides#dsp-integrations) | +| [Workflow for Advertisers](../overviews/overview-advertisers.md#workflow-for-advertisers) and [Workflow for Data Providers](../overviews/overview-data-providers.md#workflow-for-data-providers) | Organizations that collect user data and push it to DSPs. | See [Advertiser/Data Provider Integrations](../guides/summary-guides#advertiserdata-provider-integrations) | +| [Workflow for Publishers](../overviews/overview-publishers.md#workflow-for-publishers) | Organizations that propagate UID2 tokens to the bidstream via SSPs.
NOTE: Publishers can choose to integrate using Prebid, leverage the SDK for JavaScript, or complete their own server-side integration without using an SDK. | See [Publisher Integrations](../guides/summary-guides#publisher-integrations) | +| [Opt-Out Workflow](../getting-started/gs-opt-out.md#opt-out-workflow) | Consumers who engage with publishers or their SSO providers and other identity providers. | N/A | + +The following diagram summarizes all four workflows. For each workflow, the [participants](../overviews/participants-overview.md#uid2-external-participants), [components](../overviews/participants-overview.md#uid2-component-services), [UID2 identifier types](#uid2-identifier-types), and numbered steps are color-coded. + +![The UID2 Ecosystem](images/UID2Workflows.svg) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/updates-doc.md b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/updates-doc.md index 3bfeff645..03f01c827 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/updates-doc.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/updates-doc.md @@ -356,7 +356,7 @@ UID2 リクエストの暗号化とレスポンスの復号化について、追 November 30, 2023 -[Private Operator](../ref-info/glossary-uid.md#gl-private-operator) の運用を希望する UID2 参加者は、Microsoft Azure の機密コンピューティングオプションである Confidential Containers のインスタンスで UID2 Operator Service をセットアップできるようになりました。 +[Private Operator](../ref-info/glossary-uid.md#gl-private-operator) の運用を希望する UID2 参加者は、Microsoft Azure の機密コンピューティングオプションである Confidential Containers のインスタンスで UID2 Operator Service をセットアップできるようになりました。 詳細は [UID2 Private Operator for Azure Integration Guide](../guides/operator-guide-azure-enclave.md) を参照してください。 diff --git a/sidebars.js b/sidebars.js index c84662673..c43238cd6 100644 --- a/sidebars.js +++ b/sidebars.js @@ -29,7 +29,6 @@ const fullSidebar = [ }, collapsed: false, items: [ - 'ref-info/uid-principles', 'ref-info/uid-infrastructure', ], }, From 7cda5205851118fc4596e285debf7b93d6680e9a Mon Sep 17 00:00:00 2001 From: genwhittTTD Date: Tue, 18 Mar 2025 09:38:57 -0400 Subject: [PATCH 4/6] additional link fixes --- docs/guides/integration-javascript.md | 2 +- docs/guides/integration-mobile-overview.md | 6 +++--- docs/guides/mobile-plugin-gma-android.md | 2 +- docs/guides/mobile-plugin-gma-ios.md | 2 +- docs/guides/mobile-plugin-ima-android.md | 2 +- docs/guides/mobile-plugin-ima-ios.md | 2 +- docs/sdks/sdk-ref-android.md | 2 +- docs/sdks/sdk-ref-ios.md | 2 +- .../current/guides/integration-javascript.md | 2 +- .../current/guides/integration-mobile-overview.md | 2 +- .../current/guides/mobile-plugin-gma-android.md | 2 +- .../current/guides/mobile-plugin-gma-ios.md | 2 +- .../current/guides/mobile-plugin-ima-android.md | 2 +- .../current/guides/mobile-plugin-ima-ios.md | 2 +- .../current/sdks/sdk-ref-android.md | 2 +- .../current/sdks/sdk-ref-ios.md | 2 +- 16 files changed, 18 insertions(+), 18 deletions(-) diff --git a/docs/guides/integration-javascript.md b/docs/guides/integration-javascript.md index 0650c2222..b543d4dd5 100644 --- a/docs/guides/integration-javascript.md +++ b/docs/guides/integration-javascript.md @@ -51,7 +51,7 @@ The steps you'll take in the UID2 Portal are different depending on whether your Depending on access to DII, there are two methods to generate UID2 tokens using the SDK for JavaScript: client-side or server-side. -From the table in [Client-Side or Client-Server Integration](#client-side-or-client-server-integration), determine which option is best for you, and then follow the applicable integration guide. +From the table in [Client-Side or Client-Server Integration](#client-side-client-server-or-server-side-integration), determine which option is best for you, and then follow the applicable integration guide. ## Refreshing the UID2 Token diff --git a/docs/guides/integration-mobile-overview.md b/docs/guides/integration-mobile-overview.md index b9d1dd205..2239ce7e1 100644 --- a/docs/guides/integration-mobile-overview.md +++ b/docs/guides/integration-mobile-overview.md @@ -58,7 +58,7 @@ For details, refer to one of the following guides: To determine the best integration path for your mobile scenario, consider these points: -1. Do you want to retrieve the UID2 token on the client side or on the server side? See [Client-Side or Client-Server Integration](#client-side-or-client-server-integration). +1. Do you want to retrieve the UID2 token on the client side or on the server side? See [Client-Side, Client-Server, or Server-Side Integration?](#client-side-client-server-or-server-side-integration). 1. What do you want to use to retrieve and refresh the UID2 token? See [Generating, Storing, and Refreshing the UID2 Token](#generating-storing-and-refreshing-the-uid2-token). @@ -70,9 +70,9 @@ To integrate with UID2, you'll need to have a UID2 account. If you haven't yet c When initial account setup is complete, you'll receive instructions and a link to access the [UID2 Portal](../portal/portal-overview.md), where you can create your [credentials](../getting-started/gs-credentials.md) for the production environment and configure additional values, if needed. For details, see [Getting Started with the UID2 Portal](../portal/portal-getting-started.md). -The steps you'll take in the UID2 Portal are different depending on whether your implementation will be client-side, client-server, or server-side. Specific instructions are in each implementation guide. For a summary, see [Client-Side or Client-Server Integration?](#client-side-or-client-server-integration) +The steps you'll take in the UID2 Portal are different depending on whether your implementation will be client-side, client-server, or server-side. Specific instructions are in each implementation guide. For a summary, see [Client-Side, Client-Server, or Server-Side Integration?](#client-side-client-server-or-server-side-integration). -### Client-Side or Client-Server Integration? +### Client-Side, Client-Server, or Server-Side Integration? The options for integrating with UID2 using the UID2 mobile SDKs are summarized in the following table. Choose the integration approach that's best for you. diff --git a/docs/guides/mobile-plugin-gma-android.md b/docs/guides/mobile-plugin-gma-android.md index e265bc518..10c21c19f 100644 --- a/docs/guides/mobile-plugin-gma-android.md +++ b/docs/guides/mobile-plugin-gma-android.md @@ -33,7 +33,7 @@ To integrate with UID2, you'll need to have a UID2 account. If you haven't yet c When initial account setup is complete, you'll receive instructions and a link to access the [UID2 Portal](../portal/portal-overview.md), where you can create your [credentials](../getting-started/gs-credentials.md) for the production environment and configure additional values, if needed. For details, see [Getting Started with the UID2 Portal](../portal/portal-getting-started.md). -The steps you'll take in the UID2 Portal are different depending on whether your implementation will be client-side, client-server, or server-side. Specific instructions are in each implementation guide. For a summary, see [Client-Side or Client-Server Integration?](integration-mobile-overview#client-side-or-client-server-integration). +The steps you'll take in the UID2 Portal are different depending on whether your implementation will be client-side, client-server, or server-side. Specific instructions are in each implementation guide. For a summary, see [Client-Side, Client-Server, or Server-Side Integration?](integration-mobile-overview#client-side-client-server-or-server-side-integration). ## Requirements diff --git a/docs/guides/mobile-plugin-gma-ios.md b/docs/guides/mobile-plugin-gma-ios.md index d3235bdb7..2ff6dfd6a 100644 --- a/docs/guides/mobile-plugin-gma-ios.md +++ b/docs/guides/mobile-plugin-gma-ios.md @@ -33,7 +33,7 @@ To integrate with UID2, you'll need to have a UID2 account. If you haven't yet c When initial account setup is complete, you'll receive instructions and a link to access the [UID2 Portal](../portal/portal-overview.md), where you can create your [credentials](../getting-started/gs-credentials.md) for the production environment and configure additional values, if needed. For details, see [Getting Started with the UID2 Portal](../portal/portal-getting-started.md). -The steps you'll take in the UID2 Portal are different depending on whether your implementation will be client-side, client-server, or server-side. Specific instructions are in each implementation guide. For a summary, see [Client-Side or Client-Server Integration?](integration-mobile-overview#client-side-or-client-server-integration). +The steps you'll take in the UID2 Portal are different depending on whether your implementation will be client-side, client-server, or server-side. Specific instructions are in each implementation guide. For a summary, see [Client-Side, Client-Server, or Server-Side Integration?](integration-mobile-overview#client-side-client-server-or-server-side-integration). ## Requirements diff --git a/docs/guides/mobile-plugin-ima-android.md b/docs/guides/mobile-plugin-ima-android.md index 35f8f7b19..11b84162b 100644 --- a/docs/guides/mobile-plugin-ima-android.md +++ b/docs/guides/mobile-plugin-ima-android.md @@ -33,7 +33,7 @@ To integrate with UID2, you'll need to have a UID2 account. If you haven't yet c When initial account setup is complete, you'll receive instructions and a link to access the [UID2 Portal](../portal/portal-overview.md), where you can create your [credentials](../getting-started/gs-credentials.md) for the production environment and configure additional values, if needed. For details, see [Getting Started with the UID2 Portal](../portal/portal-getting-started.md). -The steps you'll take in the UID2 Portal are different depending on whether your implementation will be client-side, client-server, or server-side. Specific instructions are in each implementation guide. For a summary, see [Client-Side or Client-Server Integration?](integration-mobile-overview#client-side-or-client-server-integration). +The steps you'll take in the UID2 Portal are different depending on whether your implementation will be client-side, client-server, or server-side. Specific instructions are in each implementation guide. For a summary, see [Client-Side, Client-Server, or Server-Side Integration?](integration-mobile-overview#client-side-client-server-or-server-side-integration). ## Requirements diff --git a/docs/guides/mobile-plugin-ima-ios.md b/docs/guides/mobile-plugin-ima-ios.md index 39c8ecdc7..318feefb5 100644 --- a/docs/guides/mobile-plugin-ima-ios.md +++ b/docs/guides/mobile-plugin-ima-ios.md @@ -33,7 +33,7 @@ To integrate with UID2, you'll need to have a UID2 account. If you haven't yet c When initial account setup is complete, you'll receive instructions and a link to access the [UID2 Portal](../portal/portal-overview.md), where you can create your [credentials](../getting-started/gs-credentials.md) for the production environment and configure additional values, if needed. For details, see [Getting Started with the UID2 Portal](../portal/portal-getting-started.md). -The steps you'll take in the UID2 Portal are different depending on whether your implementation will be client-side, client-server, or server-side. Specific instructions are in each implementation guide. For a summary, see [Client-Side or Client-Server Integration?](integration-mobile-overview#client-side-or-client-server-integration). +The steps you'll take in the UID2 Portal are different depending on whether your implementation will be client-side, client-server, or server-side. Specific instructions are in each implementation guide. For a summary, see [Client-Side, Client-Server, or Server-Side Integration?](integration-mobile-overview#client-side-client-server-or-server-side-integration). ## Requirements diff --git a/docs/sdks/sdk-ref-android.md b/docs/sdks/sdk-ref-android.md index c16bd9fef..e5a663a71 100644 --- a/docs/sdks/sdk-ref-android.md +++ b/docs/sdks/sdk-ref-android.md @@ -47,7 +47,7 @@ When initial account setup is complete, you'll receive instructions and a link t - Optional: For a client-side implementation, set up configuration values such as domain names or mobile app IDs. - Optionally, configure other values, such as setting up information about team members. -The steps you'll take in the UID2 Portal are different depending on whether your implementation will be client-side, client-server, or server-side. For a summary of mobile integration options, see [Client-Side or Client-Server Integration?](../guides/integration-mobile-overview#client-side-or-client-server-integration). +The steps you'll take in the UID2 Portal are different depending on whether your implementation will be client-side, client-server, or server-side. For a summary of mobile integration options, see [Client-Side, Client-Server, or Server-Side Integration?](../guides/integration-mobile-overview#client-side-client-server-or-server-side-integration). diff --git a/docs/sdks/sdk-ref-ios.md b/docs/sdks/sdk-ref-ios.md index 919f170b4..02fc54f3a 100644 --- a/docs/sdks/sdk-ref-ios.md +++ b/docs/sdks/sdk-ref-ios.md @@ -44,7 +44,7 @@ When initial account setup is complete, you'll receive instructions and a link t - Optional: For a client-side implementation, set up configuration values such as domain names or mobile app IDs. - Optionally, configure other values, such as setting up information about team members. -The steps you'll take in the UID2 Portal are different depending on whether your implementation will be client-side, client-server, or server-side. For a summary of mobile integration options, see [Client-Side or Client-Server Integration?](../guides/integration-mobile-overview#client-side-or-client-server-integration). +The steps you'll take in the UID2 Portal are different depending on whether your implementation will be client-side, client-server, or server-side. For a summary of mobile integration options, see [Client-Side, Client-Server, or Server-Side Integration?](../guides/integration-mobile-overview#client-side-client-server-or-server-side-integration). diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-javascript.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-javascript.md index 46974704a..e769d98f9 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-javascript.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-javascript.md @@ -51,7 +51,7 @@ UID2 Portal で行う手順は、実装が Client-Side、Client-Server、また DII へのアクセスに応じて、SDK for JavaScript を使用して UID2 Token を生成するには、Client-Side または Server-Side の2つの方法があります。 -[Client-Side or Client-Server Integration](#client-side-or-client-server-integration) の表から、どちらのオプションが最適かを判断し、該当するインテグレーションガイドに従ってください。 +[Client-Side or Client-Server Integration](#client-side-client-server-or-server-side-integration) の表から、どちらのオプションが最適かを判断し、該当するインテグレーションガイドに従ってください。 ## Refreshing the UID2 Token diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-mobile-overview.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-mobile-overview.md index e8b7e309f..3e1516211 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-mobile-overview.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-mobile-overview.md @@ -70,7 +70,7 @@ UID2 とインテグレーションんするには、UID2 アカウントが必 アカウントのセットアップが完了すると、[UID2 Portal](../portal/portal-overview.md) にアクセスするためのリンクと手順が送信されます。ここで、本番環境用の [credentials](../getting-started/gs-credentials.md) を作成し、必要に応じて追加の値を設定できます。詳細は、[Getting Started with the UID2 Portal](../portal/portal-getting-started.md) を参照してください。 -UID2 Portal での手順は、実装が Client-Side、Client-Server、または Server-Side であるかによって異なります。各インテグレーションガイドに具体的な手順が記載されています。概要は、[Client-Side or Client-Server Integration?](#client-side-or-client-server-integration) を参照してください。 +UID2 Portal での手順は、実装が Client-Side、Client-Server、または Server-Side であるかによって異なります。各インテグレーションガイドに具体的な手順が記載されています。概要は、[Client-Side, Client-Server, or Server-Side Integration?](#client-side-client-server-or-server-side-integration) を参照してください。 ### Client-Side or Client-Server Integration? diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-gma-android.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-gma-android.md index a5f976251..d58f61f96 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-gma-android.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-gma-android.md @@ -33,7 +33,7 @@ UID2 とインテグレーションするには、UID2 アカウントが必要 アカウントの初期設定が完了すると、[UID2 Portal](../portal/portal-overview.md) にアクセスするための手順とリンクが送信されます。ここで、本番環境用の [credentials](../getting-started/gs-credentials.md) を作成し、必要に応じて追加の値を設定できます。詳細については、[Getting Started with the UID2 Portal](../portal/portal-getting-started.md) を参照してください。 -UID2 Portal で実行する手順は、実装が　Client-Side、Client-Server、Server-Side のいずれであるかによって異なります。各実装ガイドに具体的な手順が記載されています。概要については、[Client-Side or Client-Server Integration?](integration-mobile-overview#client-side-or-client-server-integration) を参照してください。 +UID2 Portal で実行する手順は、実装が　Client-Side、Client-Server、Server-Side のいずれであるかによって異なります。各実装ガイドに具体的な手順が記載されています。概要については、[Client-Side, Client-Server, or Server-Side Integration?](integration-mobile-overview#client-side-client-server-or-server-side-integration) を参照してください。 ## Requirements diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-gma-ios.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-gma-ios.md index 2e09f982c..2b2a664eb 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-gma-ios.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-gma-ios.md @@ -33,7 +33,7 @@ UID2 とインテグレーションするには、UID2 アカウントが必要 アカウントの初期設定が完了すると、[UID2 Portal](../portal/portal-overview.md) にアクセスするための手順とリンクが送信されます。ここで、本番環境用の [credentials](../getting-started/gs-credentials.md) を作成し、必要に応じて追加の値を設定できます。詳細については、[Getting Started with the UID2 Portal](../portal/portal-getting-started.md) を参照してください。 -UID2 Portal で実行する手順は、実装が　Client-Side、Client-Server、Server-Side のいずれであるかによって異なります。各実装ガイドに具体的な手順が記載されています。概要については、[Client-Side or Client-Server Integration?](integration-mobile-overview#client-side-or-client-server-integration) を参照してください。 +UID2 Portal で実行する手順は、実装が　Client-Side、Client-Server、Server-Side のいずれであるかによって異なります。各実装ガイドに具体的な手順が記載されています。概要については、[Client-Side, Client-Server, or Server-Side Integration?](integration-mobile-overview#client-side-client-server-or-server-side-integration) を参照してください。 ## Requirements diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-ima-android.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-ima-android.md index 899242da5..617faf259 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-ima-android.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-ima-android.md @@ -33,7 +33,7 @@ UID2 とインテグレーションするには、UID2 アカウントが必要 アカウントの初期設定が完了すると、[UID2 Portal](../portal/portal-overview.md) にアクセスするための手順とリンクが送信されます。ここで、本番環境用の [credentials](../getting-started/gs-credentials.md) を作成し、必要に応じて追加の値を設定できます。詳細については、[Getting Started with the UID2 Portal](../portal/portal-getting-started.md) を参照してください。 -UID2 Portal で実行する手順は、実装が　Client-Side、Client-Server、Server-Side のいずれであるかによって異なります。各実装ガイドに具体的な手順が記載されています。概要については、[Client-Side or Client-Server Integration?](integration-mobile-overview#client-side-or-client-server-integration) を参照してください。 +UID2 Portal で実行する手順は、実装が　Client-Side、Client-Server、Server-Side のいずれであるかによって異なります。各実装ガイドに具体的な手順が記載されています。概要については、[Client-Side, Client-Server, or Server-Side Integration?](integration-mobile-overview#client-side-client-server-or-server-side-integration) を参照してください。 ## Requirements diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-ima-ios.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-ima-ios.md index be5bb00f6..975ae57cc 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-ima-ios.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-ima-ios.md @@ -33,7 +33,7 @@ UID2 とインテグレーションするには、UID2 アカウントが必要 アカウントの初期設定が完了すると、[UID2 Portal](../portal/portal-overview.md) にアクセスするための手順とリンクが送信されます。ここで、本番環境用の [credentials](../getting-started/gs-credentials.md) を作成し、必要に応じて追加の値を設定できます。詳細については、[Getting Started with the UID2 Portal](../portal/portal-getting-started.md) を参照してください。 -UID2 Portal で実行する手順は、実装が　Client-Side、Client-Server、Server-Side のいずれであるかによって異なります。各実装ガイドに具体的な手順が記載されています。概要については、[Client-Side or Client-Server Integration?](integration-mobile-overview#client-side-or-client-server-integration) を参照してください。 +UID2 Portal で実行する手順は、実装が　Client-Side、Client-Server、Server-Side のいずれであるかによって異なります。各実装ガイドに具体的な手順が記載されています。概要については、[Client-Side, Client-Server, or Server-Side Integration?](integration-mobile-overview#client-side-client-server-or-server-side-integration) を参照してください。 ## Requirements diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-android.md b/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-android.md index 6dc4d5bf5..a8b2c9622 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-android.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-android.md @@ -47,7 +47,7 @@ UID2 とのインテグレーションを行うには、UID2 アカウントが - オプション: Client-Side の実装の場合、ドメイン名やモバイルアプリ ID などの設定値を設定します。 - オプションとして、チームメンバーに関する情報を設定するなど、他の値を設定します。 -UID2 Portal で実行する手順は、実装が Client-Side、Client-Server、Server-Side のいずれであるかによって異なります。モバイルインテグレーションオプションの概要については、[Client-Side or Client-Server Integration?](../guides/integration-mobile-overview#client-side-or-client-server-integration) を参照してください。 +UID2 Portal で実行する手順は、実装が Client-Side、Client-Server、Server-Side のいずれであるかによって異なります。モバイルインテグレーションオプションの概要については、[Client-Side, Client-Server, or Server-Side Integration?](../guides/integration-mobile-overview#client-side-client-server-or-server-side-integration) を参照してください。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-ios.md b/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-ios.md index ef817c14e..ace640732 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-ios.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-ios.md @@ -44,7 +44,7 @@ UID2 とインテグレーションするには、UID2 アカウントが必要 - オプション: Client-Side の実装の場合、ドメイン名やモバイルアプリ ID などの設定値を設定します。 - オプションとして、チームメンバーに関する情報を設定するなど、他の値を設定します。 -UID2 Portal で実行する手順は、実装が Client-Side、Client-Server、Server-Side のいずれであるかによって異なります。モバイルインテグレーションのオプションの概要については、[Client-Side or Client-Server Integration?](../guides/integration-mobile-overview#client-side-or-client-server-integration) を参照してください。 +UID2 Portal で実行する手順は、実装が Client-Side、Client-Server、Server-Side のいずれであるかによって異なります。モバイルインテグレーションのオプションの概要については、[Client-Side, Client-Server, or Server-Side Integration?](../guides/integration-mobile-overview#client-side-client-server-or-server-side-integration) を参照してください。 From a5badde57a1ce9cf0b82ed63a067d526a16dd8e3 Mon Sep 17 00:00:00 2001 From: genwhittTTD Date: Wed, 26 Mar 2025 15:02:20 -0400 Subject: [PATCH 5/6] broke out the infrastructure page --- docs/intro.md | 7 ++- docs/overviews/participants-overview.md | 4 +- docs/ref-info/ref-how-uid-is-created.md | 2 +- docs/ref-info/uid-components.md | 20 +++++++ docs/ref-info/uid-identifier-types.md | 22 ++++++++ docs/ref-info/uid-infrastructure.md | 56 ------------------- docs/ref-info/uid-workflows.md | 24 ++++++++ .../current/intro.md | 7 +++ .../overviews/participants-overview.md | 4 +- .../ref-info/ref-how-uid-is-created.md | 2 +- .../current/ref-info/uid-components.md | 20 +++++++ .../current/ref-info/uid-identifier-types.md | 22 ++++++++ .../current/ref-info/uid-infrastructure.md | 56 ------------------- .../current/ref-info/uid-workflows.md | 24 ++++++++ sidebars.js | 4 +- 15 files changed, 154 insertions(+), 120 deletions(-) create mode 100644 docs/ref-info/uid-components.md create mode 100644 docs/ref-info/uid-identifier-types.md delete mode 100644 docs/ref-info/uid-infrastructure.md create mode 100644 docs/ref-info/uid-workflows.md create mode 100644 i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-components.md create mode 100644 i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-identifier-types.md delete mode 100644 i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-infrastructure.md create mode 100644 i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-workflows.md diff --git a/docs/intro.md b/docs/intro.md index 3fe05adcf..e7c8e92a2 100644 --- a/docs/intro.md +++ b/docs/intro.md @@ -48,7 +48,12 @@ The UID2 framework is built on the following technical principles: ## Elements of the UID2 Infrastructure -For details, see [UID2 Infrastructure](ref-info/uid-infrastructure.md). +For information about key elements of the UID2 infrastructure, refer to the following pages: + +- [UID2 Identifier Types](ref-info/uid-identifier-types.md) +- [UID2 Components](ref-info/uid-components.md) +- [UID2 Participants](overviews/participants-overview.md) +- [Workflows](ref-info/uid-workflows.md) ## Components diff --git a/docs/overviews/participants-overview.md b/docs/overviews/participants-overview.md index 79d0eeadb..2a9bac85f 100644 --- a/docs/overviews/participants-overview.md +++ b/docs/overviews/participants-overview.md @@ -12,7 +12,7 @@ import Link from '@docusaurus/Link'; With its transparent and interoperable approach, UID2 provides a collaborative framework for many participants across the advertising ecosystem—advertisers, publishers, DSPs, SSPs, single sign-on (SSO) providers, customer data platforms (CDPs), consent management providers (CMPs), identity providers, third-party data providers, and measurement providers. -The following tables list the key participants and their roles in the UID2 [workflows](../ref-info/uid-infrastructure.md#workflows). They are grouped into three categories: +The following tables list the key participants and their roles in the [UID2 workflows](../ref-info/uid-workflows.md). They are grouped into three categories: - [UID2 Component Services](#uid2-component-services) - [UID2 External Participants](#uid2-external-participants) @@ -22,7 +22,7 @@ The following tables list the key participants and their roles in the UID2 [work The following table summarizes information about key participant components of the UID2 service. -For a diagram of how the different services work together, see [UID2 Workflows](../ref-info/uid-infrastructure.md#workflows). +For a diagram of how the different services work together, see [UID2 Workflows](../ref-info/uid-workflows.md). | Participant | Role Description | | :--- | :--- | diff --git a/docs/ref-info/ref-how-uid-is-created.md b/docs/ref-info/ref-how-uid-is-created.md index 96ab6999a..925dacab7 100644 --- a/docs/ref-info/ref-how-uid-is-created.md +++ b/docs/ref-info/ref-how-uid-is-created.md @@ -18,7 +18,7 @@ When a publisher sends a user's DII Some preliminary steps are taken by the publisher, but most of the processing steps are done by the UID2 Operator. It's very important that the publisher steps are performed in the correct sequence: -- When steps are performed in sequence, the resulting value can be recognized as related to other [UID2 identifiers](uid-infrastructure.md#uid2-identifier-types) generated from online activity by the same individual: the underlying [raw UID2](../ref-info/glossary-uid.md#gl-raw-uid2) matches the raw UID2s generated by other UID2 participants from the same DII, and therefore the token is suitable for targeted advertising. +- When steps are performed in sequence, the resulting value can be recognized as related to other [UID2 identifier types](uid-identifier-types.md) generated from online activity by the same individual: the underlying [raw UID2](../ref-info/glossary-uid.md#gl-raw-uid2) matches the raw UID2s generated by other UID2 participants from the same DII, and therefore the token is suitable for targeted advertising. - If steps are taken out of sequence, the resulting value cannot be related to other UID2 identifiers generated from online activity by the same individual, and therefore the token is not suitable for targeted advertising. For a summary, see [Steps to Create a UID2 Token](#steps-to-create-a-uid2-token). For an example in diagram form, see [Creating a UID2 Token—Example](#creating-a-uid2-tokenexample). diff --git a/docs/ref-info/uid-components.md b/docs/ref-info/uid-components.md new file mode 100644 index 000000000..5539c73d9 --- /dev/null +++ b/docs/ref-info/uid-components.md @@ -0,0 +1,20 @@ +--- +title: UID2 Components +description: Summary of key components of the UID2 technical infrastructure. +hide_table_of_contents: false +sidebar_position: 01 +displayed_sidebar: docs +--- + +import Link from '@docusaurus/Link'; + +# UID2 Components + +The UID2 framework consists of the following components, all of which are currently managed by The Trade Desk. + +| Component | Description | +| :--- | :--- | +| **Core Service** | A centralized service that manages access to salts, encryption keys, and other relevant data in the UID2 ecosystem. | +| **Operator Service** | A service that enables the management and storage of encryption keys and salts from the UID2 Core Service, hashing of users' personal data, encryption of raw UID2s, and decryption of UID2 tokens. There can be multiple instances of the service (public or private) operated by multiple [participants](../overviews/participants-overview.md#uid2-component-services), known as operators.
Public Operators run publicly available instances of the Operator Service and make them available to all relevant UID2 participants. There might also be Private Operators that run private instances of the Operator Service exclusively for their own use. All instances are designed with protections to keep critical UID2 data secure and interoperable, regardless of who operates the service. | +| **Opt-Out Service** | A global service that manages and stores user opt-out requests and disseminates them to publishers, operator service instances, and DSPs. | +| **Transparency and Control Portal** | A user-facing website, [https://www.transparentadvertising.com/](https://www.transparentadvertising.com/), that allows consumers to opt out of UID2 at any time. | diff --git a/docs/ref-info/uid-identifier-types.md b/docs/ref-info/uid-identifier-types.md new file mode 100644 index 000000000..1e7e91089 --- /dev/null +++ b/docs/ref-info/uid-identifier-types.md @@ -0,0 +1,22 @@ +--- +title: UID2 Identifier Types +description: Summary of xxx. +hide_table_of_contents: false +sidebar_position: 01 +displayed_sidebar: docs +--- + +import Link from '@docusaurus/Link'; + +# UID2 Identifier Types + +UID2 is a deterministic ID that is based on directly identifying information (DII), such as email address or phone number. There are two types of UID2s: raw UID2s and UID2 tokens (also known as advertising tokens). The following table explains each type. + +| ID Type | Shared in Bidstream? | Description | +| :--- | :--- | :--- | +| **Raw UID2** | No | An unencrypted alphanumeric identifier created through the UID2 APIs or SDKs with the user's verifiable personal data, such as a hashed or unhashed email address or a phone number, as input.
To avoid revealing the source data, the input value is hashed if it was not already hashed, and then hashed again using a secret salt value to create the raw UID2. The process that creates the raw UID2 is designed to create a secure, opaque value that can be stored by advertisers, third-party data providers, and demand-side platforms (DSPs).
Raw UID2s are case sensitive.
Example: A request for the raw UID2 for the fictitious email address `user@example.com` resulted in this value: `E2dxEv3oMBzNHPw5iUVmwH2Hv+60D4AXYe+2ge9U0No=`. | +| **UID2 Token (Advertising Token)** | Yes | An encrypted form of a raw UID2. UID2 tokens are generated from hashed or unhashed email addresses or phone numbers that are converted to raw UID2s and then encrypted to help ensure protection in the bidstream.
UID2 tokens are designed to be used by publishers or publisher service providers. Supply-side platforms (SSPs) pass UID2 tokens in the bidstream and DSPs decrypt them at bid request time.
UID2 tokens are case sensitive.
Example: A request for a UID2 token for the fictitious email address `user@example.com` resulted in this value: `A4AAAAs6ZBcEbwAPoFhVV7CNW5W-4R-9TKDNL4RS0ctkw1U-IkNOXSnWczvwOMgCQaXHPf3Gd1o1W6IBmlZBFIloM67XOsOgwP5jUrQrclGkq1zBJJUJmOFTe6sJJA7pM1GP9gLd-hz5did6baZvcKd8DXkUYM-WALRZFnzHivu_1YEsC_CeXNdMexKDN7EwSQ6L5eZvOd1F1RkF_nLy_J0twg`. | + +:::note +For the fictitious email address `user@example.com` used in these examples, the corresponding refresh token was: `AAAABrexFHvQVhNJqu+y/ua7rsgShF8e9NUXUJOZFmeFRD8TAsJadaLfOlLkwC5iSxcOKWFD9YwMBzbbcPa92CInba+bcPTaAFNmM2ZpIHgGy6lDcNPzvEnPQh/5fyZ3MD44SX/tHyIXa0R2OBAOLBA1A81r3jefhSsxZdyyBF58KtnaX6UbaeOEaguOfMnJdmhaPeWKj33v7vGfROWtxDWmi6wvGL5lHTX9H6iIZ9i1WSsemYPUgmoDOQeT7nzllJK968OECFj5LkCazDN3pCrYSeuJby9o0fMuSZNxzp6EVzi6XVED4ETtzpcaY0AArzzdh0IXV9MgH8jyg7bJSUWXQG+8kMPZzwbs9EB+7ddAUOLZL/GBna8Hm3Im03EjN3sJ`. +::: diff --git a/docs/ref-info/uid-infrastructure.md b/docs/ref-info/uid-infrastructure.md deleted file mode 100644 index 4f5be9d84..000000000 --- a/docs/ref-info/uid-infrastructure.md +++ /dev/null @@ -1,56 +0,0 @@ ---- -title: UID2 Infrastructure -description: Summary of key elements in the UID2 infrastructure, including identifier types, components, participants, and workflows. -hide_table_of_contents: false -sidebar_position: 01 -displayed_sidebar: docs ---- - -import Link from '@docusaurus/Link'; - -# UID2 Infrastructure - -The following sections explain and illustrate the key elements of the UID2 framework infrastructure: - -- [UID2 Identifier Types](#uid2-identifier-types) -- [UID2 Components](#uid2-components) -- [Workflows](#workflows) - -### UID2 Identifier Types - -UID2 is a deterministic ID that is based on directly identifying information (DII), such as email address or phone number. There are two types of UID2s: raw UID2s and UID2 tokens (also known as advertising tokens). The following table explains each type. - -| ID Type | Shared in Bidstream? | Description | -| :--- | :--- | :--- | -| **Raw UID2** | No | An unencrypted alphanumeric identifier created through the UID2 APIs or SDKs with the user's verifiable personal data, such as a hashed or unhashed email address or a phone number, as input.
To avoid revealing the source data, the input value is hashed if it was not already hashed, and then hashed again using a secret salt value to create the raw UID2. The process that creates the raw UID2 is designed to create a secure, opaque value that can be stored by advertisers, third-party data providers, and demand-side platforms (DSPs).
Raw UID2s are case sensitive.
Example: A request for the raw UID2 for the fictitious email address `user@example.com` resulted in this value: `E2dxEv3oMBzNHPw5iUVmwH2Hv+60D4AXYe+2ge9U0No=`. | -| **UID2 Token (Advertising Token)** | Yes | An encrypted form of a raw UID2. UID2 tokens are generated from hashed or unhashed email addresses or phone numbers that are converted to raw UID2s and then encrypted to help ensure protection in the bidstream.
UID2 tokens are designed to be used by publishers or publisher service providers. Supply-side platforms (SSPs) pass UID2 tokens in the bidstream and DSPs decrypt them at bid request time.
UID2 tokens are case sensitive.
Example: A request for a UID2 token for the fictitious email address `user@example.com` resulted in this value: `A4AAAAs6ZBcEbwAPoFhVV7CNW5W-4R-9TKDNL4RS0ctkw1U-IkNOXSnWczvwOMgCQaXHPf3Gd1o1W6IBmlZBFIloM67XOsOgwP5jUrQrclGkq1zBJJUJmOFTe6sJJA7pM1GP9gLd-hz5did6baZvcKd8DXkUYM-WALRZFnzHivu_1YEsC_CeXNdMexKDN7EwSQ6L5eZvOd1F1RkF_nLy_J0twg`. | - -:::note -For the fictitious email address `user@example.com` used in these examples, the corresponding refresh token was: `AAAABrexFHvQVhNJqu+y/ua7rsgShF8e9NUXUJOZFmeFRD8TAsJadaLfOlLkwC5iSxcOKWFD9YwMBzbbcPa92CInba+bcPTaAFNmM2ZpIHgGy6lDcNPzvEnPQh/5fyZ3MD44SX/tHyIXa0R2OBAOLBA1A81r3jefhSsxZdyyBF58KtnaX6UbaeOEaguOfMnJdmhaPeWKj33v7vGfROWtxDWmi6wvGL5lHTX9H6iIZ9i1WSsemYPUgmoDOQeT7nzllJK968OECFj5LkCazDN3pCrYSeuJby9o0fMuSZNxzp6EVzi6XVED4ETtzpcaY0AArzzdh0IXV9MgH8jyg7bJSUWXQG+8kMPZzwbs9EB+7ddAUOLZL/GBna8Hm3Im03EjN3sJ`. -::: - -### UID2 Components - -The UID2 framework consists of the following components, all of which are currently managed by The Trade Desk. - -| Component | Description | -| :--- | :--- | -| **Core Service** | A centralized service that manages access to salts, encryption keys, and other relevant data in the UID2 ecosystem. | -| **Operator Service** | A service that enables the management and storage of encryption keys and salts from the UID2 Core Service, hashing of users' personal data, encryption of raw UID2s, and decryption of UID2 tokens. There can be multiple instances of the service (public or private) operated by multiple [participants](../overviews/participants-overview.md#uid2-component-services), known as operators.
Public Operators run publicly available instances of the Operator Service and make them available to all relevant UID2 participants. There might also be Private Operators that run private instances of the Operator Service exclusively for their own use. All instances are designed with protections to keep critical UID2 data secure and interoperable, regardless of who operates the service. | -| **Opt-Out Service** | A global service that manages and stores user opt-out requests and disseminates them to publishers, operator service instances, and DSPs. | -| **Transparency and Control Portal** | A user-facing website, [https://www.transparentadvertising.com/](https://www.transparentadvertising.com/), that allows consumers to opt out of UID2 at any time. | - -### Workflows - -The following table lists four key workflows in the UID2 framework with links to their high-level overviews. It also provides links to the respective integration guides, which include diagrams, integration steps, FAQs, and other relevant information for each workflow. - -| Workflow | Intended Primary Participants | Integration Guides | -| :--- |:--- |:--- | -| [Workflow for DSPs](../overviews/overview-dsps.md#workflow-for-dsps) (Buy-Side) | DSPs who transact on UID2 tokens in the bidstream. | See [DSP Integrations](../guides/summary-guides#dsp-integrations) | -| [Workflow for Advertisers](../overviews/overview-advertisers.md#workflow-for-advertisers) and [Workflow for Data Providers](../overviews/overview-data-providers.md#workflow-for-data-providers) | Organizations that collect user data and push it to DSPs. | See [Advertiser/Data Provider Integrations](../guides/summary-guides#advertiserdata-provider-integrations) | -| [Workflow for Publishers](../overviews/overview-publishers.md#workflow-for-publishers) | Organizations that propagate UID2 tokens to the bidstream via SSPs.
NOTE: Publishers can choose to integrate using Prebid, leverage the SDK for JavaScript, or complete their own server-side integration without using an SDK. | See [Publisher Integrations](../guides/summary-guides#publisher-integrations) | -| [Opt-Out Workflow](../getting-started/gs-opt-out.md#opt-out-workflow) | Consumers who engage with publishers or their SSO providers and other identity providers. | N/A | - -The following diagram summarizes all four workflows. For each workflow, the [participants](../overviews/participants-overview.md#uid2-external-participants), [components](../overviews/participants-overview.md#uid2-component-services), [UID2 identifier types](#uid2-identifier-types), and numbered steps are color-coded. - -![The UID2 Ecosystem](images/UID2Workflows.svg) diff --git a/docs/ref-info/uid-workflows.md b/docs/ref-info/uid-workflows.md new file mode 100644 index 000000000..7cf0ccf6a --- /dev/null +++ b/docs/ref-info/uid-workflows.md @@ -0,0 +1,24 @@ +--- +title: UID2 Workflows +description: A detailed summary of UID2 workflows. +hide_table_of_contents: false +sidebar_position: 01 +displayed_sidebar: docs +--- + +import Link from '@docusaurus/Link'; + +# UID2 Workflows + +The following table lists four key workflows in the UID2 framework with links to their high-level overviews. It also provides links to the respective integration guides, which include diagrams, integration steps, FAQs, and other relevant information for each workflow. + +| Workflow | Intended Primary Participants | Integration Guides | +| :--- |:--- |:--- | +| [Workflow for DSPs](../overviews/overview-dsps.md#workflow-for-dsps) (Buy-Side) | DSPs who transact on UID2 tokens in the bidstream. | See [DSP Integrations](../guides/summary-guides#dsp-integrations) | +| [Workflow for Advertisers](../overviews/overview-advertisers.md#workflow-for-advertisers) and [Workflow for Data Providers](../overviews/overview-data-providers.md#workflow-for-data-providers) | Organizations that collect user data and push it to DSPs. | See [Advertiser/Data Provider Integrations](../guides/summary-guides#advertiserdata-provider-integrations) | +| [Workflow for Publishers](../overviews/overview-publishers.md#workflow-for-publishers) | Organizations that propagate UID2 tokens to the bidstream via SSPs.
NOTE: Publishers can choose to integrate using Prebid, leverage the SDK for JavaScript, or complete their own server-side integration without using an SDK. | See [Publisher Integrations](../guides/summary-guides#publisher-integrations) | +| [Opt-Out Workflow](../getting-started/gs-opt-out.md#opt-out-workflow) | Consumers who engage with publishers or their SSO providers and other identity providers. | N/A | + +The following diagram summarizes all four workflows. For each workflow, the [external participants](../overviews/participants-overview.md#uid2-external-participants), [components](../ref-info/uid-components.md), [UID2 identifier types](../ref-info/uid-identifier-types.md), and numbered steps are color-coded. + +![The UID2 Ecosystem](images/UID2Workflows.svg) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/intro.md b/i18n/ja/docusaurus-plugin-content-docs/current/intro.md index f56cc1101..82510d020 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/intro.md @@ -46,6 +46,13 @@ UID2 フレームワークは、以下の技術原則に基づいて構築され - **Self-reliant**: UID2 は、リアルタイムビディング (RTB) データの処理において外部サービスに依存しません。 +## Elements of the UID2 Infrastructure + +- [UID2 Identifier Types](ref-info/uid-identifier-types.md) +- [UID2 Components](ref-info/uid-components.md) +- [UID2 Participants](overviews/participants-overview.md) +- [Workflows](ref-info/uid-workflows.md) + - The bidding step is shown in the following table. | Step | Endpoint/SDK | Description | diff --git a/docs/intro.md b/docs/intro.md index e7c8e92a2..78d298489 100644 --- a/docs/intro.md +++ b/docs/intro.md @@ -32,7 +32,7 @@ The UID2 framework has the following principles as its foundation: - **Consumer control**: Consumers can opt out of UID2 at any time through the [Transparency and Control Portal](https://www.transparentadvertising.com/). -### Technical Design Principles +## Technical Design Principles The UID2 framework is built on the following technical principles: @@ -48,17 +48,13 @@ The UID2 framework is built on the following technical principles: ## Elements of the UID2 Infrastructure -For information about key elements of the UID2 infrastructure, refer to the following pages: +For information about key elements of the UID2 infrastructure, and other aspects of UID2, refer to the following pages: - [UID2 Identifier Types](ref-info/uid-identifier-types.md) - [UID2 Components](ref-info/uid-components.md) - [UID2 Participants](overviews/participants-overview.md) - [Workflows](ref-info/uid-workflows.md) -## Components - -For details, see [UID2 Component Services](overviews/participants-overview.md#uid2-component-services). - ## FAQs See [Frequently Asked Questions](getting-started/gs-faqs.md). diff --git a/docs/overviews/participants-overview.md b/docs/overviews/participants-overview.md index 2a9bac85f..9c22b8528 100644 --- a/docs/overviews/participants-overview.md +++ b/docs/overviews/participants-overview.md @@ -31,14 +31,14 @@ For a diagram of how the different services work together, see [UID2 Workflows]( ## UID2 External Participants -The following table summarizes the main types of external participant partners for UID2. +The following table summarizes the main types of external participant partners for UID2, with a link to the overview page for more information on each participant type. -| Participant | Role Description | Link to Overview Page | -| :--- | :--- | :--- | -| **Publishers** | Organizations that propagate UID2 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 UID2. Independent ID providers can handle the UID2 integration on behalf of publishers. | [UID2 Overview for Publishers](overview-publishers.md) | -| **Advertisers** | Organizations that buy impressions across a range of publisher sites and use DSPs to decide which ad impressions to purchase and how much to bid on them. | [UID2 Overview for Advertisers](overview-advertisers.md) | -| **DSPs** | DSPs integrate with the UID2 system to receive UID2s from advertisers (as first-party data) and third-party data providers (as third-party data) and leverage them to inform bidding on UID2s in the bidstream. | [UID2 Overview for DSPs](overview-dsps.md) | -| **Data Providers** | Organizations that collect user data and push it to other UID2 participants—for example, advertisers, identity graph providers, and third-party data providers. | [UID2 Overview for Data Providers](overview-data-providers.md) | +| Participant Type | Role Description | +| :--- | :--- | +| [Publishers](overview-publishers.md) | Organizations that propagate UID2 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 UID2. Independent ID providers can handle the UID2 integration on behalf of publishers. | +| [Advertisers](overview-advertisers.md) | Organizations that buy impressions across a range of publisher sites and use DSPs to decide which ad impressions to purchase and how much to bid on them. | +| [DSPs](overview-dsps.md) | DSPs integrate with the UID2 system to receive UID2s from advertisers (as first-party data) and third-party data providers (as third-party data) and leverage them to inform bidding on UID2s in the bidstream. | +| [Data Providers](overview-data-providers.md) | Organizations that collect user data and push it to other UID2 participants—for example, advertisers, identity graph providers, and third-party data providers. | ## UID2 Consumers @@ -47,13 +47,3 @@ A UID2 consumer is a user who has had a UID2 token or raw UID2 created from an e UID2 leverages multiple layers of security to help protect user and other participant data. UID2 is a privacy-compliant identifier. With UID2, consumers can enjoy more personalized advertising without compromising privacy. Consumers can opt out of UID2 in the [Transparency and Control Portal](https://www.transparentadvertising.com/). - - diff --git a/docs/ref-info/uid-identifier-types.md b/docs/ref-info/uid-identifier-types.md index 1e7e91089..f1a2903c3 100644 --- a/docs/ref-info/uid-identifier-types.md +++ b/docs/ref-info/uid-identifier-types.md @@ -1,6 +1,6 @@ --- title: UID2 Identifier Types -description: Summary of xxx. +description: Information about UID2 identifier types (raw UID2s and UID2 tokens). hide_table_of_contents: false sidebar_position: 01 displayed_sidebar: docs diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-javascript-client-server.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-javascript-client-server.md index 36392b1c1..1c7f40625 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-javascript-client-server.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-javascript-client-server.md @@ -124,8 +124,6 @@ SDKは、指定された [callback function](../sdks/sdk-ref-javascript.md#callb 1. ID 情報を [ローカルストレージまたはファーストパーティクッキー](../sdks/sdk-ref-javascript.md#uid2-storage-format) に保存します。 1. ID 情報を使用して、ターゲティング広告のリクエストを始めます。 - - ビッドステップを次の表に示します。 | Step | Endpoint/SDK | Description | diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/operator-guide-aks-enclave.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/operator-guide-aks-enclave.md index 296a30dfa..147465eb6 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/operator-guide-aks-enclave.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/operator-guide-aks-enclave.md @@ -92,8 +92,6 @@ To deploy a new UID2 Private Operator for AKS, you'll need to complete the follo ### Download ZIP File and Extract Files -[**KC__GWH01 I've commented out some of what we had -- it doesn't make sense to include the table unless we add AKS to the release matrix. We need to include instructions to get the file. What I'm putting here is just a guess... please fix as needed.**] - To get set up with the installation files, follow these steps: 1. Ask your UID2 contact for the ZIP file containing the deployment files. @@ -116,8 +114,6 @@ The latest ZIP file is linked in the AKS Download column in the following table. Run the following commands to prepare environment variables that you'll use later. Choose variable names to suit your needs. -[**KC__GWH02 do we need to say where they need to run these commands? Maybe not... just checking. At the Azure command line?**] - ``` export RESOURCE_GROUP="my-vn-aks" export LOCATION="eastus" @@ -135,7 +131,7 @@ export DEPLOYMENT_ENV="integ" ### Set Up AKS and Node Pool -To set up AKS and the node pool, complete the following steps: [**KC__GWH03 do they have to be done in sequence? If so we could use numbers rather than bullets**] +To set up AKS and the node pool, complete the following steps: - [Create Resource Group](#create-resource-group) - [Create Virtual Network](#create-virtual-network) @@ -172,7 +168,7 @@ There are some limitations with regard to location: #### Create Virtual Network -To create the virtual network, run the following command, using your own values as needed: [**KC__GWH04 please verify the intro line/modify as needed**] +To create the virtual network, run the following command, using your own values as needed: ``` az network vnet create \ @@ -184,7 +180,7 @@ az network vnet create \ #### Create Subnets -To create the subnets, run the following command, using your own values as needed: [**KC__GWH05 please verify the intro line/modify as needed**] +To create the subnets, run the following command, using your own values as needed: ``` # Default Subnet (10.0.0.0/24) @@ -212,7 +208,7 @@ az network vnet subnet create \ #### Create Public IP Address -To create the public IP address, run the following command, using your own values as needed: [**KC__GWH06 please verify the intro line/modify as needed**] +To create the public IP address, run the following command, using your own values as needed: ``` az network public-ip create --name ${PUBLIC_IP_ADDRESS_NAME} --resource-group ${RESOURCE_GROUP} --sku standard --allocation static @@ -220,7 +216,7 @@ az network public-ip create --name ${PUBLIC_IP_ADDRESS_NAME} --resource-group ${ #### Create NAT Gateway -To create the [Azure Network Address Translation (NAT) gateway](https://learn.microsoft.com/en-us/azure/nat-gateway/nat-overview), run the following command, using your own values as needed: [**KC__GWH07 please verify the intro line/modify as needed**] +To create the [Azure Network Address Translation (NAT) gateway](https://learn.microsoft.com/en-us/azure/nat-gateway/nat-overview), run the following command, using your own values as needed: ``` az network nat gateway create \ @@ -232,7 +228,7 @@ az network nat gateway create \ #### Configure NAT Service for Source Subnet -To configure the NAT service, run the following command, using your own values as needed: [**KC__GWH08 please verify the intro line/modify as needed**] +To configure the NAT service, run the following command, using your own values as needed: ``` az network vnet subnet update \ @@ -244,7 +240,7 @@ az network vnet subnet update \ #### Get the AKS Subnet ID -To create the AKS subnet ID, run the following command, using your own values as needed: [**KC__GWH09 please verify the intro line/modify as needed**] +To create the AKS subnet ID, run the following command, using your own values as needed: ``` export AKS_SUBNET_ID=$(az network vnet subnet show \ @@ -257,7 +253,7 @@ export AKS_SUBNET_ID=$(az network vnet subnet show \ #### Create an AKS Service -To create the AKS service, run the following command, using your own values as needed: [**KC__GWH10 please verify the intro line/modify as needed**] +To create the AKS service, run the following command, using your own values as needed: ``` # Create the AKS cluster @@ -284,7 +280,7 @@ az aks create \ #### Get the Principal ID of the Managed Identity -To get the Principal ID, run the following command, using your own values as needed: [**KC__GWH11 please verify the intro line/modify as needed.**] +To get the Principal ID, run the following command, using your own values as needed: ``` export MANAGED_IDENTITY_PRINCIPAL_ID="$(az aks show --resource-group ${RESOURCE_GROUP} --name ${AKS_CLUSTER_NAME} --query "identityProfile.kubeletidentity.clientId" --output tsv)" @@ -294,7 +290,7 @@ For details, see [Get the principal ID of the system-assigned managed identity]( #### Create Contributor Role for the Two Resource Groups -To create the contributor role for each group, run the following commands, using your own values as needed: [**KC__GWH12 please verify the intro line/modify as needed**] +To create the contributor role for each group, run the following commands, using your own values as needed: ``` az role assignment create \ @@ -314,7 +310,7 @@ Additional reference information in external documentation: ### Set Up AKS Cluster -To set up the AKS cluster, run the following command, using your own values as needed: [**KC__GWH13 please verify the intro line/modify as needed**] +To set up the AKS cluster, run the following command, using your own values as needed: ``` az aks get-credentials --name ${AKS_CLUSTER_NAME} --resource-group ${RESOURCE_GROUP} diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/intro.md b/i18n/ja/docusaurus-plugin-content-docs/current/intro.md index 82510d020..06dc8a72f 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/intro.md @@ -16,7 +16,7 @@ UID2 は、広告エコシステム全体の多くの [参加者](overviews/part 「UID2」という用語は、フレームワークと実際の識別子のいずれかを指すことがあります。特に断りのない限り、このページでは UID2 フレームワークの概要を説明します。 ::: -### Guiding Principles +## Guiding Principles UID2 フレームワークは、以下の原則を基本としています: @@ -32,7 +32,7 @@ UID2 フレームワークは、以下の原則を基本としています: - **Consumer control**: 消費者はいつでも [Transparency and Control Portal](https://www.transparentadvertising.com/) を通じて UID2 からの脱退を選択できます。 -### Technical Design Principles +## Technical Design Principles UID2 フレームワークは、以下の技術原則に基づいて構築されています: @@ -75,10 +75,6 @@ UID2 は、メールアドレスや電話番号など、Operator Service (via the UID2 APIs). Operators periodically receive and store up-to-date encryption keys and salts from the UID2 Core Service, salt and hash directly identifying information (DII) to return raw UID2s, encrypt raw UID2s to generate UID2 tokens, and distribute UID2 token decryption keys.
Public Operators (Open Operators) run public instances of the Operator Service. For example, The Trade Desk currently serves as a Public Operator for the UID2 framework, available to all participants. If other Public Operators are available, a participant can choose which operator to work with.
Any participant can also choose to become a Private Operator to generate and manage UID2s. | -| **DSPs** | DSPs integrate with the UID2 system to receive UID2s from advertisers (as first-party data) and third-party data providers (as third-party data) and leverage them to inform bidding on UID2s in the bidstream. | -| **Data Providers** | Organizations that collect user data and push it to other UID2 participants—for example, advertisers, identity graph providers, and third-party data providers. | -| **Advertisers** | Organizations that buy impressions across a range of publisher sites and use DSPs to decide which ad impressions to purchase and how much to bid on them. | -| **Publishers** | Organizations that propagate UID2 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 UID2. Independent ID providers can handle the UID2 integration on behalf of publishers. | -| **Consumers** | Users who have had a UID2 token or raw UID2 created from their email address or phone number. Consumers can opt out of UID2 in the [Transparency and Control Portal](https://www.transparentadvertising.com/). | --> diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-identifier-types.md b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-identifier-types.md index 1e7e91089..f1a2903c3 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-identifier-types.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-identifier-types.md @@ -1,6 +1,6 @@ --- title: UID2 Identifier Types -description: Summary of xxx. +description: Information about UID2 identifier types (raw UID2s and UID2 tokens). hide_table_of_contents: false sidebar_position: 01 displayed_sidebar: docs