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/endpoints/post-token-generate.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ You must include only **one** of the following four conditional parameters, plus
53
53
### Request Examples
54
54
55
55
:::important
56
-
To ensure that the API key used to access the service remains secret, the `POST /token/generate` endpoint must be called from the server side, unlike the [POST /token/refresh](post-token-refresh.md), which does not require using an API key.
56
+
To ensure that the API key used to access the service remains secret, the `POST /token/generate` endpoint must be called from the server side, unlike [POST /token/refresh](post-token-refresh.md) which does not require using an API key. If you want to generate tokens on the client side, see [Client-Side Integration Options](../guides/integration-options-publisher-web.md#client-side-integration-options) (for web-based implementations) or [UID2 Client-Side Integration Guide for Mobile](../guides/integration-mobile-client-side.md).
57
57
:::
58
58
59
59
The following are unencrypted JSON request body examples for each parameter, one of which you should include in your token generation requests:
Copy file name to clipboardExpand all lines: docs/getting-started/gs-normalization-encoding.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ For examples of various scenarios, see [Normalization Examples for Email](#norma
55
55
56
56
## Email Address Hash Encoding
57
57
58
-
An email hash is a Base64-encoded SHA-256 hash of a normalized email address. The email address is first normalized, then hashed using the SHA-256 hashing algorithm, and then the resulting bytes of the hash value are encoded using Base64 encoding. Note that the Base64 encoding is applied to the bytes of the hash value, not the hex-encoded string representation.
58
+
An email hash is a Base64-encoded <Linkhref="../ref-info/glossary-uid#gl-sha-256">SHA-256</Link> hash of a normalized email address. The email address is first normalized, then hashed using the SHA-256 hashing algorithm, and then the resulting bytes of the hash value are encoded using Base64 encoding. Note that the Base64 encoding is applied to the bytes of the hash value, not the hex-encoded string representation.
Copy file name to clipboardExpand all lines: docs/guides/integration-mobile-client-server.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@ You'll need to complete the following steps:
51
51
This guide provides instructions for using either of these UID2 mobile SDKs:
52
52
53
53
- SDK for Android (version 1.6.0 or later)
54
-
- SDK for iOS(version 1.7.0 or later)
54
+
- SDK for iOS(version 1.7.0 or later)
55
55
56
56
For instructions for installing the correct SDK/version into your mobile app, see [Add the UID2 Mobile SDK to Your Mobile App](#add-the-uid2-mobile-sdk-to-your-mobile-app).
Copy file name to clipboardExpand all lines: docs/guides/integration-mobile-client-side.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ To integrate with UID2 client-side, you'll need to complete the following steps:
52
52
This guide provides instructions for using either of these UID2 mobile SDKs:
53
53
54
54
- SDK for Android (version 1.6.0 or later)
55
-
- SDK for iOS(version 1.7.0 or later)
55
+
- SDK for iOS(version 1.7.0 or later)
56
56
57
57
For instructions for installing the correct SDK/version into your mobile app, see [Add the UID2 Mobile SDK to Your Mobile App](#add-the-uid2-mobile-sdk-to-your-mobile-app).
|[UID2 Integration Overview for Prebid](integration-prebid.md)| An overview of options for publishers who want to integrate with UID2 and generate UID2 tokens to be passed by Prebid.js and Prebid Mobile SDK in the RTB <Linkhref="../ref-info/glossary-uid#gl-bidstream">bidstream</Link>.|
45
-
|[UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md)| An integration guide for publishers who want to integrate with UID2 and want Prebid.js to manage token generation and automatic token refresh as well as passing the tokens into the RTB bidstream. This guide is for publishers who want to request UID2 tokens client-side, which is the easiest implementation approach. |
46
-
|[UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md)| An integration guide for publishers who want to integrate with UID2 and generate identity tokens to be passed by Prebid.js in the RTB bidstream. This guide is for publishers who are using a private operator or who want to generate tokens server-side.|
47
-
|[UID2 Integration Overview for JavaScript](integration-javascript.md)| An overview of options for publishers who want to integrate with UID2 using the JavaScript SDK.|
48
-
|[Client-Side Integration Guide for JavaScript](integration-javascript-client-side.md)| A guide for publishers who want to integrate with UID2 using only client-side JavaScript changes, which is the easiest implementation approach.<br/>The SDK for JavaScript manages token generation and token refresh automatically.|
49
-
|[Client-Server Integration Guide for JavaScript](integration-javascript-client-server.md)| This integration guide for publishers covers standard web integration scenarios that use the SDK for JavaScript and requires the token to be generated on the server side and passed to the publishers' web pages. |
50
-
|[Publisher Integration Guide, Server-Side](integration-publisher-server-side.md)| This integration guide is for publishers that do not use the SDK for JavaScript.|
51
-
|[Google Ad Manager Secure Signals Integration Guide](integration-google-ss.md)| This integration guide covers the additional steps needed for publishers using UID2 with the Google Ad Manager Secure Signals feature (previously known as Encrypted Signals for Publishers, ESP).|
42
+
| Integration Guide | Content Description |
43
+
|:---|:---|
44
+
|[UID2 Integration Overview for Prebid](integration-prebid.md)| An overview of options for publishers who want to integrate with UID2 and generate UID2 tokens to be passed by Prebid.js and Prebid Mobile SDK in the RTB <Linkhref="../ref-info/glossary-uid#gl-bidstream">bidstream</Link>. |
45
+
|[UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md)| An integration guide for publishers who want to integrate with UID2 and want Prebid.js to manage token generation and automatic token refresh as well as passing the tokens into the RTB bidstream. This guide is for publishers who want to request UID2 tokens client-side, which is the easiest implementation approach. |
46
+
|[UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md)| An integration guide for publishers who want to integrate with UID2 and generate identity tokens to be passed by Prebid.js in the RTB bidstream. This guide is for publishers who are using a private operator or who want to generate tokens server-side. |
47
+
|[UID2 Integration Overview for JavaScript](integration-javascript.md)| An overview of options for publishers who want to integrate with UID2 using the JavaScript SDK. |
48
+
|[Client-Side Integration Guide for JavaScript](integration-javascript-client-side.md)| A guide for publishers who want to integrate with UID2 using only client-side JavaScript changes, which is the easiest implementation approach.<br/>The SDK for JavaScript manages token generation and token refresh automatically. |
49
+
|[Client-Server Integration Guide for JavaScript](integration-javascript-client-server.md)| This integration guide for publishers covers standard web integration scenarios that use the SDK for JavaScript and requires the token to be generated on the server side and passed to the publishers' web pages. |
50
+
|[Publisher Integration Guide, Server-Side](integration-publisher-server-side.md)| This integration guide is for publishers that do not use the SDK for JavaScript. |
51
+
|[Google Ad Manager Secure Signals Integration Guide](integration-google-ss.md)| This integration guide covers the additional steps needed for publishers using UID2 with the Google Ad Manager Secure Signals feature (previously known as Encrypted Signals for Publishers, ESP). |
52
52
53
53
### Mobile Integrations
54
54
55
55
The following resources are available for publishers integrating with Android or iOS devices.
|Android/iOS (Overview) |[Mobile Integration Overview for Android and iOS](integration-mobile-overview.md)| An overview of options for mobile app publishers who want to integrate with UID2 using the SDK for Android or the SDK for iOS. |
60
-
|Android/iOS, Client-Side Integration |[Client-Side Integration Guide for Mobile](integration-mobile-client-side.md)| An integration guide for mobile app publishers who want to integrate with UID2 with changes only within the mobile app (no server-side changes). |
61
-
|Android/iOS, Client-Server Integration |[Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server.md)| An integration guide for mobile app publishers who want to integrate with UID2 by doing the following:<ol><li>Generating UID2 tokens server-side via either a Public or Private Operator.</li><li>Passing the resulting <Linkhref="../ref-info/glossary-uid#gl-identity">identities</Link> to a mobile app for passing into the bidstream.</li></ol> |
57
+
| Integration Guide| Content Description |
58
+
| :--- | :--- |
59
+
|[Mobile Integration Overview for Android and iOS](integration-mobile-overview.md)| An overview of options for mobile app publishers who want to integrate with UID2 using the SDK for Android or the SDK for iOS. |
60
+
|[Client-Side Integration Guide for Mobile](integration-mobile-client-side.md)| An integration guide for mobile app publishers who want to integrate with UID2 with changes only within the mobile app (no server-side changes). |
61
+
|[Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server.md)| An integration guide for mobile app publishers who want to integrate with UID2 by doing the following:<ol><li>Generating UID2 tokens server-side via either a Public or Private Operator.</li><li>Passing the resulting <Linkhref="../ref-info/glossary-uid#gl-identity">identities</Link> to a mobile app for passing into the bidstream.</li></ol> |
62
62
63
63
### CTV Integrations
64
64
@@ -72,20 +72,20 @@ The following resources are available for publisher integrations supporting CTV.
72
72
73
73
The following resources are available for publishers integrating with Prebid.
|[UID2 Integration Overview for Prebid](integration-prebid.md)| An overview of options for publishers who want to integrate with UID2 and generate UID2 tokens to be passed by Prebid.js or Prebid Mobile SDK in the RTB bidstream.|
78
-
|[UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md)| An integration guide for publishers who want to integrate with UID2 and want Prebid.js to manage token generation and automatic token refresh as well as passing the tokens into the RTB bidstream. This guide is for publishers who want to request UID2 tokens client-side, which is the easiest implementation approach. |
79
-
|[UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md)| An integration guide for publishers who want to integrate with UID2 and generate identity tokens to be passed by Prebid.js in the RTB bidstream. This guide is for publishers who are using a private operator or who want to generate tokens server-side. |
80
-
|[UID2 Mobile Integration for Prebid.js](integration-prebid-mobile-summary.md)| A summary of information resources for UID2 integration with Prebid.js on mobile devices.|
75
+
| Integration Guide | Content Description |
76
+
|:---|:---|
77
+
|[UID2 Integration Overview for Prebid](integration-prebid.md)| An overview of options for publishers who want to integrate with UID2 and generate UID2 tokens to be passed by Prebid.js or Prebid Mobile SDK in the RTB bidstream. |
78
+
|[UID2 Client-Side Integration Guide for Prebid.js](integration-prebid-client-side.md)| An integration guide for publishers who want to integrate with UID2 and want Prebid.js to manage token generation and automatic token refresh as well as passing the tokens into the RTB bidstream. This guide is for publishers who want to request UID2 tokens client-side, which is the easiest implementation approach. |
79
+
|[UID2 Client-Server Integration Guide for Prebid.js](integration-prebid-client-server.md)| An integration guide for publishers who want to integrate with UID2 and generate identity tokens to be passed by Prebid.js in the RTB bidstream. This guide is for publishers who are using a private operator or who want to generate tokens server-side. |
80
+
|[UID2 Mobile Integration for Prebid.js](integration-prebid-mobile-summary.md)| A summary of information resources for UID2 integration with Prebid.js on mobile devices. |
81
81
82
82
### Google Ad Manager Integrations
83
83
84
84
The following resources are available for publishers integrating with Google Ad Manager.
85
85
86
86
| Integration Guide | Content Description |
87
87
| :--- | :--- |
88
-
|[Publisher - Google Ad Manager Secure Signals](integration-google-ss.md)| This integration guide covers the additional steps needed for publishers using UID2 with the Google Ad Manager Secure Signals feature (previously known as Encrypted Signals for Publishers, ESP). |
88
+
|[Google Ad Manager Secure Signals Integration Guide](integration-google-ss.md)| This integration guide covers the additional steps needed for publishers using UID2 with the Google Ad Manager Secure Signals feature (previously known as Encrypted Signals for Publishers, ESP). |
89
89
|[UID2 GMA Plugin for Android Integration Guide](mobile-plugin-gma-android.md)| The UID2 Google Mobile Ads (GMA) Plugin for Android enables publishers that use the [Google GMA SDK](https://developers.google.com/ad-manager/mobile-ads-sdk) to send <Linkhref="../ref-info/glossary-uid#gl-uid2-token">UID2 tokens</Link> as [secure signals](https://support.google.com/admob/answer/11556288) in ad requests from Android apps. |
90
90
|[UID2 GMA Plugin for iOS Integration Guide](mobile-plugin-gma-ios.md)| The UID2 Google Mobile Ads (GMA) Plugin for iOS enables publishers that use the [Google GMA SDK](https://developers.google.com/ad-manager/mobile-ads-sdk) to send <Linkhref="../ref-info/glossary-uid#gl-uid2-token">UID2 tokens</Link> as [secure signals](https://support.google.com/admob/answer/11556288) in ad requests from iOS apps. |
91
91
|[UID2 IMA Plugin for Android Integration Guide](mobile-plugin-ima-android.md)| The UID2 Interactive Media Ads (IMA) Plugin for Android enables publishers that use the [Google IMA SDK for Android](https://developers.google.com/interactive-media-ads/docs/sdks/android/client-side) to send <Linkhref="../ref-info/glossary-uid#gl-uid2-token">UID2 tokens</Link> as [secure signals](https://support.google.com/admob/answer/11556288) in ad requests from Android apps. |
<dd>SHA-256 is the secure hashing algorithm that UID2 uses.</dd>
414
-
<dd>SHA-256 is part of the SHA-2 family of algorithms developed by the National Institute of Standards and Technology (NIST) and the National Security Agency (NSA) to succeed SHA-1. Each algorithm is named according to the number of bits in the output, so SHA-256 has 256 bits.</dd>
414
+
<dd>SHA-256 (sometimes called SHA256) is part of the SHA-2 family of algorithms developed by the National Institute of Standards and Technology (NIST) and the National Security Agency (NSA) to succeed SHA-1. Each algorithm is named according to the number of bits in the output, so SHA-256 has 256 bits.</dd>
415
415
<dd>For details, see <ahref="https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf">https://nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf</a> (specification).</dd>
416
416
417
417
<dt><MdxJumpAnchorid="gl-sharing"><ahref="#gl-sharing">Sharing (in UID2)</a></MdxJumpAnchor></dt>
0 commit comments