Skip to content

Commit 203cad7

Browse files
committed
add a couple of in-links to new page
1 parent 1992a36 commit 203cad7

File tree

3 files changed

+13
-1
lines changed

3 files changed

+13
-1
lines changed

docs/guides/integration-prebid-client-server.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -375,3 +375,7 @@ if you're using Prebid.js, and you're planning to pass UID2 tokens to Google usi
375375

376376
- In your Google Ad Manager account, make sure that encrypted signals are properly shared with third-party bidders: see [Allow Secure Signals Sharing](integration-google-ss.md#allow-secure-signals-sharing).
377377
- Update your Prebid.js configuration: see [Optional: Enable Secure Signals in Prebid.js](integration-google-ss.md#optional-enable-secure-signals-in-prebidjs).
378+
379+
## Implementing SSO Login
380+
381+
For information about implementing one or more Single Sign-On (SSO) options in the context of UID2 for users visiting your webpages, see [Publisher Integration with SSO Providers](../ref-info/ref-integration-sso-providers.md).

docs/guides/integration-prebid-client-side.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -196,3 +196,7 @@ if you're using Prebid.js, and you're planning to pass UID2 tokens to Google usi
196196

197197
- In your Google Ad Manager account, make sure that encrypted signals are properly shared with third-party bidders: see [Allow Secure Signals Sharing](integration-google-ss.md#allow-secure-signals-sharing).
198198
- Update your Prebid.js configuration: see [Optional: Enable Secure Signals in Prebid.js](integration-google-ss.md#optional-enable-secure-signals-in-prebidjs).
199+
200+
## Implementing SSO Login
201+
202+
For information about implementing one or more Single Sign-On (SSO) options in the context of UID2 for users visiting your webpages, see [Publisher Integration with SSO Providers](../ref-info/ref-integration-sso-providers.md).

docs/overviews/overview-publishers.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ The following steps provide a high-level outline of the workflow intended for or
3434

3535
1. A user visits a publisher website, mobile app, or CTV app.
3636

37-
1. The publisher provides transparency around its data practices and asks the user to provide an email address or phone number.
37+
1. The publisher provides transparency around its data practices and asks the user to provide an email address or phone number, by [SSO login](#implementing-sso-on-publisher-pages) or other means.
3838

3939
1. Once the user has provided an email address or phone number, the publisher sends it to the UID2 Operator via an SDK or direct API integration.
4040
:::tip
@@ -156,6 +156,10 @@ The following resources are available for publishers integrating with Google Ad
156156
| IMA for Android | [UID2 IMA Plugin for Android Integration Guide](../guides/mobile-plugin-ima-android.md) | A guide that enables publishers using the Google Interactive Media Ads (IMA) SDK to include UID2 tokens in ad requests from their Android apps. |
157157
| IMA for iOS | [UID2 IMA Plugin for iOS Integration Guide](../guides/mobile-plugin-ima-ios.md) | A guide that enables publishers using the Google Interactive Media Ads (IMA) SDK to include UID2 tokens in ad requests from their iOS apps. |
158158

159+
## Implementing SSO Login
160+
161+
For information about implementing one or more Single Sign-On (SSO) options in the context of UID2 for users visiting your webpages, see [Publisher Integration with SSO Providers](../ref-info/ref-integration-sso-providers.md).
162+
159163
## FAQs for Publishers
160164

161165
For a list of frequently asked questions for publishers using the UID2 framework, see [FAQs for Publishers](/docs/getting-started/gs-faqs.md#faqs-for-publishers).

0 commit comments

Comments
 (0)