gwh-APIDOCS-3914-change-heading-case#1010
Conversation
| 5. [Monitor for raw UID2 refresh](#5-monitor-for-raw-uid2-refresh) | ||
|
|
||
| 6. [Monitor for Opt-Out Status](#6-monitor-for-opt-out-status) | ||
| 6. [Monitor for opt-out status](#6-monitor-for-opt-out-status) |
|
|
||
| 1. [Create a clean room for UID2 collaboration](#create-clean-room-for-uid2-collaboration). | ||
| 1. [Send your Databricks sharing identifier to your UID2 contact](#send-sharing-identifier-to-uid2-contact). | ||
| 1. [Send your databricks sharing identifier to your UID2 contact](#send-sharing-identifier-to-uid2-contact). |
There was a problem hiding this comment.
uppercase "data bricks" here and elsewhere
| If your UID2s are not being passed through Google, make sure that you chose the correct Web Signal Deployment Method during setup. | ||
|
|
||
| For details, see the **Important** note in [Allow Secure Signals Sharing](#allow-secure-signals-sharing). | ||
| For details, see the **Important** note in [Allow Secure Signals sharing](#allow-secure-signals-sharing). |
There was a problem hiding this comment.
is "Secure Signals" a proper name?
| ::: | ||
|
|
||
| ## Private Operator Benefits | ||
| ## Private Operator benefits |
There was a problem hiding this comment.
is "Private Operator" a proper noun?
| <SnptUpgradePolicy /> | ||
|
|
||
| ## Keeping the Operator Key Secure | ||
| ## Keeping the operator key secure |
There was a problem hiding this comment.
Is this related to "Private Operator?" Should it be reverted to uppercase?
| | Set `params.uid2Token` to the response body as a JavaScript object. | See [Client Refresh mode uid2Token example](#client-refresh-mode-uid2token-example) | You might choose to provide the response body via `params.uid2Token` in either of these cases:<ul><li>If you are already storing a lot of data in the cookie and adding the response body might exceed the cookie size limit.</li><li>If you prefer to have the Prebid module store the token value for you.</li></ul> | | ||
|
|
||
| #### Client Refresh Mode Cookie Example | ||
| #### Client Refresh mode cookie example |
There was a problem hiding this comment.
is "Client Refresh" a proper noun?
| | :--- | :--- | :--- | | ||
| | `UID2_TOKEN` | TEXT | The value is one of the following:<ul><li>Encryption successful: The UID2 token containing the raw UID2.</li><li>Encryption not successful: `NULL`.</li></ul> | | ||
| | `ENCRYPTION_STATUS` | TEXT | The value is one of the following:<ul><li>Encryption successful: `NULL`.</li><li>Encryption not successful: The reason why the raw UID2 was not encrypted. For example: `INVALID_RAW_UID2` or `INVALID NOT_AUTHORIZED_FOR_MASTER_KEY`.<br/>For details, see [Values for the ENCRYPTION_STATUS Column](#values-for-the-encryption_status-column).</li></ul> | | ||
| | `ENCRYPTION_STATUS` | TEXT | The value is one of the following:<ul><li>Encryption successful: `NULL`.</li><li>Encryption not successful: The reason why the raw UID2 was not encrypted. For example: `INVALID_RAW_UID2` or `INVALID NOT_AUTHORIZED_FOR_MASTER_KEY`.<br/>For details, see [Values for the encryption_status column](#values-for-the-encryption_status-column).</li></ul> | |
There was a problem hiding this comment.
ENCRYPTION_STATUS should remain all caps?
| | `UID2` | TEXT | The value is one of the following:<ul><li>Decryption successful: The raw UID2 corresponding to the UID2 token.</li><li>Decryption not successful: `NULL`.</li></ul> | | ||
| | `SITE_ID` | INT | The value is one of the following:<ul><li>Decryption successful: The identifier of the UID2 participant that encrypted the token.</li><li>Decryption not successful: `NULL`.</li></ul> | | ||
| | `DECRYPTION_STATUS` | TEXT | The value is one of the following:<ul><li>Decryption successful: `NULL`.</li><li>Decryption not successful: The reason why the UID2 token was not decrypted; for example, `EXPIRED_TOKEN`.<br/>For details, see [Values for the DECRYPTION_STATUS Column](#values-for-the-decryption_status-column).</li></ul> | | ||
| | `DECRYPTION_STATUS` | TEXT | The value is one of the following:<ul><li>Decryption successful: `NULL`.</li><li>Decryption not successful: The reason why the UID2 token was not decrypted; for example, `EXPIRED_TOKEN`.<br/>For details, see [Values for the decryption_status column](#values-for-the-decryption_status-column).</li></ul> | |
There was a problem hiding this comment.
DECRYPTION_STATUS should remain all caps in description?
| | `UID` | TEXT | The value is one of the following:<ul><li>DII was successfully mapped: The UID2 associated with the DII.</li><li>DII was not successfully mapped: `NULL`.</li></ul> | | ||
| | `BUCKET_ID` | TEXT | The value is one of the following:<ul><li>DII was successfully mapped: The ID of the <Link href="../ref-info/glossary-uid#gl-salt-bucket">salt bucket</Link> used to generate the UID2. This ID maps to the bucket ID in the `SALT_BUCKETS` view.</li><li>DII was not successfully mapped: `NULL`.</li></ul> | | ||
| | `UNMAPPED` | TEXT | The value is one of the following:<ul><li>DII was successfully mapped: `NULL`.</li><li>DII was not successfully mapped: The reason why the identifier was not mapped: `OPTOUT`, `INVALID IDENTIFIER`, or `INVALID INPUT TYPE`.<br/>For details, see [Values for the UNMAPPED Column](#values-for-the-unmapped-column).</li></ul> | | ||
| | `UNMAPPED` | TEXT | The value is one of the following:<ul><li>DII was successfully mapped: `NULL`.</li><li>DII was not successfully mapped: The reason why the identifier was not mapped: `OPTOUT`, `INVALID IDENTIFIER`, or `INVALID INPUT TYPE`.<br/>For details, see [Values for the unmapped column](#values-for-the-unmapped-column).</li></ul> | |
There was a problem hiding this comment.
UNMAPPED should stay all caps?
| #### Get the Principal ID of the Managed Identity | ||
| #### Get the principal ID of the managed identity | ||
|
|
||
| To get the Principal ID, run the following command, using your own values as needed: |
| | Reloads `syslog-ng`. | `sudo /usr/sbin/syslog-ng-ctl reload` | | ||
|
|
||
| ## Keeping the Operator Key Secure | ||
| ## Keeping the operator key secure |
There was a problem hiding this comment.
should "operator" be uppercase?
| <SnptRotatingTheKeys /> | ||
|
|
||
| ## UID2 Operator Error Codes | ||
| ## UID2 Operator error codes |
There was a problem hiding this comment.
should "Operator" be lowercase?
| ``` | ||
|
|
||
| ### Set Up the Gateway Load Balancer | ||
| ### Set up the gateway load balancer |
There was a problem hiding this comment.
in body text this is a proper noun?
| To set up and configure the account that you created when you installed the gcloud CLI, complete the following steps. Replace the placeholder values with your own valid values. | ||
|
|
||
| 1. Switch to the project that you created in [Confidential Space Account Setup](#confidential-space-account-setup): | ||
| 1. Switch to the project that you created in [Confidential Space account setup](#confidential-space-account-setup): |
There was a problem hiding this comment.
is "Confidential Space" a proper noun?
| ::: | ||
|
|
||
| #### Create Secret for the Operator Key in Secret Manager | ||
| #### Create secret for the operator key in secret manager |
There was a problem hiding this comment.
is "secret manager" a proper noun?
| November 2, 2023 | ||
|
|
||
| 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 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. |
There was a problem hiding this comment.
keep "Client" uppercase?
| <CustomTagsContainer tags="Guides, Mobile, SDKs"> | ||
|
|
||
| ### IMA Mobile Plugin for Android | ||
| ### IMA mobile Plugin for Android |
There was a problem hiding this comment.
should "Plugin" also be lowercase?
| <CustomTagsContainer tags="Infrastructure"> | ||
|
|
||
| ### UID2 Website in Japanese | ||
| ### UID2 website in japanese |
| As a publisher, there are two ways to use the SDK for Java: | ||
| 1. [**Basic Usage**](#basic-usage) is for publishers who want to use this SDK's HTTP implementation (synchronous [OkHttp](https://square.github.io/okhttp/)). | ||
| 2. [**Advanced Usage**](#advanced-usage) is for publishers who prefer to use their own HTTP library. | ||
| 1. [**basic usage**](#basic-usage) is for publishers who want to use this SDK's HTTP implementation (synchronous [OkHttp](https://square.github.io/okhttp/)). |
| 2. [**Advanced Usage**](#advanced-usage) is for publishers who prefer to use their own HTTP library. | ||
| 1. [**basic usage**](#basic-usage) is for publishers who want to use this SDK's HTTP implementation (synchronous [OkHttp](https://square.github.io/okhttp/)). | ||
| 2. [**advanced usage**](#advanced-usage) is for publishers who prefer to use their own HTTP library. | ||
|
|
| @@ -24,10 +24,10 @@ The Trade Desk (現在の UID2 Administrator) とすでに取引関係がある | |||
|
|
|||
| | Your Role | Contact Email | | |||
| | :--- | :--- | | |||
| | パブリッシャー、アプリ開発者 | [UID2publishers@thetradedesk.com](mailto:UID2publishers@thetradedesk.com) | | |||
| | 代理店、ブランド、DSP、SSP、Customer Data Platform (CDP)、データプロバイダー | [UID2partners@thetradedesk.com](mailto:UID2partners@thetradedesk.com) | | |||
| | パブリッシャー、アプリ開発者 | [Uid2publishers@thetradedesk.com](mailto:UID2publishers@thetradedesk.com) | | |||
| | パブリッシャー、アプリ開発者 | [UID2publishers@thetradedesk.com](mailto:UID2publishers@thetradedesk.com) | | ||
| | 代理店、ブランド、DSP、SSP、Customer Data Platform (CDP)、データプロバイダー | [UID2partners@thetradedesk.com](mailto:UID2partners@thetradedesk.com) | | ||
| | パブリッシャー、アプリ開発者 | [Uid2publishers@thetradedesk.com](mailto:UID2publishers@thetradedesk.com) | | ||
| | 代理店、ブランド、DSP、SSP、Customer Data Platform (CDP)、データプロバイダー | [Uid2partners@thetradedesk.com](mailto:UID2partners@thetradedesk.com) | |
|
|
||
| この条件を満たす必要がある場合、または質問がある場合は、[UID2partners@thetradedesk.com](mailto:UID2partners@thetradedesk.com) までお問い合わせください。 | ||
| この条件を満たす必要がある場合、または質問がある場合は、[Uid2partners@thetradedesk.com](mailto:UID2partners@thetradedesk.com) までお問い合わせください。 |
There was a problem hiding this comment.
revert email formatting?
| @@ -80,9 +80,9 @@ Server-Side SDK を使用している場合、SDK はエンドポイントに関 | |||
| 1. [Establish identity: capture user data](#establish-identity-capture-user-data) | |||
| 2. [Bid using a UID2 token](#bid-using-a-uid2-token) | |||
| 3. [Refresh a UID2 token](#refresh-a-uid2-token) | |||
| 4. [Clear Identity: user logout](#clear-identity-user-logout) | |||
| 4. [Clear identity: user logout](#clear-identity-user-logout) | |||
| @@ -136,9 +136,9 @@ DII が電話番号の場合、UID2 [電話番号正規化](../getting-started/g | |||
| | :--- | :--- | :--- | | |||
| | `UID2` | TEXT | DII は正常にマッピングされました: <br/>DII は正常にマップされませんでした: `NULL`。 | | |||
| | `BUCKET_ID` | TEXT | DII は正常にマップされました: UID2 の生成に使われたセカンドレベルのソルトバケットの ID。この ID は `UID2_SALT_BUCKETS` ビューのバケット ID に対応します。<br/>DII は正常にマップされませんでした: `NULL`。 | | |||
| | `UNMAPPED` | TEXT | DII は正常にマッピングされました: `NULL`<br/>DII は正常にマップされませんでした: `NULL`: DII は正常にマップされませんでした: 識別子がマップされなかった理由: `OPTOUT`、`INVALID IDENTIFIER`、`INVALID INPUT TYPE` のいずれか。詳細は [Values for the UNMAPPED Column](#values-for-the-unmapped-column) を参照してください。 | | |||
| | `UNMAPPED` | TEXT | DII は正常にマッピングされました: `NULL`<br/>DII は正常にマップされませんでした: `NULL`: DII は正常にマップされませんでした: 識別子がマップされなかった理由: `OPTOUT`、`INVALID IDENTIFIER`、`INVALID INPUT TYPE` のいずれか。詳細は [Values for the unmapped column](#values-for-the-unmapped-column) を参照してください。 | | |||
There was a problem hiding this comment.
Revert "unmapped" before "column?"
| @@ -8,7 +8,7 @@ displayed_sidebar: docs | |||
|
|
|||
| import Link from '@docusaurus/Link'; | |||
|
|
|||
| # UID2 GMA Plugin for Android Integration Guide | |||
| # UID2 GMA Plugin for Android integration guide | |||
| @@ -156,7 +156,7 @@ Key Vault を作成したら、[managed identity](https://learn.microsoft.com/en | |||
| | Parameter | Description | | |||
| | :--- | :--- | | |||
| | `vaultName` | Operator Key シークレットをホストするための Key Vault の名前。選択する名前はグローバルに一意である必要があります。 | | |||
| | `operatorKeyValue` | アカウント設定の一環として UID チームから受け取った `OPERATOR_KEY` シークレット値 ([Set Up UID2 Operator Account](#set-up-uid2-operator-account) を参照)。この値はあなたに固有であり、パスワードとして機能します。安全で秘密に保つ必要があります。 | | |||
| | `operatorKeyValue` | アカウント設定の一環として UID チームから受け取った `OPERATOR_KEY` シークレット値 ([Set up UID2 Operator account](#set-up-uid2-operator-account) を参照)。この値はあなたに固有であり、パスワードとして機能します。安全で秘密に保つ必要があります。 | | |||
| @@ -749,84 +749,84 @@ SDK for JavaScript Version 3 の機能強化に伴い、ドキュメントが大 | |||
|
|
|||
| <CustomTagsContainer tags="Guides, Private Operator"> | |||
|
|
|||
| ### Private Operator Guide for Google Confidential Space | |||
| ### Private Operator guide for Google confidential space | |||
There was a problem hiding this comment.
uppercase "Confidential Space?"
|
|
||
| パブリッシャーとして、SDK for Java を使用するには 2 つの方法があります: | ||
| 1. [**Basic Usage**](#basic-usage) は、この SDK の HTTP 実装 (synchronous [OkHttp](https://square.github.io/okhttp/)) を使いたいパブリッシャー向けです。 | ||
| 2. [**Advanced Usage**](#advanced-usage) は、独自の HTTP ライブラリを使用したいパブリッシャー向けです。 | ||
| 1. [**basic usage**](#basic-usage) は、この SDK の HTTP 実装 (synchronous [OkHttp](https://square.github.io/okhttp/)) を使いたいパブリッシャー向けです。 |
| 1. [**Basic Usage**](#basic-usage) は、この SDK の HTTP 実装 (synchronous [OkHttp](https://square.github.io/okhttp/)) を使いたいパブリッシャー向けです。 | ||
| 2. [**Advanced Usage**](#advanced-usage) は、独自の HTTP ライブラリを使用したいパブリッシャー向けです。 | ||
| 1. [**basic usage**](#basic-usage) は、この SDK の HTTP 実装 (synchronous [OkHttp](https://square.github.io/okhttp/)) を使いたいパブリッシャー向けです。 | ||
| 2. [**advanced usage**](#advanced-usage) は、独自の HTTP ライブラリを使用したいパブリッシャー向けです。 |

Change all headings in the docs from heading case to sentence case, including h1 (using a Claude script).
includes YAML values.