Client-Side UID2 Integration with Google Secure Signals

This example demonstrates how a content publisher can integrate UID2 with Google Secure Signals for Google Ad Manager, using client-side token generation. For documentation, see the Client-Side Integration Guide for JavaScript and Google Ad Manager Secure Signals Integration Guide. [Source Code]

UID2 Integration Status

Ready for Targeted Advertising:
?
Indicates whether a valid UID2 token is present and can be used for personalized ad targeting.
Advertising Token:
?
The encrypted UID2 token that is passed to ad systems without exposing raw user identity. It is automatically refreshed by the SDK in the background when expired.
Is Login Required?
?
Indicates whether a new UID2 token needs to be generated. Returns "yes" when no valid identity exists or the current identity has expired.
Has Opted Out?
?
Shows whether the user has exercised opt-out, in which case no advertising token may be generated or used.
Identity Callback State:
?
The complete identity object returned by the SDK. Contains the full UID2 identity data including refresh tokens and metadata.

Google Secure Signals Status

Secure Signals automatically reads the token from storage and shares it with Google Ad Manager.

Secure Signals Loaded?
?
Indicates whether Google Secure Signals has successfully loaded and stored the UID2 token. Returns "yes" when signals are available in localStorage.
Secure Signals Value:
?
The encrypted UID2 signals stored by Google in localStorage under the key '_GESPSK-uidapi.com'. These signals are shared with Google Ad Manager.