From f5b7e35ebf06cb9f7a428753bf81a5ea15c30525 Mon Sep 17 00:00:00 2001 From: Behnam Mozafari Date: Fri, 24 Apr 2026 11:58:36 +1000 Subject: [PATCH 1/2] UID2-6960: Back-fill token validator doc edits and announce it Ports the editorial and technical edits applied in EUID-docs#401 back to the UID2 token validator reference page, and adds a Documentation Updates entry announcing the new tool and page. - Reword Overview paragraph (less blame-y, remove CRM uploads, fix raw UID2 grammar) - Restructure Using the Token Validator into numbered steps with lead-ins before each subsection - Add 'normalized and then' to the email/phone hash bullets - Remove sharing/sharing-bid-stream from sidebar exclusion lists - Add ref-info/ref-token-validator to the sidebarAdvertisers exclusions (was missing) - Add Documentation Updates entry for the UID2 Token Validator Co-Authored-By: Claude Opus 4.7 (1M context) --- docs/ref-info/ref-token-validator.md | 15 +++++++++------ docs/ref-info/updates-doc.md | 14 ++++++++++++++ sidebars.js | 10 ++++------ 3 files changed, 27 insertions(+), 12 deletions(-) diff --git a/docs/ref-info/ref-token-validator.md b/docs/ref-info/ref-token-validator.md index 7cbbc6001..978649af0 100644 --- a/docs/ref-info/ref-token-validator.md +++ b/docs/ref-info/ref-token-validator.md @@ -14,7 +14,7 @@ The [UID2 Token Validator](https://token-validator.uidapi.com/) is a web-based t ## Overview -Publishers who generate UID2 tokens by providing DII sometimes receive tokens that appear valid but are unusable in the UID2 ecosystem. This happens when the normalization or hashing steps are not performed correctly. Because UID2 uses the normalized and hashed form of DII to derive the token, an error in either step produces a raw UID2 that is unique to that publisher. This mismatched raw UID2 will not correspond to the one used by other participants for the same DII, meaning the publisher's tokens will not match up with those from other publishers, data providers, or advertisers' CRM uploads. +When publishers generate UID2 tokens by providing DII, in some cases the resulting UID2 token appears valid but is not. This is because the normalization or hashing steps are not performed correctly. Because UID2 uses the normalized and hashed form of DII to derive the token, an error in either step produces a UID2 token and underlying raw UID2 that do not correspond to the correct values generated from the same DII by other participants. ## Prerequisites @@ -27,25 +27,28 @@ If you do not have these, see [API Keys](../portal/api-keys.md) for instructions ## Using the Token Validator -Enter your **API Key** (Client Key) and **Client Secret** in the fields at the top of the Token Validation section. +To use the token validator, follow these steps: -Select the **Operator** (environment) you want to validate against. For information about UID2 environments, see [Environments](../getting-started/gs-environments.md). +1. In the fields at the top of the Token Validation section, enter your **API Key** (Client Key) and **Client Secret**. +2. Select the **Operator** (environment) you want to validate against. For information about UID2 environments, see [Environments](../getting-started/gs-environments.md). ### Validate a Single Token +To validate a single token, follow these steps: + 1. Under **Input Mode**, select **Single Validation**. 2. In the **Identifier** field, enter the DII you used to generate the token. This can be: - A raw email address - A raw phone number - - A Base64-encoded email hash - - A Base64-encoded phone hash + - A normalized and then Base64-encoded email hash + - A normalized and then Base64-encoded phone hash 3. Select the identifier type that matches your input. 4. In the **Token** field, paste the UID2 token you want to validate. 5. Click **Validate Tokens**. ### Validate Multiple Tokens (CSV) -To validate a batch of token-identifier pairs: +To validate a batch of token-identifier pairs, follow these steps: 1. Under **Input Mode**, select **CSV**. 2. Prepare a CSV file with the following columns: diff --git a/docs/ref-info/updates-doc.md b/docs/ref-info/updates-doc.md index 335dfa053..928af01a2 100644 --- a/docs/ref-info/updates-doc.md +++ b/docs/ref-info/updates-doc.md @@ -24,6 +24,20 @@ Use the Tags toolbar to view a subset of documentation updates. The following documents were released in the second quarter of 2026. + + +### UID2 Token Validator + +April 24, 2026 + +We've added a new reference page for the [UID2 Token Validator](ref-token-validator.md), a web-based tool that validates UID2 tokens against their source DII so you can confirm that your token generation process is correct. + +For details, see [UID2 Token Validator](ref-token-validator.md). + + + + + ### Rate Limiting and Parallel Request Updates for POST /identity/map diff --git a/sidebars.js b/sidebars.js index 3aaa9a2a3..82f285175 100644 --- a/sidebars.js +++ b/sidebars.js @@ -446,10 +446,10 @@ const sidebars = { 'endpoints/post-token-generate', 'endpoints/post-token-validate', 'endpoints/post-token-refresh', - 'sharing/sharing-bid-stream' - ), + 'ref-info/ref-token-validator' + ), - sidebarDSPs: removeItems(fullSidebar, + sidebarDSPs: removeItems(fullSidebar, 'overviews/overview-publishers', 'overviews/overview-advertisers', 'overviews/overview-data-providers', @@ -489,11 +489,10 @@ const sidebars = { 'guides/integration-databricks', 'guides/integration-aws-entity-resolution', 'guides/advertiser-dataprovider-endpoints', - 'sharing/sharing-bid-stream', 'ref-info/ref-token-validator' ), - sidebarDataProviders: removeItems(fullSidebar, + sidebarDataProviders: removeItems(fullSidebar, 'overviews/overview-publishers', 'overviews/overview-advertisers', 'overviews/overview-dsps', @@ -530,7 +529,6 @@ const sidebars = { 'endpoints/post-token-generate', 'endpoints/post-token-validate', 'endpoints/post-token-refresh', - 'sharing/sharing-bid-stream', 'ref-info/ref-token-validator' ), From ea91d9ec27fc43089dbd990cf64a6048ceab46b3 Mon Sep 17 00:00:00 2001 From: Behnam Mozafari Date: Fri, 24 Apr 2026 13:48:00 +1000 Subject: [PATCH 2/2] UID2-6960: Keep sharing/sharing-bid-stream sidebar exclusions Revert the sharing/sharing-bid-stream removals. The only sidebar fix needed here is adding ref-info/ref-token-validator to the Advertisers exclusions. Co-Authored-By: Claude Opus 4.7 (1M context) --- sidebars.js | 3 +++ 1 file changed, 3 insertions(+) diff --git a/sidebars.js b/sidebars.js index 82f285175..326f5a087 100644 --- a/sidebars.js +++ b/sidebars.js @@ -446,6 +446,7 @@ const sidebars = { 'endpoints/post-token-generate', 'endpoints/post-token-validate', 'endpoints/post-token-refresh', + 'sharing/sharing-bid-stream', 'ref-info/ref-token-validator' ), @@ -489,6 +490,7 @@ const sidebars = { 'guides/integration-databricks', 'guides/integration-aws-entity-resolution', 'guides/advertiser-dataprovider-endpoints', + 'sharing/sharing-bid-stream', 'ref-info/ref-token-validator' ), @@ -529,6 +531,7 @@ const sidebars = { 'endpoints/post-token-generate', 'endpoints/post-token-validate', 'endpoints/post-token-refresh', + 'sharing/sharing-bid-stream', 'ref-info/ref-token-validator' ),