diff --git a/docs/endpoints/post-token-generate.md b/docs/endpoints/post-token-generate.md index 3158a3e3c..b484b8a1a 100644 --- a/docs/endpoints/post-token-generate.md +++ b/docs/endpoints/post-token-generate.md @@ -53,7 +53,7 @@ You must include only **one** of the following four conditional parameters, plus ### 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 the [POST /token/refresh](post-token-refresh.md), which does not require using an API key. +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). ::: 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/getting-started/gs-normalization-encoding.md b/docs/getting-started/gs-normalization-encoding.md index 927663328..1df8f0a78 100644 --- a/docs/getting-started/gs-normalization-encoding.md +++ b/docs/getting-started/gs-normalization-encoding.md @@ -55,7 +55,7 @@ For examples of various scenarios, see [Normalization Examples for Email](#norma ## Email Address Hash Encoding -An email hash is a Base64-encoded SHA-256 hash of a normalized email address. The email address is first normalized, then hashed using the SHA-256 hashing algorithm, and then the resulting bytes of the hash value are encoded using Base64 encoding. Note that the Base64 encoding is applied to the bytes of the hash value, not the hex-encoded string representation. +An email hash is a Base64-encoded SHA-256 hash of a normalized email address. The email address is first normalized, then hashed using the SHA-256 hashing algorithm, and then the resulting bytes of the hash value are encoded using Base64 encoding. Note that the Base64 encoding is applied to the bytes of the hash value, not the hex-encoded string representation. | Type | Example | Comments and Usage | | :--- | :--- | :--- | diff --git a/docs/guides/integration-mobile-client-server.md b/docs/guides/integration-mobile-client-server.md index 67f769e52..b59315906 100644 --- a/docs/guides/integration-mobile-client-server.md +++ b/docs/guides/integration-mobile-client-server.md @@ -51,7 +51,7 @@ You'll need to complete the following steps: This guide provides instructions for using either of these UID2 mobile SDKs: - SDK for Android (version 1.6.0 or later) -- SDK for iOS(version 1.7.0 or later) +- SDK for iOS (version 1.7.0 or later) For instructions for installing the correct SDK/version into your mobile app, see [Add the UID2 Mobile SDK to Your Mobile App](#add-the-uid2-mobile-sdk-to-your-mobile-app). diff --git a/docs/guides/integration-mobile-client-side.md b/docs/guides/integration-mobile-client-side.md index 8a9181ee2..8f3c1c4c1 100644 --- a/docs/guides/integration-mobile-client-side.md +++ b/docs/guides/integration-mobile-client-side.md @@ -52,7 +52,7 @@ To integrate with UID2 client-side, you'll need to complete the following steps: This guide provides instructions for using either of these UID2 mobile SDKs: - SDK for Android (version 1.6.0 or later) -- SDK for iOS(version 1.7.0 or later) +- SDK for iOS (version 1.7.0 or later) For instructions for installing the correct SDK/version into your mobile app, see [Add the UID2 Mobile SDK to Your Mobile App](#add-the-uid2-mobile-sdk-to-your-mobile-app). diff --git a/docs/guides/integration-mobile-overview.md b/docs/guides/integration-mobile-overview.md index 4918f3a70..5ff59b1de 100644 --- a/docs/guides/integration-mobile-overview.md +++ b/docs/guides/integration-mobile-overview.md @@ -98,7 +98,7 @@ The following table summarizes the functionality available with the various inte All options support either client-side or server-side integration. | Implementation Option | Generate Token from DII | Refresh Token | Android/iOS? | Send Token to Bidstream | -| :--- | :--- | :--- | :--- | :--- | +| :--- | :--- | :--- | :--- | :--- | | UID2 SDK for Android | ✅ | ✅ | Android | * | | UID2 SDK for iOS | ✅| ✅ | iOS | * | | GMA Plugin for Android
(Requires UID2 SDK for Android) | — | — | Android | ✅** | diff --git a/docs/guides/mobile-plugin-gma-ios.md b/docs/guides/mobile-plugin-gma-ios.md index 0a0a3e79b..a8be9260d 100644 --- a/docs/guides/mobile-plugin-gma-ios.md +++ b/docs/guides/mobile-plugin-gma-ios.md @@ -65,8 +65,8 @@ dependencies: [ In the XCode user interface, under Package Dependencies, add the following entry for your apps: -| Name | Location | Dependency Rule | -| :--- | :--- |:---------------------| +| 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-ios.md b/docs/guides/mobile-plugin-ima-ios.md index 8f1af6ce6..79b8727d9 100644 --- a/docs/guides/mobile-plugin-ima-ios.md +++ b/docs/guides/mobile-plugin-ima-ios.md @@ -65,8 +65,8 @@ dependencies: [ In the XCode user interface, under Package Dependencies, add the following entry for your apps: -| Name | Location | Dependency Rule | -| :--- | :--- |:---------------------| +| 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/summary-guides.md b/docs/guides/summary-guides.md index 5acc72f1e..2a722e874 100644 --- a/docs/guides/summary-guides.md +++ b/docs/guides/summary-guides.md @@ -39,26 +39,26 @@ The following resources are available for publisher web integrations. For a detailed summary of web integration options, see [Web Integration Overview](integration-options-publisher-web.md). ::: -| 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 and 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 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. | -| [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). | +| 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 and 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 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. | +| [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 The following resources are available for publishers integrating with Android or iOS devices. -| Integration Type| Documentation | Content Description | -| :--- | :--- | :--- | -| Android/iOS (Overview) | [Mobile Integration Overview for Android and iOS](integration-mobile-overview.md) | An overview of options for mobile app publishers who want to integrate with UID2 using the SDK for Android or the SDK for iOS. | -| Android/iOS, Client-Side Integration | [Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) | An integration guide for mobile app publishers who want to integrate with UID2 with changes only within the mobile app (no server-side changes). | -| Android/iOS, Client-Server Integration | [Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server.md) | An integration guide for mobile app publishers who want to integrate with UID2 by doing the following:
  1. Generating UID2 tokens server-side via either a Public or Private Operator.
  2. Passing the resulting identities to a mobile app for passing into the bidstream.
| +| Integration Guide | Content Description | +| :--- | :--- | +| [Mobile Integration Overview for Android and iOS](integration-mobile-overview.md) | An overview of options for mobile app publishers who want to integrate with UID2 using the SDK for Android or the SDK for iOS. | +| [Client-Side Integration Guide for Mobile](integration-mobile-client-side.md) | An integration guide for mobile app publishers who want to integrate with UID2 with changes only within the mobile app (no server-side changes). | +| [Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server.md) | An integration guide for mobile app publishers who want to integrate with UID2 by doing the following:
  1. Generating UID2 tokens server-side via either a Public or Private Operator.
  2. Passing the resulting identities to a mobile app for passing into the bidstream.
| ### CTV Integrations @@ -72,12 +72,12 @@ The following resources are available for publisher integrations supporting CTV. 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 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 Mobile Integration for Prebid.js](integration-prebid-mobile-summary.md) | A summary of information resources for UID2 integration with Prebid.js on mobile devices. | +| 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 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 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 @@ -85,7 +85,7 @@ The following resources are available for publishers integrating with Google Ad | Integration Guide | Content Description | | :--- | :--- | -| [Publisher - Google Ad Manager Secure Signals](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). | +| [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). | | [UID2 GMA Plugin for Android Integration Guide](mobile-plugin-gma-android.md) | The UID2 Google Mobile Ads (GMA) Plugin for Android enables publishers that use the [Google GMA SDK](https://developers.google.com/ad-manager/mobile-ads-sdk) to send UID2 tokens as [secure signals](https://support.google.com/admob/answer/11556288) in ad requests from Android apps. | | [UID2 GMA Plugin for iOS Integration Guide](mobile-plugin-gma-ios.md) | The UID2 Google Mobile Ads (GMA) Plugin for iOS enables publishers that use the [Google GMA SDK](https://developers.google.com/ad-manager/mobile-ads-sdk) to send UID2 tokens as [secure signals](https://support.google.com/admob/answer/11556288) in ad requests from iOS apps. | | [UID2 IMA Plugin for Android Integration Guide](mobile-plugin-ima-android.md) | The UID2 Interactive Media Ads (IMA) Plugin for Android enables publishers that use the [Google IMA SDK for Android](https://developers.google.com/interactive-media-ads/docs/sdks/android/client-side) to send UID2 tokens as [secure signals](https://support.google.com/admob/answer/11556288) in ad requests from Android apps. | diff --git a/docs/ref-info/glossary-uid.md b/docs/ref-info/glossary-uid.md index d73cebfe0..0eb77deb8 100644 --- a/docs/ref-info/glossary-uid.md +++ b/docs/ref-info/glossary-uid.md @@ -411,7 +411,7 @@ import Link from '@docusaurus/Link';
SHA-256
SHA-256 is the secure hashing algorithm that UID2 uses.
-
SHA-256 is part of the SHA-2 family of algorithms developed by the National Institute of Standards and Technology (NIST) and the National Security Agency (NSA) to succeed SHA-1. Each algorithm is named according to the number of bits in the output, so SHA-256 has 256 bits.
+
SHA-256 (sometimes called SHA256) is part of the SHA-2 family of algorithms developed by the National Institute of Standards and Technology (NIST) and the National Security Agency (NSA) to succeed SHA-1. Each algorithm is named according to the number of bits in the output, so SHA-256 has 256 bits.
For details, see https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf (specification).
Sharing (in UID2)
diff --git a/docs/sdks/sdk-ref-ios.md b/docs/sdks/sdk-ref-ios.md index f95b85c1b..ff78fdf8b 100644 --- a/docs/sdks/sdk-ref-ios.md +++ b/docs/sdks/sdk-ref-ios.md @@ -87,8 +87,8 @@ dependencies: [ In the XCode user interface, under Package Dependencies, add the following entry for your apps: -| Name | Location | Dependency Rule | -| :--- | :--- |:----------------------------------------| +| Name | Location | Dependency Rule | +| :--- | :--- | :--- | | uid2-ios-sdk | `git@github.com:IABTechLab/uid2-ios-sdk.git` | Up to next major version: 1.7.0 < 2.0.0 | ### Installing with CocoaPods @@ -192,4 +192,3 @@ The Identity variable stores and returns the current UID2Identity data object be #### identityStatus The identityStatus variable stores and returns the status of the current UID2 Identity being managed by the SDK. - diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-normalization-encoding.md b/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-normalization-encoding.md index 1433f9e90..7a4b94025 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-normalization-encoding.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/getting-started/gs-normalization-encoding.md @@ -55,7 +55,7 @@ UID2 Operator Service にハッシュ化されていないメールアドレス ## Email Address Hash Encoding -メールアドれづハッシュは、正規化されたメールアドレスの SHA-256 ハッシュを Base64 エンコードしたものです。メールアドレスはまず正規化され、次に SHA-256 ハッシュアルゴリズムを使ってハッシュ化され、その結果のハッシュ値のバイトが Base64 エンコーディングを使ってエンコードされます。Base64 エンコーディングはハッシュ値のバイトに適用されるのであって、16 進エンコーディングされた文字列表現には適用されないことに注意してください。 +メールアドれづハッシュは、正規化されたメールアドレスの SHA-256 ハッシュを Base64 エンコードしたものです。メールアドレスはまず正規化され、次に SHA-256 ハッシュアルゴリズムを使ってハッシュ化され、その結果のハッシュ値のバイトが Base64 エンコーディングを使ってエンコードされます。Base64 エンコーディングはハッシュ値のバイトに適用されるのであって、16 進エンコーディングされた文字列表現には適用されないことに注意してください。 | Type | Example | Comments and Usage | | :--- | :--- | :--- | 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 6f2bff821..2ff0c78d1 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 @@ -49,8 +49,8 @@ UID2 は、[Android](../sdks/sdk-ref-android.md) および [iOS](../sdks/sdk-ref このガイドは、次のいずれかの UID2 mobile SDK のバージョン 1.2.0 以上を使用する方法について説明します: -- SDK for Android -- SDK for iOS +- SDK for Android (version 1.6.0 or later) +- SDK for iOS (version 1.7.0 or later) 正しい SDK/バージョンをモバイルアプリにインストールする手順については、[Add the UID2 Mobile SDK to Your Mobile App](#add-the-uid2-mobile-sdk-to-your-mobile-app) を参照してください。 diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-gma-ios.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-gma-ios.md index 0f754c752..33f2bc11d 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-gma-ios.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-gma-ios.md @@ -65,8 +65,8 @@ dependencies: [ XCode ユーザーインターフェースで、パッケージ依存関係の下に、次のエントリを追加します: -| Name | Location | Dependency Rule | -| :--- | :--- |:---------------------| +| 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/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-ima-ios.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-ima-ios.md index 7b51953b8..1cfb71df1 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-ima-ios.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/guides/mobile-plugin-ima-ios.md @@ -65,8 +65,8 @@ dependencies: [ XCode ユーザーインターフェースで、パッケージ依存関係の下に、次のエントリを追加します: -| Name | Location | Dependency Rule | -| :--- | :--- |:----------------------------------------| +| 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/i18n/ja/docusaurus-plugin-content-docs/current/guides/summary-guides.md b/i18n/ja/docusaurus-plugin-content-docs/current/guides/summary-guides.md index 0725e9dfd..cfe6badb2 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 @@ -48,7 +48,7 @@ Web インテグレーションオプションの詳細は [Web Integration Over | [Client-Side Integration Guide for JavaScript](integration-javascript-client-side.md) | 最も簡単な実装方法で、Clent-Side の JavaScript の変更だけで UID2 とインテグレーションしたいパブリッシャー向けのインテグレーションガイドです。SDK for JavaScriptは、トークンの生成と更新を自動的に管理します。 | | [Client-Server Integration Guide for JavaScript](integration-javascript-client-server.md) | パブリッシャー向けのこのインテグレーションガイドでは、SDK for JavaScript を使用する標準的なウェブインテグレーションシナリオについて説明し、トークンを Server-Side で生成し、パブリッシャーのウェブページに渡す必要があります。 | | [Publisher Integration Guide, Server-Side](integration-publisher-server-side.md) | このインテグレーションガイドは、SDK for JavaScript を使用していないパブリッシャー向けです。 | -| [Publisher - Google Ad Manager Secure Signals](integration-google-ss.md) | このインテグレーションガイドでは、UID2 を Google Ad Manager のセキュアシグナル機能(旧称: Encrypted Signals for Publishers、ESP) で使用するパブリッシャーに必要な追加手順について説明します。 | +| [Google Ad Manager Secure Signals Integration Guide](integration-google-ss.md) | このインテグレーションガイドでは、UID2 を Google Ad Manager のセキュアシグナル機能(旧称: Encrypted Signals for Publishers、ESP) で使用するパブリッシャーに必要な追加手順について説明します。 | ### Mobile Integrations @@ -85,7 +85,7 @@ Google Ad Managerとインテグレーションするパブリッシャーは、 | Integration Guide | Content Description | | :--- | :--- | -| [Publisher - Google Ad Manager Secure Signals](integration-google-ss.md) | このインテグレーションガイドは、UID2 を Google Ad Manager の**secure signals**機能 (旧称: encrypted signals from publishers、ESP) で使用するパブリッシャーに必要な追加ステップをカバーしています。 | +| [Google Ad Manager Secure Signals Integration Guide](integration-google-ss.md) | このインテグレーションガイドは、UID2 を Google Ad Manager の**secure signals**機能 (旧称: encrypted signals from publishers、ESP) で使用するパブリッシャーに必要な追加ステップをカバーしています。 | | [UID2 GMA Plugin for Android Integration Guide](mobile-plugin-gma-android.md) | UID2 Google Mobile Ads (GMA) Plugin for Android は、[Google GMA SDK](https://developers.google.com/ad-manager/mobile-ads-sdk) を使用するパブリッシャーが、Android アプリからの広告リクエストで UID2 token を [secure signals](https://support.google.com/admob/answer/11556288) として送信できるようにします。 | | [UID2 GMA Plugin for iOS Integration Guide](mobile-plugin-gma-ios.md) | UID2 Google Mobile Ads (GMA) Plugin for iOS は、[Google GMA SDK](https://developers.google.com/ad-manager/mobile-ads-sdk) を使用するパブリッシャーが、iOS アプリからの広告リクエストで UID2 token を [secure signals](https://support.google.com/admob/answer/11556288) として送信できるようにします。 | | [UID2 IMA Plugin for Android Integration Guide](mobile-plugin-ima-android.md) | UID2 Interactive Media Ads (IMA) Plugin for Android は、[Google IMA SDK for Android](https://developers.google.com/interactive-media-ads/docs/sdks/android/client-side) を使用するパブリッシャーが、Android アプリからの広告リクエストで UID2 token を [secure signals](https://support.google.com/admob/answer/11556288) として送信できるようにします。 | diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-ios.md b/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-ios.md index bbbc45f44..7efb78ef0 100644 --- a/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-ios.md +++ b/i18n/ja/docusaurus-plugin-content-docs/current/sdks/sdk-ref-ios.md @@ -89,8 +89,8 @@ dependencies: [ アプリの Package Dependencies に次のエントリを追加します: -| Name | Location | Dependency Rule | -| :--- | :--- |:----------------------------------------| +| Name | Location | Dependency Rule | +| :--- | :--- | :--- | | uid2-ios-sdk | `git@github.com:IABTechLab/uid2-ios-sdk.git` | Up to next major version: 1.7.0 < 2.0.0 | ### Installing with CocoaPods