|
| 1 | +--- |
| 2 | +title: How the UID2 Token Is Created |
| 3 | +description: Reference information about the process for generating a UID2 token. |
| 4 | +hide_table_of_contents: false |
| 5 | +sidebar_position: 06 |
| 6 | +--- |
| 7 | + |
| 8 | +import Link from '@docusaurus/Link'; |
| 9 | + |
| 10 | +# How the UID2 Token Is Created |
| 11 | + |
| 12 | +:::note |
| 13 | +This article describes how the UID2 token that the publisher sends in the bidstream is created. The process is the same for advertisers creating UID2 tokens for conversion pixels. It does not apply to <Link href="../ref-info/glossary-uid#gl-tokenized-sharing">tokenized sharing</Link>, where raw UID2s are encrypted into UID2 tokens before sending to another sharing participant. |
| 14 | +::: |
| 15 | + |
| 16 | +When a publisher sends a user's <Link href="../ref-info/glossary-uid#gl-dii">DII</Link>—<Link href="../ref-info/glossary-uid#gl-hash">hashed</Link> or unhashed email addresses or phone numbers—to the UID2 Operator, and in return receives a <Link href="../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. |
| 17 | + |
| 18 | + Some preliminary steps are taken by the publisher, but most of the processing steps are done by the UID2 <Link href="../ref-info/glossary-uid#gl-operator">Operator</Link>. |
| 19 | + |
| 20 | +It's very important that the publisher steps are performed in the correct sequence: |
| 21 | +- When steps are performed in sequence, the resulting value can be recognized as related to other [UID2 identifiers](../intro.md#uid2-identifier-types) generated from online activity by the same individual: the underlying [raw UID2](../ref-info/glossary-uid.md#gl-raw-uid2) matches the raw UID2s generated by other UID2 participants from the same DII, and therefore the token is suitable for targeted advertising. |
| 22 | +- If steps are taken out of sequence, the resulting value cannot be related to other UID2 identifiers generated from online activity by the same individual, and therefore the token is not suitable for targeted advertising. |
| 23 | + |
| 24 | +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). |
| 25 | + |
| 26 | +## Steps to Create a UID2 Token |
| 27 | + |
| 28 | +The following table shows the steps for creating a UID2 token from DII, the sequence, and who performs each step. |
| 29 | + |
| 30 | +For an example with sample values, see [Creating a UID2 Token—Example](#creating-a-uid2-tokenexample). |
| 31 | + |
| 32 | +<table width="100%"> |
| 33 | + <thead> |
| 34 | + <tr> |
| 35 | + <th width="5%">Step</th> |
| 36 | + <th width="35%">Action</th> |
| 37 | + <th width="30%">Who Does It?</th> |
| 38 | + <th width="35%">Documentation</th> |
| 39 | + </tr> |
| 40 | + </thead> |
| 41 | + <tbody> |
| 42 | + <tr> |
| 43 | + <td>1</td> |
| 44 | + <td><Link href="../ref-info/glossary-uid#gl-normalize">Normalization</Link></td> |
| 45 | + <td>**Email**: Publisher or UID2 Operator<br/>**Phone number**: Publisher must normalize</td> |
| 46 | + <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> |
| 47 | + </tr> |
| 48 | + <tr> |
| 49 | + <td>2</td> |
| 50 | + <td><Link href="../ref-info/glossary-uid#gl-sha-256">SHA-256</Link> hashing of normalized email address</td> |
| 51 | + <td>Publisher or UID2 Operator</td> |
| 52 | + <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> |
| 53 | + </tr> |
| 54 | + <tr> |
| 55 | + <td>3</td> |
| 56 | + <td>Base64 encoding of SHA-256 hash</td> |
| 57 | + <td>Publisher or UID2 Operator</td> |
| 58 | + <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> |
| 59 | + </tr> |
| 60 | + <tr> |
| 61 | + <td>4</td> |
| 62 | + <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 | + <td>Publisher</td> |
| 64 | + <td>Various: for a summary, see [Implementation Resources](../overviews/overview-publishers.md#implementation-resources)</td> |
| 65 | + </tr> |
| 66 | + <tr> |
| 67 | + <td>5</td> |
| 68 | + <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> |
| 69 | + <td>UID2 Operator</td> |
| 70 | + <td>Not applicable: these steps are all performed by the UID2 Operator.</td> |
| 71 | + </tr> |
| 72 | + <tr> |
| 73 | + <td>6</td> |
| 74 | + <td>Encrypt the raw UID2 to create a UID2 token.</td> |
| 75 | + <td>UID2 Operator</td> |
| 76 | + <td>Not applicable: performed by the UID2 Operator.</td> |
| 77 | + </tr> |
| 78 | + </tbody> |
| 79 | +</table> |
| 80 | + |
| 81 | +## Creating a UID2 Token—Example |
| 82 | + |
| 83 | +The following diagram shows the high-level steps for creating a [raw UID2](../ref-info/glossary-uid.md#gl-raw-uid2) (first column, second column) and then a [UID2 token](../ref-info/glossary-uid.md#gl-uid2-token) (third column). |
| 84 | + |
| 85 | +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. |
| 86 | + |
| 87 | + |
0 commit comments