Server-Side EUID Integration Example with Google Secure Signals
This example demonstrates how a content publisher can use the EUID services with Secure Signals to implement Server-Side Integration. [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.
|
no |
|
Advertising Token:
?
The encrypted EUID token that is passed to ad systems without exposing raw user identity. It is automatically refreshed by the server when expired.
|
undefined |
|
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.
|
yes |
|
Has Opted Out?
?
Shows whether the user has exercised opt-out, in which case no advertising token may be generated or used.
|
no |
|
Identity State:
?
The complete identity object from the server. Contains the full EUID identity data including refresh tokens and metadata.
|
null |
Google Secure Signals Status
Secure Signals automatically reads the server-generated token 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.
|
no |
|
Secure Signals Value:
?
The encrypted EUID signals stored by Google in localStorage under the key '_GESPSK-uidapi.com'. These signals are shared with Google Ad Manager.
|
undefined |