diff --git a/docs/endpoints/post-identity-buckets.md b/docs/endpoints/post-identity-buckets.md index 3b7644dd4..952169ef4 100644 --- a/docs/endpoints/post-identity-buckets.md +++ b/docs/endpoints/post-identity-buckets.md @@ -17,7 +17,7 @@ Used by: This endpoint is used mainly by advertisers and data providers. For det :::important If you're using the latest version (v3) of `POST /v3/identity/map`, you don't need to use `POST /identity/buckets` at all. You only need to use it if you're using the earlier version (v2) of `POST /v2/identity/map`. -If you're using the v2 version, we recommend that you upgrade as soon as possible, to take advantage of improvements. For migration guidance, see [Migration from v2 Identity Map](post-identity-map.md#migration-from-v2-identity-map). +If you're using the v2 version, we recommend that you upgrade as soon as possible, to take advantage of improvements. For migration guidance, see [Migration from POST /v2/identity/map](post-identity-map.md#migration-from-post-v2identitymap). ::: ## Request Format diff --git a/docs/endpoints/post-identity-map-v2.md b/docs/endpoints/post-identity-map-v2.md index dfe44d160..88be2e642 100644 --- a/docs/endpoints/post-identity-map-v2.md +++ b/docs/endpoints/post-identity-map-v2.md @@ -1,5 +1,5 @@ --- -title: POST /identity/map (v2) +title: POST /v2/identity/map description: Maps DII to raw UID2s and salt bucket IDs. hide_table_of_contents: false sidebar_position: 07 @@ -7,7 +7,7 @@ sidebar_position: 07 import Link from '@docusaurus/Link'; -# POST /identity/map (v2) +# POST /v2/identity/map Maps multiple email addresses, phone numbers, or their respective hashes to their raw UID2s and salt bucket IDs. You can also use this endpoint to check for updates to opt-out information. @@ -17,10 +17,10 @@ For details about the UID2 opt-out workflow and how users can opt out, see [User ## Version -This documentation is for version 2 of this endpoint, which is not the latest version. For the latest version, v3, see [POST /identity/map](post-identity-map.md). +This documentation is for version 2 of this endpoint, which is not the latest version. For the latest version, v3, see [POST /v3/identity/map](post-identity-map.md). :::note -If you're using an earlier version, we recommend that you upgrade as soon as possible, to take advantage of improvements. For migration guidance, see [Migration from v2 Identity Map](post-identity-map.md#migration-from-v2-identity-map). For deprecation information, see [Deprecation Schedule: Endpoint Versions](../ref-info/deprecation-schedule.md#endpoint-versions). +If you're using an earlier version, we recommend that you upgrade as soon as possible, to take advantage of improvements. For migration guidance, see [Migration from POST /v2/identity/map](post-identity-map.md#migration-from-post-v2identitymap). For deprecation information, see [Deprecation Schedule: Endpoint Versions](../ref-info/deprecation-schedule.md#endpoint-versions). ::: ## Batch Size and Request Parallelization Requirements @@ -33,7 +33,7 @@ Here's what you need to know: ## Rate Limiting -To ensure fair usage and platform stability, the `POST /identity/map` endpoint enforces rate limits to safeguard against bursts of incoming traffic. If you send many requests in quick succession, you might receive `429` error responses. +To ensure fair usage and platform stability, the `POST /v2/identity/map` endpoint enforces rate limits to safeguard against bursts of incoming traffic. If you send many requests in quick succession, you might receive `429` error responses. To handle rate limit errors gracefully, we recommend implementing [exponential backoff](https://en.wikipedia.org/wiki/Exponential_backoff) with random jitter when retrying requests. To maximize throughput within the limit, use the maximum batch size of 5,000 items per request rather than sending many small requests. @@ -72,7 +72,7 @@ You must include only **one** of the following four conditional parameters as a ### Request Examples -The following are unencrypted JSON request body examples for each parameter, one of which you should include in your requests to the `POST /identity/map` endpoint: +The following are unencrypted JSON request body examples for each parameter, one of which you should include in your requests to the `POST /v2/identity/map` endpoint: ```json { @@ -107,7 +107,7 @@ The following are unencrypted JSON request body examples for each parameter, one } ``` -Here's an encrypted request example to the `POST /identity/map` endpoint for a phone number: +Here's an encrypted request example to the `POST /v2/identity/map` endpoint for a phone number: ```sh echo '{"phone": ["+12345678901", "+441234567890"]}' | python3 uid2_request.py https://prod.uidapi.com/v2/identity/map [Your-Client-API-Key] [Your-Client-Secret] diff --git a/docs/endpoints/post-identity-map.md b/docs/endpoints/post-identity-map.md index 13738bf7c..def39ab33 100644 --- a/docs/endpoints/post-identity-map.md +++ b/docs/endpoints/post-identity-map.md @@ -1,5 +1,5 @@ --- -title: POST /identity/map +title: POST /v3/identity/map description: Maps DII to raw UID2s. hide_table_of_contents: false sidebar_position: 08 @@ -9,7 +9,7 @@ displayed_sidebar: docs import Link from '@docusaurus/Link'; import SnptPOSTIdentityMapImprovements from '../snippets/_snpt-post-identity-map-improvements-v3.mdx'; -# POST /identity/map +# POST /v3/identity/map Maps multiple email addresses, phone numbers, or their respective hashes to their raw UID2s. You can also use this endpoint to check for updates to opt-out information, check when a raw UID2 can be refreshed, or view the previous UID2 if the current UID2 is less than 90 days old. @@ -21,7 +21,7 @@ For details about the UID2 opt-out workflow and how users can opt out, see [User This documentation is for the latest version of this endpoint, version 3. -If needed, documentation is also available for the previous version: see [POST /identity/map (v2)](post-identity-map-v2.md). +If needed, documentation is also available for the previous version: see [POST /v2/identity/map](post-identity-map-v2.md). ## Batch Size and Request Parallelization Requirements @@ -210,7 +210,7 @@ If the `status` value is anything other than `success`, the `message` field prov 429 responses do not include a JSON response body. ::: -## Migration from v2 Identity Map +## Migration from POST /v2/identity/map The following sections provide general information and guidance for migrating to version 3 from earlier versions, including: diff --git a/docs/endpoints/post-token-generate.md b/docs/endpoints/post-token-generate.md index 023d0d2d8..08acae5fc 100644 --- a/docs/endpoints/post-token-generate.md +++ b/docs/endpoints/post-token-generate.md @@ -55,7 +55,7 @@ You must include only **one** of the following four conditional parameters as ke ### Request Examples :::important -To ensure that the API key used to access the service remains secret, the `POST /token/generate` endpoint must be called from the server side, unlike [POST /token/refresh](post-token-refresh.md) which does not require using an API key. If you want to generate tokens on the client side, see [Client-Side Integration Options](../guides/integration-options-publisher-web.md#client-side-integration-options) (for web-based implementations) or [UID2 Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side.md). +To ensure that the API key used to access the service remains secret, the `POST /token/generate` endpoint must be called from the server side, unlike [POST /token/refresh](post-token-refresh.md) which does not require using an API key. If you want to generate tokens on the client side, see [Client-Side Integration Options](../guides/integration-options-publisher-web.md#client-side-integration-options) (for web-based implementations) or [Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side.md). ::: The following are unencrypted JSON request body examples for each parameter, one of which you should include in your token generation requests: diff --git a/docs/endpoints/summary-endpoints.md b/docs/endpoints/summary-endpoints.md index fbcad26d0..c4274cdd8 100644 --- a/docs/endpoints/summary-endpoints.md +++ b/docs/endpoints/summary-endpoints.md @@ -38,7 +38,7 @@ The following endpoints are for retrieving and managing UID2 tokens (identity to The following endpoints are used by advertisers and third-party data providers. Publishers do not need to use these endpoints. -### Latest Identity Map Endpoint (v3) +### Latest POST /v3/identity/map Endpoint In the latest identity map integration, you only need to call one endpoint, `POST /identity/map`. The `POST /identity/buckets` endpoint is not part of the workflow. diff --git a/docs/getting-started/gs-auth.md b/docs/getting-started/gs-auth.md index d54fe3ac6..c872c1eb3 100644 --- a/docs/getting-started/gs-auth.md +++ b/docs/getting-started/gs-auth.md @@ -17,5 +17,5 @@ To authenticate to the UID2 endpoints in a server-side implementation, you need - A client secret for encrypting API requests and decrypting API responses. This is needed for all endpoints except [POST /token/refresh](../endpoints/post-token-refresh.md).
For details, and encryption/decryption examples in several different programming languages, see [Encrypting Requests and Decrypting Responses](gs-encryption-decryption.md). :::note -If you're a publisher and are implementing UID2 on the client side, the authentication and authorization is managed automatically by your implementation, such as Prebid.js (see [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md)) or the JavaScript SDK (see [Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md)). +If you're a publisher and are implementing UID2 on the client side, the authentication and authorization is managed automatically by your implementation, such as Prebid.js (see [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md)) or the JavaScript SDK (see [Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md)). ::: diff --git a/docs/getting-started/gs-credentials.md b/docs/getting-started/gs-credentials.md index 13211530f..01927f6d9 100644 --- a/docs/getting-started/gs-credentials.md +++ b/docs/getting-started/gs-credentials.md @@ -14,8 +14,8 @@ Each UID2 Subscription ID
  • Public key
    • These two, together, are sometimes called client keypair. | Integrations using one of these: | -| Participants using a client-server implementation | Both of the following: | Integrations using one of these: | +| Participants using a client-side implementation | Both of the following: These two, together, are sometimes called client keypair. | Integrations using one of these: | +| Participants using a client-server implementation | Both of the following: | Integrations using one of these: | | Participants using a server-side implementation | Both of the following: | Integrations using one of these: | ## Separate Credentials Per Environment/Role @@ -23,7 +23,7 @@ Each UID2     environment as well as the production environment, you'll get a separate set of credentials for each environment. See [Getting Your Credentials](#getting-your-credentials). In addition, in some cases, we recommend, but do not require, that you have a different set of credentials for a different scenario. For example: -- If you're a publisher who generates UID2 tokens (via [POST /token/generate](../endpoints/post-token-generate.md) or in some other way), but you also create/map raw UID2s on your own behalf (see [POST /identity/map](../endpoints/post-identity-map.md)), you might have separate credentials for each of these activities. +- If you're a publisher who generates UID2 tokens (via [POST /token/generate](../endpoints/post-token-generate.md) or in some other way), but you also create/map raw UID2s on your own behalf (see [POST /v3/identity/map](../endpoints/post-identity-map.md)), you might have separate credentials for each of these activities. - If you're an advertiser, in a scenario where you allow multiple service providers to operate using your advertiser keys, you might choose to have separate credentials for each service provider. ## Getting Your Credentials @@ -79,7 +79,7 @@ To get your credentials, ask your UID2 contact. ## Subscription ID and Public Key -If you're using a client-side implementation (see [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) or [Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md)), you'll receive the following credentials: +If you're using a client-side implementation (see [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) or [Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md)), you'll receive the following credentials: - **Subscription ID**: This value identifies your site to the UID2 service. - **Public key**: This value is used for encryption. @@ -97,7 +97,7 @@ Notes: ## API Key and Client Secret -If you're using a client-server or server-side implementation (see [UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) or [Client-Server Integration Guide for JavaScript](../guides/integration-javascript-client-server.md)), the API key and client secret allow you to connect to the Operator Service and call API endpoints. These values identify you to the service. +If you're using a client-server or server-side implementation (see [Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) or [Client-Server Integration Guide for JavaScript](../guides/integration-javascript-client-server.md)), the API key and client secret allow you to connect to the Operator Service and call API endpoints. These values identify you to the service. Here is some information about API keys and client secrets: - You must keep these values secure. For details, see [Security of API Key and Client Secret](#security-of-api-key-and-client-secret). diff --git a/docs/getting-started/gs-encryption-decryption.md b/docs/getting-started/gs-encryption-decryption.md index 3d833dd80..97c971992 100644 --- a/docs/getting-started/gs-encryption-decryption.md +++ b/docs/getting-started/gs-encryption-decryption.md @@ -14,7 +14,7 @@ import SnptIdentityGenerateResponse from '../snippets/_snpt-example-identity-gen # Encrypting Requests and Decrypting Responses :::note -If you're a publisher and are implementing UID2 on the client side, encryption and decryption is managed automatically by your implementation, such as Prebid.js (see [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md)) or the JavaScript SDK (see [Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md)). +If you're a publisher and are implementing UID2 on the client side, encryption and decryption is managed automatically by your implementation, such as Prebid.js (see [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md)) or the JavaScript SDK (see [Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md)). ::: For almost all UID2 [endpoints](../endpoints/summary-endpoints.md), requests sent to the endpoint must be [encrypted](#encrypting-requests) and responses from the endpoint must be [decrypted](#decrypting-responses). diff --git a/docs/getting-started/gs-faqs.md b/docs/getting-started/gs-faqs.md index 65e211411..c2bd65ce9 100644 --- a/docs/getting-started/gs-faqs.md +++ b/docs/getting-started/gs-faqs.md @@ -98,8 +98,8 @@ If the user has opted out, the API response notifies you in either of these case #### Where should I make token generation calls—from the server side or the client side? You can generate UID2 tokens from either the client side or the server side. For more information, see: -- Generating tokens from the client side using Prebid.js: [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md). -- Generating tokens from the server side using Prebid.js: [UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md). +- Generating tokens from the client side using Prebid.js: [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md). +- Generating tokens from the server side using Prebid.js: [Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md). - Other server-side options: [Publisher Integrations](../guides/summary-guides.md#publisher-integrations). #### Can I make token refresh calls from the client side? diff --git a/docs/getting-started/gs-permissions.md b/docs/getting-started/gs-permissions.md index 67a284233..7a845e8a5 100644 --- a/docs/getting-started/gs-permissions.md +++ b/docs/getting-started/gs-permissions.md @@ -27,4 +27,4 @@ The following table lists the key permissions, the types of participants that co | Generator | Publishers | Permission to call the [POST /token/generate](../endpoints/post-token-generate.md), [POST /token/validate](../endpoints/post-token-validate.md), and [POST /token/refresh](../endpoints/post-token-refresh.md) endpoints, to generate UID2 tokens from DII and to refresh them, using one of these integration methods: | | Bidder | DSPs | Permission to decrypt UID2 tokens coming in from the bidstream from publishers into raw UID2s for bidding purposes. | | Sharer | Any participant type that takes part in UID2 sharing.
    For details, see [UID2 Sharing: Overview](../sharing/sharing-overview.md). | Permission to do both of the following: | -| Mapper | Advertisers
    Data Providers | Permission to call the following endpoints to map multiple email addresses, phone numbers, or their respective hashes to their raw UID2s, previous raw UID2s, and refresh timestamps: | +| Mapper | Advertisers
    Data Providers | Permission to call the following endpoints to map multiple email addresses, phone numbers, or their respective hashes to their raw UID2s, previous raw UID2s, and refresh timestamps: | diff --git a/docs/guides/integration-advertiser-dataprovider-endpoints.md b/docs/guides/integration-advertiser-dataprovider-endpoints.md index d14924918..1e3abc002 100644 --- a/docs/guides/integration-advertiser-dataprovider-endpoints.md +++ b/docs/guides/integration-advertiser-dataprovider-endpoints.md @@ -100,7 +100,7 @@ You could also send conversion information via API or pixels for measurement (at A raw UID2 is an identifier for a user at a specific moment in time. The raw UID2 for a specific user changes roughly once per year as part of the UID2 refresh process. -The v3 Identity Map API provides a refresh timestamp (`r` field) in the response that indicates when each raw UID2 might rotate. Use this timestamp to determine when to regenerate raw UID2s for your stored data. +The v3 `POST /identity/map` API provides a refresh timestamp (`r` field) in the response that indicates when each raw UID2 might rotate. Use this timestamp to determine when to regenerate raw UID2s for your stored data. The raw UID2 does not change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. @@ -134,7 +134,7 @@ There are two ways that you can check with the UID2 ### Make Sure Token Lifetime and Expiration Are Valid @@ -128,8 +128,8 @@ For an example of code that does this, refer to the `IsDomainOrAppNameAllowedFor For more information about client-side UID2 integration, refer to one of these integration guides: - [Client-Side Integration Guide for JavaScript](integration-javascript-client-side.md) -- [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) -- [UID2 Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) +- [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) +- [Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) ## Honor User Opt-Out After Token Decryption diff --git a/docs/guides/integration-mobile-client-server.md b/docs/guides/integration-mobile-client-server.md index dc92d48eb..7efab75b8 100644 --- a/docs/guides/integration-mobile-client-server.md +++ b/docs/guides/integration-mobile-client-server.md @@ -1,7 +1,7 @@ --- -title: UID2 Client-Server Integration Guide for Mobile +title: Client-Server Integration Guide for Mobile sidebar_label: Client-Server Integration for Mobile -pagination_label: UID2 Client-Server Integration Guide for Mobile +pagination_label: Client-Server Integration Guide for Mobile description: Setting up a mobile integration with token generate on server and refresh on client. hide_table_of_contents: false sidebar_position: 04 @@ -19,13 +19,13 @@ import SnptGMAIMA_Plugins from '../snippets/_snpt-mobile_docs_gmaima-plugin-gss. import SnptPrebidMobileSDK from '../snippets/_snpt-mobile_docs_prebid-mobile.mdx'; import SnptErrorResponseStates from '../snippets/_snpt-mobile-docs-error-response-states.mdx'; -# UID2 Client-Server Integration Guide for Mobile +# Client-Server Integration Guide for Mobile This guide is for mobile app publishers who want to integrate with UID2 by generating UID2 tokens server-side via a Public Operator or Private Operator and then passing the tokens and user identities into their mobile apps, which will in turn pass the tokens for bidstream use.   This is called client-server integration because some integration steps are client-side and some are server-side. -If you want to integrate with UID2 via client-side only changes (that is, all integration changes required are within the mobile apps), refer to the [UID2 Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) instead. +If you want to integrate with UID2 via client-side only changes (that is, all integration changes required are within the mobile apps), refer to the [Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) instead. This page provides a high-level overview of integration steps and links to additional documentation. diff --git a/docs/guides/integration-mobile-client-side.md b/docs/guides/integration-mobile-client-side.md index ca5b04a62..60ddc85dd 100644 --- a/docs/guides/integration-mobile-client-side.md +++ b/docs/guides/integration-mobile-client-side.md @@ -1,7 +1,7 @@ --- -title: UID2 Client-Side Integration Guide for Mobile +title: Client-Side Integration Guide for Mobile sidebar_label: Client-Side Integration for Mobile -pagination_label: UID2 Client-Side Integration Guide for Mobile +pagination_label: Client-Side Integration Guide for Mobile description: Setting up a mobile integration with token generate and refresh both on the client side. hide_table_of_contents: false sidebar_position: 04 @@ -19,7 +19,7 @@ import SnptGMAIMA_Plugins from '../snippets/_snpt-mobile_docs_gmaima-plugin-gss. import SnptPrebidMobileSDK from '../snippets/_snpt-mobile_docs_prebid-mobile.mdx'; import SnptErrorResponseStates from '../snippets/_snpt-mobile-docs-error-response-states.mdx'; -# UID2 Client-Side Integration Guide for Mobile +# Client-Side Integration Guide for Mobile This guide is for mobile app publishers who want to integrate with UID2 with changes only within their mobile app. diff --git a/docs/guides/integration-mobile-overview.md b/docs/guides/integration-mobile-overview.md index 13600d015..bdf393ccd 100644 --- a/docs/guides/integration-mobile-overview.md +++ b/docs/guides/integration-mobile-overview.md @@ -12,7 +12,7 @@ import Link from '@docusaurus/Link'; import SnptIntegratingWithSSO from '../snippets/_snpt-integrating-with-sso.mdx'; import SnptPreparingEmailsAndPhoneNumbers from '../snippets/_snpt-preparing-emails-and-phone-numbers.mdx'; -# UID2 Mobile Integration Overview for Android and iOS +# Mobile Integration Overview for Android and iOS This guide is an overview of integration options for mobile app publishers who want to integrate with UID2 using the SDK for Android or the SDK for iOS. @@ -86,8 +86,8 @@ For details, see [Integration Approaches](../ref-info/ref-integration-approaches | Scenario | Option | Integration Guide | | :--- | :--- | :--- | -| You have access to DII (email address or phone number) on the client side/within the mobile app, and want to keep changes within your app only. | Client-Side integration | [UID2 Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) | -| You have access to DII on the server side only and can do the necessary development to generate UID2 tokens server-side, but you want to refresh tokens on the client side—or you are using a Private Operator. | Client-Server Integration | [UID2 Client-Server Integration Guide for Mobile](integration-mobile-client-server.md) | +| You have access to DII (email address or phone number) on the client side/within the mobile app, and want to keep changes within your app only. | Client-Side integration | [Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) | +| You have access to DII on the server side only and can do the necessary development to generate UID2 tokens server-side, but you want to refresh tokens on the client side—or you are using a Private Operator. | Client-Server Integration | [Client-Server Integration Guide for Mobile](integration-mobile-client-server.md) | | You have access to DII on the server side only and can do the necessary development to generate UID2 tokens server-side, or you are using a Private Operator. | Server-Side Integration | [UID2 Server-Side Integration Guide for Mobile](integration-mobile-server-side.md) | ### Generating, Storing, and Refreshing the UID2 Token @@ -106,12 +106,12 @@ The following table summarizes the mobile integration options for managing the U UID2 Android SDK [SDK for Android Reference Guide](../sdks/sdk-ref-android.md) - One of the following: + One of the following: UID2 iOS SDK [SDK for iOS Reference Guide](../sdks/sdk-ref-ios.md) - One of the following: + One of the following: diff --git a/docs/guides/integration-options-publisher-web.md b/docs/guides/integration-options-publisher-web.md index 76dc04d11..bb1e8b23b 100644 --- a/docs/guides/integration-options-publisher-web.md +++ b/docs/guides/integration-options-publisher-web.md @@ -85,7 +85,7 @@ The following table summarizes the options for publishers who want to generate t | Option | Documentation | | :--- | :--- | -| Prebid.js client-side implementation (8.21.0 or later) | [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | +| Prebid.js client-side implementation (8.21.0 or later) | [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | | SDK for JavaScript, client-side implementation | [Client-Side Integration Guide for JavaScript](integration-javascript-client-side.md) | ### Server-Side Integration Options @@ -115,8 +115,8 @@ The following table shows the integration options that support refreshing the UI | Option | Documentation | | :--- | :--- | -| Prebid.js client-side implementation (8.21.0 or later) | [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | -| Prebid.js client-server implementation (7.53.0 or later) | [UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | +| Prebid.js client-side implementation (8.21.0 or later) | [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | +| Prebid.js client-server implementation (7.53.0 or later) | [Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | | SDK for JavaScript, client-side implementation | [Client-Side Integration Guide for JavaScript](integration-javascript-client-side.md) | | SDK for JavaScript, client-server implementation | [Client-Server Integration Guide for JavaScript](integration-javascript-client-server.md) | | SDK for Java | - [Publisher Integration Guide, Server-Side](integration-publisher-server-side.md)
    - [SDK for Java](../sdks/sdk-ref-java.md) | @@ -131,8 +131,8 @@ The following table shows integration options that support passing UID2 token in | Option | Documentation | | :--- | :--- | -| Prebid.js client-side implementation (8.21.0 or later) | [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | -| Prebid.js client-server implementation (7.53.0 or later) | [UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | +| Prebid.js client-side implementation (8.21.0 or later) | [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | +| Prebid.js client-server implementation (7.53.0 or later) | [Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | | Google Ad Manager Secure Signals| [Google Ad Manager Secure Signals Integration Guide](integration-google-ss.md) | :::note diff --git a/docs/guides/integration-prebid-client-server.md b/docs/guides/integration-prebid-client-server.md index 0092483a9..c73c2bac9 100644 --- a/docs/guides/integration-prebid-client-server.md +++ b/docs/guides/integration-prebid-client-server.md @@ -1,5 +1,5 @@ --- -title: UID2 Client-Server Integration Guide for Prebid.js +title: Client-Server Integration Guide for Prebid.js sidebar_label: Client-Server Integration for Prebid.js pagination_label: UID2 Client-Server Integration for Prebid.js description: Information about setting up a client-server Prebid.js integration. @@ -14,7 +14,7 @@ import SnptPreparingEmailsAndPhoneNumbers from '../snippets/_snpt-preparing-emai import SnptAddPrebidjsToYourSite from '../snippets/_snpt-prebid-add-prebidjs-to-your-site.mdx'; import SnptStoreUID2TokenInBrowser from '../snippets/_snpt-prebid-storing-uid2-token-in-browser.mdx'; -# UID2 Client-Server Integration Guide for Prebid.js +# Client-Server Integration Guide for Prebid.js This guide is for publishers who have access to DII (email address or phone number) on the server side and want to integrate with UID2 and generate UID2 tokens (advertising tokens) to be passed by Prebid.js in the RTB bidstream. diff --git a/docs/guides/integration-prebid-client-side.md b/docs/guides/integration-prebid-client-side.md index c730dbb6a..42cd28917 100644 --- a/docs/guides/integration-prebid-client-side.md +++ b/docs/guides/integration-prebid-client-side.md @@ -1,7 +1,7 @@ --- -title: UID2 Client-Side Integration Guide for Prebid.js +title: Client-Side Integration Guide for Prebid.js sidebar_label: Client-Side Integration for Prebid.js -pagination_label: UID2 Client-Side Integration for Prebid.js +pagination_label: Client-Side Integration for Prebid.js description: Information about setting up a client-side Prebid.js integration. hide_table_of_contents: false sidebar_position: 04 @@ -14,7 +14,7 @@ import SnptPreparingEmailsAndPhoneNumbers from '../snippets/_snpt-preparing-emai import SnptAddPrebidjsToYourSite from '../snippets/_snpt-prebid-add-prebidjs-to-your-site.mdx'; import SnptStoreUID2TokenInBrowser from '../snippets/_snpt-prebid-storing-uid2-token-in-browser.mdx'; -# UID2 Client-Side Integration Guide for Prebid.js +# Client-Side Integration Guide for Prebid.js This guide is for publishers who have access to DII (email address or phone number) on the client side and want to integrate with UID2 and generate UID2 tokens (advertising tokens) to be passed by Prebid.js in the RTB bidstream. @@ -26,7 +26,7 @@ This implementation requires Prebid.js version 8.21.0 or later. For version info -If you need to use an earlier version of Prebid.js, use the implementation solution presented in the [UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) instead. +If you need to use an earlier version of Prebid.js, use the implementation solution presented in the [Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) instead. ## Integrating with Single Sign-On (SSO) diff --git a/docs/guides/integration-prebid-mobile-summary.md b/docs/guides/integration-prebid-mobile-summary.md index 3c9b9fa0f..741fb9af9 100644 --- a/docs/guides/integration-prebid-mobile-summary.md +++ b/docs/guides/integration-prebid-mobile-summary.md @@ -16,5 +16,5 @@ UID2 integration with Prebid is also supported for Android and iOS mobile device For details, see the following sections of the mobile integration guides: -- [UID2 Client-Side Integration Guide for Mobile: UID2 Integration with Prebid Mobile SDK](integration-mobile-client-side#optional-uid2-integration-with-prebid-mobile-sdk) -- [UID2 Client-Server Integration Guide for Mobile: UID2 Integration with Prebid Mobile SDK](integration-mobile-client-server#optional-uid2-integration-with-prebid-mobile-sdk) +- [Client-Side Integration Guide for Mobile: UID2 Integration with Prebid Mobile SDK](integration-mobile-client-side#optional-uid2-integration-with-prebid-mobile-sdk) +- [Client-Server Integration Guide for Mobile: UID2 Integration with Prebid Mobile SDK](integration-mobile-client-server#optional-uid2-integration-with-prebid-mobile-sdk) diff --git a/docs/guides/integration-prebid.md b/docs/guides/integration-prebid.md index 42c320d02..9429b157c 100644 --- a/docs/guides/integration-prebid.md +++ b/docs/guides/integration-prebid.md @@ -50,8 +50,8 @@ Determine which method is best for you, and then follow the applicable integrati | Scenario | Integration Guide | | :--- | :--- | -| You have access to DII on the client side and want to do front-end development only | [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | -| You have access to DII on the server side and can do server-side development | [UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | +| You have access to DII on the client side and want to do front-end development only | [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | +| You have access to DII on the server side and can do server-side development | [Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | ### Refreshing the UID2 Token @@ -65,8 +65,8 @@ The Prebid.js UID2 module can automatically refresh the UID2 tokens. If you pref To configure the UID2 module, call `pbjs.setConfig`. For details on supported parameters, refer to the guide that applies to your implementation: -- [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) -- [UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) +- [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) +- [Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) When the UID2 module is configured, it manages a UID2 token for the user and stores it in the user's browser. @@ -82,8 +82,8 @@ At a high level, to integrate your site with UID2 using Prebid.js, you'll need t For detailed instructions, refer to one of the following integration guides: -- [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) -- [UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) +- [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) +- [Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) ## UID2 Integration with Prebid Mobile SDK for Mobile Devices diff --git a/docs/guides/operator-guide-aws-marketplace.md b/docs/guides/operator-guide-aws-marketplace.md index 9a4f87955..2668c8a0d 100644 --- a/docs/guides/operator-guide-aws-marketplace.md +++ b/docs/guides/operator-guide-aws-marketplace.md @@ -158,7 +158,7 @@ To avoid passing certificates associated with your domain into the enclave, inbo ### VPC Chart -The following diagram illustrates the virtual private cloud that hosts private operators. +The following diagram illustrates the virtual private cloud that hosts the Private Operator. ![UID2 Operator VPC Chart](images/aws-vpc-chart-uid2.png) @@ -263,7 +263,7 @@ To check the UID2 Operator status of your Load Balancer, complete the following ## Upgrading the UID2 Operator -For each operator version update, each private operator receives an email notification with an upgrade window. After the upgrade window, the old version is deactivated and is no longer supported. +For each operator version update, each Private Operator receives an email notification with an upgrade window. After the upgrade window, the old version is deactivated and is no longer supported. Here's what you need to know about upgrading: diff --git a/docs/guides/operator-guide-azure-enclave.md b/docs/guides/operator-guide-azure-enclave.md index 407d53250..fea7fae53 100644 --- a/docs/guides/operator-guide-azure-enclave.md +++ b/docs/guides/operator-guide-azure-enclave.md @@ -334,7 +334,7 @@ The following table provides information about supported protocols. ## Upgrading -When a new version of UID2 Azure Confidential Containers is released, private operators receive an email notification of the update, with a new release link. There is a window of time for upgrade, after which the older version is deactivated and is no longer supported. +When a new version of UID2 Azure Confidential Containers is released, Private Operators receive an email notification of the update, with a new release link. There is a window of time for upgrade, after which the older version is deactivated and is no longer supported. To upgrade, complete the following steps: diff --git a/docs/guides/operator-private-gcp-confidential-space.md b/docs/guides/operator-private-gcp-confidential-space.md index 259dd3746..e9fea80ab 100644 --- a/docs/guides/operator-private-gcp-confidential-space.md +++ b/docs/guides/operator-private-gcp-confidential-space.md @@ -520,7 +520,7 @@ The following example shows the health check for the `gcloud` command line optio ## Upgrading -When a new version of UID2 Google Cloud Platform Confidential Space is released, private operators receive an email notification of the update, with a new image version. There is a window of time for upgrade, after which the older version is deactivated and is no longer supported. +When a new version of UID2 Google Cloud Platform Confidential Space is released, Private Operators receive an email notification of the update, with a new image version. There is a window of time for upgrade, after which the older version is deactivated and is no longer supported. If you're upgrading to a new version, the upgrade process depends on the deployment option you chose. Follow the applicable steps: diff --git a/docs/guides/summary-guides.md b/docs/guides/summary-guides.md index 8111111ca..3cd80c94a 100644 --- a/docs/guides/summary-guides.md +++ b/docs/guides/summary-guides.md @@ -44,8 +44,8 @@ For a detailed summary of web integration options, see [Publisher Web Integratio | Integration Guide | Content Description | | :--- | :--- | | [UID2 Integration Overview for Prebid](integration-prebid.md) | An overview of options for publishers who want to integrate with UID2 and generate UID2 tokens (advertising tokens) to be passed by Prebid.js and the Prebid Mobile SDK in the RTB bidstream. | -| [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | An integration guide for publishers who want to integrate with UID2 and want Prebid.js to manage token generation and automatic token refresh as well as passing the tokens into the RTB bidstream. This guide is for publishers who want to request UID2 tokens client-side, which is the easiest implementation approach. | -| [UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | An integration guide for publishers who want to integrate with UID2 and generate identity tokens to be passed by Prebid.js in the RTB bidstream. This guide is for publishers who are using a Private Operator or who want to generate tokens server-side. | +| [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | An integration guide for publishers who want to integrate with UID2 and want Prebid.js to manage token generation and automatic token refresh as well as passing the tokens into the RTB bidstream. This guide is for publishers who want to request UID2 tokens client-side, which is the easiest implementation approach. | +| [Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | An integration guide for publishers who want to integrate with UID2 and generate identity tokens to be passed by Prebid.js in the RTB bidstream. This guide is for publishers who are using a Private Operator or who want to generate tokens server-side. | | [UID2 Integration Overview for JavaScript](integration-javascript.md) | An overview of options for publishers who want to integrate with UID2 using the JavaScript SDK. | | [Client-Side Integration Guide for JavaScript](integration-javascript-client-side.md) | A guide for publishers who want to integrate with UID2 using only client-side JavaScript changes, which is the easiest implementation approach.
    The SDK for JavaScript manages token generation and token refresh automatically. | | [Client-Server Integration Guide for JavaScript](integration-javascript-client-server.md) | This integration guide for publishers covers standard web integration scenarios that use the SDK for JavaScript and requires the token to be generated on the server side and passed to the publishers' web pages. | @@ -78,8 +78,8 @@ The following resources are available for publishers integrating with Prebid. | Integration Guide | Content Description | | :--- | :--- | | [UID2 Integration Overview for Prebid](integration-prebid.md) | An overview of options for publishers who want to integrate with UID2 and generate UID2 tokens to be passed by Prebid.js or the Prebid Mobile SDK in the RTB bidstream. | -| [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | An integration guide for publishers who want to integrate with UID2 and want Prebid.js to manage token generation and automatic token refresh as well as passing the tokens into the RTB bidstream. This guide is for publishers who want to request UID2 tokens client-side, which is the easiest implementation approach. | -| [UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | An integration guide for publishers who want to integrate with UID2 and generate identity tokens to be passed by Prebid.js in the RTB bidstream. This guide is for publishers who are using a Private Operator or who want to generate tokens server-side. | +| [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | An integration guide for publishers who want to integrate with UID2 and want Prebid.js to manage token generation and automatic token refresh as well as passing the tokens into the RTB bidstream. This guide is for publishers who want to request UID2 tokens client-side, which is the easiest implementation approach. | +| [Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | An integration guide for publishers who want to integrate with UID2 and generate identity tokens to be passed by Prebid.js in the RTB bidstream. This guide is for publishers who are using a Private Operator or who want to generate tokens server-side. | | [UID2 Mobile Integration for Prebid.js](integration-prebid-mobile-summary.md) | A summary of information resources for UID2 integration with Prebid.js on mobile devices. | ### Google Ad Manager Integrations diff --git a/docs/portal/client-side-integration.md b/docs/portal/client-side-integration.md index 2db6531b6..c2059fedf 100644 --- a/docs/portal/client-side-integration.md +++ b/docs/portal/client-side-integration.md @@ -42,8 +42,8 @@ Client-side implementation options are shown in the following table. The options | Client-Side Implementation Option | Available For (Role) | Documentation Link | | :--- | :--- | :---| | UID2 JavaScript SDK | Publishers, Advertisers | [Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md) | -| Prebid.js client-side integration | Publishers only |[UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) | -| UID2 Mobile SDK | Publishers only |[UID2 Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side.md) | +| Prebid.js client-side integration | Publishers only |[Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) | +| UID2 Mobile SDK | Publishers only |[Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side.md) | ## Adding and Managing Key Pairs diff --git a/docs/ref-info/glossary-uid.md b/docs/ref-info/glossary-uid.md index f5eeebd59..318d7c208 100644 --- a/docs/ref-info/glossary-uid.md +++ b/docs/ref-info/glossary-uid.md @@ -185,13 +185,13 @@ import MdxJumpAnchor from '@site/src/components/MdxJumpAnchor';
    Client-server integration
    One of the UID2 integration approaches is to integrate partially on the client side and partially on the server side (client-server).
    For example, in a client-server integration for a publisher, the UID2 token is generated on the server side and refreshed on the client side.
    -
    Examples of documentation for publisher client-server integrations:
    - UID2 Client-Server Integration Guide for Prebid.js
    - Client-Server Integration Guide for JavaScript
    - UID2 Client-Server Integration Guide for Mobile
    +
    Examples of documentation for publisher client-server integrations:
    - Client-Server Integration Guide for Prebid.js
    - Client-Server Integration Guide for JavaScript
    - Client-Server Integration Guide for Mobile
    Client-side integration
    One of the UID2 integration approaches is to integrate entirely on the client side.
    In a client-side integration, UID2 tokens are generated and refreshed on the client side.
    For example, in a client-side integration, advertisers generate UID2 tokens on the client side for tracking pixels, and publishers generate UID2 tokens on the client side for bidstream use, as well as refreshing the tokens.
    -
    Examples of documentation for publisher client-side integrations:
    - UID2 Client-Side Integration Guide for Prebid.js
    - Client-Side Integration Guide for JavaScript
    - UID2 Client-Side Integration Guide for Mobile
    +
    Examples of documentation for publisher client-side integrations:
    - Client-Side Integration Guide for Prebid.js
    - Client-Side Integration Guide for JavaScript
    - Client-Side Integration Guide for Mobile
    Closed Operator
    Closed Operator is another term for a Private Operator.
    @@ -385,7 +385,7 @@ import MdxJumpAnchor from '@site/src/components/MdxJumpAnchor';
    Public key
    For client-side publisher integrations, the public key is one of the two values issued to publishers to uniquely identify the account. For details, see Subscription ID and Public Key.
    -
    In UID2 integrations, this value is often represented as serverPublicKey: for example, in the UID2 Client-Side Integration Guide for Prebid.js, the Client-Side Integration Guide for JavaScript, and the UID2 Client-Side Integration Guide for Mobile.
    +
    In UID2 integrations, this value is often represented as serverPublicKey: for example, in the Client-Side Integration Guide for Prebid.js, the Client-Side Integration Guide for JavaScript, and the Client-Side Integration Guide for Mobile.
    Public Operator
    A Public Operator is an entity that runs a public instance of the UID2 Operator Service. For example, The Trade Desk currently serves as a Public Operator for the UID2 framework, available to all participants.
    @@ -423,11 +423,11 @@ import MdxJumpAnchor from '@site/src/components/MdxJumpAnchor';
    Salt bucket
    A salt bucket is used to manage secret salt values, used to generate raw UID2s or UID2 tokens, over time. Each bucket contains a single current salt value, which remains active for a period of time before being rotated to a new value. Buckets can be updated independently of one another.
    There are over one million salt buckets, and each email address or phone number is assigned to a specific bucket in a deterministic manner. However, this assignment is not permanent; it might change when the bucket's current salt is rotated to a new value.
    -
    In versions of the [POST /identity/map](../endpoints/post-identity-map.md) endpoint earlier than version 3, such as [POST /identity/map (v2)](../endpoints/post-identity-map-v2.md), the endpoint returns salt bucket IDs. In v3 and later, salt bucket information is not needed.
    +
    In versions of the [POST /v3/identity/map](../endpoints/post-identity-map.md) endpoint earlier than version 3, such as [POST /v2/identity/map](../endpoints/post-identity-map-v2.md), the endpoint returns salt bucket IDs. In v3 and later, salt bucket information is not needed.
    Salt bucket ID
    A salt bucket ID is a unique string of characters that identifies a specific salt bucket. The salt bucket ID can be used to check which salt buckets have recently had their salt values updated, indicating which emails or phone numbers need their raw UID2 values regenerated.
    -
    In versions of the [POST /identity/map](../endpoints/post-identity-map.md) endpoint earlier than version 3, such as [POST /identity/map (v2)](../endpoints/post-identity-map-v2.md), the endpoint returns salt bucket IDs. In v3 and later, salt bucket information is not needed.
    +
    In versions of the [POST /v3/identity/map](../endpoints/post-identity-map.md) endpoint earlier than version 3, such as [POST /v2/identity/map](../endpoints/post-identity-map-v2.md), the endpoint returns salt bucket IDs. In v3 and later, salt bucket information is not needed.
    For an example of a salt bucket ID, see the response to the `POST /v2/identity/buckets` endpoint: Decrypted JSON Response Format. If you're using `POST /v3/identity/map`, you don't need to use `POST /v2/identity/buckets` at all.
    Salted hash
    diff --git a/docs/ref-info/integration-sample-sites.md b/docs/ref-info/integration-sample-sites.md index 0cec89d0a..da73a9cdb 100644 --- a/docs/ref-info/integration-sample-sites.md +++ b/docs/ref-info/integration-sample-sites.md @@ -62,7 +62,7 @@ This sample is for publishers who have access to DII on the client side and want - Site: [Client-Side UID2 Integration with Prebid.js](https://prebid-client.samples.uidapi.com/) - Code: [uid2-examples/web-integrations/prebid-integrations/client-side](https://github.com/IABTechLab/uid2-examples/tree/main/web-integrations/prebid-integrations/client-side) -- Doc: [UID2 Client-Side Integration Guide for Prebid.js](https://unifiedid.com/docs/guides/integration-prebid-client-side) +- Doc: [Client-Side Integration Guide for Prebid.js](https://unifiedid.com/docs/guides/integration-prebid-client-side) ### Client-Server Integration with Prebid.js @@ -70,7 +70,7 @@ This sample is for publishers who have access to DII on the server side and can - Site: [Client-Server UID2 Integration with Prebid.js](https://prebid-client-server.samples.uidapi.com/) - Code: [uid2-examples/web-integrations/prebid-integrations/client-server](https://github.com/IABTechLab/uid2-examples/tree/main/web-integrations/prebid-integrations/client-server) -- Doc: [UID2 Client-Server Integration Guide for Prebid.js](https://unifiedid.com/docs/guides/integration-prebid-client-server) +- Doc: [Client-Server Integration Guide for Prebid.js](https://unifiedid.com/docs/guides/integration-prebid-client-server) ### Deferred Client-Side Integration with Prebid.js @@ -78,7 +78,7 @@ This sample demonstrates how publishers who already have Prebid.js configured ca - Site: [Deferred Client-Side UID2 Integration with Prebid.js](https://prebid-deferred.samples.uidapi.com/) - Code: [uid2-examples/web-integrations/prebid-integrations/client-side-deferred](https://github.com/IABTechLab/uid2-examples/tree/main/web-integrations/prebid-integrations/client-side-deferred) -- Doc: [UID2 Client-Side Integration Guide for Prebid.js](https://unifiedid.com/docs/guides/integration-prebid-client-side) +- Doc: [Client-Side Integration Guide for Prebid.js](https://unifiedid.com/docs/guides/integration-prebid-client-side) ### Prebid.js with Secure Signals diff --git a/docs/ref-info/ref-integration-approaches.md b/docs/ref-info/ref-integration-approaches.md index 4d8767ca2..c4fbe9d13 100644 --- a/docs/ref-info/ref-integration-approaches.md +++ b/docs/ref-info/ref-integration-approaches.md @@ -29,9 +29,9 @@ For example: Examples of documentation for publisher client-side integrations: -- [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) +- [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) - [Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md) -- [UID2 Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side.md) +- [Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side.md) Advertisers integrating on the client side can use the JavaScript SDK: @@ -56,9 +56,9 @@ For example, in a client-server integration for a publisher, the UID2 token is g Examples of documentation for publisher client-server integrations: -- [UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) +- [Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) - [Client-Server Integration Guide for JavaScript](../guides/integration-javascript-client-server.md) -- [UID2 Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server.md) +- [Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server.md) ### Client-Server Integration: Credentials diff --git a/docs/ref-info/updates-doc.md b/docs/ref-info/updates-doc.md index 928af01a2..8128c0eb7 100644 --- a/docs/ref-info/updates-doc.md +++ b/docs/ref-info/updates-doc.md @@ -101,7 +101,7 @@ The following documents were released in this quarter. -### Identity Map v3 (Python SDK, Snowflake) +### POST /v3/identity/map (Python SDK, Snowflake) July 31, 2025 @@ -122,7 +122,7 @@ We updated the following additional implementations and corresponding documentat July 11, 2025 -We've released a new version of the Identity Map API (v3) that provides significant improvements for advertisers and data providers. This update includes documentation for the [POST /identity/map](../endpoints/post-identity-map.md) endpoint, the [SDK for Java Reference Guide](../sdks/sdk-ref-java.md#usage-for-advertisersdata-providers), and the [Advertiser/Data Provider Integration Overview](../guides/integration-advertiser-dataprovider-overview.md). +We've released a new version of the Identity Map API (v3) that provides significant improvements for advertisers and data providers. This update includes documentation for the [POST /v3/identity/map](../endpoints/post-identity-map.md) endpoint, the [SDK for Java Reference Guide](../sdks/sdk-ref-java.md#usage-for-advertisersdata-providers), and the [Advertiser/Data Provider Integration Overview](../guides/integration-advertiser-dataprovider-overview.md). @@ -406,8 +406,8 @@ July 2, 2024 We've added a section to the two mobile integration guides with instructions for mobile integration using Prebid, currently for Android only: -- [UID2 Client-Side Integration Guide for Mobile: Prebid Integration](../guides/integration-mobile-client-side#optional-uid2-integration-with-prebid-mobile-sdk) -- [UID2 Client-Server Integration Guide for Mobile: Prebid Integration](../guides/integration-mobile-client-server#optional-uid2-integration-with-prebid-mobile-sdk) +- [Client-Side Integration Guide for Mobile: Prebid Integration](../guides/integration-mobile-client-side#optional-uid2-integration-with-prebid-mobile-sdk) +- [Client-Server Integration Guide for Mobile: Prebid Integration](../guides/integration-mobile-client-server#optional-uid2-integration-with-prebid-mobile-sdk) @@ -456,8 +456,8 @@ May 17, 2024 We've added the following integration guides to support publishers who want to implement UID2 for their Android or iOS mobile apps: - [UID2 Mobile Integration Overview for Android and iOS](../guides/integration-mobile-overview) -- [UID2 Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side) -- [UID2 Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server) +- [Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side) +- [Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server) @@ -648,8 +648,8 @@ In addition, the existing guides have been restructured and simplified. For details, see: - [UID2 Integration Overview for Prebid](../guides/integration-prebid.md) -- [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) -- [UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) +- [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) +- [Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) @@ -725,15 +725,15 @@ This document was updated in January 2024 to [Client-Side Integration Guide for November 2, 2023 -The UID2 Client-Side Integration Guide for Prebid.js is a completely new document at the existing URL, covering a way of integrating UID2 with Prebid that does not require any server-side work. +The Client-Side Integration Guide for Prebid.js is a completely new document at the existing URL, covering a way of integrating UID2 with Prebid that does not require any server-side work. The content that was in the previous version of the Prebid document is now in a supplementary document, *Prebid.js Advanced Integration Guide*, for publishers who are using a Private Operator or who prefer to implement token generate on the server side. :::note These documents were further updated in later revisions. Updated links are as follows: - [UID2 Integration Overview for Prebid](../guides/integration-prebid.md) -- [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) -- [UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) +- [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) +- [Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) ::: diff --git a/docs/sdks/sdk-ref-java.md b/docs/sdks/sdk-ref-java.md index 349ef83c6..87d94dfc5 100644 --- a/docs/sdks/sdk-ref-java.md +++ b/docs/sdks/sdk-ref-java.md @@ -300,7 +300,7 @@ If you're using server-side integration (see [Publisher Integration Guide, Serve The following instructions provide an example of how to map DII to raw UID2s using the latest version of the `POST /identity/map` endpoint. -For the earlier version, see [Previous SDK Version (using POST /identity/map v2)](#previous-sdk-version-using-post-identitymap-v2). For migration steps to the latest version, see [Migration From Version Using v2 Identity Map](#migration-from-version-using-v2-identity-map). +For the earlier version, see [Previous SDK Version (using POST /v2/identity/map)](#previous-sdk-version-using-post-v2identitymap). For migration steps to the latest version, see [Migration From Version Using v2 Identity Map](#migration-from-version-using-v2-identity-map). 1. Create an IdentityMapV3Client as an instance variable: ```java @@ -487,7 +487,7 @@ The following changes are **optional** but allow you to take advantage of new v3 String rawReason = unmapped.getRawReason(); ``` -## Previous SDK Version (using POST /identity/map v2) +## Previous SDK Version (using POST /v2/identity/map) :::note An earlier version of the SDK for Java, which references the `POST /identity/map` v2 endpoint is also available, for backwards compatibility. Migrate to the current SDK for improved performance, multi-identity type support, and better UID rotation management. New integrations should not use this version. diff --git a/docs/sdks/sdk-ref-javascript-v3.md b/docs/sdks/sdk-ref-javascript-v3.md index fca8d2730..f4a706872 100644 --- a/docs/sdks/sdk-ref-javascript-v3.md +++ b/docs/sdks/sdk-ref-javascript-v3.md @@ -35,7 +35,7 @@ Use this SDK to facilitate the process of generating or establishing client iden The following sections describe the high-level [workflow](#workflow-overview) for establishing UID2 identity, provide the SDK [API reference](#api-reference), and explain the UID2 [storage format](#uid2-storage-format). :::tip -If you're using Prebid.js with the UID2 Identity Module, or with another product that has UID2 support, you probably don't need to use the SDK at all. The Prebid.js module manages everything. For details, see [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md). +If you're using Prebid.js with the UID2 Identity Module, or with another product that has UID2 support, you probably don't need to use the SDK at all. The Prebid.js module manages everything. For details, see [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md). ::: This page describes version 3 of the SDK. If you are using an earlier version, we recommend that you upgrade your integration, using the [migration guide](#migration-guide). If needed, documentation for [earlier versions of the SDK](./sdk-ref-javascript-v2.md) is also available. diff --git a/docs/sdks/sdk-ref-javascript.md b/docs/sdks/sdk-ref-javascript.md index 4f6e6ec78..20a33f5b9 100644 --- a/docs/sdks/sdk-ref-javascript.md +++ b/docs/sdks/sdk-ref-javascript.md @@ -19,7 +19,7 @@ Use this SDK to facilitate the process of generating or establishing client iden The following sections describe the high-level [workflow](#workflow-overview) for establishing UID2 identity, provide the SDK [API reference](#api-reference), and explain the UID2 [storage format](#uid2-storage-format). :::tip -If you're using Prebid.js with the UID2 Identity Module, or with another product that has UID2 support, you probably don't need to use the SDK at all. The Prebid.js module manages everything. For details, see [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md). +If you're using Prebid.js with the UID2 Identity Module, or with another product that has UID2 support, you probably don't need to use the SDK at all. The Prebid.js module manages everything. For details, see [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md). ::: For integration steps for publishers, refer to one of the following: diff --git a/docs/sharing/sharing-tokenized-from-data-bid-stream.md b/docs/sharing/sharing-tokenized-from-data-bid-stream.md index 111e90b25..761b6e335 100644 --- a/docs/sharing/sharing-tokenized-from-data-bid-stream.md +++ b/docs/sharing/sharing-tokenized-from-data-bid-stream.md @@ -37,8 +37,8 @@ The following approaches are available for encrypting the DII directly into a UI | Integration Option | Token Generated Client-Side or Server-Side? | Integration Guide | | :--- | :--- | :--- | -| Prebid.js | Client-Side | [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) | -| Prebid.js | Server-Side | [UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) | +| Prebid.js | Client-Side | [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) | +| Prebid.js | Server-Side | [Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) | | JavaScript SDK | Client-Side | [Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md) | | JavaScript SDK | Server-Side | [Client-Server Integration Guide for JavaScript](../guides/integration-javascript-client-server.md) | | Java SDK | Server-Side | [SDK for Java Reference Guide](../sdks/sdk-ref-java.md) | diff --git a/docs/snippets/_snpt-private-operator-upgrade-policy.mdx b/docs/snippets/_snpt-private-operator-upgrade-policy.mdx index a086589c9..2a3ef4e9c 100644 --- a/docs/snippets/_snpt-private-operator-upgrade-policy.mdx +++ b/docs/snippets/_snpt-private-operator-upgrade-policy.mdx @@ -3,5 +3,5 @@ To maintain security and operational integrity, outdated operator versions will be disabled after 12 months, which may cause affected deployments to shut down or fail to start. Upgrading ensures the use of the latest security and feature enhancements. We recommend upgrading proactively to avoid disruptions. :::note -For critical security or operational issues, or where contract terms apply, we reserve the right to enforce tighter upgrade timelines for private operators. +For critical security or operational issues, or where contract terms apply, we reserve the right to enforce tighter upgrade timelines for Private Operators. ::: \ No newline at end of file diff --git a/docs/snippets/_snpt-publisher-implementation-resources.mdx b/docs/snippets/_snpt-publisher-implementation-resources.mdx index b8b73bef9..241d170ee 100644 --- a/docs/snippets/_snpt-publisher-implementation-resources.mdx +++ b/docs/snippets/_snpt-publisher-implementation-resources.mdx @@ -19,8 +19,8 @@ For a detailed summary of web integration options, see [Publisher Web Integratio | Integration Type| Documentation | Content Description | | :--- | :--- | :--- | | Prebid (Overview) | [UID2 Integration Overview for Prebid](../guides/integration-prebid.md) | An overview of options for publishers who want to integrate with UID2 and generate UID2 tokens (advertising tokens) to be passed by Prebid.js or the Prebid Mobile SDK in the RTB bidstream. | -| Prebid.js Client-Side Integration | [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) | A guide for publishers who want to request UID2 tokens client-side, which is the easiest implementation approach, and choose to have Prebid.js manage the following: | -| Prebid.js Client-Server Integration | [UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) | A guide for publishers who want to integrate with UID2 and generate UID2 tokens to be passed by Prebid.js in the RTB bidstream, but want to generate tokens server-side: for example, publishers who are using a Private Operator. | +| Prebid.js Client-Side Integration | [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) | A guide for publishers who want to request UID2 tokens client-side, which is the easiest implementation approach, and choose to have Prebid.js manage the following: | +| Prebid.js Client-Server Integration | [Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) | A guide for publishers who want to integrate with UID2 and generate UID2 tokens to be passed by Prebid.js in the RTB bidstream, but want to generate tokens server-side: for example, publishers who are using a Private Operator. | | JavaScript (Overview) | [UID2 Integration Overview for JavaScript](../guides/integration-javascript.md) | An overview of options for publishers who want to integrate with UID2 using the JavaScript SDK. | | JavaScript Client-Side Integration | [Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md) | A guide for publishers who want to integrate with UID2 using only client-side JavaScript changes, which is the easiest implementation approach.
    The SDK for JavaScript manages token generation and token refresh automatically. | | JavaScript Client-Server Integration | [Client-Server Integration Guide for JavaScript](../guides/integration-javascript-client-server.md) | A publisher guide covering standard web integration scenarios that use the SDK for JavaScript and require tokens to be generated on the server side and passed to the publisher web pages. | @@ -55,8 +55,8 @@ The following resources are available for publishers integrating with Prebid. | Integration Type| Documentation | Content Description | | :--- | :--- | :--- | | Prebid (Overview) | [UID2 Integration Overview for Prebid](../guides/integration-prebid.md) | An overview of options for publishers who want to integrate with UID2 and generate UID2 tokens (advertising tokens) to be passed by Prebid.js or the Prebid Mobile SDK in the RTB bidstream. | -| Prebid.js Client-Side Integration | [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) | A guide for publishers who want to request UID2 tokens client-side, which is the easiest implementation approach, and choose to have Prebid.js manage the following: | -| Prebid.js Client-Server Integration | [UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) | A guide for publishers who want to integrate with UID2 and generate UID2 tokens to be passed by Prebid.js in the RTB bidstream, but want to generate tokens server-side: for example, publishers who are using a Private Operator. | +| Prebid.js Client-Side Integration | [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) | A guide for publishers who want to request UID2 tokens client-side, which is the easiest implementation approach, and choose to have Prebid.js manage the following: | +| Prebid.js Client-Server Integration | [Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) | A guide for publishers who want to integrate with UID2 and generate UID2 tokens to be passed by Prebid.js in the RTB bidstream, but want to generate tokens server-side: for example, publishers who are using a Private Operator. | | Prebid.js on Mobile | [UID2 Mobile Integration for Prebid.js](../guides/integration-prebid-mobile-summary.md) | A summary of information resources for UID2 integration with Prebid.js on mobile devices. | ### Google Ad Manager Integrations diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/post-identity-buckets.md b/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/post-identity-buckets.md index 043ac65ff..e6dd96bc2 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/post-identity-buckets.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/post-identity-buckets.md @@ -17,7 +17,7 @@ Used by: このエンドポイントは、主に広告主とデータプロバ :::important 最新バージョン (v3) の `POST /v3/identity/map` を使用している場合は、`POST /identity/buckets` を使用する必要はありません。以前のバージョン (v2) の `POST /v2/identity/map` を使用している場合にのみ必要です。 -v2 バージョンを使用している場合は、改善点を活用するためにできるだけ早くアップグレードすることをお勧めします。移行ガイダンスは、[Migration from v2 Identity Map](post-identity-map.md#migration-from-v2-identity-map) を参照してください。 +v2 バージョンを使用している場合は、改善点を活用するためにできるだけ早くアップグレードすることをお勧めします。移行ガイダンスは、[Migration from POST /v2/identity/map](post-identity-map.md#migration-from-post-v2identitymap) を参照してください。 ::: ## Request Format diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/post-identity-map-v2.md b/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/post-identity-map-v2.md index c938f0d71..3442a374f 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/post-identity-map-v2.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/post-identity-map-v2.md @@ -1,5 +1,5 @@ --- -title: POST /identity/map (v2) +title: POST /v2/identity/map description: DII を raw UID2 とソルトバケット ID にマッピング。 hide_table_of_contents: false sidebar_position: 07 @@ -7,7 +7,7 @@ sidebar_position: 07 import Link from '@docusaurus/Link'; -# POST /identity/map (v2) +# POST /v2/identity/map 複数のメールアドレス、電話番号、またはそれぞれのハッシュを、raw UID2 と ソルトバケット ID にマッピングします。このエンドポイントを使用して、オプトアウト情報の更新をチェックすることもできます。 @@ -17,10 +17,10 @@ UID2 のオプトアウトワークフローとユーザーがオプトアウト ## Version -このドキュメントは、このエンドポイントのバージョン 2 のものであり、最新バージョンではありません。最新バージョン v3 の詳細は、[POST /identity/map](post-identity-map.md) を参照してください。 +このドキュメントは、このエンドポイントのバージョン 2 のものであり、最新バージョンではありません。最新バージョン v3 の詳細は、[POST /v3/identity/map](post-identity-map.md) を参照してください。 :::note -以前のバージョンを使用している場合は、改善点を活用するためにできるだけ早くアップグレードすることを推奨します。移行ガイダンスは、[Migration from v2 Identity Map](post-identity-map.md#migration-from-v2-identity-map) を参照してください。廃止に関する情報は、[Deprecation Schedule: Endpoint Versions](../ref-info/deprecation-schedule.md#endpoint-versions) を参照してください。 +以前のバージョンを使用している場合は、改善点を活用するためにできるだけ早くアップグレードすることを推奨します。移行ガイダンスは、[Migration from POST /v2/identity/map](post-identity-map.md#migration-from-post-v2identitymap) を参照してください。廃止に関する情報は、[Deprecation Schedule: Endpoint Versions](../ref-info/deprecation-schedule.md#endpoint-versions) を参照してください。 ::: ## Batch Size and Request Parallelization Requirements diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/post-identity-map.md b/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/post-identity-map.md index ef4c99caf..e7e48a4b4 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/post-identity-map.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/post-identity-map.md @@ -1,5 +1,5 @@ --- -title: POST /identity/map +title: POST /v3/identity/map description: DII を raw UID2 にマップします。 hide_table_of_contents: false sidebar_position: 08 @@ -9,7 +9,7 @@ displayed_sidebar: docs import Link from '@docusaurus/Link'; import SnptPOSTIdentityMapImprovements from '../snippets/_snpt-post-identity-map-improvements-v3.mdx'; -# POST /identity/map +# POST /v3/identity/map 複数のメールアドレス、電話番号、またはそれぞれのハッシュを、raw UID2 にマッピングします。このエンドポイントを使用して、オプトアウト情報の更新をチェックしたり、raw UID2 の更新が可能な時期を確認したり、現在の raw UID2 が発行されてから 90 日未満の場合に前の UID2 を表示することもできます。 @@ -21,7 +21,7 @@ UID2 のオプトアウト手順とユーザーがオプトアウトする方法 このドキュメントは、エンドポイントの最新版であるバージョン 3 を対象としています。 -必要に応じて、以前のバージョンのドキュメントも利用可能です: [POST /identity/map (v2)](post-identity-map-v2.md) を参照してください。 +必要に応じて、以前のバージョンのドキュメントも利用可能です: [POST /v2/identity/map](post-identity-map-v2.md) を参照してください。 ## Batch Size and Request Parallelization Requirements @@ -200,7 +200,7 @@ raw UID2 はリフレッシュタイムスタンプの前では変化しませ `status` プロパティの値が `success` 以外の場合、`message` フィールドには問題に関する追加情報が提供されます。 -## Migration from v2 Identity Map +## Migration from POST /v2/identity/map 以下のセクションでは、以前のバージョンからバージョン 3 への移行に関する一般的な情報とガイダンスを提供します: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/post-token-generate.md b/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/post-token-generate.md index 449ef7947..ad3aa7cce 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/post-token-generate.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/post-token-generate.md @@ -55,7 +55,7 @@ Used by: このエンドポイントは、主にパブリッシャーが使用 ### Request Examples :::important -サービスへのアクセスに使用する API キーを秘密にしておくため、[POST /token/generate](post-token-generate.md) エンドポイントは、[POST /token/refresh](post-token-refresh.md) とは異なり、Server-Side から呼び出す必要があります。Client-Side でトークンを生成する場合は、[Client-Side Integration Options](../guides/integration-options-publisher-web.md#client-side-integration-options) (Web ベースの実装) または [UID2 Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side.md) を参照してください。 +サービスへのアクセスに使用する API キーを秘密にしておくため、[POST /token/generate](post-token-generate.md) エンドポイントは、[POST /token/refresh](post-token-refresh.md) とは異なり、Server-Side から呼び出す必要があります。Client-Side でトークンを生成する場合は、[Client-Side Integration Options](../guides/integration-options-publisher-web.md#client-side-integration-options) (Web ベースの実装) または [Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side.md) を参照してください。 ::: 以下は、各パラメータの暗号化されていない JSON リクエストボディの例で、このうちの 1 つはトークン生成リクエストに含める必要があります: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/summary-endpoints.md b/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/summary-endpoints.md index 95f1bae60..40eb0c951 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/summary-endpoints.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/endpoints/summary-endpoints.md @@ -38,7 +38,7 @@ import Link from '@docusaurus/Link'; 以下のエンドポイントは、広告主とサードパーティのデータプロバイダーが使用します。パブリッシャーはこれらのエンドポイントを使用する必要はありません。 -### Latest Identity Map Endpoint (v3) +### Latest POST /v3/identity/map Endpoint 最新の Identity Map インテグレーションでは、1 つのエンドポイント `POST /identity/map` を呼び出すだけで済みます。`POST /identity/buckets` エンドポイントはワークフローの一部ではありません。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-auth.md b/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-auth.md index d3622d03d..f41eb228c 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-auth.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-auth.md @@ -17,5 +17,5 @@ Server-Side 実装で UID2 エンドポイントへの認証を行うには、 - API リクエストを暗号化し、API レスポンスを復号化するための Client Secret 。これは、[POST /token/refresh](../endpoints/post-token-refresh.md) を除くすべてのエンドポイントで必要です。
    詳細と、いくつかのプログラミング言語での暗号化/復号化の例は、[Encrypting Requests and Decrypting Responses](gs-encryption-decryption.md) を参照してください。 :::note -パブリッシャーの場合、Client-Side に UID2 を実装しているなら、認証と認可は Prebid.js ([UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) を参照) や JavaScript SDK ([Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md) を参照) などの実装によって自動的に管理されます。 +パブリッシャーの場合、Client-Side に UID2 を実装しているなら、認証と認可は Prebid.js ([Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) を参照) や JavaScript SDK ([Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.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 07bf59c9f..8eab04bc1 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 @@ -14,8 +14,8 @@ UID2 の
  • Subscription ID
  • Public key
    • これら 2 つをあわせて client keypair と呼ぶこともあります。 | 次のいずれかを使用したインテグレーション: | -| Client-Server 実装を使用する参加者 | 次の両方: | 次のいずれかを使用したインテグレーション: | +| Client-Side 実装を使用する参加者 | 次の両方: これら 2 つをあわせて client keypair と呼ぶこともあります。 | 次のいずれかを使用したインテグレーション: | +| Client-Server 実装を使用する参加者 | 次の両方: | 次のいずれかを使用したインテグレーション: | | Server-Side 実装を使用する参加者 | 次の両方: | 次のいずれかを使用したインテグレーション: | ## Separate Credentials Per Environment/Role @@ -23,7 +23,7 @@ UID2 の     環境 と本番環境の両方を使用している場合、それぞれの環境用に別々の認証情報が提供されます。詳細は [Getting Your Credentials](#getting-your-credentials) を参照してください。 さらに、いくつかのケースでは、異なるシナリオに対して異なるセットの認証情報を持つことを推奨しますが、必須ではありません。たとえば: -- UID2 Token を生成するパブリッシャーである場合([POST /token/generate](../endpoints/post-token-generate.md) または他の方法で)、自分のために raw UID2 を生成/マッピングする場合([POST /identity/map](../endpoints/post-identity-map.md) を参照)、それぞれの活動に対して異なる認証情報を持つことがあります。 +- UID2 Token を生成するパブリッシャーである場合([POST /token/generate](../endpoints/post-token-generate.md) または他の方法で)、自分のために raw UID2 を生成/マッピングする場合([POST /v3/identity/map](../endpoints/post-identity-map.md) を参照)、それぞれの活動に対して異なる認証情報を持つことがあります。 - 広告主の場合、広告主キーを使用して複数のサービスプロバイダーが運用するシナリオで、各サービスプロバイダーに対して異なる認証情報を割り当てることができます。 ## Getting Your Credentials @@ -79,7 +79,7 @@ To get your credentials, ask your UID2 contact. ## Subscription ID and Public Key -Client-Side の実装([UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) または [Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md) を参照) を使用している場合は、以下の認証情報を受け取ります: +Client-Side の実装([Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) または [Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md) を参照) を使用している場合は、以下の認証情報を受け取ります: - **Subscription ID**: UID2 Service に対してサイトを識別する値です。 - **Public key**: この値は暗号化に使用されます。 @@ -97,7 +97,7 @@ Notes: ## API Key and Client Secret -Client-Server または Server-Side の実装を使用している場合([UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) または [Client-Server Integration Guide for JavaScript](../guides/integration-javascript-client-server.md) を参照)、API Key と Client Secret を使用して、Operator Service に接続し、API エンドポイントを呼び出すことができます。これらの値は、サービスの参加者を識別します。 +Client-Server または Server-Side の実装を使用している場合([Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) または [Client-Server Integration Guide for JavaScript](../guides/integration-javascript-client-server.md) を参照)、API Key と Client Secret を使用して、Operator Service に接続し、API エンドポイントを呼び出すことができます。これらの値は、サービスの参加者を識別します。 以下は API Key と Client Secret に関する情報です: - これらの値は安全に保管する必要があります。詳細は、[Security of API Key and Client Secret](#security-of-api-key-and-client-secret) を参照してください。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-encryption-decryption.md b/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-encryption-decryption.md index 1124507a9..e686d1345 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-encryption-decryption.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-encryption-decryption.md @@ -14,7 +14,7 @@ import SnptIdentityGenerateResponse from '../snippets/_snpt-example-identity-gen # Encrypting Requests and Decrypting Responses :::note -パブリッシャーの場合、Client-Side に UID2 を実装しているなら、暗号化と復号化は、Prebid.js ([UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) を参照) や JavaScript SDK ([Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md) を参照) などの実装によって自動的に管理されます。 +パブリッシャーの場合、Client-Side に UID2 を実装しているなら、暗号化と復号化は、Prebid.js ([Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) を参照) や JavaScript SDK ([Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md) を参照) などの実装によって自動的に管理されます。 ::: ほとんどすべての UID2 [endpoints](../endpoints/summary-endpoints.md) では、エンドポイントに送られるリクエストは [暗号化](#encrypting-requests) され、エンドポイントからのレスポンスは [復号化](#decrypting-responses) する必要があります。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-faqs.md b/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-faqs.md index 9c9972f07..6161a6231 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-faqs.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-faqs.md @@ -107,8 +107,8 @@ UID2 フレームワークを使用するパブリッシャーからのよくあ トークン生成の呼び出しは、Server-Side と Client-Side のどちらで行うべきですか？ UID2 Token は、Client-Side、Server-Sideのどちらでも生成できます。詳細は、以下を参照してください: -- Prebid.js を使用して Client-Side からトークンを生成します: [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md). -- Prebid.js を使用して Server-Side からトークンを生成します: [UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md). +- Prebid.js を使用して Client-Side からトークンを生成します: [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md). +- Prebid.js を使用して Server-Side からトークンを生成します: [Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md). - その他の Server-Side オプション: [Publisher Integrations](../guides/summary-guides.md#publisher-integrations). #### Can I make token refresh calls from the client side? @@ -221,9 +221,9 @@ raw UID2 は、リフレッシュタイムスタンプの前では変化しま インクリメンタルアップデートの場合、オーディエンスの更新は毎日行うことを推奨します。 -特定のユーザーの raw UID2 は、およそ年に 1 回変化します。[POST /identity/map](../endpoints/post-identity-map.md) エンドポイントの最新バージョンでは、各 raw UID2 がリフレッシュされる可能性のある時点を示すリフレッシュタイムスタンプが提供されます。オーディエンスターゲティングのために raw UID2 を最新かつ有効な状態に保つために、これらのタイムスタンプを毎日確認することを推奨します。 +特定のユーザーの raw UID2 は、およそ年に 1 回変化します。[POST /v3/identity/map](../endpoints/post-identity-map.md) エンドポイントの最新バージョンでは、各 raw UID2 がリフレッシュされる可能性のある時点を示すリフレッシュタイムスタンプが提供されます。オーディエンスターゲティングのために raw UID2 を最新かつ有効な状態に保つために、これらのタイムスタンプを毎日確認することを推奨します。 -このエンドポイントの以前のバージョン ([POST /identity/map (v2)](../endpoints/post-identity-map-v2.md)) を参照する実装の場合: +このエンドポイントの以前のバージョン ([POST /v2/identity/map](../endpoints/post-identity-map-v2.md)) を参照する実装の場合: 各 ソルトバケット はおよそ年に 1 回更新されますが、個々のバケットの更新は年間を通じて分散されています。つまり、全バケットの約 1/365 が毎日ローテーションされます。忠実度が重要な場合は、[POST /identity/buckets](../endpoints/post-identity-buckets.md) エンドポイントをより頻繁に（例：1 時間ごと）呼び出すことを検討してください。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides-operator-private/_category_.json b/i18n/ja/docusaurus-plugin-content-docs/current/guides-operator-private/_category_.json index 041dc9154..b80ef1e7b 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides-operator-private/_category_.json +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides-operator-private/_category_.json @@ -3,6 +3,6 @@ "position": 06, "link": { "type": "generated-index", - "description": "Information for private operators." + "description": "Information for Private Operators." } } 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 3485d0f32..d410b30b2 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 @@ -134,7 +134,7 @@ UID2 Operator Service< UID2 のオプトアウト手順の詳細と、ユーザーがどのようにオプトアウトできるかは、[User Opt-Out](../getting-started/gs-opt-out.md) を参照してください。 -## Using POST /identity/map Version 2 +## Using POST /v2/identity/map :::note 以下の情報は、`POST /identity/map` エンドポイントのバージョン 2 またはそれ以前を使用している場合にのみ関連し、参照用に提供されています。新しい実装では最新バージョンを使用する必要があります。手順は、[High-Level Steps](#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 aebf83cc5..de6b6c132 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 @@ -49,7 +49,7 @@ UID2 とインテグレーションする広告主とデータプロバイダー 6. [Monitor for Opt-Out Status](#6-monitor-for-opt-out-status) :::note -[POST /identity/map](../endpoints/post-identity-map.md) エンドポイントのバージョン 3 より前のバージョンを使用している場合は、[Using POST /identity/map Version 2](#using-post-identitymap-version-2) を参照してください。このバージョンを使用している場合は、強化された機能を利用するためにできるだけ早くアップグレードすることを推奨します。 +[POST /identity/map](../endpoints/post-identity-map.md) エンドポイントのバージョン 3 より前のバージョンを使用している場合は、[Using POST /v2/identity/map](#using-post-v2identitymap) を参照してください。このバージョンを使用している場合は、強化された機能を利用するためにできるだけ早くアップグレードすることを推奨します。 ::: ## Summary of Implementation Options @@ -152,7 +152,7 @@ UID2 Operator Service< UID2 オプトアウトワークフローの詳細や、ユーザーがオプトアウトする方法は、[User Opt-Out](../getting-started/gs-opt-out.md) を参照してください。 -## Using POST /identity/map Version 2 +## Using POST /v2/identity/map :::note 以下の情報は、`POST /identity/map` エンドポイントの以前のバージョン 2 を使用するインテグレーションアプローチにのみ関連し、参照用に提供されています。新しい実装では最新バージョンを使用する必要があります: [High-Level Steps](#high-level-steps) を参照してください。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-ctv-guide.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-ctv-guide.md index ca516b70d..6d1115b6c 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-ctv-guide.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-ctv-guide.md @@ -79,14 +79,14 @@ Client-Side オプションは、UID2 Token を完全に Client-Side で管理 このセットアップでは、すべてのコード変更が CTV アプリ内で行う必要があります。 -この方法で実装するには、[UID2 Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) の手順に従ってください。 +この方法で実装するには、[Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) の手順に従ってください。 次の表は、対応するオペレーティングシステムと、関連するドキュメントリソースへのリンクを示しています。 | Operating System | Integration Guide | Link to SDK Guide | | :--- | :--- | :--- | -| [Apple tvOS](https://developer.apple.com/tvos/) | [UID2 Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side.md) | [SDK for iOS Reference Guide](../sdks/sdk-ref-ios.md) | -| [Android TV](https://www.android.com/tv/) | [UID2 Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side.md) | [SDK for Android Reference Guide](../sdks/sdk-ref-android.md) | +| [Apple tvOS](https://developer.apple.com/tvos/) | [Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side.md) | [SDK for iOS Reference Guide](../sdks/sdk-ref-ios.md) | +| [Android TV](https://www.android.com/tv/) | [Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side.md) | [SDK for Android Reference Guide](../sdks/sdk-ref-android.md) | ### Server-Side Integration for CTV Apps @@ -113,14 +113,14 @@ Server-Side コードが Java または Python である場合、UID2 SDK のい - トークンは Server-Side で生成されます。 - トークンは CTV アプリ内から必要に応じて Client-Side でリフレッシュされます。 -この方法で実装するには、[UID2 Client-Server Integration Guide for Mobile](integration-mobile-client-server.md) の手順に従ってください。 +この方法で実装するには、[Client-Server Integration Guide for Mobile](integration-mobile-client-server.md) の手順に従ってください。 次の表は、対応するオペレーティングシステムと、関連するドキュメントリソースへのリンクを示しています。 | Operating System | Integration Guide | Link to SDK Guide | | :--- | :--- | :--- | -| [Apple tvOS](https://developer.apple.com/tvos/) | [UID2 Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server.md) | [SDK for iOS Reference Guide](../sdks/sdk-ref-ios.md) | -| [Android TV](https://www.android.com/tv/) | [UID2 Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server.md) | [SDK for Android Reference Guide](../sdks/sdk-ref-android.md) | +| [Apple tvOS](https://developer.apple.com/tvos/) | [Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server.md) | [SDK for iOS Reference Guide](../sdks/sdk-ref-ios.md) | +| [Android TV](https://www.android.com/tv/) | [Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server.md) | [SDK for Android Reference Guide](../sdks/sdk-ref-android.md) | ## Best Practices diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-dsp-no-sdk.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-dsp-no-sdk.md index f0b7faa3c..08fbd474a 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-dsp-no-sdk.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-dsp-no-sdk.md @@ -87,8 +87,8 @@ This step, which is only for tokens generated on the client side, is additional For more information about client-side UID2 integration, refer to one of these integration guides: - [Client-Side Integration Guide for JavaScript](integration-javascript-client-side.md) -- [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) -- [UID2 Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) +- [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) +- [Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) --> ### Make Sure Token Lifetime and Expiration Are Valid @@ -128,8 +128,8 @@ Client-Side で生成されたトークンの場合、トークンを復号化 Client-Side UID2 インテグレーションの詳細は、以下のインテグレーションガイドのいずれかを参照してください: - [Client-Side Integration Guide for JavaScript](integration-javascript-client-side.md) -- [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) -- [UID2 Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) +- [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) +- [Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) ## Honor User Opt-Out After Token Decryption diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-mobile-client-server.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-mobile-client-server.md index d65b1db58..76a1de56c 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-mobile-client-server.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-mobile-client-server.md @@ -1,7 +1,7 @@ --- -title: UID2 Client-Server Integration Guide for Mobile +title: Client-Server Integration Guide for Mobile sidebar_label: Client-Server Integration for Mobile -pagination_label: UID2 Client-Server Integration Guide for Mobile +pagination_label: Client-Server Integration Guide for Mobile description: トークンをサーバーで生成し、クライアントで更新するモバイルインテグレーションの設定。 hide_table_of_contents: false sidebar_position: 04 @@ -19,13 +19,13 @@ import SnptGMAIMA_Plugins from '../snippets/_snpt-mobile_docs_gmaima-plugin-gss. import SnptPrebidMobileSDK from '../snippets/_snpt-mobile_docs_prebid-mobile.mdx'; import SnptErrorResponseStates from '../snippets/_snpt-mobile-docs-error-response-states.mdx'; -# UID2 Client-Server Integration Guide for Mobile +# Client-Server Integration Guide for Mobile このガイドは、Public Operator または Private Operator を介して Server-Side で UID2 Token を生成し、そのトークンとユーザー ID をモバイルアプリに渡して UID2 とインテグレーションしたいモバイルアプリパブリッシャー向けです。モバイルアプリは、そのトークンを ビッドストリーム に使用するために渡します。 これは Client-Server インテグレーションと呼ばれます。これは、いくつかのインテグレーションステップがクライアントサイドで行われ、いくつかがサーバーサイドで行われるためです。 -Client-Side のみの変更で UID2 とインテグレーションしたい場合 (つまり、すべてのインテグレーション変更がモバイルアプリ内で行われる場合) は、代わりに [UID2 Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) を参照してください。 +Client-Side のみの変更で UID2 とインテグレーションしたい場合 (つまり、すべてのインテグレーション変更がモバイルアプリ内で行われる場合) は、代わりに [Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) を参照してください。 このページでは、インテグレーション手順の概要と、追加のドキュメントへのリンクを提供します。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-mobile-client-side.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-mobile-client-side.md index ab2e18b08..99e8e13fc 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-mobile-client-side.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-mobile-client-side.md @@ -1,7 +1,7 @@ --- -title: UID2 Client-Side Integration Guide for Mobile +title: Client-Side Integration Guide for Mobile sidebar_label: Client-Side Integration for Mobile -pagination_label: UID2 Client-Side Integration Guide for Mobile +pagination_label: Client-Side Integration Guide for Mobile description: Client-Side でトークン生成とリフレッシュの両方を行うモバイルインテグレーションの設定。 hide_table_of_contents: false sidebar_position: 04 @@ -19,7 +19,7 @@ import SnptGMAIMA_Plugins from '../snippets/_snpt-mobile_docs_gmaima-plugin-gss. import SnptPrebidMobileSDK from '../snippets/_snpt-mobile_docs_prebid-mobile.mdx'; import SnptErrorResponseStates from '../snippets/_snpt-mobile-docs-error-response-states.mdx'; -# UID2 Client-Side Integration Guide for Mobile +# Client-Side Integration Guide for Mobile このガイドは、モバイルアプリのみの変更で UID2 とインテグレーションしたいモバイルアプリパブリッシャー向けです。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-mobile-overview.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-mobile-overview.md index 3e0f85ebd..11e305cdb 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-mobile-overview.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-mobile-overview.md @@ -12,7 +12,7 @@ import Link from '@docusaurus/Link'; import SnptIntegratingWithSSO from '../snippets/_snpt-integrating-with-sso.mdx'; import SnptPreparingEmailsAndPhoneNumbers from '../snippets/_snpt-preparing-emails-and-phone-numbers.mdx'; -# UID2 Mobile Integration Overview for Android and iOS +# Mobile Integration Overview for Android and iOS このガイドは、SDK for Android または SDK for iOS を使用して UID2 とインテグレーションしたいモバイルアプリのパブリッシャー向けのインテグレーションオプションの概要です。 @@ -86,8 +86,8 @@ UID2 mobile SDK を使用して UID2 とインテグレーションするため | Scenario | Option | Integration Guide | | :--- | :--- | :--- | -| Client-Side/モバイルアプリ内で DII（メールアドレスまたは電話番号）にアクセス可能であり、変更内容をアプリ内のみで保持したい。 | Client-Side integration | [UID2 Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) | -| Server-Side でのみ DII にアクセス可能であり、Server-Side で UID2 Token を生成するために必要な開発が可能だが、Client-Side でトークンをリフレッシュしたい場合、または Private Operator を使用している場合。 | Client-Server Integration | [UID2 Client-Server Integration Guide for Mobile](integration-mobile-client-server.md) | +| Client-Side/モバイルアプリ内で DII（メールアドレスまたは電話番号）にアクセス可能であり、変更内容をアプリ内のみで保持したい。 | Client-Side integration | [Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) | +| Server-Side でのみ DII にアクセス可能であり、Server-Side で UID2 Token を生成するために必要な開発が可能だが、Client-Side でトークンをリフレッシュしたい場合、または Private Operator を使用している場合。 | Client-Server Integration | [Client-Server Integration Guide for Mobile](integration-mobile-client-server.md) | | Server-Side でのみ DII にアクセス可能であり、Server-Side で UID2 Token を生成するために必要な開発が可能な場合、または Private Operator を使用している場合。 | Server-Side Integration | [UID2 Server-Side Integration Guide for Mobile](integration-mobile-server-side.md) | ### Generating, Storing, and Refreshing the UID2 Token @@ -106,12 +106,12 @@ UID2 mobile SDK を使用して UID2 とインテグレーションするため UID2 Android SDK [SDK for Android Reference Guide](../sdks/sdk-ref-android.md) - 以下のいずれか: + 以下のいずれか: UID2 iOS SDK [SDK for iOS Reference Guide](../sdks/sdk-ref-ios.md) - 以下のいずれか: + 以下のいずれか: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-options-publisher-web.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-options-publisher-web.md index c067264fc..10b0c7e70 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-options-publisher-web.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-options-publisher-web.md @@ -85,7 +85,7 @@ Client-Side のインテグレーションを選択した場合、アカウン | Option | Documentation | | :--- | :--- | -| Prebid.js client-side implementation (8.21.0 or later) | [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | +| Prebid.js client-side implementation (8.21.0 or later) | [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | | SDK for JavaScript, client-side implementation | [Client-Side Integration Guide for JavaScript](integration-javascript-client-side.md) | ### Server-Side Integration Options @@ -115,8 +115,8 @@ Server-Side で UID2 Token を生成することには、次のような利点 | Option | Documentation | | :--- | :--- | -| Prebid.js client-side implementation (8.21.0 or later) | [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | -| Prebid.js client-server implementation (7.53.0 or later) | [UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | +| Prebid.js client-side implementation (8.21.0 or later) | [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | +| Prebid.js client-server implementation (7.53.0 or later) | [Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | | SDK for JavaScript, client-side implementation | [Client-Side Integration Guide for JavaScript](integration-javascript-client-side.md) | | SDK for JavaScript, client-server implementation | [Client-Server Integration Guide for JavaScript](integration-javascript-client-server.md) | | SDK for Java | - [Publisher Integration Guide, Server-Side](integration-publisher-server-side.md)
    - [SDK for Java](../sdks/sdk-ref-java.md) | @@ -131,8 +131,8 @@ Server-Side で UID2 Token を生成することには、次のような利点 | Option | Documentation | | :--- | :--- | -| Prebid.js client-side implementation (8.21.0 or later) | [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | -| Prebid.js client-server implementation (7.53.0 or later) | [UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | +| Prebid.js client-side implementation (8.21.0 or later) | [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | +| Prebid.js client-server implementation (7.53.0 or later) | [Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | | Google Ad Manager Secure Signals| [Google Ad Manager Secure Signals Integration Guide](integration-google-ss.md) | :::note diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-prebid-client-server.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-prebid-client-server.md index 1c52a6f01..191f857dc 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-prebid-client-server.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-prebid-client-server.md @@ -1,5 +1,5 @@ --- -title: UID2 Client-Server Integration Guide for Prebid.js +title: Client-Server Integration Guide for Prebid.js sidebar_label: Client-Server Integration for Prebid.js pagination_label: UID2 Client-Server Integration for Prebid.js description: Client-Server での Prebid.js インテグレーションの設定に関する情報。 @@ -14,7 +14,7 @@ import SnptPreparingEmailsAndPhoneNumbers from '../snippets/_snpt-preparing-emai import SnptAddPrebidjsToYourSite from '../snippets/_snpt-prebid-add-prebidjs-to-your-site.mdx'; import SnptStoreUID2TokenInBrowser from '../snippets/_snpt-prebid-storing-uid2-token-in-browser.mdx'; -# UID2 Client-Server Integration Guide for Prebid.js +# Client-Server Integration Guide for Prebid.js このガイドは、Server-Side で DII (メールアドレスまたは電話番号) にアクセスでき、UID2 とインテグレーションして、RTB ビッドストリームで Prebid.js によって渡される UID2 Token (Advertising Token) を生成したいパブリッシャー向けのものです。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-prebid-client-side.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-prebid-client-side.md index d6a57397a..4dd3e7737 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-prebid-client-side.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-prebid-client-side.md @@ -1,7 +1,7 @@ --- -title: UID2 Client-Side Integration Guide for Prebid.js +title: Client-Side Integration Guide for Prebid.js sidebar_label: Client-Side Integration for Prebid.js -pagination_label: UID2 Client-Side Integration for Prebid.js +pagination_label: Client-Side Integration for Prebid.js description: Client-Side での Prebid.js インテグレーションの設定に関する情報。 hide_table_of_contents: false sidebar_position: 04 @@ -14,7 +14,7 @@ import SnptPreparingEmailsAndPhoneNumbers from '../snippets/_snpt-preparing-emai import SnptAddPrebidjsToYourSite from '../snippets/_snpt-prebid-add-prebidjs-to-your-site.mdx'; import SnptStoreUID2TokenInBrowser from '../snippets/_snpt-prebid-storing-uid2-token-in-browser.mdx'; -# UID2 Client-Side Integration Guide for Prebid.js +# Client-Side Integration Guide for Prebid.js このガイドは、Client-Side で DII (メールアドレスまたは電話番号) にアクセスでき、UID2 とインテグレーションして、RTB ビッドストリームで Prebid.js によって渡される UID2 Token (Advertising Token) を生成したいパブリッシャー向けのものです。 @@ -26,7 +26,7 @@ Prebid.js を使用して UID2 とインテグレーションするには、サ -以前のバージョンの Prebid.js を使用する必要がある場合は、代わりに [UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) で説明している実装ソリューションを使用してください。 +以前のバージョンの Prebid.js を使用する必要がある場合は、代わりに [Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) で説明している実装ソリューションを使用してください。 ## Integrating with Single Sign-On (SSO) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-prebid-mobile-summary.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-prebid-mobile-summary.md index 1d544f977..26d52bda3 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-prebid-mobile-summary.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-prebid-mobile-summary.md @@ -16,5 +16,5 @@ UID2 の Prebid とのインテグレーションは、Prebid Mobile SDK オプ 詳細は以下のモバイルインテグレーションガイドのセクションを参照してください: -- [UID2 Client-Side Integration Guide for Mobile: Prebid Integration](integration-mobile-client-side#optional-uid2-integration-with-prebid-mobile-sdk) -- [UID2 Client-Server Integration Guide for Mobile: Prebid Integration](integration-mobile-client-server#optional-uid2-integration-with-prebid-mobile-sdk) +- [Client-Side Integration Guide for Mobile: Prebid Integration](integration-mobile-client-side#optional-uid2-integration-with-prebid-mobile-sdk) +- [Client-Server Integration Guide for Mobile: Prebid Integration](integration-mobile-client-server#optional-uid2-integration-with-prebid-mobile-sdk) diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-prebid.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-prebid.md index 4f9577b6a..ea760885c 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-prebid.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-prebid.md @@ -50,8 +50,8 @@ DII へのアクセスに応じて、Prebid.js で使用する UID2 Token を生 | Scenario | Integration Guide | | :--- | :--- | -| Client-Side で DII にアクセスでき、フロントエンドの開発のみを行いたい。 | [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | -| Server-Side で DII にアクセスし、Server-Side の開発ができる。 | [UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | +| Client-Side で DII にアクセスでき、フロントエンドの開発のみを行いたい。 | [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | +| Server-Side で DII にアクセスし、Server-Side の開発ができる。 | [Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | ### Refreshing the UID2 Token @@ -65,8 +65,8 @@ Prebid.js UID2 Module は、UID2 Token を自動的にリフレッシュする UID2 module を設定するには `pbjs.setConfig` を呼び出します。サポートされているパラメータの詳細は、実装に適用されるガイドを参照してください: -- [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) -- [UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) +- [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) +- [Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) UID2 module が設定されると、ユーザーの UID2 Token を管理し、ユーザーのブラウザに保存します。 @@ -82,8 +82,8 @@ Prebid.js を使ってサイトを UID2 とインテグレーションするに 詳細な手順は、以下のインテグレーションガイドのいずれかを参照してください: -- [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) -- [UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) +- [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) +- [Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) ## UID2 Integration with Prebid Mobile SDK for Mobile Devices diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/summary-guides.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/summary-guides.md index fc8851438..2e6fcf39f 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/summary-guides.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/summary-guides.md @@ -44,8 +44,8 @@ Web インテグレーションオプションの詳細は [Publisher Web Integr | Integration Guide | Content Description | | :--- | :--- | | [UID2 Integration Overview for Prebid](integration-prebid.md) | UID2 とインテグレーションし、RTB ビッドストリームで Prebid.js または Prebid Mobile SDK から渡される UID2 Token (Advertising Token) を生成したいパブリッシャー向けのインテグレーションオプションの概要です。 | | -| [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | UID2 とインテグレーションし、トークンの生成とトークンの自動更新を Prebid.js に管理させ、トークンを RTB ビッドストリームに渡したいパブリッシャー向けのインテグレーションガイドです。このガイドは、Client-Side で UID2 Token をリクエストしたいパブリッシャー向けのもので、最も簡単な実装方法です。 | -| [UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | UID2 とインテグレーションし、RTB ビッドストリームで Prebid から渡される ID トークンを生成したいパブリッシャー向けのインテグレーションガイドです。このガイドは、Private Operator を使用しているか、Server-Side でトークンを生成したいパブリッシャー向けです。 | +| [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | UID2 とインテグレーションし、トークンの生成とトークンの自動更新を Prebid.js に管理させ、トークンを RTB ビッドストリームに渡したいパブリッシャー向けのインテグレーションガイドです。このガイドは、Client-Side で UID2 Token をリクエストしたいパブリッシャー向けのもので、最も簡単な実装方法です。 | +| [Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | UID2 とインテグレーションし、RTB ビッドストリームで Prebid から渡される ID トークンを生成したいパブリッシャー向けのインテグレーションガイドです。このガイドは、Private Operator を使用しているか、Server-Side でトークンを生成したいパブリッシャー向けです。 | | [UID2 Integration Overview for JavaScript](integration-javascript.md) | JavaScript SDK を使って UID2 とインテグレーションしたいパブリッシャー向けのオプションの概要です。 | | [Client-Side Integration Guide for JavaScript](integration-javascript-client-side.md) | 最も簡単な実装方法で、Client-Side の JavaScript の変更だけで UID2 とインテグレーションしたいパブリッシャー向けのインテグレーションガイドです。SDK for JavaScript は、トークンの生成と更新を自動的に管理します。 | | [Client-Server Integration Guide for JavaScript](integration-javascript-client-server.md) | パブリッシャー向けのこのインテグレーションガイドでは、SDK for JavaScript を使用する標準的なウェブインテグレーションシナリオについて説明し、トークンを Server-Side で生成し、パブリッシャーのウェブページに渡す必要があります。 | @@ -78,8 +78,8 @@ CTV とインテグレーションするパブリッシャー向けには、以 | Integration Guide | Content Description | | :--- | :--- | | [UID2 Integration Overview for Prebid](integration-prebid.md) | UID2 とインテグレーションし、Prebid.js または Prebid Mobile SDK が RTB ビッドストリームで発行する UID2 Token を生成したいパブリッシャー向けのオプションの概要です。 | -| [UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | UID2 とインテグレーションし、トークンの生成とトークンの自動更新を Prebid.js に管理させ、トークンを RTB ビッドストリームに渡したいパブリッシャー向けのインテグレーションガイドです。このガイドは、Client-Side で UID2 Token をリクエストしたいパブリッシャー向けのもので、最も簡単な実装方法です。 | -| [UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | UID2 とインテグレーションし、RTB ビッドストリームで Prebid から渡される ID トークンを生成したいパブリッシャー向けのインテグレーションガイドです。このガイドは、Private Operator を使用しているパブリッシャー、または Server-Side でトークンを生成したいパブリッシャー向けです。 | +| [Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md) | UID2 とインテグレーションし、トークンの生成とトークンの自動更新を Prebid.js に管理させ、トークンを RTB ビッドストリームに渡したいパブリッシャー向けのインテグレーションガイドです。このガイドは、Client-Side で UID2 Token をリクエストしたいパブリッシャー向けのもので、最も簡単な実装方法です。 | +| [Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md) | UID2 とインテグレーションし、RTB ビッドストリームで Prebid から渡される ID トークンを生成したいパブリッシャー向けのインテグレーションガイドです。このガイドは、Private Operator を使用しているパブリッシャー、または Server-Side でトークンを生成したいパブリッシャー向けです。 | | [UID2 Mobile Integration for Prebid.js](integration-prebid-mobile-summary.md) | モバイルデバイス上の Prebid.js と UID2 のインテグレーションに関する情報リソースのまとめです。 | ### Google Ad Manager Integrations diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/portal/client-side-integration.md b/i18n/ja/docusaurus-plugin-content-docs/current/portal/client-side-integration.md index e5f4e920f..053595cea 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/portal/client-side-integration.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/portal/client-side-integration.md @@ -42,8 +42,8 @@ Client-Side の実装オプションは、次の表に示すとおりです。 | Client-Side Implementation Option | Available For (Role) | Documentation Link | | :--- | :--- | :--- | | UID2 JavaScript SDK | パブリッシャー、広告主 | [Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md) | -| Prebid.js client-side integration | パブリッシャーのみ |[UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) | -| UID2 Mobile SDK | パブリッシャーのみ |[UID2 Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side.md) | +| Prebid.js client-side integration | パブリッシャーのみ |[Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) | +| UID2 Mobile SDK | パブリッシャーのみ |[Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side.md) | ## Adding and Managing Key Pairs 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 04fc612f8..45ac4d33b 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 @@ -185,13 +185,13 @@ import MdxJumpAnchor from '@site/src/components/MdxJumpAnchor';
    Client-Server Integration
    UID2の インテグレーションアプローチ の1つは、Client-Side と Server-Side の両方でインテグレーションする方法です (Client-Server)。
    たとえば、パブリッシャーの Client-Server インテグレーションでは、UID2 Token は Server-Side で生成され、Client-Side でリフレッシュされます。
    -
    パブリッシャーの Client-Server インテグレーションに関するドキュメントの例: UID2 Client-Server Integration Guide for Prebid.js, Client-Server Integration Guide for JavaScript, UID2 Client-Server Integration Guide for Mobile.
    +
    パブリッシャーの Client-Server インテグレーションに関するドキュメントの例: Client-Server Integration Guide for Prebid.js, Client-Server Integration Guide for JavaScript, Client-Server Integration Guide for Mobile.
    Client-side integration
    UID2の インテグレーションアプローチ の1つは、完全に Client-Side でインテグレーションする方法です。
    Client-Side インテグレーションでは、UID2 Token はクライアントサイドで生成およびリフレッシュされます。
    たとえば、広告主は、トラッキングピクセルのために Client-Side で UID2 Token を生成し、パブリッシャーは、ビッドストリームのために Client-Side で UID2 Token を生成し、トークンをリフレッシュします。
    -
    パブリッシャーの Client-Side インテグレーションに関するドキュメントの例: UID2 Client-Side Integration Guide for Prebid.js, Client-Side Integration Guide for JavaScript, UID2 Client-Side Integration Guide for Mobile.
    +
    パブリッシャーの Client-Side インテグレーションに関するドキュメントの例: Client-Side Integration Guide for Prebid.js, Client-Side Integration Guide for JavaScript, Client-Side Integration Guide for Mobile.
    Closed Operator
    Closed Operator は Private Operator の別名です。
    @@ -385,7 +385,7 @@ import MdxJumpAnchor from '@site/src/components/MdxJumpAnchor';
    Public key
    Client-Side のパブリッシャーインテグレーションでは、パブリッシャーに発行される2つの値のうちの1つがアカウントを一意に識別する公開鍵です。詳細は Subscription ID and Public Key を参照してください。
    -
    UID2 のインテグレーションでは、この値はしばしば serverPublicKey として表されます。たとえば、UID2 Client-Side Integration Guide for Prebid.js、Client-Side Integration Guide for JavaScript、UID2 Client-Side Integration Guide for Mobile など。
    +
    UID2 のインテグレーションでは、この値はしばしば serverPublicKey として表されます。たとえば、Client-Side Integration Guide for Prebid.js、Client-Side Integration Guide for JavaScript、Client-Side Integration Guide for Mobile など。
    Public Operator
    Public Operator は、UID2 Operator Service のパブリックインスタンスを実行する組織です。たとえば、The Trade Desk は現在、UID2 フレームワークの Public Operator として機能しており、すべての参加者が利用できます。
    @@ -423,11 +423,11 @@ import MdxJumpAnchor from '@site/src/components/MdxJumpAnchor';
    Salt bucket
    ソルトバケットは、raw UID2 や UID2 Token を生成するために使用される秘密のソルト値を、時間経過とともに管理するために使用されます。各バケットには単一の現在のソルト値が含まれており、一定期間アクティブな状態を維持した後、新しい値にローテーションされます。バケットは互いに独立して更新できます。
    100万個以上のソルトバケットが存在し、各メールアドレスまたは電話番号は決定論的な方法で特定のバケットに割り当てられます。ただし、この割り当ては永続的なものではなく、バケットの現在のソルトが新しい値にローテーションされると変更される可能性があります。
    -
    [POST /identity/map](../endpoints/post-identity-map.md) エンドポイントのバージョン 3 以前では、ソルトバケットは ソルトバケット ID を使用して識別されます。バージョン 3 以降では、ソルトバケット情報は必要ありません。
    +
    [POST /v3/identity/map](../endpoints/post-identity-map.md) エンドポイントのバージョン 3 以前では、ソルトバケットは ソルトバケット ID を使用して識別されます。バージョン 3 以降では、ソルトバケット情報は必要ありません。
    Salt bucket ID
    ソルトバケット ID は、特定の ソルトバケット を識別する一意の文字列です。ソルトバケット ID を使用すると、最近、ソルト値が更新されたソルトバケットを確認し、どのメールアドレスまたは電話番号が raw UID2 値を再生成する必要があるかを確認できます。
    -
    [POST /identity/map](../endpoints/post-identity-map.md) エンドポイントのバージョン 3 以前、たとえば [POST /identity/map (v2)](../endpoints/post-identity-map-v2.md) では、エンドポイントはソルトバケット ID を返します。バージョン 3 以降では、ソルトバケット情報は必要ありません。
    +
    [POST /v3/identity/map](../endpoints/post-identity-map.md) エンドポイントのバージョン 3 以前、たとえば [POST /v2/identity/map](../endpoints/post-identity-map-v2.md) では、エンドポイントはソルトバケット ID を返します。バージョン 3 以降では、ソルトバケット情報は必要ありません。
    ソルトバケット ID の例は、[POST /v2/identity/buckets](../endpoints/post-identity-buckets.md) エンドポイントのレスポンスを参照してください: Decrypted JSON Response Format。`POST /v3/identity/map` を使用している場合、`POST /v2/identity/buckets` を使用する必要はありません。
    Salted hash
    diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/integration-sample-sites.md b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/integration-sample-sites.md index c4a14d7bc..3da1e2f4e 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/integration-sample-sites.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/integration-sample-sites.md @@ -62,7 +62,7 @@ import Link from '@docusaurus/Link'; - Site: [Client-Side UID2 Integration with Prebid.js](https://prebid-client.samples.uidapi.com/) - Code: [uid2-examples/web-integrations/prebid-integrations/client-side](https://github.com/IABTechLab/uid2-examples/tree/main/web-integrations/prebid-integrations/client-side) -- Doc: [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side) +- Doc: [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side) ### Client-Server Integration with Prebid.js @@ -70,7 +70,7 @@ import Link from '@docusaurus/Link'; - Site: [Client-Server UID2 Integration with Prebid.js](https://prebid-client-server.samples.uidapi.com/) - Code: [uid2-examples/web-integrations/prebid-integrations/client-server](https://github.com/IABTechLab/uid2-examples/tree/main/web-integrations/prebid-integrations/client-server) -- Doc: [UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server) +- Doc: [Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server) ### Deferred Client-Side Integration with Prebid.js @@ -78,7 +78,7 @@ import Link from '@docusaurus/Link'; - Site: [Deferred Client-Side UID2 Integration with Prebid.js](https://prebid-deferred.samples.uidapi.com/) - Code: [uid2-examples/web-integrations/prebid-integrations/client-side-deferred](https://github.com/IABTechLab/uid2-examples/tree/main/web-integrations/prebid-integrations/client-side-deferred) -- Doc: [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side) +- Doc: [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side) ### Prebid.js with Secure Signals diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/ref-integration-approaches.md b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/ref-integration-approaches.md index 010560867..53b7455bc 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/ref-integration-approaches.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/ref-info/ref-integration-approaches.md @@ -29,9 +29,9 @@ Client-Side インテグレーションでは、UID2 Token は Client-Side で パブリッシャーの Client-Side インテグレーションの例: -- [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) +- [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) - [Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md) -- [UID2 Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side.md) +- [Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side.md) Client-Side でインテグレーションする広告主は、JavaScript SDK を使用できます: @@ -56,9 +56,9 @@ Client-Server インテグレーションでは、一部のインテグレーシ パブリッシャーの Client-Server インテグレーションの例: -- [UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) +- [Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) - [Client-Server Integration Guide for JavaScript](../guides/integration-javascript-client-server.md) -- [UID2 Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server.md) +- [Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server.md) ### Client-Server Integration: Credentials 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 e7d311afe..0d35442ad 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 @@ -66,7 +66,7 @@ UID2 Databricks Clean Rooms インテグレーションガイドを追加しま -### Identity Map v3 (Python SDK, Snowflake) +### POST /v3/identity/map (Python SDK, Snowflake) July 31, 2025 @@ -87,7 +87,7 @@ July 11 に発表された Identity Map API (v3) の新バージョンに対応 July 11, 2025 -Identity Map API (v3) の新バージョンをリリースしました。このバージョンは、広告主とデータプロバイダーに大幅な改善を提供します。この更新には、[POST /identity/map](../endpoints/post-identity-map.md) エンドポイント、[SDK for Java Reference Guide](../sdks/sdk-ref-java.md#usage-for-advertisersdata-providers)、および [Advertiser/Data Provider Integration Overview](../guides/integration-advertiser-dataprovider-overview.md) のドキュメントが含まれています。 +Identity Map API (v3) の新バージョンをリリースしました。このバージョンは、広告主とデータプロバイダーに大幅な改善を提供します。この更新には、[POST /v3/identity/map](../endpoints/post-identity-map.md) エンドポイント、[SDK for Java Reference Guide](../sdks/sdk-ref-java.md#usage-for-advertisersdata-providers)、および [Advertiser/Data Provider Integration Overview](../guides/integration-advertiser-dataprovider-overview.md) のドキュメントが含まれています。 @@ -371,8 +371,8 @@ July 2, 2024 2 つのモバイルインテグレーションガイドに、Prebid を使用したモバイルインテグレーションの新しいセクションを追加しました。現在は Android のみです。 -- [UID2 Client-Side Integration Guide for Mobile: Prebid Integration](../guides/integration-mobile-client-side#optional-uid2-integration-with-prebid-mobile-sdk) -- [UID2 Client-Server Integration Guide for Mobile: Prebid Integration](../guides/integration-mobile-client-server#optional-uid2-integration-with-prebid-mobile-sdk) +- [Client-Side Integration Guide for Mobile: Prebid Integration](../guides/integration-mobile-client-side#optional-uid2-integration-with-prebid-mobile-sdk) +- [Client-Server Integration Guide for Mobile: Prebid Integration](../guides/integration-mobile-client-server#optional-uid2-integration-with-prebid-mobile-sdk) @@ -421,8 +421,8 @@ May 17, 2024 Android または iOS モバイルアプリのパブリッシャーが UID2 を実装するためのサポートを提供するため、以下のインテグレーションガイドを追加しました: - [UID2 Mobile Integration Overview for Android and iOS](../guides/integration-mobile-overview) -- [UID2 Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side) -- [UID2 Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server) +- [Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side) +- [Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server) @@ -613,8 +613,8 @@ December 20, 2023 詳細は 以下を参照してください: - [UID2 Integration Overview for Prebid](../guides/integration-prebid.md) -- [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) -- [UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) +- [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) +- [Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) @@ -690,15 +690,15 @@ Client-Side Integration Guide for JavaScript は、既存の URL の全く新し November 2, 2023 -UID2 Client-Side Integration Guide for Prebid.js は、既存の URL にまったく新しいドキュメントを追加したもので、UID2 と Prebid をインテグレーションする、Server-Side の作業を必要としない、よりシンプルな新しい方法について説明しています。 +Client-Side Integration Guide for Prebid.js は、既存の URL にまったく新しいドキュメントを追加したもので、UID2 と Prebid をインテグレーションする、Server-Side の作業を必要としない、よりシンプルな新しい方法について説明しています。 前バージョンの Prebid ドキュメントにあった内容は、Private Operator を使用しているパブリッシャーや、Server-Side でトークン生成を実装したいパブリッシャーのために、補足ドキュメントである *Prebid.js Advanced Integration Guide* に追加されました。 :::note これらのドキュメントは、その後の改訂でさらに更新されました。更新されたリンクは以下のとおりです: - [UID2 Integration Overview for Prebid](../guides/integration-prebid.md) -- [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) -- [UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) +- [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) +- [Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) ::: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-java.md b/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-java.md index d7c31b84f..8f59a9a48 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-java.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-java.md @@ -300,7 +300,7 @@ Server-Side Integration ([Publisher Integration Guide, Server-Side](../guides/in 以下の手順は、最新バージョンの `POST /identity/map` エンドポイントを使用して DII を raw UID2 にマップする方法の例です。 -以前のバージョンを使用する場合は、[Previous SDK Version (using POST /identity/map v2)](#previous-sdk-version-using-post-identitymap-v2) を参照してください。最新バージョンへの移行手順については、[Migration From Version Using v2 Identity Map](#migration-from-version-using-v2-identity-map) を参照してください。 +以前のバージョンを使用する場合は、[Previous SDK Version (using POST /v2/identity/map)](#previous-sdk-version-using-post-v2identitymap) を参照してください。最新バージョンへの移行手順については、[Migration From Version Using v2 Identity Map](#migration-from-version-using-v2-identity-map) を参照してください。 1. IdentityMapClient のインスタンスをインスタンス変数として作成します: ```java @@ -487,7 +487,7 @@ import com.uid2.client.UnmappedIdentityReason; String rawReason = unmapped.getRawReason(); ``` -## Previous SDK Version (using POST /identity/map v2) +## Previous SDK Version (using POST /v2/identity/map) :::note 下位互換性のために、`POST /identity/map` v2 エンドポイントを参照する SDK for Java の以前のバージョンも利用可能です。パフォーマンスの向上、複数の ID タイプのサポート、UID ローテーション管理の改善のために、現在の SDK に移行してください。新しいインテグレーションではこのバージョンを使用しないでください。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-javascript-v3.md b/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-javascript-v3.md index d8657d21e..0f5ce7696 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-javascript-v3.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-javascript-v3.md @@ -35,7 +35,7 @@ export const Deprecated3100 = () => ( 以下のセクションでは、UID2 ID の確立のための高レベルな [ワークフロー](#workflow-overview)、SDK [API リファレンス](#api-reference)、および UID2 [ストレージフォーマット](#uid2-storage-format) を説明します。 :::tip -UID2 Identify Module、または UID2 サポートのある他の製品と Prebid.js を使用している場合、SDK を使用する必要はありません。Prebid.js モジュールがすべてを管理します。詳細は、[UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) を参照してください。 +UID2 Identify Module、または UID2 サポートのある他の製品と Prebid.js を使用している場合、SDK を使用する必要はありません。Prebid.js モジュールがすべてを管理します。詳細は、[Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) を参照してください。 ::: このページでは、SDK のバージョン 3 について説明します。以前のバージョンを使用している場合は、[移行ガイド](#migration-guide) を使用してインテグレーションをアップグレードすることを推奨します。必要に応じて、[SDK の以前のバージョン](./sdk-ref-javascript-v2.md) のドキュメントも利用できます。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-javascript.md b/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-javascript.md index 671e29d1c..b16ba1c09 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-javascript.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-javascript.md @@ -19,7 +19,7 @@ import SnptExampleJavaScriptInit from '../snippets/_snpt-example-javascript-init 以下のセクションでは、UID2 ID の確立のための高レベルな [ワークフロー](#workflow-overview)、SDK [API リファレンス](#api-reference)、および UID2 [ストレージフォーマット](#uid2-storage-format) を説明します。 :::tip -UID2 Identify Module、または UID2 サポートのある他の製品と Prebid.js を使用している場合、SDK を使用する必要はありません。Prebid.js モジュールがすべてを管理します。詳細は、[UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) を参照してください。 +UID2 Identify Module、または UID2 サポートのある他の製品と Prebid.js を使用している場合、SDK を使用する必要はありません。Prebid.js モジュールがすべてを管理します。詳細は、[Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) を参照してください。 ::: コンテンツパブリッシャー向けのインテグレーション手順は、以下のガイドを参照してください: diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/sharing/sharing-tokenized-from-data-bid-stream.md b/i18n/ja/docusaurus-plugin-content-docs/current/sharing/sharing-tokenized-from-data-bid-stream.md index 378c7d30c..5a7f69197 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/sharing/sharing-tokenized-from-data-bid-stream.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/sharing/sharing-tokenized-from-data-bid-stream.md @@ -37,8 +37,8 @@ DII を直接 UID2 Token に暗号化してビッドストリームに送信す | Integration Option | Token Generated Client-Side or Server-Side? | Integration Guide | | :--- | :--- | :--- | -| Prebid.js | Client-Side | [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) | -| Prebid.js | Server-Side | [UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) | +| Prebid.js | Client-Side | [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) | +| Prebid.js | Server-Side | [Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) | | JavaScript SDK | Client-Side | [Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md) | | JavaScript SDK | Server-Side | [Client-Server Integration Guide for JavaScript](../guides/integration-javascript-client-server.md) | | Java SDK | Server-Side | [SDK for Java Reference Guide](../sdks/sdk-ref-java.md) | diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/snippets/_snpt-publisher-implementation-resources.mdx b/i18n/ja/docusaurus-plugin-content-docs/current/snippets/_snpt-publisher-implementation-resources.mdx index 732b13db2..2fb14b55e 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/snippets/_snpt-publisher-implementation-resources.mdx +++ b/i18n/ja/docusaurus-plugin-content-docs/current/snippets/_snpt-publisher-implementation-resources.mdx @@ -19,8 +19,8 @@ Web インテグレーションオプションの詳細は [Publisher Web Integr | Integration Type| Documentation | Content Description | | :--- | :--- | :--- | | Prebid (Overview) | [UID2 Integration Overview for Prebid](../guides/integration-prebid.md) | UID2 とインテグレーションし、RTB ビッドストリームで Prebid.js または Prebid Mobile SDK から渡される UID2 Token (Advertising Token) を生成したいパブリッシャー向けのインテグレーションオプションの概要です。 | -| Prebid.js Client-Side Integration | [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) | 最も簡単な実装方法であるClient-Side で UID2 Token をリクエストし、Prebid.js に以下を管理させることを選択したいパブリッシャー向けのガイドです: | -| Prebid.js Client-Server Integration | [UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) | UID2 とインテグレーションし、RTB ビッドストリームで Prebid.js から渡される UID2 Token を生成したいが、トークンを Server-Side で生成したいパブリッシャー向けのガイドです: たとえば、Private Operator を利用しているパブリッシャーなど。 | +| Prebid.js Client-Side Integration | [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) | 最も簡単な実装方法であるClient-Side で UID2 Token をリクエストし、Prebid.js に以下を管理させることを選択したいパブリッシャー向けのガイドです: | +| Prebid.js Client-Server Integration | [Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) | UID2 とインテグレーションし、RTB ビッドストリームで Prebid.js から渡される UID2 Token を生成したいが、トークンを Server-Side で生成したいパブリッシャー向けのガイドです: たとえば、Private Operator を利用しているパブリッシャーなど。 | | JavaScript (Overview) | [UID2 Integration Overview for JavaScript](../guides/integration-javascript.md) | JavaScript SDK を使って UID2 とインテグレーションしたいパブリッシャー向けのオプションの概要です。 | | JavaScript Client-Side Integration | [Client-Side Integration Guide for JavaScript](../guides/integration-javascript-client-side.md) | Client-Side の JavaScript の変更だけで UID2 とインテグレーションしたいパブリッシャー向けのガイドで、最も簡単な実装方法です。
    SDK for JavaScript は、トークン生成とトークンリフレッシュを自動的に管理します。 | | JavaScript Client-Server Integration | [Client-Server Integration Guide for JavaScript](../guides/integration-javascript-client-server.md) | SDK for JavaScript を使用し、トークンを Server-Side で生成してパブリッシャーのウェブページに渡す必要がある、標準的なWeb インテグレーションシナリオを網羅したパブリッシャーガイドです。 | @@ -55,8 +55,8 @@ Prebid とインテグレーションするパブリッシャーには、以下 | Integration Type| Documentation | Content Description | | :--- | :--- | :--- | | Prebid (Overview) | [UID2 Integration Overview for Prebid](../guides/integration-prebid.md) | UID2 とインテグレーションし、RTB ビッドストリームで Prebid.js または Prebid Mobile SDK から渡される UID2 Token (Advertising Token) を生成したいパブリッシャー向けのインテグレーションオプションの概要。 | -| Prebid.js Client-Side Integration | [UID2 Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) | 最も簡単な実装方法である Client-Side で UID2 Token をリクエストし、Prebid.js に以下を管理させることを選択したいパブリッシャー向けのガイドです: | -| Prebid.js Client-Server Integration | [UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) | UID2 とインテグレーションし、RTB ビッドストリームで Prebid.js から渡される UID2 Token を生成したいが、トークンを Server-Side で生成したいパブリッシャー向けのガイドです: たとえば、Private Operatorを使用しているパブリッシャーなどです。 | +| Prebid.js Client-Side Integration | [Client-Side Integration Guide for Prebid.js](../guides/integration-prebid-client-side.md) | 最も簡単な実装方法である Client-Side で UID2 Token をリクエストし、Prebid.js に以下を管理させることを選択したいパブリッシャー向けのガイドです: | +| Prebid.js Client-Server Integration | [Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) | UID2 とインテグレーションし、RTB ビッドストリームで Prebid.js から渡される UID2 Token を生成したいが、トークンを Server-Side で生成したいパブリッシャー向けのガイドです: たとえば、Private Operatorを使用しているパブリッシャーなどです。 | | Prebid.js on Mobile | [UID2 Mobile Integration for Prebid.js](../guides/integration-prebid-mobile-summary.md) | モバイルデバイス上の Prebid.js と UID2 のインテグレーションに関する情報リソースのまとめです。 | ### Google Ad Manager Integrations