Processor features

Share secure signals with bidders (Beta)

For publishers

Publishers can share secure signals on RTB requests through Authorized Buyers, Open Bidding, and SDK Bidding with the third-party bidders 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.

Secure signals will only be shared at the publisher’s explicit instruction and only with bidders the publisher has allowed to receive the signals. At no point will information contained in the signals be visible or readable by Google or its platforms.

Obfuscated data examples:

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

PII in the clear. Examples: phone number, email address.
Structured data that makes otherwise “non-plain text” information understandable. Examples: .json, .xml files that provides an explanation of the data it contains.

Secure signals are subject to the Google Ad Manager Partner Guidelines. When you turn on secure signals, you acknowledge that you've reviewed and accepted the Ads Data Processing Terms.

In this article:

To view and edit Secure signal sharing, turn on View and Edit bidder 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 .
Click Save.

Share contact information (Optional)

You can select a contact to receive notices from Google about the Ads Data Processing Terms and EU General Data Protection Regulation.

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.

Contact information is shared with Google and not directly with bidders.

Select allowed secure signals

Complete the following steps to select the secure signals to share with bidders:

Sign in to Google Ad Manager.
Click Inventory, then Secure signals. A table shows the secure signals you can share.
To share a secure signal, under "Enable app integration" or "Enable web integration," turn on the toggle .
For web integrations only, Google can deploy the signal collection script for you.
Select Google deploy under "Signal collection deployment".

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.
Alternatively, deploy the signal collection script for an existing Prebid UserID module ^(Beta) .
Under "Signal collection deployment", select Prebid UserID module ^(Beta) .
Under "Secure signals settings," select Share to share secure signals on non-personalized (NPA) ad requests.
Click Save.

If you're using a Content Security Policy (CSP), ensure the signals you select are allowed by the publisher. Google will load the vendor 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.

Web signal deploy option	Google actions	Publisher actions
Publisher deploy	None	Publisher is fully responsible: To load the vendor’s script. For any integrations required for the script’s operation.
Google deploy	Google will load the script from a location shared by the provider. Google does not: Validate the script in any way. Perform any additional integrations.	The publisher is responsible for any additional integrations required for the script’s operation.
Prebid UserID module	Google passes output of a Prebid UserID module(s) per configuration in the Ad Manager UI.	Prebid UserID module integration can be manually controlled by the publisher, or you can choose to automatically pass all Prebid UserID modules through secure signals. To use auto-configuration: Select Inventory, then Secure signals. Select the checkbox "Use your Prebid configuration to automatically configure your Secure signals settings". This overrides any manual configurations set in Ad Manager for the secure signals that are detected in the Prebid UserID module. When this toggle is turned on, you won't be able to use Ad Manager to individually control those secure signals.

Web signal deploy option

Google actions

Publisher actions

Publisher deploy

None

Publisher is fully responsible:

To load the vendor’s script.
For any integrations required for the script’s operation.

Google deploy

Google will load the script from a location shared by the provider.

Google does not:

Validate the script in any way.
Perform any additional integrations.

The publisher is responsible for any additional integrations required for the script’s operation.

Prebid UserID module

Google passes output of a Prebid UserID module(s) per configuration in the Ad Manager UI.

Prebid UserID module integration can be manually controlled by the publisher, or you can choose to automatically pass all Prebid UserID modules through secure signals.

To use auto-configuration:

Select Inventory, then Secure signals.
Select the checkbox "Use your Prebid configuration to automatically configure your Secure signals settings".
This overrides any manual configurations set in Ad Manager for the secure signals that are detected in the Prebid UserID module.

When this toggle is turned on, you won't be able to use Ad Manager to individually control those secure signals.

Select bidders to share secure signals

You can share secure signals with all bidders or specific bidders.

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.
Click Save.

Report on secure signals

Use the following dimensions to report on secure signals.

Secure signal presence ^Beta reports the presence of the secure signals in the ad request.
Secure signal delivery ^Beta reports if secure signals were sent to the bidder who won the impression.
Secure signal name (presented) ^Beta reports the names of the secure signals sent in the ad request.
Secure signal name (delivered) ^Betareports the names of the secure signals that were sent to the bidder who won the impression.

Learn more about report dimensions for secure signals.

Was this helpful?

How can we improve it?