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
<dd>When we say a UID2 token is an opaque string, we mean that the way that the token is computed is not shared. No assumptions should be made about the format or length of the string, or any other aspect of it.</dd>
Copy file name to clipboardExpand all lines: docs/ref-info/ref-tokens.md
+9-12Lines changed: 9 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,21 +9,20 @@ import Link from '@docusaurus/Link';
9
9
10
10
# UID2 Tokens and Refresh Tokens
11
11
12
-
When a publisher sends a user's <Linkhref="../ref-info/glossary-uid#gl-dii">DII</Link> (email address or phone number) to the UID2 Operator, whether via one of the UID2 SDKs or the [POST /token/generate](../endpoints/post-token-generate.md) endpoint, the UID2 Operator returns a <ahref="glossary-uid#gl-uid2-token">UID2 token</a> with associated values such as refresh token. The token is an opaque alphanumeric string. Every time a token is generated from DII input, the token value is different. Token values are never the same. Because of the way UID2 works, different instances of activity, on browsers, CTV, and electronic devices such as phone and tablets, can be matched without compromising the privacy of the individual. The token is designed so that it cannot be reverse engineered to arrive at the original email address or phone number.
12
+
When a publisher sends a user's <Linkhref="../ref-info/glossary-uid#gl-dii">DII</Link> (email address or phone number) to the UID2 Operator, whether via one of the UID2 SDKs or the [POST /token/generate](../endpoints/post-token-generate.md) endpoint, the UID2 Operator returns a <ahref="glossary-uid#gl-uid2-token">UID2 token</a> with associated values, including a refresh token. The token is an alphanumeric string. Each time a token is generated from DII input, the token value is different. Because of the way UID2 works, different instances of activity, on browsers, CTV, and electronic devices such as phone and tablets, can still be matched to the same <ahref="glossary-uid#gl-raw-uid2">raw UID2</a> generated from the user's DII, even though the token might be different. The token is designed to protect against reverse engineering that might reveal the original email address or phone number.
13
13
14
-
For security reasons, the UID2 token has a short life. Along with the UID2 token, the UID2 Operator sends a <ahref="glossary-uid#gl-refresh-token">refresh token</a> that the publisher can use to generate a new UID2 token. If the token is not refreshed before it expires, it becomes invalid and cannot be used for targeted advertising.
14
+
The UID2 token has a short life. Along with the UID2 token, the UID2 Operator sends a <ahref="glossary-uid#gl-refresh-token">refresh token</a> that the publisher can use to generate a new UID2 token. If the UID2 token is not refreshed before the refresh token expires, it becomes invalid.
15
15
16
16
## UID2 Tokens: Key Information
17
17
18
18
Here are some key points about UID2 tokens:
19
19
20
20
- The UID2 token is a unique value: no two UID2 tokens are the same.
21
21
- UID2 tokens are case sensitive.
22
-
- The token value is opaque: do not make any assumptions about the format or about the length of the string.
22
+
- The token value is an <ahref="glossary-uid#gl-opaque">opaque</a> string: do not make any assumptions about the format or length of the string.
23
23
- The token generation logic checks for user opt-out. If the user has opted out of UID2, no UID2 token is generated. For details, see [User Opt-Out](../getting-started/gs-opt-out.md).
24
24
- The token has a limited life, but can be refreshed using the refresh token.
25
-
- The token can be refreshed many times, to get a new UID2 token, as long as the UID2 token is always refreshed before the refresh token expires.
26
-
- As an alternative to refreshing an existing UID2 token, you can always generate a new UID2 token from the original hashed or unhashed email address or phone number instead.
25
+
- You can refresh many times, to get a new UID2 token and corresponding new refresh token, as long as the current UID2 token is always refreshed before the current refresh token expires.
27
26
- If the token has expired, or as an alternative to refreshing an existing token, you can always generate a new UID2 token from the original hashed or unhashed email address or phone number.
28
27
- Publishers send UID2 tokens in the bidstream.
29
28
- Refreshing a UID2 token does not invalidate/expire the original or previous UID2 token. You can still use the earlier token until it expires.
@@ -32,23 +31,21 @@ Here are some key points about UID2 tokens:
32
31
33
32
Here are some key points about refresh tokens:
34
33
35
-
- A refresh token is an opaque string that is issued along with the <ahref="glossary-uid#gl-uid2-token">UID2 token</a>.
34
+
- A refresh token is a string that is issued along with the <ahref="glossary-uid#gl-uid2-token">UID2 token</a>.
36
35
- Refresh tokens are case sensitive.
37
-
- The token value is opaque: do not make any assumptions about the format or about the length of the string.
38
-
- You can use the refresh token to generate a new UID2 token before the old one expires.
36
+
- The token value is <ahref="glossary-uid#gl-opaque">opaque</a>: do not make any assumptions about the format or length of the string.
37
+
- You can use the refresh token to generate a new UID2 token and new refresh token before the current refresh token expires.
39
38
- Using refresh tokens is optional: you could choose to generate a new token from DII each time rather than refreshing an existing token.
40
39
- Token refresh can be managed in a variety of ways, such as:
41
40
- With a UID2 SDK (see [SDK Functionality](../sdks/summary-sdks.md#sdk-functionality))
42
41
- By calling the [POST /token/refresh](../endpoints/post-token-refresh.md) endpoint
43
42
- By using the UID2 Prebid.js module (see [UID2 Integration Overview for Prebid.js](../guides/integration-prebid.md))
44
43
- The [POST /token/refresh](../endpoints/post-token-refresh.md) endpoint does not require authentication with your UID2 credentials.
45
44
- When a new UID2 token is generated and returned, a new refresh token is returned along with it.
46
-
- As long as you refresh the token before it expires, you can refresh many times. There is no limit as long as the UID2 token and corresponding refresh token are valid.
47
-
- If you refresh the token, and get a new token before the old one has expired, you can use either the new token or the old one, as long as you use a token that is still valid/has not expired.
48
-
- In most cases, you can refresh tokens on the client side, even if the token was generated on the server side. For details about refresh functionality for the various SDKs, see [SDK Functionality](../sdks/summary-sdks.md#sdk-functionality) (Refresh UID2 Token column).
45
+
- In most cases, you can refresh tokens on the client side, even if the token was generated on the server side. For details about refresh functionality for the various SDKs, see [SDK Functionality](../sdks/summary-sdks.md#sdk-functionality) (*Refresh UID2 Token* column).
49
46
- When the UID2 Operator service receives the refresh token with a request for a new UID2 token, it checks for user opt-out. If the user has opted out of UID2, no new UID2 token is generated. For details, see [User Opt-Out](../getting-started/gs-opt-out.md).
Copy file name to clipboardExpand all lines: i18n/ja/docusaurus-plugin-content-docs/current/ref-info/ref-tokens.md
+9-12Lines changed: 9 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,21 +9,20 @@ import Link from '@docusaurus/Link';
9
9
10
10
# UID2 Tokens and Refresh Tokens
11
11
12
-
When a publisher sends a user's <Linkhref="../ref-info/glossary-uid#gl-dii">DII</Link> (email address or phone number) to the UID2 Operator, whether via one of the UID2 SDKs or the [POST /token/generate](../endpoints/post-token-generate.md) endpoint, the UID2 Operator returns a <ahref="glossary-uid#gl-uid2-token">UID2 token</a> with associated values such as refresh token. The token is an opaque alphanumeric string. Every time a token is generated from DII input, the token value is different. Token values are never the same. Because of the way UID2 works, different instances of activity, on browsers, CTV, and electronic devices such as phone and tablets, can be matched without compromising the privacy of the individual. The token is designed so that it cannot be reverse engineered to arrive at the original email address or phone number.
12
+
When a publisher sends a user's <Linkhref="../ref-info/glossary-uid#gl-dii">DII</Link> (email address or phone number) to the UID2 Operator, whether via one of the UID2 SDKs or the [POST /token/generate](../endpoints/post-token-generate.md) endpoint, the UID2 Operator returns a <ahref="glossary-uid#gl-uid2-token">UID2 token</a> with associated values, including a refresh token. The token is an alphanumeric string. Each time a token is generated from DII input, the token value is different. Because of the way UID2 works, different instances of activity, on browsers, CTV, and electronic devices such as phone and tablets, can still be matched to the same <ahref="glossary-uid#gl-raw-uid2">raw UID2</a> generated from the user's DII, even though the token might be different. The token is designed to protect against reverse engineering that might reveal the original email address or phone number.
13
13
14
-
For security reasons, the UID2 token has a short life. Along with the UID2 token, the UID2 Operator sends a <ahref="glossary-uid#gl-refresh-token">refresh token</a> that the publisher can use to generate a new UID2 token. If the token is not refreshed before it expires, it becomes invalid and cannot be used for targeted advertising.
14
+
The UID2 token has a short life. Along with the UID2 token, the UID2 Operator sends a <ahref="glossary-uid#gl-refresh-token">refresh token</a> that the publisher can use to generate a new UID2 token. If the UID2 token is not refreshed before the refresh token expires, it becomes invalid.
15
15
16
16
## UID2 Tokens: Key Information
17
17
18
18
Here are some key points about UID2 tokens:
19
19
20
20
- The UID2 token is a unique value: no two UID2 tokens are the same.
21
21
- UID2 tokens are case sensitive.
22
-
- The token value is opaque: do not make any assumptions about the format or about the length of the string.
22
+
- The token value is an <ahref="glossary-uid#gl-opaque">opaque</a> string: do not make any assumptions about the format or length of the string.
23
23
- The token generation logic checks for user opt-out. If the user has opted out of UID2, no UID2 token is generated. For details, see [User Opt-Out](../getting-started/gs-opt-out.md).
24
24
- The token has a limited life, but can be refreshed using the refresh token.
25
-
- The token can be refreshed many times, to get a new UID2 token, as long as the UID2 token is always refreshed before the refresh token expires.
26
-
- As an alternative to refreshing an existing UID2 token, you can always generate a new UID2 token from the original hashed or unhashed email address or phone number instead.
25
+
- You can refresh many times, to get a new UID2 token and corresponding new refresh token, as long as the current UID2 token is always refreshed before the current refresh token expires.
27
26
- If the token has expired, or as an alternative to refreshing an existing token, you can always generate a new UID2 token from the original hashed or unhashed email address or phone number.
28
27
- Publishers send UID2 tokens in the bidstream.
29
28
- Refreshing a UID2 token does not invalidate/expire the original or previous UID2 token. You can still use the earlier token until it expires.
@@ -32,23 +31,21 @@ Here are some key points about UID2 tokens:
32
31
33
32
Here are some key points about refresh tokens:
34
33
35
-
- A refresh token is an opaque string that is issued along with the <ahref="glossary-uid#gl-uid2-token">UID2 token</a>.
34
+
- A refresh token is a string that is issued along with the <ahref="glossary-uid#gl-uid2-token">UID2 token</a>.
36
35
- Refresh tokens are case sensitive.
37
-
- The token value is opaque: do not make any assumptions about the format or about the length of the string.
38
-
- You can use the refresh token to generate a new UID2 token before the old one expires.
36
+
- The token value is <ahref="glossary-uid#gl-opaque">opaque</a>: do not make any assumptions about the format or length of the string.
37
+
- You can use the refresh token to generate a new UID2 token and new refresh token before the current refresh token expires.
39
38
- Using refresh tokens is optional: you could choose to generate a new token from DII each time rather than refreshing an existing token.
40
39
- Token refresh can be managed in a variety of ways, such as:
41
40
- With a UID2 SDK (see [SDK Functionality](../sdks/summary-sdks.md#sdk-functionality))
42
41
- By calling the [POST /token/refresh](../endpoints/post-token-refresh.md) endpoint
43
42
- By using the UID2 Prebid.js module (see [UID2 Integration Overview for Prebid.js](../guides/integration-prebid.md))
44
43
- The [POST /token/refresh](../endpoints/post-token-refresh.md) endpoint does not require authentication with your UID2 credentials.
45
44
- When a new UID2 token is generated and returned, a new refresh token is returned along with it.
46
-
- As long as you refresh the token before it expires, you can refresh many times. There is no limit as long as the UID2 token and corresponding refresh token are valid.
47
-
- If you refresh the token, and get a new token before the old one has expired, you can use either the new token or the old one, as long as you use a token that is still valid/has not expired.
48
-
- In most cases, you can refresh tokens on the client side, even if the token was generated on the server side. For details about refresh functionality for the various SDKs, see [SDK Functionality](../sdks/summary-sdks.md#sdk-functionality) (Refresh UID2 Token column).
45
+
- In most cases, you can refresh tokens on the client side, even if the token was generated on the server side. For details about refresh functionality for the various SDKs, see [SDK Functionality](../sdks/summary-sdks.md#sdk-functionality) (*Refresh UID2 Token* column).
49
46
- When the UID2 Operator service receives the refresh token with a request for a new UID2 token, it checks for user opt-out. If the user has opted out of UID2, no new UID2 token is generated. For details, see [User Opt-Out](../getting-started/gs-opt-out.md).
0 commit comments