From ad317abab22684bbcc65cdea0e9cfa2ee569a0db Mon Sep 17 00:00:00 2001 From: genwhittTTD Date: Thu, 19 Dec 2024 18:11:03 -0500 Subject: [PATCH] mods --- ...ation-advertiser-dataprovider-endpoints.md | 10 +- .../integration-advertiser-dataprovider.md | 113 ------------------ .../integration-aws-entity-resolution.md | 2 +- docs/guides/snowflake_integration.md | 2 +- ...ation-advertiser-dataprovider-endpoints.md | 8 +- ...ration-advertiser-dataprovider-overview.md | 26 ++-- .../integration-advertiser-dataprovider.md | 111 ----------------- sidebars.js | 7 +- 8 files changed, 29 insertions(+), 250 deletions(-) delete mode 100644 docs/guides/integration-advertiser-dataprovider.md delete mode 100644 i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-advertiser-dataprovider.md diff --git a/docs/guides/integration-advertiser-dataprovider-endpoints.md b/docs/guides/integration-advertiser-dataprovider-endpoints.md index 0c3207c84..dbc277e7f 100644 --- a/docs/guides/integration-advertiser-dataprovider-endpoints.md +++ b/docs/guides/integration-advertiser-dataprovider-endpoints.md @@ -1,7 +1,7 @@ --- -title: Advertiser/Data Provider Integration by Calling to HTTP Endpoints +title: Advertiser/Data Provider Integration Directly to HTTP Endpoints sidebar_label: HTTP Endpoints -description: Integration for organizations that collect user data and push it to other participants. +description: Integration for organizations that collect user data and push it to other participants, coding to HTTP endpoints rather than an SDK or Snowflake. hide_table_of_contents: false sidebar_position: 07 displayed_sidebar: sidebarAdvertisers @@ -9,12 +9,12 @@ displayed_sidebar: sidebarAdvertisers import Link from '@docusaurus/Link'; -# Advertiser/Data Provider Integration By Calling HTTP Endpoints +# Advertiser/Data Provider Integration Directly to HTTP Endpoints -This guide covers integration steps for advertisers and data providers to integration by writing code to call UID2 HTTP endpoints, rather than using another implementation options such as an SDK, Snowflake, or AWS Entity Resolution. +This guide covers integration steps for advertisers and data providers to integrate with UID2 by writing code to call UID2 HTTP endpoints, rather than using another implementation options such as an SDK, Snowflake, or AWS Entity Resolution. :::tip -For a summary of UID2 integration options and steps for advertisers and data providers, see [Advertiser/Data Provider Integration Overview](integration-advertiser-dataprovider-overview.md). +For a summary of all integration options and steps for advertisers and data providers, see [Advertiser/Data Provider Integration Overview](integration-advertiser-dataprovider-overview.md). ::: ### High-Level Steps diff --git a/docs/guides/integration-advertiser-dataprovider.md b/docs/guides/integration-advertiser-dataprovider.md deleted file mode 100644 index 20cceec98..000000000 --- a/docs/guides/integration-advertiser-dataprovider.md +++ /dev/null @@ -1,113 +0,0 @@ ---- -title: Advertiser/Data Provider Integration -sidebar_label: Advertiser/Data Provider Integration Guide -description: Integration for organizations that collect user data and push it to other participants. -hide_table_of_contents: false -sidebar_position: 07 -displayed_sidebar: sidebarAdvertisers ---- - -import Link from '@docusaurus/Link'; - -# Advertiser/Data Provider Integration Guide - -This guide covers integration steps for organizations that collect user data and push it to other UID2 participants. Data collectors include advertisers, data on-boarders, measurement providers, identity graph providers, third-party data providers, and any other organizations that send data to other participants. - -If you are using a Public Operator service hosted in the Snowflake Data Marketplace, see also [Snowflake Integration Guide](snowflake_integration.md). - -## Advertiser/Data Provider Routes to Use UID2 - -Within the ad tech industry, advertisers use identity to build audiences, track conversions, and generate their graphs. The following table shows some examples of how you, as an advertiser or as a data provider acting on behalf of an advertiser, can accomplish some of these goals with UID2. - -:::note -There are other ways that you can use UID2, outside these use cases. These are just some examples. -::: - -| Send/Receive? | Action | Advantage/Result | -| --- | --- | --- | -| Send | Send UID2s via API or pixels | Create audiences. | -| Send | Send UID2s as conversion information | Use conversion information for measurement (attribution) or for retargeting via API or pixels. | -| Receive | Receive UID2s from graph/data providers via API or pixels | Build graph data. | - - - -### High-Level Steps - -At a high level, the steps for advertisers and data providers integrating with UID2 are as follows: - -1. Generate a raw UID2 from directly identifying information (DII), or receive UID2s from another UID2 participant such as a data provider acting on your behalf. - -1. Use the UID2s you received in Step 1. For example, you might do one or more of the following: - - Do some manipulation: for example, combine UID2s you generated from DII and UID2s received from another participant such as an advertiser or data provider. - - Add new UID2s into an existing audience. - -1. Use the raw UID2s for some purpose such as measurement. - -## Integration Diagram - -The following diagram outlines the steps that data collectors must complete to map DII to raw UID2s for audience building and targeting. - -DII refers to a user's normalized email address or phone number, or the normalized and SHA-256-hashed email address or phone number. - -![Advertiser Flow](images/advertiser-flow-mermaid.png) - - - -Refer to the following sections for details about the different parts of the diagram: -1. [Retrieve a raw UID2 for DII](#1-retrieve-a-raw-uid2-for-dii) -2. [Send stored raw UID2s to DSPs to create audiences or conversions](#2-send-stored-raw-uid2s-to-dsps-to-create-audiences-or-conversions) -3. [Monitor for salt bucket rotations related to your stored raw UID2s](#3-monitor-for-salt-bucket-rotations-related-to-your-stored-raw-uid2s) - -### 1: Retrieve a raw UID2 for DII - -| Step | Endpoint | Description | -| --- | --- | --- | -| 1-a | [POST /identity/map](../endpoints/post-identity-map.md) request | Send a request containing DII to the identity mapping endpoint. | -| 1-b | [POST /identity/map](../endpoints/post-identity-map.md) response | The `advertising_id` (raw UID2) returned in the response can be used to target audiences on relevant DSPs.
The response returns a user's raw UID2 and the corresponding `bucket_id` for the salt bucket. The salt assigned to the bucket rotates annually, which impacts the generated raw UID2. For details on how to check for salt bucket rotation, see [3: Monitor for salt bucket rotations](#3-monitor-for-salt-bucket-rotations-related-to-your-stored-raw-uid2s).
For ease of maintenance, a recommended approach is to store a user's raw UID2 and `bucket_id` in a mapping table. For guidance on incremental updates, see [Use an incremental process to continuously update raw UID2s](#use-an-incremental-process-to-continuously-update-raw-uid2s). | - -### 2: Send stored raw UID2s to DSPs to create audiences or conversions - -Send the `advertising_id` (raw UID2) returned in Step 1-b to a DSP while building your audiences. Each DSP has a unique integration process for building audiences; follow the integration guidance provided by the DSP for sending raw UID2s to build an audience. - -### 3: Monitor for salt bucket rotations related to your stored raw UID2s -A raw UID2 is an identifier for a user at a specific moment in time. The raw UID2 for a specific user changes at least once per year, as a result of the salt rotation. - -Even though each salt bucket is updated approximately once per year, individual bucket updates are spread over the year. Approximately 1/365th of all salt buckets are rotated daily. - -:::important -To ensure that your integration has the current raw UID2s, check salt bucket rotation for active users every day. -::: - -| Step | Endpoint | Description | -| --- | --- | --- | -| 3-a | [POST /identity/buckets](../endpoints/post-identity-buckets.md) | Send a request to the bucket status endpoint for all salt buckets that have changed since a specific timestamp. | -| 3-b | [POST /identity/buckets](../endpoints/post-identity-buckets.md) | UID2 service: The bucket status endpoint returns a list of `bucket_id` and `last_updated` timestamps. | -| 3-c | [POST /identity/map](../endpoints/post-identity-map.md) | Compare the returned `bucket_id` to the salt buckets of raw UID2s that you've cached.
If you find that the salt bucket was updated for one or more raw UID2s, re-send the DII to the identity mapping service for a new raw UID2. | -| 3-d | [POST /identity/map](../endpoints/post-identity-map.md) | Store the new values returned for `advertising_id` and `bucket_id`. | - -## Use an Incremental Process to Continuously Update Raw UID2s - -To keep your UID2-based audience information accurate and up to date, follow these integration steps every day: - -1. The response from the [UID2 retrieval step](#1-retrieve-a-raw-uid2-for-dii) contains mapping information. Cache the following: - - The mapping between DII (`identifier`), raw UID2 (`advertising_id`), and salt bucket (`bucket_id`). - - The most recent `last_updated` timestamp. -2. Using the results from Step 3, [Monitor for salt bucket rotations related to your stored raw UID2s](#3-monitor-for-salt-bucket-rotations-related-to-your-stored-raw-uid2s), remap any raw UID2 for which the salt buckets have been rotated by retrieving new raw UID2 for those IDs, following Step 1, [Retrieve a raw UID2 for DII](#1-retrieve-a-raw-uid2-for-dii). - - Then, use the refreshed UID2s to update audiences or conversions, following Step 2, [send raw UID2 to a DSP](#2-send-stored-raw-uid2s-to-dsps-to-create-audiences-or-conversions). - -## Check Opt-Out Status - -It's important to honor user opt-out status. Here are two ways you can check that you have the latest opt-out information: - -- The UID2 Operator Service distributes opt-out information to advertisers and data providers via the [POST /identity/map](../endpoints/post-identity-map.md) endpoint. - -- Advertisers and data providers can check the opt-out status of raw UID2s using the [POST /optout/status](../endpoints/post-optout-status.md) endpoint. - -For details about the UID2 opt-out workflow and how users can opt out, see [User Opt-Out](../getting-started/gs-opt-out.md). - -## FAQs - -For a list of frequently asked questions for advertisers and data providers using the UID2 framework, see [FAQs for Advertisers and Data Providers](../getting-started/gs-faqs.md#faqs-for-advertisers-and-data-providers). diff --git a/docs/guides/integration-aws-entity-resolution.md b/docs/guides/integration-aws-entity-resolution.md index 15595a772..c70622d9f 100644 --- a/docs/guides/integration-aws-entity-resolution.md +++ b/docs/guides/integration-aws-entity-resolution.md @@ -22,7 +22,7 @@ If you're not currently part of the UID2 ecosystem, go to the [Request Access to For a video presentation about integration with UID2 by using AWS Entity Resolution, and a demo, see [Getting Started with AWS Entity Resolution Integration with Unified ID 2.0](https://www.youtube.com/watch?v=ORbSsKMgVj8) on YouTube. :::tip -For a summary of UID2 integration options and steps for advertisers and data providers, see [Advertiser/Data Provider Integration Overview](integration-advertiser-dataprovider-overview.md). +For a summary of all integration options and steps for advertisers and data providers, see [Advertiser/Data Provider Integration Overview](integration-advertiser-dataprovider-overview.md). ::: ## Functionality diff --git a/docs/guides/snowflake_integration.md b/docs/guides/snowflake_integration.md index c287898dd..b842b42d6 100644 --- a/docs/guides/snowflake_integration.md +++ b/docs/guides/snowflake_integration.md @@ -18,7 +18,7 @@ The following listings for UID2 are available on the Snowflake marketplace: - For data providers: [Unified ID 2.0: Data Provider Identity Solution](https://app.snowflake.com/marketplace/listing/GZT0ZRYXTN0/unified-id-2-0-unified-id-2-0-data-provider-identity-solution?originTab=provider&providerName=Unified+ID+2.0) :::tip -For a summary of UID2 integration options and steps for advertisers and data providers, see [Advertiser/Data Provider Integration Overview](integration-advertiser-dataprovider-overview.md). +For a summary of all integration options and steps for advertisers and data providers, see [Advertiser/Data Provider Integration Overview](integration-advertiser-dataprovider-overview.md). ::: ## Functionality diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-advertiser-dataprovider-endpoints.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-advertiser-dataprovider-endpoints.md index 0c3207c84..2ec6a76fa 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-advertiser-dataprovider-endpoints.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-advertiser-dataprovider-endpoints.md @@ -1,7 +1,7 @@ --- -title: Advertiser/Data Provider Integration by Calling to HTTP Endpoints +title: Advertiser/Data Provider Integration Directly to HTTP Endpoints sidebar_label: HTTP Endpoints -description: Integration for organizations that collect user data and push it to other participants. +description: Integration for organizations that collect user data and push it to other participants, coding to HTTP endpoints rather than an SDK or Snowflake. hide_table_of_contents: false sidebar_position: 07 displayed_sidebar: sidebarAdvertisers @@ -9,12 +9,12 @@ displayed_sidebar: sidebarAdvertisers import Link from '@docusaurus/Link'; -# Advertiser/Data Provider Integration By Calling HTTP Endpoints +# Advertiser/Data Provider Integration Directly to HTTP Endpoints This guide covers integration steps for advertisers and data providers to integration by writing code to call UID2 HTTP endpoints, rather than using another implementation options such as an SDK, Snowflake, or AWS Entity Resolution. :::tip -For a summary of UID2 integration options and steps for advertisers and data providers, see [Advertiser/Data Provider Integration Overview](integration-advertiser-dataprovider-overview.md). +For a summary of all integration options and steps for advertisers and data providers, see [Advertiser/Data Provider Integration Overview](integration-advertiser-dataprovider-overview.md). ::: ### High-Level Steps diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-advertiser-dataprovider-overview.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-advertiser-dataprovider-overview.md index 01fa68d89..d20e72dd3 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-advertiser-dataprovider-overview.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-advertiser-dataprovider-overview.md @@ -31,6 +31,19 @@ There are other ways that you can use UID2, outside these use cases. These are j - **Send in conversions**: You can send UID2s as conversion information that can be used for measurement (attribution) or retargeting via API or pixels - **Receive graph data**: You can receive UID2s from graph/data providers via API or pixels. --> +## Summary of Implementation Options + +The following table shows the implementation options that are available for advertisers and data providers, for each of the high-level steps. Some steps are managed solely as part of your own custom implementation; some steps can be managed by one or more of the UID2 implementation options available. Click through on each option for applicable documentation. + +| High-Level Step | Implementation Options | +| --- | --- | +| 1. Generate a raw UID2 | Any of the following options: | +| 2. Manipulate or combine raw UID2s | Custom (your choice) | +| 3. Use the raw UID2s | Custom (your choice) | +| 4. Store raw UID2s and salt bucket IDs | Custom (your choice) | +| 5. Monitor for salt bucket rotation | Any of the following options: | +| 6. Monitor for opt-out status | API call to the [POST /optout/status](../endpoints/post-optout-status.md) endpoint: see [Check Opt-Out Status](#check-opt-out-status) | + ## High-Level Steps At a high level, the steps for advertisers and data providers integrating with UID2 are as follows: @@ -52,19 +65,6 @@ At a high level, the steps for advertisers and data providers integrating with U 6. Periodically, monitor for opt-out status, to be sure that you don't continue using UID2s for users that have recently opted out. For details, see [Check Opt-Out Status](#check-opt-out-status). -## Summary of Implementation Options - -The following table shows the implementation options that are available for advertisers and data providers, for each of the high-level steps. Some steps are managed solely as part of your own custom implementation; some steps can be managed by one or more of the UID2 implementation options available. Click through on each option for applicable documentation. - -| High-Level Step | Implementation Options | -| --- | --- | -| 1. Generate a raw UID2 | Any of the following options: | -| 2. Manipulate or combine raw UID2s | Custom (your choice) | -| 3. Use the raw UID2s | Custom (your choice) | -| 4. Store raw UID2s and salt bucket IDs | Custom (your choice) | -| 5. Monitor for salt bucket rotation | Any of the following options: | -| 6. Monitor for opt-out status | API call to the [POST /optout/status](../endpoints/post-optout-status.md) endpoint: see [Check Opt-Out Status](#check-opt-out-status) | - ## Integration Diagram The following diagram outlines the steps that data collectors must complete to map DII to raw UID2s for audience building and targeting. diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-advertiser-dataprovider.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-advertiser-dataprovider.md deleted file mode 100644 index 5a65e03de..000000000 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-advertiser-dataprovider.md +++ /dev/null @@ -1,111 +0,0 @@ ---- -title: Advertiser/Data Provider Integration -sidebar_label: Advertiser/Data Provider Integration Guide -description: ユーザーデータを収集し、それを他の UID2 参加者にプッシュする組織のためのインテグレーション手順。 -hide_table_of_contents: false -sidebar_position: 07 -displayed_sidebar: sidebarAdvertisers ---- - -import Link from '@docusaurus/Link'; - -# Advertiser/Data Provider Integration Guide - -このガイドでは、ユーザーデータを収集し、DSP にプッシュする組織のためのインテグレーション手順について説明します。データコレクターには、広告主、データオンボーダー、測定プロバイダー、ID グラフプロバイダー、サードパーティデータプロバイダー、および DSP にデータを送信する他の組織が含まれます。 - -Snowflake Data Marketplace でホストされる Open Operator Service を使用する場合は、[Snowflake Integration Guide](../guides/snowflake_integration.md) も参照してください。 - -## Advertiser/Data Provider Routes to Use UID2 - -アドテクノロジー業界では、広告主は ID を使用してオーディエンスを構築し、コンバージョンを追跡し、グラフを生成します。広告主または広告主の代理としてデータプロバイダーが UID2 を使用してこれらの目標を達成する方法の例を以下に示します。 - -:::note -これらのユースケース以外にも、UID2 を使用する方法はあります。これらはいくつかの例です。 -::: - -| Send/Receive? | Action | Advantage/Result | -| --- | --- | --- | -| Send | UID2 を API またはピクセルを介して送信 | オーディエンスを作成します。 | -| Send | UID2 をコンバージョン情報として送信 | コンバージョン情報を使用して測定 (アトリビューション) またはリターゲティングに使用します。 | -| Receive | API またはピクセルを介してグラフ/データプロバイダーから UID2 を受信 | グラフデータを構築します。 | - - - -### High-Level Steps - -広告主およびデータプロバイダーが UID2 とインテグレーションする手順は次のとおりです: - -1. directly identifying information (DII) から UID2 を生成するか、広告主やデータプロバイダーなどの他の UID2 参加者から UID2 を受け取ります。 - -1. Step1 で受け取った UID2 を使用します。たとえば、以下のいずれかを行うかもしれません: - - 何らかの操作を行う: たとえば、DII から生成した UID2 と広告主やデータプロバイダーなどの他の参加者から受け取った UID2 を組み合わせます。 - - 既存のオーディエンスに新しい UID2 を追加します。 - -1. Raw UID2 を計測目的で使用します。 - -## Integration Diagram - -以下の図は、オーディエンスの構築とターゲティングのために DII を raw UID2 にマッピングするためにデータコレクターが完了する必要がある手順を示しています。 - -DII とは、正規化されたメールアドレスや電話番号、あるいは正規化され SHA-256 ハッシュ化されたメールアドレスや電話番号のことです。 - -![Advertiser Flow](images/advertiser-flow-mermaid.png) - - - -図の各部の詳細については、以下のセクションを参照してください: -1. [Retrieve a raw UID2 for DII](#1-retrieve-a-raw-uid2-for-dii) -2. [Send stored raw UID2s to DSPs to create audiences or conversions](#2-send-stored-raw-uid2s-to-dsps-to-create-audiences-or-conversions) -3. [Monitor for salt bucket rotations related to your stored raw UID2s](#3-monitor-for-salt-bucket-rotations-related-to-your-stored-raw-uid2s) - -### 1: Retrieve a raw UID2 for DII - -| Step | Endpoint | Description | -| --- | --- | --- | -| 1-a | [POST /identity/map](../endpoints/post-identity-map.md)リクエスト | DII を含むリクエストを ID マッピングエンドポイントに送信します。 | -| 1-b | [POST /identity/map](../endpoints/post-identity-map.md) レスポンス | レスポンスで返される `advertising_id` (raw UID2) は、関連する DSP でオーディエンスをターゲティングするために使用できます。
このレスポンスは、ユーザーの raw UID2 と、ソルトバケットに対応する `bucket_id` を返します。バケットに割り当てられたソルトは毎年ローテーションされ、生成される raw UID2 に影響を与えます。ソルトバケットのローテーションをチェックする方法の詳細は [3: Monitor for salt bucket rotations](#3-monitor-for-salt-bucket-rotations-related-to-your-stored-raw-uid2s) を参照してください。
メンテナンスを簡単にするために、ユーザの raw UID2 と `bucket_id` をマッピングテーブルに格納することを推奨します。インクリメンタルな更新に関するガイダンスについては、[Use an incremental process to continuous-update raw UID2s](#use-an-incremental-process-to-continuously-update-raw-uid2s) を参照してください。| - -### 2: Send stored raw UID2s to DSPs to create audiences or conversions - -Step 1-b で返された `advertising_id` (raw UID2) を、オーディエンスを構築しながら DSP に送信します。各 DSP はオーディエンスを構築するための独自のインテグレーションプロセスを持っています。raw UID2 を送信してオーディエンスを構築するには、DSP が提供するインテグレーションガイダンスに従ってください。 - -### 3: Monitor for salt bucket rotations related to your stored raw UID2s -raw UID2 は、特定の時点のユーザーに対する識別子です。特定のユーザーの raw UID2 は、ソルトのローテーションの結果、少なくとも 1 年に 1 回は変化します。 - -ソルトバケットの更新は 1 年に 1 回程度ですが、個々のバケットの更新は 1 年に分散しています。全ソルトバケットの約 1/365 を毎日ローテーションしています。 - -:::important -あなたのインテグレーションが最新の raw UID2 を持っていることを確認するために、アクティブなユーザーのソルトバケットのローテーションを毎日チェックしてください。 -::: - -| Step | Endpoint | Description | -| --- | --- | --- | -| 3-a | [POST /identity/buckets](../endpoints/post-identity-buckets.md) | 特定のタイムスタンプ以降に変更されたすべてのソルトバケットについて、バケットステータスエンドポイントにリクエストを送信します。 | -| 3-b | [POST /identity/buckets](../endpoints/post-identity-buckets.md) | UID2 service: バケットステータスエンドポイントは `bucket_id` と `last_updated` のタイムスタンプのリストを返します。 | -| 3-c | [POST /identity/map](../endpoints/post-identity-map.md) | 返された`bucket_id`を、キャッシュしておいた raw UID2 のソルトバケットと比較します。
1 つ以上の raw UID2 についてソルトバケットが更新されていることがわかったら、新しい raw UID2 について ID マッピングサービスに DII を再送信します。 | -| 3-d | [POST /identity/map](../endpoints/post-identity-map.md) | `advertising_id`と`bucket_id`に返された新しい値を保存します。 | - -## Use an Incremental Process to Continuously Update Raw UID2s - -UID2 ベースのオーディエンス情報を正確かつ最新の状態に保つために、毎日以下のインテグレーション手順を実行してください: - -1. [UID2 retrieval step](#1-retrieve-a-raw-uid2-for-dii) のレスポンスにはマッピング情報が含まれています。以下をキャッシュします: - - DII (`identifier`) と raw UID2 (`advertising_id`) とソルトバケット (`bucket_id`) のマッピング。 - - 最新の `last_updated` タイムスタンプ。 -2. Step 3の結果を使用して、[Monitor for salt bucket rotations related to your stored raw UID2s](#3-monitor-for-salt-bucket-rotations-related-to-your-stored-raw-uid2s)、 Step1 の [Retrieve a raw UID2 for DII](#1-retrieve-a-raw-uid2-for-dii) に従って、ソルトバケットがローテーションされた ID の新しい raw UID2 を取得して、ソルトバケットの raw UID2 を再マッピングします。 - - 次に、Step 2 の[send raw UID2 to a DSP](#2-send-stored-raw-uid2s-to-dsps-to-create-audiences-or-conversions) に従って、リフレッシュされた UID2 を使ってオーディエンスまたはコンバージョンを更新します。 - -## Check Opt-Out Status - -ユーザーのオプトアウトステータスを受け入れることは重要です。最新のオプトアウト情報を確認するために、次の 2 つの方法を使用できます: - -- UID2 Operator Service は、広告主やデータプロバイダーに、[POST /identity/map](../endpoints/post-identity-map.md) エンドポイントを介してオプトアウト情報を配布します。 - -- 広告主やデータプロバイダーは、[POST /optout/status](../endpoints/post-optout-status.md) エンドポイントを使用して、生の UID2 のオプトアウトステータスを確認できます。 - -## FAQs - -UID2 フレームワークを使用する広告主およびデータプロバイダー向けのよくある質問は、[FAQs for Advertisers and Data Providers](../getting-started/gs-faqs.md#faqs-for-advertisers-and-data-providers) を参照してください。 diff --git a/sidebars.js b/sidebars.js index b4b61e5e0..152a210ab 100644 --- a/sidebars.js +++ b/sidebars.js @@ -86,7 +86,7 @@ const fullSidebar = [ link: { type: 'generated-index', }, - collapsed: false, + collapsed: true, items: [ { @@ -195,7 +195,6 @@ const fullSidebar = [ 'guides/snowflake_integration', 'guides/integration-aws-entity-resolution', 'guides/integration-advertiser-dataprovider-endpoints', - 'guides/integration-javascript-client-side', ], }, @@ -333,6 +332,7 @@ const sidebars = { 'guides/snowflake_integration', 'guides/integration-aws-entity-resolution', 'guides/advertiser-dataprovider-endpoints', + 'DSP Integrations', 'guides/dsp-guide', 'endpoints/post-identity-buckets', 'endpoints/post-identity-map', @@ -370,6 +370,7 @@ const sidebars = { 'guides/mobile-plugin-gma-ios', 'guides/mobile-plugin-ima-android', 'guides/mobile-plugin-ima-ios', + 'DSP Integrations', 'guides/dsp-guide', 'endpoints/post-token-generate', 'endpoints/post-token-validate', @@ -409,6 +410,7 @@ const sidebars = { 'guides/mobile-plugin-gma-ios', 'guides/mobile-plugin-ima-android', 'guides/mobile-plugin-ima-ios', + 'Advertiser/Data Provider Integrations', 'guides/integration-advertiser-dataprovider-overview', 'guides/snowflake_integration', 'guides/integration-aws-entity-resolution', @@ -447,6 +449,7 @@ const sidebars = { 'guides/mobile-plugin-gma-ios', 'guides/mobile-plugin-ima-android', 'guides/mobile-plugin-ima-ios', + 'DSP Integrations', 'guides/dsp-guide', 'endpoints/post-token-generate', 'endpoints/post-token-validate',