Troubleshoot secure signals

Find out why secure signals aren't delivering. #securesignals

To ensure secure signals are being included in all eligible RTB ad requests, there are a number of troubleshooting steps possible.

Identify missing secure signal providers on requests

In Ad Manager reporting, use the appropriate "Demand channel" filter (Ad Exchange, Open Bidding, or SDK Bidding) and combine it with the "Secure signal name (presented)" or "Secure signal name (delivered)" dimensions to see which secure signal providers are being sent on ad requests. You can also use the "Date" and "Inventory types (expanded)" dimensions to help limit the focus of your report to a specific time period or environment.

Ensure secure signal delivery

Review your secure signals controls in Demand channel settings and ensure that any default settings or override groups align with your preferences. If default settings are toggled on for some or all demand channels, ensure there isn't a conflicting setting in an override group that may prevent some or all bidders from receiving the signal. 

In demand channel settings, you can also control whether Authorized Buyers can use bid request data to build user profiles for uses such as interest-based ads and remarketing.

For SDK Bidding specifically, learn how to ensure bidders can send their own signals by verifying your SDK Bidding setup.

Use Delivery tools or Ad inspector

In mobile app environments, you can verify signals are being passed using either Delivery tools or Ad inspector. If secure signals are missing, make sure that the ad units coded into the map exactly match the ad units in Google Ad Manager, because they are case sensitive. You can learn more about troubleshooting secure signals delivery in mobile app environments by reviewing the Verify your SDK Bidding setup and Inspect mobile app ad delivery articles.

Use Developer tools

In web environments, you can inspect a browser’s local storage to find if signals are present.

1. In Chrome, click , then More tools, and then < > Developer tools.
2. Click the "Application" tab.
3. Under the "Storage' pane and "Local storage," click the URL (such as https://example.com). The site's local storage data displays.
4. Identify the "Key" corresponding to the signal provider.
   It may be in the form of _GESPSK-<signal-provider.com>.
5. If you see the desired signal(s) in the corresponding entry, the signal has been cached in the browser’s local storage and is being sent.

Consult with your secure signal provider

We recommend that publishers work with their secure signal provider(s) to ensure their implementation is healthy. Additionally, go through previous steps to manage errors and misconfigurations. Working with your secure signal provider directly ensures the script is loading and operating as expected.