Google Secure Signals enables publishers to deploy the ID5 ID and make it available as a secure signal on RTB requests through Authorized Buyers, Open Bidding and SDK bidding. Signals will only be generated and shared at the Publishers explicit instruction and only with the bidders the publisher has permitted to receive the signals. Publishers benefit by bringing their identity strategy to their Google tech stack with a lightweight integration, resulting in more addressable inventory and improved monetization.
-
For publishers to integrate with ID5 through Google Secure Signals, a Partner Number will be needed from ID5 Partner Number. This can be requested by signing up with ID5 on our website).
-
Once you have the Partner Number, you should add the following code to the <head> part of your website:
<script>
window.ID5EspConfig = {
partnerId: 123 // 123 should be modified with your own partnerId
};
</script>
- After updating your website, to turn on Secure Signal sharing, Sign in to Google Ad Manager.
- Click Admin, then Global settings, and then Ad exchange account settings.
- In the "Secure signal sharing" section, click the toggle on to allow secure signal sharing and click Save.
- Click Inventory, then Secure Signals, this will show you a list of secure signals you can share.
- Toggle ID5 on
- For web integrations, there are a few integration options:
- a) Deploy the signal collection script for an existing Prebid UserID module. Under "Signal collection deployment", select Prebid UserID module. This will enable Google to collect the ID5 ID from your current Prebid UserID deployment of the ID5 ID. If you haven’t done so already, to receive the most valuable ID5 IDs, ensure you are passing ID5 additional signals such as hashed email.
- b) Google can deploy the signal collection script for you by selecting Google deploy under “Signal collection deployment”.Note, this integration does not support the provision of additional signals like hashed emails to ID5 and therefore may reduce ID precision.
- c) Under "Signal collection deployment", select the "Publisher deploy" option, deploy the ID5 JS API. The benefit of this option is that you can provide ID5 additional signals such as hashed email resulting in more valuable ID5 IDs.
- Under "Signal collection deployment", select Share to share secure signals on non-personalized (NPA) ad requests.
- To share secure signals with bidders, click Delivery, then Demand channel settings.
- Under the "Default settings" tab, click Secure signal sharing.
- Turn on the toggle for the desired demand channels. Bidders can now receive the secure signals you share with them.
Bidders must choose whether they want to receive a signal (from any publisher) when it's available. We recommend reaching out to your main bidders and letting them know to pick up the encrypted ID5 ID.
You can read more about Google’s Secure Signals here.