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-how-uid-is-created.md
+10-19Lines changed: 10 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,74 +9,67 @@ import Link from '@docusaurus/Link';
9
9
10
10
# How the UID2 Token Is Created
11
11
12
-
When a publisher sends <Linkhref="../ref-info/glossary-uid#gl-dii">DII</Link> (email or phone number) to UID2, and in return receives a <Linkhref="../ref-info/glossary-uid#gl-uid2-token">UID2 token</Link> to use for targeted advertising, there is a very specific sequence of processing steps that occurs along the way.
12
+
When a publisher sends a user's <Linkhref="../ref-info/glossary-uid#gl-dii">DII</Link>—<Linkhref="../ref-info/glossary-uid#gl-hash">hashed</Link> or unhashed email addresses or phone numbers—to the UID2 Operator, and in return receives a <Linkhref="../ref-info/glossary-uid#gl-uid2-token">UID2 token</Link> to use for targeted advertising, there is a very specific sequence of processing steps that occurs along the way.
13
13
14
14
Some preliminary steps are taken by the publisher, but most of the processing steps are done by the UID2 <Linkhref="../ref-info/glossary-uid#gl-operator">Operator</Link>.
15
15
16
16
It's very important that the publisher steps are performed in the correct sequence:
17
-
- When steps are performed in sequence, the resulting value **matches**other instances of tokens generated from online activity by the same individual, and therefore the token is **valuable** for targeted advertising.
18
-
- If steps are taken out of sequence, the resulting value **does not match**other instances of tokens generated from online activity by the same individual, and therefore the token is **not valid** for targeted advertising.
17
+
- When steps are performed in sequence, the resulting value can be recognized as related to other instances of tokens generated from online activity by the same individual: the underlying [raw UID2](../ref-info/glossary-uid.md#gl-raw-uid2) matches other tokens generated from the same raw UID2, and therefore the token is suitable for targeted advertising.
18
+
- If steps are taken out of sequence, the resulting value cannot be related to other instances of tokens generated from online activity by the same individual, and therefore the token is not suitable for targeted advertising.
19
19
20
20
For a summary, see [Steps to Create a UID2 Token](#steps-to-create-a-uid2-token). For an example in diagram form, see [Creating a UID2 Token—Example](#creating-a-uid2-tokenexample).
21
21
22
22
## Steps to Create a UID2 Token
23
23
24
24
The following table shows the steps for creating a UID2 token from DII, the sequence, and who performs each step.
25
25
26
-
For an example showing each step performed on a sample value, see [Creating a UID2 Token—Example](#creating-a-uid2-tokenexample).
26
+
For an example with sample values, see [Creating a UID2 Token—Example](#creating-a-uid2-tokenexample).
<td>**Email**: Publisher or UID2 Operator<br/>**Phone number**: Publisher must normalize</td>
43
42
<td>[Email Address Normalization](../getting-started/gs-normalization-encoding.md#email-address-normalization)<br/>[Phone Number Normalization](../getting-started/gs-normalization-encoding.md#phone-number-normalization)</td>
44
-
<td>Not shown. For examples, see [Normalization Examples for Email](../getting-started/gs-normalization-encoding.md#normalization-examples-for-email).</td>
45
43
</tr>
46
44
<tr>
47
45
<td>2</td>
48
-
<td>SHA-256 hashing of normalized email address</td>
46
+
<td><Link href="../ref-info/glossary-uid#gl-sha-256">SHA-256</Link> hashing of normalized email address</td>
49
47
<td>Publisher or UID2 Operator</td>
50
48
<td>[Email Address Hash Encoding](../getting-started/gs-normalization-encoding.md#email-address-hash-encoding)<br/>[Phone Number Hash Encoding](../getting-started/gs-normalization-encoding.md#phone-number-hash-encoding)</td>
51
-
<td>Column 1</td>
52
49
</tr>
53
50
<tr>
54
51
<td>3</td>
55
-
<td>Hex to Base64 encoding of SHA-256 hash</td>
52
+
<td>Base64 encoding of SHA-256 hash</td>
56
53
<td>Publisher or UID2 Operator</td>
57
54
<td>[Email Address Hash Encoding](../getting-started/gs-normalization-encoding.md#email-address-hash-encoding)<br/>[Phone Number Hash Encoding](../getting-started/gs-normalization-encoding.md#phone-number-hash-encoding)</td>
58
-
<td>Column 1</td>
59
55
</tr>
60
56
<tr>
61
57
<td>4</td>
62
58
<td>Send value to UID2 Operator via the [POST /token/generate](../endpoints/post-token-generate.md) endpoint, an SDK, Prebid.js, or another supported integration.</td>
63
59
<td>Publisher</td>
64
60
<td>Various: for a summary, see [Implementation Resources](../overviews/overview-publishers.md#implementation-resources)</td>
65
-
<td>Not shown</td>
66
61
</tr>
67
62
<tr>
68
63
<td>5</td>
69
64
<td>Perform multiple steps including hashing and adding the secret <Link href="../ref-info/glossary-uid#gl-salt">salt</Link> value to create a raw UID2.</td>
70
65
<td>UID2 Operator</td>
71
66
<td>Not applicable: these steps are all performed by the UID2 Operator.</td>
72
-
<td>Column 2</td>
73
67
</tr>
74
68
<tr>
75
69
<td>6</td>
76
70
<td>Encrypt the raw UID2 to create a UID2 token.</td>
77
71
<td>UID2 Operator</td>
78
72
<td>Not applicable: performed by the UID2 Operator.</td>
79
-
<td>Column 3</td>
80
73
</tr>
81
74
</tbody>
82
75
</table>
@@ -88,5 +81,3 @@ The following diagram shows the high-level steps for creating a [raw UID2](../re
88
81
The publisher can send a request to the [POST /token/generate](../endpoints/post-token-generate.md) endpoint or use one of the other integration options, such as an SDK or Prebid. Whatever the integration option, the result is a UID2 token—an encrypted value that the publisher can send in the bidstream for targeted advertising.
89
82
90
83
91
-
92
-
The token cannot be reverse engineered to tie back to the advertiser side. The UID2 process operates by passing an email or its hashed equivalent to the UID2 Operator, and the Operator then processes and encrypts the value to create a UID2 token. Demand-Side Platforms (DSPs) decrypt this token to arrive at the underlying raw UID2, and can then align it with UID2 segments predefined by advertisers who have transformed their data into UID2 format. Each participant only has access to their own specific information.
Copy file name to clipboardExpand all lines: i18n/ja/docusaurus-plugin-content-docs/current/ref-info/ref-how-uid-is-created.md
+10-19Lines changed: 10 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,74 +9,67 @@ import Link from '@docusaurus/Link';
9
9
10
10
# How the UID2 Token Is Created
11
11
12
-
When a publisher sends <Linkhref="../ref-info/glossary-uid#gl-dii">DII</Link> (email or phone number) to UID2, and in return receives a <Linkhref="../ref-info/glossary-uid#gl-uid2-token">UID2 token</Link> to use for targeted advertising, there is a very specific sequence of processing steps that occurs along the way.
12
+
When a publisher sends a user's <Linkhref="../ref-info/glossary-uid#gl-dii">DII</Link>—<Linkhref="../ref-info/glossary-uid#gl-hash">hashed</Link> or unhashed email addresses or phone numbers—to the UID2 Operator, and in return receives a <Linkhref="../ref-info/glossary-uid#gl-uid2-token">UID2 token</Link> to use for targeted advertising, there is a very specific sequence of processing steps that occurs along the way.
13
13
14
14
Some preliminary steps are taken by the publisher, but most of the processing steps are done by the UID2 <Linkhref="../ref-info/glossary-uid#gl-operator">Operator</Link>.
15
15
16
16
It's very important that the publisher steps are performed in the correct sequence:
17
-
- When steps are performed in sequence, the resulting value **matches**other instances of tokens generated from online activity by the same individual, and therefore the token is **valuable** for targeted advertising.
18
-
- If steps are taken out of sequence, the resulting value **does not match**other instances of tokens generated from online activity by the same individual, and therefore the token is **not valid** for targeted advertising.
17
+
- When steps are performed in sequence, the resulting value can be recognized as related to other instances of tokens generated from online activity by the same individual: the underlying [raw UID2](../ref-info/glossary-uid.md#gl-raw-uid2) matches other tokens generated from the same raw UID2, and therefore the token is suitable for targeted advertising.
18
+
- If steps are taken out of sequence, the resulting value cannot be related to other instances of tokens generated from online activity by the same individual, and therefore the token is not suitable for targeted advertising.
19
19
20
20
For a summary, see [Steps to Create a UID2 Token](#steps-to-create-a-uid2-token). For an example in diagram form, see [Creating a UID2 Token—Example](#creating-a-uid2-tokenexample).
21
21
22
22
## Steps to Create a UID2 Token
23
23
24
24
The following table shows the steps for creating a UID2 token from DII, the sequence, and who performs each step.
25
25
26
-
For an example showing each step performed on a sample value, see [Creating a UID2 Token—Example](#creating-a-uid2-tokenexample).
26
+
For an example with sample values, see [Creating a UID2 Token—Example](#creating-a-uid2-tokenexample).
<td>**Email**: Publisher or UID2 Operator<br/>**Phone number**: Publisher must normalize</td>
43
42
<td>[Email Address Normalization](../getting-started/gs-normalization-encoding.md#email-address-normalization)<br/>[Phone Number Normalization](../getting-started/gs-normalization-encoding.md#phone-number-normalization)</td>
44
-
<td>Not shown. For examples, see [Normalization Examples for Email](../getting-started/gs-normalization-encoding.md#normalization-examples-for-email).</td>
45
43
</tr>
46
44
<tr>
47
45
<td>2</td>
48
-
<td>SHA-256 hashing of normalized email address</td>
46
+
<td><Link href="../ref-info/glossary-uid#gl-sha-256">SHA-256</Link> hashing of normalized email address</td>
49
47
<td>Publisher or UID2 Operator</td>
50
48
<td>[Email Address Hash Encoding](../getting-started/gs-normalization-encoding.md#email-address-hash-encoding)<br/>[Phone Number Hash Encoding](../getting-started/gs-normalization-encoding.md#phone-number-hash-encoding)</td>
51
-
<td>Column 1</td>
52
49
</tr>
53
50
<tr>
54
51
<td>3</td>
55
-
<td>Hex to Base64 encoding of SHA-256 hash</td>
52
+
<td>Base64 encoding of SHA-256 hash</td>
56
53
<td>Publisher or UID2 Operator</td>
57
54
<td>[Email Address Hash Encoding](../getting-started/gs-normalization-encoding.md#email-address-hash-encoding)<br/>[Phone Number Hash Encoding](../getting-started/gs-normalization-encoding.md#phone-number-hash-encoding)</td>
58
-
<td>Column 1</td>
59
55
</tr>
60
56
<tr>
61
57
<td>4</td>
62
58
<td>Send value to UID2 Operator via the [POST /token/generate](../endpoints/post-token-generate.md) endpoint, an SDK, Prebid.js, or another supported integration.</td>
63
59
<td>Publisher</td>
64
60
<td>Various: for a summary, see [Implementation Resources](../overviews/overview-publishers.md#implementation-resources)</td>
65
-
<td>Not shown</td>
66
61
</tr>
67
62
<tr>
68
63
<td>5</td>
69
64
<td>Perform multiple steps including hashing and adding the secret <Link href="../ref-info/glossary-uid#gl-salt">salt</Link> value to create a raw UID2.</td>
70
65
<td>UID2 Operator</td>
71
66
<td>Not applicable: these steps are all performed by the UID2 Operator.</td>
72
-
<td>Column 2</td>
73
67
</tr>
74
68
<tr>
75
69
<td>6</td>
76
70
<td>Encrypt the raw UID2 to create a UID2 token.</td>
77
71
<td>UID2 Operator</td>
78
72
<td>Not applicable: performed by the UID2 Operator.</td>
79
-
<td>Column 3</td>
80
73
</tr>
81
74
</tbody>
82
75
</table>
@@ -88,5 +81,3 @@ The following diagram shows the high-level steps for creating a [raw UID2](../re
88
81
The publisher can send a request to the [POST /token/generate](../endpoints/post-token-generate.md) endpoint or use one of the other integration options, such as an SDK or Prebid. Whatever the integration option, the result is a UID2 token—an encrypted value that the publisher can send in the bidstream for targeted advertising.
89
82
90
83
91
-
92
-
The token cannot be reverse engineered to tie back to the advertiser side. The UID2 process operates by passing an email or its hashed equivalent to the UID2 Operator, and the Operator then processes and encrypts the value to create a UID2 token. Demand-Side Platforms (DSPs) decrypt this token to arrive at the underlying raw UID2, and can then align it with UID2 segments predefined by advertisers who have transformed their data into UID2 format. Each participant only has access to their own specific information.
0 commit comments