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/guides/integration-javascript-client-server.md b/docs/guides/integration-javascript-client-server.md index 92a16e629..cf7e0387a 100644 --- a/docs/guides/integration-javascript-client-server.md +++ b/docs/guides/integration-javascript-client-server.md @@ -124,8 +124,6 @@ Based on the status and availability of a valid identity, the SDK does the follo 1. Stores identity information in [local storage or a first-party cookie](../sdks/sdk-ref-javascript.md#uid2-storage-format). 1. Uses the identity information to initiate requests for targeted advertising. - - The bidding step is shown in the following table. | Step | Endpoint/SDK | Description | diff --git a/docs/guides/mobile-plugin-gma-ios.md b/docs/guides/mobile-plugin-gma-ios.md index d962863f2..6386bd81f 100644 --- a/docs/guides/mobile-plugin-gma-ios.md +++ b/docs/guides/mobile-plugin-gma-ios.md @@ -34,6 +34,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, Client-Server, or Server-Side Integration?](integration-mobile-overview#client-side-client-server-or-server-side-integration) + ## Requirements To run this plugin, install the following: diff --git a/docs/intro.md b/docs/intro.md index e504519e7..78d298489 100644 --- a/docs/intro.md +++ b/docs/intro.md @@ -10,21 +10,21 @@ 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. ::: -### 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. +- **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 [components](#components) is publicly available. +- **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. @@ -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: @@ -42,73 +42,18 @@ The UID2 framework is built on the following technical principles: - **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. +- **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 -The following sections explain and illustrate the key elements of the UID2 framework infrastructure: +For information about key elements of the UID2 infrastructure, and other aspects of UID2, refer to the following pages: -- [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) +- [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) ## 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 new file mode 100644 index 000000000..9c22b8528 --- /dev/null +++ b/docs/overviews/participants-overview.md @@ -0,0 +1,49 @@ +--- +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-workflows.md). 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-workflows.md). + +| 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, with a link to the overview page for more information on each participant type. + +| 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 + +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/glossary-uid.md b/docs/ref-info/glossary-uid.md index e3ebcea19..ef708a91b 100644 --- a/docs/ref-info/glossary-uid.md +++ b/docs/ref-info/glossary-uid.md @@ -137,7 +137,7 @@ import Link from '@docusaurus/Link';
API key
-
Each UID2 participant using a server-side implementation has an API key (client key) and also a secret value associated with the key, called the client secret (API secret). The client secret is known only to the participant and the UID2 service.
+
Each UID2 participant using a server-side implementation has an API key (client key) and also a secret value associated with the key, called the client secret (API secret). The client secret is known only to the participant and the UID2 service.
For details, see UID2 Credentials.
API secret
@@ -177,7 +177,7 @@ import Link from '@docusaurus/Link';
For details, see Subscription ID and Public Key.
Client secret
-
Each UID2 participant using a server-side implementation has an API key (client key) and also a secret value associated with the key, called the client secret (API secret). The client secret is known only to the participant and the UID2 service.
+
Each UID2 participant using a server-side implementation has an API key (client key) and also a secret value associated with the key, called the client secret (API secret). The client secret is known only to the participant and the UID2 service.
For details, see UID2 Credentials.
Client-server integration
@@ -210,7 +210,7 @@ import Link from '@docusaurus/Link';
Core Service
The UID2 Core Service is a centralized service that manages access to secret salts, encryption keys, and other relevant data in the UID2 ecosystem.
-
For an overview of all the UID2 services, see Components.
+
For an overview of all the UID2 services, see UID2 Component Services.
@@ -220,7 +220,7 @@ import Link from '@docusaurus/Link';
Data provider
In the context of UID2, a data provider is any entity that provides data and measurement services relating to advertising, such as a data partner, measurement partner, or offline measurement provider.
-
For details, see participant (Data Providers).
+
For details, see participant (Data Providers).
Demand-side platform
A demand-side platform (DSP) provides services to companies that want to buy digital advertising, such as advertisers, brands, and media agencies.
@@ -346,7 +346,7 @@ import Link from '@docusaurus/Link';
An Operator is an organization or entity that runs the UID2 Operator Service. The UID2 Operator is the API server in the UID2 ecosystem.
Operators perform multiple functions, such as receiving encryption keys and secret salts from the UID2 Core Service, salting and hashing personal data (DII) to return raw UID2s, and encrypting raw UID2s to generate UID2 tokens.
A participant can also choose to become a Private Operator to access UID2 APIs and to generate raw UID2s and UID2 tokens from within a private infrastructure.
-
For details, see participants and The UID2 Operator.
+
For details, see participants and The UID2 Operator.
Operator key
Each UID2 Private Operator has an operator key that allows the Private Operator Service to connect to the Core Service and Opt-Out Service and call some endpoints on it.
@@ -354,7 +354,7 @@ import Link from '@docusaurus/Link';
Operator Service
A service that enables all functions of the Operator.
-
For an overview of all the UID2 services, see Components.
+
For an overview of all the UID2 services, see UID2 Component Services.
Opt-out
An end user who participates in the UID2 ecosystem can opt out at any time by going to the Transparency and Control Portal.
@@ -362,7 +362,7 @@ import Link from '@docusaurus/Link';
Opt-Out Service
The Opt-Out Service is a global UID2 service that manages and stores user opt-out requests.
-
For an overview of all the UID2 services, see Components.
+
For an overview of all the UID2 services, see UID2 Component Services.
@@ -372,7 +372,7 @@ import Link from '@docusaurus/Link';
Participant
An entity that fulfils a key role in UID2. Participants include the following: Core Administrator, Operator, DSP, data provider, advertiser, publisher, consumer.
-
For details, see participants.
+
For details, see participants.
Private Operator
A Private Operator is an entity that runs a private instance of the Operator Service. The Private Operator generates and manages UID2s for itself, using its own resources (such as hardware) in a secure environment.
@@ -397,7 +397,7 @@ import Link from '@docusaurus/Link';
Raw UID2
An unencrypted alphanumeric identifier created through the UID2 APIs or SDKs with the user's directly identifying information (email address or phone number) as input. The raw UID2 is encrypted to create a UID2 token. The raw UID2 is a unique value; no two raw UID2s are the same. Raw UID2s, and their associated UID2 tokens, are case sensitive.
-
For details, see UID2 Identifier Types.
+
For details, see UID2 Identifier Types.
Refresh token
A refresh token is an opaque string that is issued along with the UID2 token. It is used to refresh the UID2 token, which has a limited life.
@@ -493,13 +493,13 @@ import Link from '@docusaurus/Link';
There are many similarities between UID2 and EUID, but they are completely separate, and their tokens are not interchangeable.
UID2 framework
-
The Unified ID 2.0 (UID2) framework enables deterministic identity for advertising opportunities on the open internet for many participants across the advertising ecosystem. It 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.
+
The Unified ID 2.0 (UID2) framework enables deterministic identity for advertising opportunities on the open internet for many participants across the advertising ecosystem. It 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 operates in North America, parts of Asia, and some other regions.
There are many similarities between UID2 and EUID, but they are completely separate, and their tokens are not interchangeable.
UID2 identifier
There are two Unified ID 2.0 (UID2) identifier types: raw UID2s and UID2 tokens (also known as advertising tokens).
-
For details, see UID2 Identifier Types.
+
For details, see UID2 Identifier Types.
UID2 Portal
The UID2 Portal is a separate user interface that allows UID2 participants to manage their accounts.
@@ -515,7 +515,7 @@ import Link from '@docusaurus/Link';
The token value is opaque: No assumptions should be made about the format or about the length of the string.
The token has a limited life, but can be refreshed in the background using the refresh token.
Publishers send UID2 tokens in the bidstream.
-
For details, see UID2 Identifier Types, UID2 Tokens: Key Information, and How the UID2 Token Is Created.
+
For details, see UID2 Identifier Types, UID2 Tokens: Key Information, and How the UID2 Token Is Created.
Unified ID 2.0
The term UID2 can be used to mean the UID2 framework, the UID2 service, a raw UID2, or a UID2 token (advertising token).
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/ref-how-uid-is-created.md b/docs/ref-info/ref-how-uid-is-created.md index c3c5e58fb..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](../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 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..f1a2903c3 --- /dev/null +++ b/docs/ref-info/uid-identifier-types.md @@ -0,0 +1,22 @@ +--- +title: UID2 Identifier Types +description: Information about UID2 identifier types (raw UID2s and UID2 tokens). +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-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/docs/ref-info/updates-doc.md b/docs/ref-info/updates-doc.md index 7483e6884..764812592 100644 --- a/docs/ref-info/updates-doc.md +++ b/docs/ref-info/updates-doc.md @@ -416,7 +416,7 @@ For details, see [Encryption and Decryption Code Examples](../getting-started/gs November 30, 2023 -A UID2 participant who wants to be a [Private Operator](../ref-info/glossary-uid.md#gl-private-operator) can now set up the UID2 Operator Service in an instance of [Confidential Containers](https://learn.microsoft.com/en-us/azure/confidential-computing/confidential-containers), a confidential computing option from Microsoft Azure. +A UID2 participant who wants to be a [Private Operator](../ref-info/glossary-uid.md#gl-private-operator) can now set up the UID2 Operator Service in an instance of [Confidential Containers](https://learn.microsoft.com/en-us/azure/confidential-computing/confidential-containers), a confidential computing option from Microsoft Azure. For details, see [UID2 Private Operator for Azure Integration Guide](../guides/operator-guide-azure-enclave.md). diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-credentials.md b/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-credentials.md index 0198548f4..d7f2abcb0 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-credentials.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-credentials.md @@ -9,7 +9,7 @@ import Link from '@docusaurus/Link'; # UID2 Credentials -UID2 の 参加者は、UID2 にどのように参加しているかによって、少なくとも 1 つの固有の認証情報のセットが必要です。必要な認証情報のセットは、次の表に示すように、UID2 にどのように参加しているかによって異なります。 +UID2 の 参加者は、UID2 にどのように参加しているかによって、少なくとも 1 つの固有の認証情報のセットが必要です。必要な認証情報のセットは、次の表に示すように、UID2 にどのように参加しているかによって異なります。 | Audience | Credentials | Integration | | :--- | :--- | :--- | diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-opt-out.md b/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-opt-out.md index 073173a6b..06138bbb3 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-opt-out.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-opt-out.md @@ -9,7 +9,7 @@ import Link from '@docusaurus/Link'; # User Opt-Out -さまざまなパブリッシャーや広告主が UID2 を使用しています。しかし、UID2 全体としては、すべての UID2 [参加者](../ref-info/glossary-uid.md#gl-participant) が受け入れるべき、具体的なオプトアウトプロセスがあります。 +さまざまなパブリッシャーや広告主が UID2 を使用しています。しかし、UID2 全体としては、すべての UID2 [参加者](overviews/participants-overview.md#uid2-external-participants) が受け入れるべき、具体的なオプトアウトプロセスがあります。 ## How Users Can Opt Out of UID2 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 2f57ffe6c..06dc8a72f 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/intro.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/intro.md @@ -10,21 +10,21 @@ import Link from '@docusaurus/Link'; # Unified ID 2.0 Overview -UID2 は、広告エコシステム全体の多くの [参加者](#participants) がオープンインターネット上で広告機会を得るための決定論的な ID を可能にするフレームワークです。UID2 フレームワークにより、パブリッシャーのウェブサイト、モバイルアプリ、Connected TV (CTV)アプリからのログイン体験が、プログラマティックワークフローを通じて収益化できるようになります。独自の名前空間を持つオープンソースのスタンドアローンソリューションとして構築されたこのフレームワークは、ローカル市場の要件に合わせて設計された透明性とプライバシー制御をユーザーに提供します。 +UID2 は、広告エコシステム全体の多くの [参加者](overviews/participants-overview.md#uid2-external-participants) がオープンインターネット上で広告機会を得るための決定論的な ID を可能にするフレームワークです。UID2 フレームワークにより、パブリッシャーのウェブサイト、モバイルアプリ、Connected TV (CTV)アプリからのログイン体験が、プログラマティックワークフローを通じて収益化できるようになります。独自の名前空間を持つオープンソースのスタンドアローンソリューションとして構築されたこのフレームワークは、ローカル市場の要件に合わせて設計された透明性とプライバシー制御をユーザーに提供します。 :::note 「UID2」という用語は、フレームワークと実際の識別子のいずれかを指すことがあります。特に断りのない限り、このページでは UID2 フレームワークの概要を説明します。 ::: -### Guiding Principles +## Guiding Principles UID2 フレームワークは、以下の原則を基本としています: - **First-party relationships**: UID2 により、広告主はオープンインターネット上のパブリッシャーウェブサイトでファーストパーティデータを有効にできます。 -- **Non-proprietary (universal) standard**: 適切な参加契約を締結した広告エコシステムのすべての [参加者](#participants) が UID2 にアクセスできます。 +- **Non-proprietary (universal) standard**: 適切な参加契約を締結した広告エコシステムのすべての [参加者](overviews/participants-overview.md#uid2-external-participants) が UID2 にアクセスできます。 -- **Open source**: UID2 の[コンポーネント](#components) のソースコードは一般に公開されています。 +- **Open source**: [UID2 Component Services](overviews/participants-overview.md#uid2-component-services) のソースコードは一般に公開されています。 - **Interoperable**: このフレームワークにより、他の ID ソリューション (商用およびプロプライエタリ) が UID2 Token をインテグレーションし、提供できるようになります。 @@ -32,7 +32,7 @@ UID2 フレームワークは、以下の原則を基本としています: - **Consumer control**: 消費者はいつでも [Transparency and Control Portal](https://www.transparentadvertising.com/) を通じて UID2 からの脱退を選択できます。 -### Technical Design Principles +## Technical Design Principles UID2 フレームワークは、以下の技術原則に基づいて構築されています: @@ -42,20 +42,27 @@ UID2 フレームワークは、以下の技術原則に基づいて構築され - **Lean infrastructure**: UID2 システムは軽量で安価に運用できます。 -- **Internet scale**: UID2 インフラは、継続的に増加する[参加者](#participants) のニーズに対応し、特定の地域の性能要求に応えるために拡張できます。 +- **Internet scale**: UID2 インフラは、継続的に増加する[参加者](overviews/participants-overview.md#uid2-external-participants) のニーズに対応し、特定の地域の性能要求に応えるために拡張できます。 - **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) + + -### UID2 Identifier Types + -### 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..9c22b8528 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/overviews/participants-overview.md @@ -0,0 +1,49 @@ +--- +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-workflows.md). 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-workflows.md). + +| 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, with a link to the overview page for more information on each participant type. + +| 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 + +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 a5ebe4d1d..66a0b9d65 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 @@ -137,7 +137,7 @@ import Link from '@docusaurus/Link';
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
@@ -177,7 +177,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
@@ -210,7 +210,7 @@ import Link from '@docusaurus/Link';
Core Service
UID2 Core Serviceは、UID2 エコシステムの 秘密の ソルト、暗号化キー、その他の関連データへのアクセスを管理する一元的なサービスです。
-
すべてのUID2 Service の概要については、Components を参照してください。
+
すべてのUID2 Service の概要については、UID2 Component Services を参照してください。
@@ -220,7 +220,7 @@ import Link from '@docusaurus/Link';
Data provider
UID2 のコンテキストでは、データプロバイダーは、データパートナー、測定パートナー、オフライン測定プロバイダーなど、広告に関連するデータおよび測定サービスを提供する事業社を指します。
-
詳細は participant (Data Providers) を参照してください。
+
詳細は participant (Data Providers) を参照してください。
Demand-side platform (DSP)
デマンドサイドプラットフォーム (DSP)は、広告主、ブランド、メディアエージェンシーなど、デジタル広告を購入したい企業にサービスを提供するプラットフォームです。
@@ -346,7 +346,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 を持っています。
@@ -354,7 +354,7 @@ import Link from '@docusaurus/Link';
Operator Service
Operator のすべての機能を可能にするサービスです
-
すべての UID2 Service の概要については、Components を参照してください。
+
すべての UID2 Service の概要については、UID2 Component Services を参照してください。
Opt-Out
UID2 エコシステムに参加しているエンドユーザーは、Transparency and Control Portal にアクセスすることで、いつでもオプトアウトすることができます。
@@ -362,7 +362,7 @@ import Link from '@docusaurus/Link';
Opt-Out Service
Opt-Out Service は、ユーザーのオプトアウト要求を管理・保存するグローバルな UID2 Service です。
-
すべての UID2 Service の概要については、Components を参照してください。
+
すべての UID2 Service の概要については、UID2 Component Services を参照してください。
@@ -372,7 +372,7 @@ import Link from '@docusaurus/Link';
Participant
UID2 において重要な役割を果たすエンティティです。参加者には以下が含まれます: Core Administrator、Operator、DSP、データプロバイダー、広告主、パブリッシャー、消費者。
-
詳細は、参加者 を参照してください。
+
詳細は、参加者 を参照してください。
Private Operator
Private operator は、Operator Service のプライベートインスタンスを実行する事業社です。Private Operator は、安全な環境で独自のリソース (ハードウェアなど) を使用して、自身のために UID2 を生成および管理します。
@@ -397,7 +397,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 の有効期限を更新するために使用されます。
@@ -493,13 +493,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 参加者が自分のアカウントを管理するための独立したユーザーインターフェースです。
@@ -515,7 +515,7 @@ import Link from '@docusaurus/Link';
トークンの値は不透明です。文字列のフォーマットや長さについて、推測してはなりません。
トークンの寿命は限られていますが、refresh token を使ってバックグラウンドでリフレッシュすることができます。
パブリッシャーは、ビッドストリームに UID2 Token を送信します。
-
詳細は UID2 Identifier Types、 UID2 Tokens: Key Information と How the UID2 Token Is Created を参照してください。
+
詳細は UID2 Identifier Types、 UID2 Tokens: Key Information と How the UID2 Token Is Created を参照してください。
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 a85060b0e..37fef35ec 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 @@ import Link from '@docusaurus/Link'; パブリッシャーによってはいくつかの事前作業が行われますが、ほとんどの処理ステップは UID2 Operator によって行われます。 パブリッシャーの手順を正しい順序で実行することが非常に重要です: -- 手順が順番に実行された場合、その結果の値は、同じ個人のオンラインアクティビティから生成された他の [UID2 identifiers](../intro.md#uid2-identifier-types) と関連付けられることが認識されます: 基礎となる [raw UID2](../ref-info/glossary-uid.md#gl-raw-uid2) は、同じ DII から生成された他の UID2 参加者による raw UID2 と一致し、したがってそのトークンはターゲティング広告に適しています。 +- 手順が順番に実行された場合、その結果の値は、同じ個人のオンラインアクティビティから生成された他の [UID2 identifier types](uid-identifier-types.md) と関連付けられることが認識されます: 基礎となる [raw UID2](../ref-info/glossary-uid.md#gl-raw-uid2) は、同じ DII から生成された他の UID2 参加者による raw UID2 と一致し、したがってそのトークンはターゲティング広告に適しています。 - 順序を間違えると、その結果の値は、同じ個人のオンラインアクティビティから生成された他の UID2 identifiers と関連付けられることができません。そのため、そのトークンはターゲティング広告に適していません。 概要については、[Steps to Create a UID2 Token](#steps-to-create-a-uid2-token) を参照してください。図形式の例については、[Creating a UID2 Token—Example](#creating-a-uid2-tokenexample) を参照してください。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-components.md b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-components.md new file mode 100644 index 000000000..5539c73d9 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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/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 new file mode 100644 index 000000000..f1a2903c3 --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-identifier-types.md @@ -0,0 +1,22 @@ +--- +title: UID2 Identifier Types +description: Information about UID2 identifier types (raw UID2s and UID2 tokens). +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/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-workflows.md b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/uid-workflows.md new file mode 100644 index 000000000..7cf0ccf6a --- /dev/null +++ b/i18n/ja/docusaurus-plugin-content-docs/current/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/ref-info/updates-doc.md b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/updates-doc.md index 1ec628466..82d760ba9 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 @@ -396,7 +396,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 43fc3c67a..15390826b 100644 --- a/sidebars.js +++ b/sidebars.js @@ -20,13 +20,27 @@ function removeItems(sidebar, ...remove) { const fullSidebar = [ - 'intro', + { + type: 'category', + label: 'Overview', + link: { + type: 'doc', + id: 'intro', + }, + collapsed: false, + items: [ + 'ref-info/uid-identifier-types', + 'ref-info/uid-components', + 'ref-info/uid-workflows', + ], + }, { type: 'category', label: 'UID2 Participants', link: { - type: 'generated-index', + type: 'doc', + id: 'overviews/participants-overview', }, collapsed: true, items: [