Skip to content

Commit d95d9cb

Browse files
committed
update the placement of Integrating with Single Sign-On section
1 parent e169024 commit d95d9cb

13 files changed

+49
-49
lines changed

docs/guides/integration-ctv-guide.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,10 @@ At a high level, to integrate with UID2, you'll implement these three key steps:
2323

2424
To determine how you'll implement these steps, choose from the [CTV Integration Options](#ctv-integration-options).
2525

26+
## Integrating with Single Sign-On (SSO)
27+
28+
<IntegratingWithSSO />
29+
2630
## CTV Integration Options
2731

2832
You can decide on the integration option that's best for you based on where you want to generate and refresh the UID2 token. There are three options, as follows:
@@ -82,7 +86,3 @@ The following table shows supported operating systems, with links to applicable
8286
| :--- | :--- | :--- |
8387
| [Apple tvOS](https://developer.apple.com/tvos/) | [UID2 Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server.md) | [SDK for iOS Reference Guide](../sdks/sdk-ref-ios.md) |
8488
| [Android TV](https://www.android.com/tv/) | [UID2 Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server.md) | [SDK for Android Reference Guide](../sdks/sdk-ref-android.md) |
85-
86-
## Integrating with Single Sign-On (SSO)
87-
88-
<IntegratingWithSSO />

docs/guides/integration-google-ss.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,10 @@ If you want to use Secure Signals with Prebid.js, you must complete both these a
6161

6262
For details, see [ESP Configurations](https://docs.prebid.org/dev-docs/modules/userId.html#esp-configurations) in the Prebid documentation.
6363

64+
## Integrating with Single Sign-On (SSO)
65+
66+
<IntegratingWithSSO />
67+
6468
## Publisher Integration
6569

6670
When an encrypted signal is cached, the secure signals feature does not execute the handler to generate a new signal. Because of this, it is necessary to clear the cache before and after data capture.
@@ -121,10 +125,6 @@ The following sample implementations are available to illustrate how to integrat
121125

122126
Each sample implementation has its own instructions.
123127

124-
## Integrating with Single Sign-On (SSO)
125-
126-
<IntegratingWithSSO />
127-
128128
## Troubleshooting
129129

130130
Here is some troubleshooting information that might help you in working with Google Secure Signals for your UID2 integration:

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -47,6 +47,10 @@ For integration scenarios for publishers that do not use the SDK for JavaScript,
4747
If you are using Google Ad Manager and want to use the secure signals feature, first follow the steps in this guide and then follow the additional steps in the [Google Ad Manager Secure Signals Integration Guide](integration-google-ss.md).
4848
:::
4949

50+
## Integrating with Single Sign-On (SSO)
51+
52+
<IntegratingWithSSO />
53+
5054
## Integration Steps
5155

5256
The following diagram outlines the steps required for establishing a user's UID2 token with a publisher and how the UID2 token integrates with the RTB bidstream.
@@ -157,10 +161,6 @@ The client lifecycle is complete when the user decides to log out from the publi
157161
</script>
158162
```
159163

160-
## Integrating with Single Sign-On (SSO)
161-
162-
<IntegratingWithSSO />
163-
164164
## FAQs
165165

166166
For a list of frequently asked questions for the publisher audience, see [FAQs for Publishers](../getting-started/gs-faqs.md#faqs-for-publishers).

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -64,6 +64,10 @@ For a sample implementation, see this example:
6464

6565
<!-- (Source code for running site: https://github.com/IABTechLab/uid2-web-integrations) -->
6666

67+
## Integrating with Single Sign-On (SSO)
68+
69+
<IntegratingWithSSO />
70+
6771
## Complete UID2 Account Setup
6872

6973
Complete the UID2 account setup by following the steps described in the [Account Setup](../getting-started/gs-account-setup.md) page. As part of the account setup process, you'll need to provide a list of **domain names** for the sites that you'll be using with this SDK for JavaScript.
@@ -386,7 +390,3 @@ function bytesToBase64(bytes) {
386390
return btoa(binString);
387391
}
388392
```
389-
390-
## Integrating with Single Sign-On (SSO)
391-
392-
<IntegratingWithSSO />

docs/guides/integration-javascript.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,10 @@ UID2 provides an SDK for JavaScript that supports the following:
2626

2727
For additional flexibility, UID2 also provides alternative methods for some of the features and complementary products, such as a Prebid integration.
2828

29+
## Integrating with Single Sign-On (SSO)
30+
31+
<IntegratingWithSSO />
32+
2933
## Client-Side or Client-Server Integration
3034

3135
The options for integrating with UID2 using the SDK for JavaScript are summarized in the following table. Choose the option that's best for you.
@@ -70,7 +74,3 @@ For detailed instructions, refer to one of the following integration guides:
7074

7175
- [Client-Side Integration Guide for JavaScript](integration-javascript-client-side.md)
7276
- [Client-Server Integration Guide for JavaScript](integration-javascript-client-server.md)
73-
74-
## Integrating with Single Sign-On (SSO)
75-
76-
<IntegratingWithSSO />

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -56,6 +56,10 @@ This guide provides instructions for using either of these UID2 mobile SDKs:
5656

5757
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).
5858

59+
## Integrating with Single Sign-On (SSO)
60+
61+
<IntegratingWithSSO />
62+
5963
## Complete the UID2 Account Setup
6064

6165
To set up your account, follow the steps described in [Account Setup](../getting-started/gs-account-setup.md).
@@ -315,10 +319,6 @@ The UID2 integration with Prebid Mobile SDK requires version 1.6.0 of the UID2 S
315319

316320
<PrebidMobileSDK />
317321

318-
## Integrating with Single Sign-On (SSO)
319-
320-
<IntegratingWithSSO />
321-
322322
## Error Response States
323323

324324
<ErrorResponseStates />

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -191,6 +191,10 @@ see UID2SDKDevelopmentApp/UID2SDKDevelopmentApp/Info.plist
191191
192192
If necessary, you can also change the default Subscription ID and public key to values assigned to you, and connect to the UID2 Production environment. For details, see [Optional: Specifying the API Base URL to Reduce Latency](#optional-specifying-the-api-base-url-to-reduce-latency).
193193
194+
## Integrating with Single Sign-On (SSO)
195+
196+
<IntegratingWithSSO />
197+
194198
## Complete the UID2 Account Setup
195199
196200
To set up your account, follow the steps described in [Account Setup](../getting-started/gs-account-setup.md). As part of the account setup process, you'll need to provide a list of <Link href="../ref-info/glossary-uid#gl-app-name">app names</Link> for all the mobile apps that you'll be integrating with the UID2 mobile SDKs, including any of these values that apply:
@@ -725,10 +729,6 @@ The UID2 integration with Prebid Mobile SDK requires version 1.6.0 of the UID2 S
725729
726730
<PrebidMobileSDK />
727731
728-
## Integrating with Single Sign-On (SSO)
729-
730-
<IntegratingWithSSO />
731-
732732
## Error Response States
733733
734734
<ErrorResponseStates />

docs/guides/integration-mobile-overview.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,10 @@ UID2 provides SDKs for Android/iOS that support the following:
2929

3030
For additional flexibility, UID2 also provides alternative methods for some of the features and complementary products, such as UID2 Google GMA/IMA Plugins. Available options are described in the individual guides: see [Integration Overview: High-Level Steps](#integration-overview-high-level-steps).
3131

32+
## Integrating with Single Sign-On (SSO)
33+
34+
<IntegratingWithSSO />
35+
3236
## Integration Overview: High-Level Steps
3337

3438
At a high level, to integrate your mobile app with UID2 using the UID2 mobile SDKs, you'll need to complete the following steps:
@@ -169,7 +173,3 @@ Some error responses indicate a networking problem resulting in your app not be
169173
The SDK tries to refresh the UID2 token in the background. If an error such as an IOException occurs, the SDK retries multiple times. If retry is not successful, this exception is displayed.
170174

171175
Another good troubleshooting step is to enable logging. For details, see [Enable Logging](integration-mobile-client-side.md#enable-logging).
172-
173-
## Integrating with Single Sign-On (SSO)
174-
175-
<IntegratingWithSSO />

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,10 @@ Information about how to integrate Prebid with UID2 is also in the following loc
3939
4040
GWH note 12/14/23: We have client-side and server-side examples for JS SDK but only server-side for Prebid. -->
4141

42+
## Integrating with Single Sign-On (SSO)
43+
44+
<IntegratingWithSSO />
45+
4246
## Integration Overview: High-Level Steps
4347

4448
You'll need to complete the following steps:
@@ -376,7 +380,3 @@ if you're using Prebid.js, and you're planning to pass UID2 tokens to Google usi
376380

377381
- 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).
378382
- Update your Prebid.js configuration: see [Optional: Enable Secure Signals in Prebid.js](integration-google-ss.md#optional-enable-secure-signals-in-prebidjs).
379-
380-
## Integrating with Single Sign-On (SSO)
381-
382-
<IntegratingWithSSO />

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,10 @@ An example of the UID2 Prebid.js client-side integration is available at the fol
3333
- Code: [Example Prebid.js UID2 Integration](https://github.com/IABTechLab/uid2docs/tree/main/static/examples/cstg-prebid-example)
3434
- Running site: [UID2 Prebid.js Client-Side Integration Example](https://unifiedid.com/examples/cstg-prebid-example/)
3535

36+
## Integrating with Single Sign-On (SSO)
37+
38+
<IntegratingWithSSO />
39+
3640
## Integration Overview: High-Level Steps
3741

3842
You'll need to complete the following steps:
@@ -197,7 +201,3 @@ if you're using Prebid.js, and you're planning to pass UID2 tokens to Google usi
197201

198202
- 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).
199203
- Update your Prebid.js configuration: see [Optional: Enable Secure Signals in Prebid.js](integration-google-ss.md#optional-enable-secure-signals-in-prebidjs).
200-
201-
## Integrating with Single Sign-On (SSO)
202-
203-
<IntegratingWithSSO />

0 commit comments

Comments
 (0)