You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/ref-info/ref-token-validator.md
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ The [UID2 Token Validator](https://token-validator.uidapi.com/) is a web-based t
14
14
15
15
## Overview
16
16
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 <Linkhref="../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 <Linkhref="../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.
18
18
19
19
## Prerequisites
20
20
@@ -27,25 +27,28 @@ If you do not have these, see [API Keys](../portal/api-keys.md) for instructions
27
27
28
28
## Using the Token Validator
29
29
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:
31
31
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).
33
34
34
35
### Validate a Single Token
35
36
37
+
To validate a single token, follow these steps:
38
+
36
39
1. Under **Input Mode**, select **Single Validation**.
37
40
2. In the **Identifier** field, enter the DII you used to generate the token. This can be:
38
41
- A raw email address
39
42
- 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
42
45
3. Select the identifier type that matches your input.
43
46
4. In the **Token** field, paste the UID2 token you want to validate.
44
47
5. Click **Validate Tokens**.
45
48
46
49
### Validate Multiple Tokens (CSV)
47
50
48
-
To validate a batch of token-identifier pairs:
51
+
To validate a batch of token-identifier pairs, follow these steps:
Copy file name to clipboardExpand all lines: docs/ref-info/updates-doc.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,6 +24,20 @@ Use the Tags toolbar to view a subset of documentation updates.
24
24
25
25
The following documents were released in the second quarter of 2026.
26
26
27
+
<CustomTagsContainertags="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
+
27
41
<CustomTagsContainertags="Endpoints">
28
42
29
43
### Rate Limiting and Parallel Request Updates for POST /identity/map
0 commit comments