Client-Server EUID SDK Integration Example with Google Secure Signals
This example demonstrates how a content publisher can use the EUID services and the EUID SDK for JavaScript to implement the client-server EUID integration with Secure Signals. [Source Code]
EUID Integration Status
|
Ready for Targeted Advertising:
?
Indicates whether a valid EUID token is present and can be used for personalized ad targeting.
|
|
|
Advertising Token:
?
The encrypted EUID 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 EUID token needs to be generated. Returns "yes" when no valid identity exists or the current identity has expired.
|
|
|
Identity Callback State:
?
The complete identity object returned by the SDK. Contains the full EUID 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 EUID token. Returns "yes" when signals are available in localStorage.
|
|
|
Secure Signals Value:
?
The encrypted EUID signals stored by Google in localStorage under the key ''. These signals are shared with Google Ad Manager.
|