Client-Side ${IDENTITY_NAME} SDK Integration Example with Google Secure Signals
-
- This example demonstrates how a content publisher can follow the
- Client-Side Integration Guide for JavaScript to implement ${IDENTITY_NAME} integration and generate ${IDENTITY_NAME} tokens.
- Secure Signals is updated when the page is reloaded.
- Reload the page in order to update Secure Signals in local storage.
- Note: This is a test-only integration environment—not for production use.
- It does not perform real user authentication or generate production-level tokens.
- Do not use real user data on this page.
-
-
-
-
-
-
-
-
-
-
-
-
Ready for Targeted Advertising:
-
-
-
-
${IDENTITY_NAME} Advertising Token:
-
-
-
-
Is ${IDENTITY_NAME} Login Required?
-
-
-
-
${IDENTITY_NAME} Identity Callback State:
-
-
-
-
Secure Signals Loaded?
-
-
-
-
Secure Signals Value:
-
-
-
-
-
-
The email address you entered has opted out of ${IDENTITY_NAME}.
-
-
-
-
-
-
-
+
+
+
+
Client-Side ${IDENTITY_NAME} Integration with Google Secure Signals
+ Indicates whether a valid ${IDENTITY_NAME} token is present and can be used for personalized ad targeting.
+
+
+
+
+
+
+
+
+
+ Advertising Token:
+
+ ?
+
+ The encrypted ${IDENTITY_NAME} 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 ${IDENTITY_NAME} 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 ${IDENTITY_NAME} identity data including refresh tokens and metadata.
+
+
+
+
+
+
+
+
+
+ Secure Signals Loaded?
+
+ ?
+
+ Indicates whether Google Secure Signals has successfully loaded and stored the ${IDENTITY_NAME} token. Returns "yes" when signals are available in localStorage.
+
+
+
+
+
+
+
+
+
+ Secure Signals Value:
+
+ ?
+
+ The encrypted ${IDENTITY_NAME} signals stored by Google in localStorage under the key '${UID_SECURE_SIGNALS_STORAGE_KEY}'. These signals are shared with Google Ad Manager.
+
Client-Side ${IDENTITY_NAME} Integration Example using JavaScript SDK
-
- This example demonstrates how a content publisher can follow the
- Client-Side Integration Guide for JavaScript
-
- to implement ${IDENTITY_NAME} integration and generate ${IDENTITY_NAME} tokens.
- Note: This is a test-only integration environment—not for production
- use. It does not perform real user authentication or generate production-level tokens. Do not
- use real user data on this page.
-
-
+
+
+
+
Client-Side ${IDENTITY_NAME} Integration Example using JavaScript SDK
+
+ This example demonstrates how a content publisher can integrate ${IDENTITY_NAME} using client-side token generation, where the SDK generates tokens directly in the browser using public credentials. For documentation, see the
+ Client-Side Integration Guide for JavaScript.
+
+
${IDENTITY_NAME} Integration Status
+
-
Ready for Targeted Advertising:
+
+
+ Ready for Targeted Advertising:
+
+ ?
+
+ Indicates whether a valid ${IDENTITY_NAME} token is present and can be used for personalized ad targeting.
+
+
+
+
-
Advertising Token:
+
+
+ Advertising Token:
+
+ ?
+
+ The encrypted ${IDENTITY_NAME} 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?
+
+
+ Is Login Required?
+
+ ?
+
+ Indicates whether a new ${IDENTITY_NAME} token needs to be generated. Returns "yes" when no valid identity exists or the current identity has expired.
+
+
+
+
-
Has opted out?
+
+
+ Has opted out?
+
+ ?
+
+ Shows whether the user has exercised opt-out, in which case no advertising token may be generated or used.
+
+
+
+
-
Identity Updated Counter:
-
-
-
-
Identity Callback State:
+
+
+ Identity Callback State:
+
+ ?
+
+ The complete identity object returned by the SDK. Contains the full ${IDENTITY_NAME} identity data including refresh tokens and metadata.
+
+
+
+
@@ -133,15 +169,68 @@
Client-Side ${IDENTITY_NAME} Integration Example using JavaScript SDK