Client-Side UID2 Integration with Prebid.js (with Google Secure Signals)
This example demonstrates how a content publisher can integrate UID2 with both Prebid.js (for header bidding) and Google Secure Signals (for Google Ad Manager), using client-side token generation. Prebid manages the UID2 token, and Google Secure Signals reads from Prebid's storage automatically. For documentation, see UID2 Client-Side Integration Guide for Prebid.js 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.
|
|
|
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.
|
Prebid Integration Status
Prebid.js is configured to handle the entire token lifecycle—generation, storage, and automatic refresh.
|
Prebid Token Storage:
?
Shows the UID2 token stored by Prebid in localStorage under the key '__uid2_advertising_token'. This storage is shared between Prebid and Google Secure Signals.
|
Google Secure Signals Status
Prebid's encryptedSignalSources config enables automatic sharing of encrypted UID2 tokens with Google Ad Manager.
|
Secure Signals Configured?
?
Indicates whether Google Secure Signals integration is properly configured in Prebid. When "yes", encrypted UID2 signals are sent to Google Ad Manager.
|