Skip to content

Commit

Permalink
Merge pull request #701 from IABTechLab/gwh-APIDOCS-2580-secure-signa…
Browse files Browse the repository at this point in the history
…ls-config-update

To SS GAM doc, add note re config option
  • Loading branch information
genwhittTTD authored Sep 9, 2024
2 parents bd4f330 + f57007c commit 2b52138
Showing 1 changed file with 20 additions and 0 deletions.
20 changes: 20 additions & 0 deletions docs/guides/google-ss-integration.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,12 @@ For your Google Ad Manager account to be eligible to receive encrypted UID2 toke

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.

:::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.
:::

## 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.
Expand Down Expand Up @@ -92,3 +98,17 @@ The following sample applications are available to illustrate how to integrate w
- [Code repository](https://github.com/IABTechLab/uid2-web-integrations/tree/main/examples/google-secure-signals-integration/with_sdk_v3)

Each sample application has its own instructions.

## Troubleshooting Tips for UID2 Integration with Google Secure Signals

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

- [I enabled Secure Signals within Google Ad Manager, but UID2s are not being passed through Google](#i-enabled-secure-signals-within-google-ad-manager-but-uid2s-are-not-being-passed-through-google)

#### I enabled Secure Signals within Google Ad Manager, but UID2s are not being passed through Google

In some cases, after choosing Secure Signals within Google Ad Manager, successful UID2s were not being passed through Google because the participant had an incorrect **Web Signal Deployment Method** configuration.

If your UID2s are not being passed through Google, make sure that you chose the correct Web Signal Deployment Method during setup.

For details, see the **Important** note in [Allow Secure Signals Sharing](#allow-secure-signals-sharing).

0 comments on commit 2b52138

Please sign in to comment.