diff --git a/docs/guides/advertiser-dataprovider-guide.md b/docs/guides/advertiser-dataprovider-guide.md
index 997d951f8..ea6747e1d 100644
--- a/docs/guides/advertiser-dataprovider-guide.md
+++ b/docs/guides/advertiser-dataprovider-guide.md
@@ -56,7 +56,7 @@ DII refers to a user's normalized email address or phone number, or the normaliz
Refer to the following sections for details about the different parts of the diagram:
-1. [Retrieve a raw UID2 for DII using the identity map endpoints](#1-retrieve-a-raw-uid2-for-dii-using-the-identity-map-endpoint)
+1. [Retrieve a raw UID2 for DII using the identity map endpoint](#1-retrieve-a-raw-uid2-for-dii-using-the-identity-map-endpoint)
2. [Send stored raw UID2s to DSPs to create audiences or conversions](#2-send-stored-raw-uid2s-to-dsps-to-create-audiences-or-conversions)
3. [Monitor for salt bucket rotations related to your stored raw UID2s](#3-monitor-for-salt-bucket-rotations-related-to-your-stored-raw-uid2s)
diff --git a/docs/guides/integration-javascript-client-side.md b/docs/guides/integration-javascript-client-side.md
index 1a0dc4fe1..e86f1a60e 100644
--- a/docs/guides/integration-javascript-client-side.md
+++ b/docs/guides/integration-javascript-client-side.md
@@ -28,7 +28,7 @@ This approach is used by the following participant types:
This guide does not apply to publishers who want to use a Private Operator, or who want to generate tokens server-side. Those publishers should follow the [Client-Server Integration Guide for JavaScript](integration-javascript-client-server.md).
-UID2 provides a SDK for JavaScript (see [SDK for JavaScript Reference Guide](../sdks/sdk-ref-javascript.md)) with the following features:
+UID2 provides an SDK for JavaScript (see [SDK for JavaScript Reference Guide](../sdks/sdk-ref-javascript.md)) with the following features:
- UID2 token generation
- Automatic refreshing of UID2 tokens
@@ -37,7 +37,7 @@ UID2 provides a SDK for JavaScript (see [SDK for JavaScript Reference Guide](../
To implement, you'll need to complete the following steps:
1. [Complete UID2 account setup](#complete-uid2-account-setup)
-2. [Add SDK For JavaScript to your site](#add-sdk-for-javascript-to-your-site)
+2. [Add SDK for JavaScript to your site](#add-sdk-for-javascript-to-your-site)
3. [Configure the SDK for JavaScript](#configure-the-sdk-for-javascript)
4. [Check that the token was successfully generated](#check-that-the-token-was-successfully-generated)
@@ -74,7 +74,7 @@ When account setup is complete, you'll receive a client keypair consisting of tw
Only root-level domains are required for account setup. For example, if you're going to use SDK for JavaScript on example.com, shop.example.com, and example.org, you only need to provide the domain names example.com and example.org.
:::
-## Add SDK For JavaScript to Your Site
+## Add SDK for JavaScript to Your Site
The following code snippet provides an overview of the code you will need to add to your website. It also illustrates the different events that the SDK can trigger.
@@ -149,7 +149,7 @@ UID2 provides the publisher with the following values required to use the client
* A Subscription ID
* A public key
-You'll have one set of these values for your publisher Integration environment, and a separate set for your production environment.
+You'll have one set of these values for your publisher integration environment, and a separate set for your production environment.
To configure the SDK, call one of the following methods, with an object containing the **public key** and **Subscription ID** that you received during account setup, as well as the user's hashed or unhashed DII (email address or phone number):
@@ -269,14 +269,14 @@ In this scenario:
After calling one of the methods listed in [Configure the SDK for JavaScript](#configure-the-sdk-for-javascript) successfully, an identity is generated and stored in local storage, under the key `UID2-sdk-identity`. The SDK refreshes the UID2 token periodically.
:::warning
-The format of the object stored in local storage could change without notice. We recommend that you do **not** read or update the object in local storage directly.
+The format of the object stored in local storage could change without notice. We recommend that you do **not** read or update the object in local storage directly.
:::
## Example Integration Code and When to Pass DII to the UID2 SDK
If you're a publisher and this is the first page load with no identity, to start the token generation call you'll need to call one of the `setIdentity` methods with DII. Once an identity is generated, the advertising token (UID2 token) that you would send to the bidstream will be available by waiting for the `IdentityUpdated` event from the SDK. For an example, see how the value for `advertising_token_to_use` is set in the following code snippet.
-In some cases, the user's DII is not available on page load, and getting the DII has some associated cost. For example, an API call might be required to fetch the DII, or the user has to be prompted to provide the DII information.
+In some cases, the user's DII is not available on page load, and getting the DII has some associated cost. For example, an API call might be required to fetch the DII, or the user has to be prompted to provide it.
You can potentially avoid that cost by checking for an existing token that you can use or refresh. To do this, call
[__uid2.isLoginRequired](../sdks/sdk-ref-javascript#isloginrequired-boolean) which returns a Boolean value. If it returns `true`, this means that the UID2 SDK cannot create a new advertising token with the existing resource and DII is required to generate a brand new UID2 token.
diff --git a/docs/guides/integration-mobile-overview.md b/docs/guides/integration-mobile-overview.md
index 5ff59b1de..b724a85fa 100644
--- a/docs/guides/integration-mobile-overview.md
+++ b/docs/guides/integration-mobile-overview.md
@@ -145,7 +145,7 @@ Podspec is the name of the file in CocoaPods that defines the libraries to be in
Here's some additional information to help you troubleshoot your UID2 mobile integrations:
-- [Android SDK cannot connect in Production environment](#android-sdk-cannot-connect-in-production-environment)
+- [Android SDK Cannot Connect in Production Environment](#android-sdk-cannot-connect-in-production-environment)
#### Android SDK Cannot Connect in Production Environment
diff --git a/docs/guides/integration-options-private-operator.md b/docs/guides/integration-options-private-operator.md
index 47db4414a..a1ae4ddc1 100644
--- a/docs/guides/integration-options-private-operator.md
+++ b/docs/guides/integration-options-private-operator.md
@@ -70,7 +70,7 @@ The basic workflow for a Private Operator is as follows:
Each supported Private Operator implementation must meet rigorous security standards. Some security points include:
-- The Private Operator runs in a hardware-based trusted execution environment (TEE) hosted by one of the supported cloud providers listed in [Hosting Options for Private Operators](#hosting-options-for-private-operators).
+- The Private Operator runs in a hardware-based trusted execution environment (TEE) hosted by a supported cloud provider listed in [Hosting Options for Private Operators](#hosting-options-for-private-operators).
- The Private Operator must complete an attestation process before accessing the information needed to process UID2s.
- The information on S3 is encrypted at rest and also encrypted in transit through TLS. In addition, access is limited to only correctly authorized and attested Private Operators.
- The information retrieved at startup is not stored locally at any point. It is only ever held in memory, and the Private Operator is running in a protected environment that makes it difficult for anyone running the Operator (such as an Administrator), as well as any external players, to see the data that's in memory.
diff --git a/docs/guides/integration-options-publisher-web.md b/docs/guides/integration-options-publisher-web.md
index d9342a988..13d333ab7 100644
--- a/docs/guides/integration-options-publisher-web.md
+++ b/docs/guides/integration-options-publisher-web.md
@@ -14,15 +14,6 @@ As a publisher, there are many ways that you can integrate with UID2 to generate
On this page, you'll find a high-level overview of integration steps and integration options, with links to additional information for each option.
-
-
## Key Integration Steps
At a high level, to integrate with UID2, you'll implement these three key activities:
@@ -44,7 +35,7 @@ To accomplish all steps, you can combine solutions. For example, you could use t
| [Prebid.js client-side (8.21.0 or later)](integration-prebid-client-side.md) | ✅ | ✅ | ✅ |
| [Prebid.js client-server (7.53.0 or later)](integration-prebid-client-server.md) | — | ✅ | ✅ |
| [SDK for JavaScript, client-side](integration-javascript-client-side.md) | ✅ | ✅ | — |
-| [SDK for JavaScript, server-side](integration-javascript-client-server.md) | ✅ | ✅ | — |
+| [SDK for JavaScript, client-server](integration-javascript-client-server.md) | ✅ | ✅ | — |
| [SDK for Java](../sdks/sdk-ref-java.md) | ✅ | ✅ | — |
| [SDK for Python](../sdks/sdk-ref-python.md) | ✅ | ✅ | — |
| [Direct integration (API endpoints)](integration-publisher-server-side.md) | ✅ | ✅ | — |
@@ -100,8 +91,6 @@ Generating the UID2 token on the server side has the following advantages:
The following table summarizes the options for publishers who want to generate the UID2 token on the server side.
-
-
| Option | Documentation |
| :--- | :--- |
| SDK for JavaScript, client-server implementation | [Client-Server Integration Guide for JavaScript](integration-javascript-client-server.md) |
@@ -142,119 +131,3 @@ The following table shows integration options that support passing UID2 token in
:::note
As long as you generate the token and keep it refreshed, you can also use other options for passing the UID2 token into the bidstream.
:::
-
-
-
-
-
-
-
-
-
diff --git a/docs/guides/integration-prebid-client-server.md b/docs/guides/integration-prebid-client-server.md
index 5563e406d..553327541 100644
--- a/docs/guides/integration-prebid-client-server.md
+++ b/docs/guides/integration-prebid-client-server.md
@@ -23,10 +23,13 @@ To integrate with UID2 using Prebid.js, you'll need to:
- Make server-side changes for token generation (and, optionally, token refresh).
## Prebid.js Version
+
This implementation requires Prebid.js version 7.53.0 or later. For version information, see [https://github.com/prebid/Prebid.js/releases](https://github.com/prebid/Prebid.js/releases).
+
+
## UID2 Prebid Module Page
-
+
Information about how to integrate Prebid with UID2 is also in the following locations:
- On the Prebid site, on the [Unified ID 2.0](https://docs.prebid.org/dev-docs/modules/userid-submodules/unified2.html) page for the Prebid User ID submodule.
- In the Prebid GitHub repository, on the [UID2 User ID Submodule](https://github.com/prebid/Prebid.js/blob/master/modules/uid2IdSystem.md) page.
diff --git a/docs/guides/integration-prebid-client-side.md b/docs/guides/integration-prebid-client-side.md
index 98d471d80..521d249f7 100644
--- a/docs/guides/integration-prebid-client-side.md
+++ b/docs/guides/integration-prebid-client-side.md
@@ -21,6 +21,8 @@ To integrate with UID2 using Prebid.js, you'll need to make changes to the HTML
This implementation requires Prebid.js version 8.21.0 or later. For version information, see [https://github.com/prebid/Prebid.js/releases](https://github.com/prebid/Prebid.js/releases).
+
+
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.
## Integration Example
@@ -119,7 +121,7 @@ If there is no existing token, or the token has expired and cannot be refreshed,
Configure the UID2 module with the user's DII on each page load. This is the recommended approach.
:::
-In some cases, the user's DII is not available on page load, and getting the DII has some associated cost. For example, an API call might be required to fetch the DII, or the user has to be prompted to provide the DII information.
+In some cases, the user's DII is not available on page load, and getting the DII has some associated cost. For example, an API call might be required to fetch the DII, or the user has to be prompted to provide it.
If the UID2 token has expired and cannot be refreshed, you must configure the UID2 module with DII to generate a new token. To do this, check the value returned by `pbjs.getUserIds().uid2`, as shown in the following example:
diff --git a/docs/guides/mobile-plugin-gma-android.md b/docs/guides/mobile-plugin-gma-android.md
index 2deebdab7..0056d02e7 100644
--- a/docs/guides/mobile-plugin-gma-android.md
+++ b/docs/guides/mobile-plugin-gma-android.md
@@ -74,4 +74,3 @@ To install with Maven, add the SDK as a dependency in the `pom.xml` file:
If you are using R8, the shrinking and obfuscation rules are included automatically.
If you are using ProGuard, you must manually add the option specified in [uid2-gma.pro](https://github.com/IABTechLab/uid2-android-sdk/blob/main/securesignals-gma/uid2-gma.pro).
-
diff --git a/docs/guides/mobile-plugin-gma-ios.md b/docs/guides/mobile-plugin-gma-ios.md
index a8be9260d..adbb77811 100644
--- a/docs/guides/mobile-plugin-gma-ios.md
+++ b/docs/guides/mobile-plugin-gma-ios.md
@@ -66,7 +66,7 @@ dependencies: [
In the XCode user interface, under Package Dependencies, add the following entry for your apps:
| Name | Location | Dependency Rule |
-| :--- | :--- | :--- |
+| :--- | :--- | :--- |
| uid2-ios-plugin-google-gma | `git@github.com:IABTechLab/uid2-ios-plugin-google-gma.git` | Exact Version: 1.0.0 |
### Installing with CocoaPods
diff --git a/docs/guides/mobile-plugin-ima-android.md b/docs/guides/mobile-plugin-ima-android.md
index e47e4ec05..c2cee3e2f 100644
--- a/docs/guides/mobile-plugin-ima-android.md
+++ b/docs/guides/mobile-plugin-ima-android.md
@@ -74,4 +74,3 @@ To install with Maven, add the SDK as a dependency in the `pom.xml` file:
If you are using R8, the shrinking and obfuscation rules are included automatically.
If you are using ProGuard, you must manually add the option specified in [uid2-ima.pro](https://github.com/IABTechLab/uid2-android-sdk/blob/main/securesignals-ima/uid2-ima.pro).
-
diff --git a/docs/guides/mobile-plugin-ima-ios.md b/docs/guides/mobile-plugin-ima-ios.md
index 79b8727d9..6334ccaeb 100644
--- a/docs/guides/mobile-plugin-ima-ios.md
+++ b/docs/guides/mobile-plugin-ima-ios.md
@@ -66,7 +66,7 @@ dependencies: [
In the XCode user interface, under Package Dependencies, add the following entry for your apps:
| Name | Location | Dependency Rule |
-| :--- | :--- | :--- |
+| :--- | :--- | :--- |
| uid2-ios-plugin-google-ima | `git@github.com:IABTechLab/uid2-ios-plugin-google-ima.git` | Exact Version: 1.0.0 |
### Installing with CocoaPods
diff --git a/docs/guides/operator-guide-aws-marketplace.md b/docs/guides/operator-guide-aws-marketplace.md
index 9e8209317..f2ee5afc7 100644
--- a/docs/guides/operator-guide-aws-marketplace.md
+++ b/docs/guides/operator-guide-aws-marketplace.md
@@ -132,7 +132,7 @@ To avoid passing certificates associated with your domain into the enclave, inbo
| Port Number | Direction | Protocol | Description |
| ----------- | --------- | -------- | ------ |
-| 80 | Inbound | HTTP | Serves all UID2 APIs, including the healthcheck endpoint `/ops/healthcheck`. When everything is up and running, the endpoint returns HTTP 200 with a response body of `OK`. For details, see [Checking UID2 Operator Status](#checking-uid2-operator-status).|
+| 80 | Inbound | HTTP | Serves all UID2 APIs, including the healthcheck endpoint `/ops/healthcheck`. When everything is up and running, the endpoint returns HTTP 200 with a response body of `OK`. For details, see [Checking UID2 Operator Status](#checking-uid2-operator-status). |
| 9080 | Inbound | HTTP | Serves Prometheus metrics (`/metrics`). |
| 443 | Outbound | HTTPS | Calls the UID2 Core Service; updates opt-out data and key store. |
@@ -280,6 +280,7 @@ When the operator instance has been deployed, the default log rotation settings
#### Log Rotation Default Settings
The following are the default logrotate settings, defined in `/etc/logrotate.d/operator-logrotate.conf`:
+
```
/var/log/operator.log*
{
diff --git a/docs/guides/summary-guides.md b/docs/guides/summary-guides.md
index b3f667005..89f8fbbf3 100644
--- a/docs/guides/summary-guides.md
+++ b/docs/guides/summary-guides.md
@@ -43,11 +43,11 @@ For a detailed summary of web integration options, see [Web Integration Overview
| :--- | :--- |
| [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. |
+| [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. |
| [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. |
-| [Publisher Integration Guide, Server-Side](integration-publisher-server-side.md) | This integration guide is for publishers that do not use the SDK for JavaScript. |
+| [Publisher Integration Guide, Server-Side](integration-publisher-server-side.md) | This integration guide is for publishers that do not use the [SDK for JavaScript](../sdks/sdk-ref-javascript.md). |
| [Google Ad Manager Secure Signals Integration Guide](integration-google-ss.md) | This integration guide covers the additional steps needed for publishers using UID2 with the Google Ad Manager Secure Signals feature (previously known as Encrypted Signals for Publishers, ESP). |
### Mobile Integrations
@@ -76,7 +76,7 @@ The following resources are available for publishers integrating with Prebid.
| :--- | :--- |
| [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. |
+| [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. |
| [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/i18n/ja/docusaurus-plugin-content-docs/current/guides/advertiser-dataprovider-guide.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/advertiser-dataprovider-guide.md
index 644a74870..f50cf3b26 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/advertiser-dataprovider-guide.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/advertiser-dataprovider-guide.md
@@ -56,7 +56,7 @@ DII とは、正規化されたメールアドレスや電話番号、あるい
図の各部の詳細については、以下のセクションを参照してください:
-1. [Retrieve a raw UID2 for DII using the identity map endpoints](#1-retrieve-a-raw-uid2-for-dii-using-the-identity-map-endpoint)
+1. [Retrieve a raw UID2 for DII using the identity map endpoint](#1-retrieve-a-raw-uid2-for-dii-using-the-identity-map-endpoint)
2. [Send stored raw UID2s to DSPs to create audiences or conversions](#2-send-stored-raw-uid2s-to-dsps-to-create-audiences-or-conversions)
3. [Monitor for salt bucket rotations related to your stored raw UID2s](#3-monitor-for-salt-bucket-rotations-related-to-your-stored-raw-uid2s)
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-javascript-client-side.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-javascript-client-side.md
index 72b6ec285..2d223c2ab 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-javascript-client-side.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-javascript-client-side.md
@@ -37,7 +37,7 @@ UID2 は、SDK for JavaScript を提供しています (詳細は [SDK for JavaS
実装するには、以下の手順を完了する必要があります:
1. [Complete UID2 account setup](#complete-uid2-account-setup)
-2. [Add SDK For JavaScript to your site](#add-sdk-for-javascript-to-your-site)
+2. [Add SDK for JavaScript to your site](#add-sdk-for-javascript-to-your-site)
3. [Configure the SDK for JavaScript](#configure-the-sdk-for-javascript)
4. [Check that the token was successfully generated](#check-that-the-token-was-successfully-generated)
@@ -74,7 +74,7 @@ SDK のデバッグビルドを使用したい場合は、代わりに以下の
アカウント設定に必要なのは、ルートレベルのドメインだけです。例えば、JavaScript 用の UID2 SDK を example.com、shop.example.com、example.org で使用する場合、ドメイン名 example.com と example.org を指定するだけです。
:::
-## Add SDK For JavaScript to Your Site
+## Add SDK for JavaScript to Your Site
以下のコードスニペットは、ウェブサイトに追加する必要があるコードの概要です。また、SDK がトリガーできるさまざまなイベントも示しています。
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 8038c4132..952018b1a 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
@@ -14,15 +14,6 @@ import Link from '@docusaurus/Link';
このページでは、インテグレーションステップとインテグレーションオプションの概要と、各オプションの追加情報へのリンクを紹介します。
-
-
## Key Integration Steps
UID2 とインテグレーションするには、次の 3 つの主要なアクティビティを実装します。
@@ -44,7 +35,7 @@ UID2 とインテグレーションするには、次の 3 つの主要なアク
| [Prebid.js client-side (8.21.0 or later)](integration-prebid-client-side.md) | ✅ | ✅ | ✅ |
| [Prebid.js client-server (7.53.0 or later)](integration-prebid-client-server.md) | — | ✅ | ✅ |
| [SDK for JavaScript, client-side](integration-javascript-client-side.md) | ✅ | ✅ | — |
-| [SDK for JavaScript, server-side](integration-javascript-client-server.md) | ✅ | ✅ | — |
+| [SDK for JavaScript, client-server](integration-javascript-client-server.md) | ✅ | ✅ | — |
| [SDK for Java](../sdks/sdk-ref-java.md) | ✅ | ✅ | — |
| [SDK for Python](../sdks/sdk-ref-python.md) | ✅ | ✅ | — |
| [Direct integration (API endpoints)](integration-publisher-server-side.md) | ✅ | ✅ | — |
@@ -100,8 +91,6 @@ Server-Side で UID2 Token を生成することには、次のような利点
次の表は、Server-Side で UID2 Token を生成したいパブリッシャー向けのオプションをまとめたものです。
-
-
| Option | Documentation |
| :--- | :--- |
| SDK for JavaScript, client-server implementation | [Client-Server Integration Guide for JavaScript](integration-javascript-client-server.md) |
@@ -142,119 +131,3 @@ Server-Side で UID2 Token を生成することには、次のような利点
:::note
トークンを生成し、それをリフレッシュし続ける限り、UID2 Token をビッドストリームに渡すために他のオプションを使用することもできます。
:::
-
-
-
-
-
-
-
-
-
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 fe272d18b..2392ea576 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
@@ -23,10 +23,11 @@ Prebid.js を使って UID2 とインテグレーションするには、以下
- トークン生成のためにサーバーサイドを変更します(オプションでトークンのリフレッシュ)。
## Prebid.js Version
+
この実装には、Prebid.js version 7.53.0 以降が必要です。バージョン情報については、[https://github.com/prebid/Prebid.js/releases](https://github.com/prebid/Prebid.js/releases) を参照してください。
## UID2 Prebid Module Page
-
+
Prebid と UID2 のインテグレーション方法に関する情報は、以下の場所にもあります:
- Prebid サイトの Prebid User ID Submodule の [Unified ID 2.0](https://docs.prebid.org/dev-docs/modules/userid-submodules/unified2.html) ページ。
- Prebid GitHub リポジトリの [UID2 User ID Submodule](https://github.com/prebid/Prebid.js/blob/master/modules/uid2IdSystem.md) ページ。