Merge pull request #714 from IABTechLab/gwh-APIDOCS-2598-prebid-ss-mi…

…nor-mod

GAM SS doc, add step to update Prebid config

docs/guides/google-ss-integration.md

@@ -31,14 +31,35 @@ With this framework, the following steps occur:
 
 For your Google Ad Manager account to be eligible to receive encrypted UID2 tokens, you must make sure that encrypted signals are properly shared with third-party bidders on your Google Ad Manager account.
 
-For details, see [Share encrypted signals with bidders](https://support.google.com/admanager/answer/10488752) (Google reference documentation) and then follow the steps in [Use a third-party signal provider](https://developers.google.com/interactive-media-ads/docs/sdks/html5/client-side/securesignals) to switch on UID2 as your signal provider.
+For details, see [Share encrypted signals with bidders](https://support.google.com/admanager/answer/10488752) in the Google documentation, and then follow the steps in [Use a third-party signal provider](https://developers.google.com/interactive-media-ads/docs/sdks/html5/client-side/securesignals) to switch on UID2 as your signal provider.
 
 :::important
-When you're following the steps, in [Select allowed secure signals](https://support.google.com/admanager/answer/10488752#select-signals), under **Web Signal Deploy Option**, choose **Google Deploy**.
-If you choose the **Prebid User ID Module**, your UID2s will not be correctly processed unless you also choose the **Use your Prebid configuration to automatically configure your Secure signals settings** field.
-Before saving your configuration, double-check that you've selected the correct option.
+When you're following the steps, in [Select allowed secure signals](https://support.google.com/admanager/answer/10488752#select-signals), under **Web Signal Deploy Option**, choose **Google Deploy**. If you're using Prebid.js, see [Optional: Enable Secure Signals in Prebid.js](#optional-enable-secure-signals-in-prebidjs).
 :::
 
+### Optional: Enable Secure Signals in Prebid.js
+
+If you want to use Secure Signals with Prebid.js, you must complete both these additional steps so that your UID2s are correctly processed:
+
+1. In Google Ad Manager, when you're making sure that encrypted signals are properly shared with third-party bidders: Choose the **Prebid User ID Module**, and then also choose **Use your Prebid configuration to automatically configure your Secure signals settings**. Before saving your configuration, double-check that you've selected the correct option.
+
+1. In your Prebid.js setup: update the `encryptedSignalSources` section in your Prebid configuration, as shown in the following code:
+
+   ```
+   "encryptedSignalSources": {
+     "sources":[
+       {
+         "source":[
+           "uidapi.com"
+         ],
+         "encrypt":false
+       }
+     ]
+   }
+   ```
+
+   For details, see [ESP Configurations](https://docs.prebid.org/dev-docs/modules/userId.html#esp-configurations) in the Prebid documentation.
+
 ## Publisher Integration
 
 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.

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

@@ -365,3 +365,10 @@ pbjs.setConfig({
   } 
 }); 
 ```
+
+## Optional: Prebid.js Integration with Google Secure Signals
+
+if you're using Prebid.js, and you're planning to pass UID2 tokens to Google using Google Secure Signals, there are a couple of additional configuration steps:
+
+- In your Google Ad Manager account, make sure that encrypted signals are properly shared with third-party bidders: see [Allow Secure Signals Sharing](google-ss-integration.md#allow-secure-signals-sharing).
+- Update your Prebid.js configuration: see [Optional: Enable Secure Signals in Prebid.js](google-ss-integration.md#optional-enable-secure-signals-in-prebidjs).

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

@@ -187,3 +187,10 @@ pbjs.setConfig({
   } 
 }); 
 ```
+
+## Optional: Prebid.js Integration with Google Secure Signals
+
+if you're using Prebid.js, and you're planning to pass UID2 tokens to Google using Google Secure Signals, there are a couple of additional configuration steps:
+
+- In your Google Ad Manager account, make sure that encrypted signals are properly shared with third-party bidders: see [Allow Secure Signals Sharing](google-ss-integration.md#allow-secure-signals-sharing).
+- Update your Prebid.js configuration: see [Optional: Enable Secure Signals in Prebid.js](google-ss-integration.md#optional-enable-secure-signals-in-prebidjs).