Publishers can share secure signals on requests through Authorized Buyers, Open Bidding, SDK Bidding and with curation partners they choose. These signals can be created through a signal collection script or adapter provided by a bidder or secure signal provider whom the publisher chooses.
The publisher is ultimately responsible for what information is contained in their chosen signals. The signals must be obfuscated before being sent to Google.
On this page:
- Allow secure signal sharing
- Select allowed secure signals
- Select recipients to share secure signals
- Report on secure signals
Examples
Obfuscated data:
- Encrypting, hashing, or otherwise transforming data to a non-human readable format.
- Any information that doesn’t include a self-describing component and is not recognizable as PII or structured data.
Non obfuscated data:
- PII in the clear. Examples: phone number, email address.
- Structured data that makes otherwise "non-plain text" information understandable. Examples: .json, .xml files that provide an explanation of the data they contain.
Tip: To view and edit Secure signal sharing, turn on the "View bidders" and "Edit bidders" permissions. By default, these permissions include the following user roles:
- View: admin, executive, trafficker, salesperson, and sales manager.
- Edit: admin, trafficker, salesperson, and sales manager.
Allow secure signal sharing
Complete the following steps to allow 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. To disable secure signal sharing, click the toggle off
.
- (Optional) Share contact information: You can select a contact to receive notices from Google about the Ads Data Processing Terms and EU General Data Protection Regulation. Note that contact information is shared with Google and not directly with bidders. Under "Share contact information (optional)":
- Select the type of contact: Primary contact, EU representative, or Data Protection Officer.
- Provide the following contact information:
- Enter the contact’s name.
- Enter the contact’s email address.
- (Optional) Enter the contact’s phone number and address.
- Click Save.
Select allowed secure signals
Complete the following steps to select the secure signals to share with bidders and curation partners:
- Sign in to Google Ad Manager.
- Click Inventory, then Secure signals. A table shows the secure signals you can share.
Note: Secure Signals automatically collect any signals you configure in Prebid UserID. You can disable Prebid UserID by deselecting the checkbox "Use your Prebid configuration to automatically configure your secure signals settings."
You can still make changes to the collection method of any signal. Your selection takes precedence over collection from Prebid UserID, which is used as a fallback method in case your selected method fails to generate a signal.
- Choose a default global sensitive traffic control. Selecting a global control applies by default for any secure signal where the publisher has not chosen an override. Options include Disabled, Non-personalized ads, and Non-personalized and limited ads.
- To share a secure signal, under "Enable app integration" or "Enable web integration," turn on the toggle
- For web integration deployment, choose from Publisher deploy, Google deploy, or Prebid UserID module. Learn more about web integration deployment types.
- Choose to share secure signals on your non-personalized and limited ads inventory. Options include Default, Disabled, Non-personalized ads, and Non-personalized and limited ads.
- Click Save.
Notes:
- If you're using a Content Security Policy (CSP), ensure the signals you select are allowed by the publisher. Google will load the vendor's script from a URL provided by the provider. If the script requires any further integration for its correct operation, it is the publisher's responsibility. You should contact the vendor for additional information.
- If you select the "Publisher deploy" option, you must deploy the signal collection script on your own. You should also contact the signal provider(s) directly to understand additional requirements or if issues arise.
- When "Google deploy" or "Publisher deploy" is enabled for a given signal but fails, Prebid UserID module is used as a fallback when applicable.
| Web signal deploy option | Google actions | Publisher actions |
|---|---|---|
| Publisher deploy | None |
Publisher is fully responsible:
|
| Google deploy |
Google will load the script from a location shared by the provider. (Web only) Google does not:
|
The publisher is responsible for any additional integrations required for the script’s operation. Tip: Using this option only deploys the signal to your page from a location provided by the signal collector.
If the signal collection script requires information or integration, work with your signal provider. |
| Prebid UserID module (Beta) |
Google passes output of a Prebid UserID module(s) per configuration in the Ad Manager UI. (Web only) |
Automatically pass Prebid UserID modules you're using (that are available in Ad Manager) through Secure Signals. To use auto-configuration:
|
Select partners to share secure signals
You can share secure signals with all bidders or specific recipients.
Share secure signals with all bidders
To allow secure signals to be shared with all bidders:
- Sign in to Google Ad Manager.
- 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. The bidders must choose whether they want to receive a signal (from any publisher) when it's available.
Share secure signals with specific bidders
To allow or not allow secure signals to be shared with the bidders in an override group:
- Sign in to Google Ad Manager.
- Click Delivery, then Demand channel settings.
- Click Override groups, and then select an existing override group or create a new override group.
- In the override group settings, click Secure signal sharing, and then:
- To allow secure signal sharing for the group, turn the toggle on
- To not allow secure signal sharing for the group, turn the toggle off
The setting applies to all bidders in the selected override group.
- To allow secure signal sharing for the group, turn the toggle on
- Click Save.
Share secure signals with curation partners
- Sign in to Google Ad Manager.
- Click Inventory, and then Curation settings.
- Under "Curation partner," review the list of partners.
- For each curation partner, control the signal sharing settings:
- Share secure signals: This data helps partners match data segments. To enable secure signal sharing with the curation partner, turn the switch on
Tip: Before you can share secure signals with curation partners, you must first allow secure signal sharing for your network and then select secure signals to collect. - Click Save.
Report on secure signals
Use the following dimensions to report on secure signals.
- Secure signal presence: Reports the presence of the secure signals in the ad request.
- Secure signal delivery: Reports if secure signals were sent to the bidder who won the impression.
- Secure signal name (presented): Reports the names of the secure signals sent in the ad request.
- Secure signal name (delivered): Reports the names of the secure signals that were sent to the bidder who won the impression.
Learn more about dimensions in Ad Manager.
