UID2-6592: Document UID2 token validator in integration guides by BehnamMozafari · Pull Request #1001 · IABTechLab/uid2docs

BehnamMozafari · 2026-03-06T03:35:04Z

Added new reference page "UID2 Token Validator" giving an overview and instructions
Linked to reference page in "Preparing DII for Processing" section of integration guides
Linked to tool reference page in "Normalization and Encoding"

…ink error

docs/getting-started/gs-normalization-encoding.md

docs/ref-info/ref-token-validator.md

i18n/ja/docusaurus-plugin-content-docs/current/ref-info/ref-token-validator.md

genwhittTTD

Looks good! Few small edits and I sent the proposed updates to the sidebars file via Slack.

Great work.

docs/getting-started/gs-normalization-encoding.md

docs/ref-info/ref-token-validator.md

docs/snippets/_snpt-preparing-emails-and-phone-numbers.mdx

sidebars.js

genwhittTTD · 2026-03-10T15:09:11Z

docs/ref-info/ref-token-validator.md

+
+## 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 <Link href="../ref-info/glossary-uid#gl-raw-uid2">Raw UID2</Link> 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.


Two instances Raw UID2 > raw UID2. We do not generally initial cap this term (only at the beginning of a sentence, in a heading, that type of instance).

genwhittTTD · 2026-03-10T15:11:08Z

docs/ref-info/ref-token-validator.md

+   - A raw phone number
+   - A Base64-encoded email hash
+   - A Base64-encoded phone hash
+3. Select the **Identifier Type** that matches your input.


Because you're not referring to the name of the UI element here, bold and initial cap not needed:

Suggested change

3. Select the **Identifier Type** that matches your input.

3. Select the identifier type that matches your input.

genwhittTTD · 2026-03-10T15:13:28Z

docs/ref-info/ref-token-validator.md

+3. Upload the CSV file.
+4. Click **Validate Tokens**.
+
+## Interpreting Validation Results


Keep headings in the same form... "Interpret" in this case (Validate, Interpret):

Suggested change

## Interpreting Validation Results

## Interpret Validation Results

genwhittTTD · 2026-03-10T15:15:49Z

docs/ref-info/ref-token-validator.md

+
+## Interpreting Validation Results
+
+After clicking **Validate Tokens**, the **Validation Results** table displays a row for each token-identifier pair:


Couple of things here. Technically the table is the subject of the sentence, but you are the one clicking. Reword for clarity.
Plus, just our internal standards, we uses "as shown in the following table" or something like that, and no colon before a table, just a colon before a list.

Suggested change

After clicking **Validate Tokens**, the **Validation Results** table displays a row for each token-identifier pair:

When you click **Validate Tokens**, the **Validation Results** table displays a row for each token-identifier pair, in the format shown in the following table.

genwhittTTD · 2026-03-10T15:17:42Z

docs/ref-info/ref-token-validator.md

+| `Failed: {"status":"unauthorized"}` | The API credentials provided are invalid or unauthorized. |
+
+:::tip
+If the result is **Failed: Token does not match identifier**, compare the **Normalized Hash** shown in the results with what your own implementation produced for the same DII. If they differ, the issue is in your normalization or hashing steps. See [Normalization and Encoding](../getting-started/gs-normalization-encoding.md) and [Preparing Emails and Phone Numbers for Processing](ref-preparing-emails-and-phone-numbers-for-processing.md).


Again just our TTD doc standards... rather than "see", we use "For details, see" consistently.

Suggested change

If the result is **Failed: Token does not match identifier**, compare the **Normalized Hash** shown in the results with what your own implementation produced for the same DII. If they differ, the issue is in your normalization or hashing steps. See [Normalization and Encoding](../getting-started/gs-normalization-encoding.md) and [Preparing Emails and Phone Numbers for Processing](ref-preparing-emails-and-phone-numbers-for-processing.md).

If the result is **Failed: Token does not match identifier**, compare the **Normalized Hash** shown in the results with what your own implementation produced for the same DII. If they differ, the issue is in your normalization or hashing steps. For details, see [Normalization and Encoding](../getting-started/gs-normalization-encoding.md) and [Preparing Emails and Phone Numbers for Processing](ref-preparing-emails-and-phone-numbers-for-processing.md).

genwhittTTD · 2026-03-10T15:18:30Z

docs/ref-info/ref-token-validator.md

+
+1. Under **Input Mode**, select **CSV**.
+2. Prepare a CSV file with the following columns: 
+   - `identifier`: The DII (raw email, raw phone, email hash, or phone hash)


There is a period (full stop) only on the third item. Period on each one for consistency.

genwhittTTD

Few more small edits.
And then there is one more thing... I built both languages and there are errors in the Japanese, as I'd suspected there would be, because you're adding new content.
If you could just address these few edits please, I'll check in the Japanese updates and you'll be good to go.

BehnamMozafari added 5 commits March 6, 2026 14:07

Add token validator reference page

608693b

Add reference page to integration guides

993d585

Added reference to token validator in Normalization and Encoding page

77911b2

Removed reference to token validator from liveramp guide

1a2d224

Copied over ref-token-validator.md to japanese folder to fix broken l…

874040d

…ink error

BehnamMozafari requested review from genwhittTTD, jon8787 and sunnywu March 6, 2026 03:35

BehnamMozafari self-assigned this Mar 6, 2026

sunnywu reviewed Mar 6, 2026

View reviewed changes

docs/getting-started/gs-normalization-encoding.md Outdated Show resolved Hide resolved

sunnywu reviewed Mar 6, 2026

View reviewed changes

docs/ref-info/ref-token-validator.md Outdated Show resolved Hide resolved

sunnywu reviewed Mar 6, 2026

View reviewed changes

i18n/ja/docusaurus-plugin-content-docs/current/ref-info/ref-token-validator.md Outdated Show resolved Hide resolved

BehnamMozafari added 2 commits March 6, 2026 15:22

Address review comments

063d814

Address review comments

5d4c139

genwhittTTD requested changes Mar 6, 2026

View reviewed changes

BehnamMozafari added 2 commits March 10, 2026 10:51

Address Gen's review comments

4c29e90

Merge branch 'main' into bmz-UID2-6592-token-validator

7038637

BehnamMozafari requested a review from genwhittTTD March 10, 2026 00:05

Link "Raw UID2" to glossary

a708b07

genwhittTTD reviewed Mar 10, 2026

View reviewed changes

genwhittTTD requested changes Mar 10, 2026

View reviewed changes


		## 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 <Link href="../ref-info/glossary-uid#gl-raw-uid2">Raw UID2</Link> 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.

	3. Select the Identifier Type that matches your input.
	3. Select the identifier type that matches your input.

	## Interpreting Validation Results
	## Interpret Validation Results


		## Interpreting Validation Results

		After clicking Validate Tokens, the Validation Results table displays a row for each token-identifier pair:

	After clicking Validate Tokens, the Validation Results table displays a row for each token-identifier pair:
	When you click Validate Tokens, the Validation Results table displays a row for each token-identifier pair, in the format shown in the following table.

Conversation

BehnamMozafari commented Mar 6, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

genwhittTTD left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

genwhittTTD Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

genwhittTTD Mar 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

genwhittTTD Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

genwhittTTD Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

genwhittTTD Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

genwhittTTD Mar 10, 2026

Choose a reason for hiding this comment

Uh oh!

genwhittTTD left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

genwhittTTD Mar 10, 2026 •

edited

Loading