Skip to content

Commit 92b0d24

Browse files
Merge pull request #1014 from IABTechLab/bmz-UID2-6960-backfill-token-validator-docs
UID2-6960: Back-fill token validator doc edits + Documentation Updates entry
2 parents 60144c0 + ea91d9e commit 92b0d24

3 files changed

Lines changed: 28 additions & 10 deletions

File tree

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

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ The [UID2 Token Validator](https://token-validator.uidapi.com/) is a web-based t
1414

1515
## Overview
1616

17-
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.
17+
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 <Link href="../ref-info/glossary-uid#gl-raw-uid2">raw UID2</Link> that do not correspond to the correct values generated from the same DII by other participants.
1818

1919
## Prerequisites
2020

@@ -27,25 +27,28 @@ If you do not have these, see [API Keys](../portal/api-keys.md) for instructions
2727

2828
## Using the Token Validator
2929

30-
Enter your **API Key** (Client Key) and **Client Secret** in the fields at the top of the Token Validation section.
30+
To use the token validator, follow these steps:
3131

32-
Select the **Operator** (environment) you want to validate against. For information about UID2 environments, see [Environments](../getting-started/gs-environments.md).
32+
1. In the fields at the top of the Token Validation section, enter your **API Key** (Client Key) and **Client Secret**.
33+
2. Select the **Operator** (environment) you want to validate against. For information about UID2 environments, see [Environments](../getting-started/gs-environments.md).
3334

3435
### Validate a Single Token
3536

37+
To validate a single token, follow these steps:
38+
3639
1. Under **Input Mode**, select **Single Validation**.
3740
2. In the **Identifier** field, enter the DII you used to generate the token. This can be:
3841
- A raw email address
3942
- A raw phone number
40-
- A Base64-encoded email hash
41-
- A Base64-encoded phone hash
43+
- A normalized and then Base64-encoded email hash
44+
- A normalized and then Base64-encoded phone hash
4245
3. Select the identifier type that matches your input.
4346
4. In the **Token** field, paste the UID2 token you want to validate.
4447
5. Click **Validate Tokens**.
4548

4649
### Validate Multiple Tokens (CSV)
4750

48-
To validate a batch of token-identifier pairs:
51+
To validate a batch of token-identifier pairs, follow these steps:
4952

5053
1. Under **Input Mode**, select **CSV**.
5154
2. Prepare a CSV file with the following columns:

docs/ref-info/updates-doc.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,20 @@ Use the Tags toolbar to view a subset of documentation updates.
2424

2525
The following documents were released in the second quarter of 2026.
2626

27+
<CustomTagsContainer tags="Reference">
28+
29+
### UID2 Token Validator
30+
31+
April 24, 2026
32+
33+
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.
34+
35+
For details, see [UID2 Token Validator](ref-token-validator.md).
36+
37+
<!-- UID2-6592 -->
38+
39+
</CustomTagsContainer>
40+
2741
<CustomTagsContainer tags="Endpoints">
2842

2943
### Rate Limiting and Parallel Request Updates for POST /identity/map

sidebars.js

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -446,10 +446,11 @@ const sidebars = {
446446
'endpoints/post-token-generate',
447447
'endpoints/post-token-validate',
448448
'endpoints/post-token-refresh',
449-
'sharing/sharing-bid-stream'
450-
),
449+
'sharing/sharing-bid-stream',
450+
'ref-info/ref-token-validator'
451+
),
451452

452-
sidebarDSPs: removeItems(fullSidebar,
453+
sidebarDSPs: removeItems(fullSidebar,
453454
'overviews/overview-publishers',
454455
'overviews/overview-advertisers',
455456
'overviews/overview-data-providers',
@@ -493,7 +494,7 @@ const sidebars = {
493494
'ref-info/ref-token-validator'
494495
),
495496

496-
sidebarDataProviders: removeItems(fullSidebar,
497+
sidebarDataProviders: removeItems(fullSidebar,
497498
'overviews/overview-publishers',
498499
'overviews/overview-advertisers',
499500
'overviews/overview-dsps',

0 commit comments

Comments
 (0)