From 1dbb8f5a47258503f5b692f749db75df929f7e83 Mon Sep 17 00:00:00 2001 From: eiman eltigani Date: Tue, 24 Mar 2026 16:33:26 +0100 Subject: [PATCH 01/25] add uid verify to integration samples and tools page --- docs/ref-info/integration-sample-sites.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/ref-info/integration-sample-sites.md b/docs/ref-info/integration-sample-sites.md index 4a670913c..41bcc4428 100644 --- a/docs/ref-info/integration-sample-sites.md +++ b/docs/ref-info/integration-sample-sites.md @@ -134,6 +134,13 @@ This tool is for developers or clients validating data preparation, such as hash - Code: [uid2-examples/tools/hashing-tool](https://github.com/IABTechLab/uid2-examples/tree/main/tools/hashing-tool) - Doc: [Normalization and Encoding](https://unifiedid.com/docs/getting-started/gs-normalization-encoding) +### UID Verify Chrome Extension + +UID Verify is a Chrome browser extension for debugging UID2 and EUID integrations. It inspects SDK information on websites, tracks events and event history, and monitors storage (cookies and local storage). The extension supports integrations using Prebid.js and Google Secure Signals. + +- Site: [UID Verify on Chrome Web Store](https://chromewebstore.google.com/detail/uid-detective/cfpjjmdagnkmmolcddnoagffeoekkmle) +- Code: [uid2-detective](https://github.com/IABTechLab/uid2-detective) + :::note The sample sites on this page highlight some common integrations, but do not represent all available UID2 integration options. For a summary of all the integration options available, see [UID2 Integration Guides: Summary](https://unifiedid.com/docs/guides/summary-guides). ::: From e88945c76e7acb4d99dee8eb8f500dc0cebf42a5 Mon Sep 17 00:00:00 2001 From: eiman eltigani Date: Tue, 31 Mar 2026 12:24:10 -0600 Subject: [PATCH 02/25] add seperate page for uid verify and include in sidebar --- docs/ref-info/ref-uid-verify.md | 122 ++++++++++++++++++++++++++++++++ sidebars.js | 1 + 2 files changed, 123 insertions(+) create mode 100644 docs/ref-info/ref-uid-verify.md diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md new file mode 100644 index 000000000..8ddba1907 --- /dev/null +++ b/docs/ref-info/ref-uid-verify.md @@ -0,0 +1,122 @@ +--- +title: UID Verify Chrome Extension +description: How to use the UID Verify Chrome extension to debug and inspect UID2 or EUID integrations on any web page. +hide_table_of_contents: false +sidebar_position: 03 +displayed_sidebar: docs +--- + +import Link from '@docusaurus/Link'; + +# UID Verify Chrome Extension + +UID Verify is a browser extension for debugging UID2 and EUID integrations. It inspects the UID2 or EUID implementation on the current page in real time, surfacing SDK configuration, identity storage, event history, and errors — without requiring any code changes to the page. + +The extension supports integrations using the UID2 JavaScript SDK, Prebid.js, and Google Secure Signals. + +## Overview + +When integrating UID2 or EUID, it can be difficult to tell whether the SDK is initializing correctly, whether tokens are valid, or where in the lifecycle an error is occurring. UID Verify solves this by reading the SDK state, storage, and event stream directly from the page and presenting it in a structured, searchable interface. + +The extension detects whether a page uses the UID2 SDK directly, Prebid.js, or Google Secure Signals (or a combination), and adjusts the displayed information accordingly. It supports both UID2 and EUID deployments. + +## Prerequisites + +UID Verify requires: + +- **Google Chrome** or **Microsoft Edge** browser +- A web page that has a UID2 or EUID integration — one of the following must be present on the page: + - The UID2 JavaScript SDK (`window.__uid2`) or EUID JavaScript SDK (`window.__euid`) + - Prebid.js with a UID2 or EUID user ID module configured + - Google Publisher Tags (GPT) with a UID2 or EUID Secure Signals provider registered + +If more than one integration type is detected, you can switch between them using the integration type tabs at the top of the popup. If neither a UID2/EUID SDK, Prebid.js, nor Google Secure Signals integration is detected, the popup displays a message indicating that no supported integration was found. + +## Installing the Extension + +Install UID Verify from the Chrome Web Store: + +1. Go to the [UID Verify listing](https://chromewebstore.google.com/detail/uid-detective/cfpjjmdagnkmmolcddnoagffeoekkmle) in the Chrome Web Store. +2. Click **Add to Chrome**. +3. When prompted, click **Add extension**. +4. Pin the extension to your toolbar for easy access: click the Extensions icon in your browser, then click the pin icon next to UID Verify. + +## Using UID Verify + +1. Navigate to a web page that has a UID2 or EUID integration. +2. Click the **UID Verify** icon in your browser toolbar to open the extension popup. +3. The extension detects the integration type on the page and displays the appropriate tabs. + +:::note +If both a UID2 and an EUID integration are detected on the same page, the extension displays an error. A page should use either UID2 (for North America and parts of Asia) or EUID (for Europe and other GDPR-applicable regions), not both. +::: + +## Interpreting Results + +### Config Tab + +The **Config** tab provides a snapshot of the integration's current state. + +**For SDK integrations, this includes:** + +- SDK version +- SDK initialization options +- The current identity object, including: + - Advertising token + - Refresh token + - Token and refresh expiration timestamps +- The result of `getAdvertisingToken()` +- The result of `isLoginRequired()` +- Status banners highlighting any issues (for example, outdated SDK version, opted-out identity, or missing configuration) + +**For Prebid.js integrations, this includes:** + +- Whether Prebid.js is detected and the UID2/EUID module is active +- The user ID configuration from `pbjs.getUserIds()` +- Token validity status + +**For Google Secure Signals integrations, this includes:** + +- Whether Google Publisher Tags is detected +- Whether the UID2 or EUID provider ID is registered +- Whether `getAdvertisingTokenAsync` is available +- The registered collector function code +- A status banner indicating whether the Secure Signals configuration is complete + +### Storage Tab + +The **Storage** tab shows the raw identity data stored in the browser for the current integration. + +**For SDK integrations:** + +| Field | Description | +|---|---| +| Storage Type | Whether the identity is stored in a cookie or `localStorage`. | +| Storage Key | The name of the cookie or `localStorage` key (`__uid_2`, `__euid`, `UID2-sdk-identity`, or `EUID-sdk-identity`). | +| Stored Value | The raw identity JSON with syntax highlighting. | +| Validity | Whether the stored identity is currently valid or opted out. | + +**For Prebid.js integrations**, the tab shows the Prebid token storage location and current value. + +**For Google Secure Signals integrations**, the tab shows the cached Secure Signals value (stored under `_GESPSK-uidapi.com` for UID2 or `_GESPSK-euid.eu` for EUID) and whether the signal was sent via the SDK or Prebid. + +### Callbacks Tab + +The **Callbacks** tab is available for SDK integrations only. It displays the source code of all callback functions registered with the SDK, with syntax highlighting. This is useful for confirming that the correct callbacks are wired up and identifying where events are being handled in the page code. + +### Event History Tab + +The **Event History** tab shows a searchable, real-time log of SDK events as they occur on the page. Each row in the table includes: + +| Column | Description | +|---|---| +| Date | The date the event was recorded. | +| Time | The time the event was recorded. | +| Event | The event type (for example, `SdkLoaded`, `InitCompleted`, `TokenUpdated`). | +| Advertising Token | The advertising token associated with the event, if present. | + +Use the search bar to filter by event type or token value. + +This tab also includes an **Error Log** when errors are detected. The extension captures several categories of errors: failed network requests to the UID2 operator, failed resource loads (such as the SDK script), `console.error` calls from SDK code, and errors thrown by SDK methods. + +For known error patterns, the extension displays contextual troubleshooting guidance alongside the error. diff --git a/sidebars.js b/sidebars.js index 1c901d6b5..fe94f0457 100644 --- a/sidebars.js +++ b/sidebars.js @@ -369,6 +369,7 @@ const fullSidebar = [ 'getting-started/gs-normalization-encoding', 'ref-info/ref-preparing-emails-and-phone-numbers-for-processing', 'ref-info/ref-token-validator', + 'ref-info/ref-uid-verify', 'getting-started/gs-opt-out', 'ref-info/ref-operators-public-private', 'ref-info/ref-integration-approaches', From 129cb9a152a795aef27cfd28f5743018efd32bc5 Mon Sep 17 00:00:00 2001 From: eiman eltigani Date: Tue, 31 Mar 2026 12:30:48 -0600 Subject: [PATCH 03/25] add new doc reference to Tools page and update headers in uid verify page --- docs/ref-info/integration-sample-sites.md | 1 + docs/ref-info/ref-uid-verify.md | 10 ++++------ 2 files changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/ref-info/integration-sample-sites.md b/docs/ref-info/integration-sample-sites.md index 41bcc4428..29a508726 100644 --- a/docs/ref-info/integration-sample-sites.md +++ b/docs/ref-info/integration-sample-sites.md @@ -140,6 +140,7 @@ UID Verify is a Chrome browser extension for debugging UID2 and EUID integration - Site: [UID Verify on Chrome Web Store](https://chromewebstore.google.com/detail/uid-detective/cfpjjmdagnkmmolcddnoagffeoekkmle) - Code: [uid2-detective](https://github.com/IABTechLab/uid2-detective) +- Doc: [UID Verify Chrome Extension](https://unifiedid.com/docs/ref-info/ref-uid-verify) :::note The sample sites on this page highlight some common integrations, but do not represent all available UID2 integration options. For a summary of all the integration options available, see [UID2 Integration Guides: Summary](https://unifiedid.com/docs/guides/summary-guides). diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index 8ddba1907..fd98df287 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -55,9 +55,9 @@ If both a UID2 and an EUID integration are detected on the same page, the extens ### Config Tab -The **Config** tab provides a snapshot of the integration's current state. +The **Config** tab provides a snapshot of the integration's current state, including status banners for successful token generation, errors, opt-out identities, and other configuration states. The information displayed depends on the integration type: -**For SDK integrations, this includes:** +**SDK integrations:** - SDK version - SDK initialization options @@ -67,21 +67,19 @@ The **Config** tab provides a snapshot of the integration's current state. - Token and refresh expiration timestamps - The result of `getAdvertisingToken()` - The result of `isLoginRequired()` -- Status banners highlighting any issues (for example, outdated SDK version, opted-out identity, or missing configuration) -**For Prebid.js integrations, this includes:** +**Prebid.js integrations:** - Whether Prebid.js is detected and the UID2/EUID module is active - The user ID configuration from `pbjs.getUserIds()` - Token validity status -**For Google Secure Signals integrations, this includes:** +**Google Secure Signals integrations:** - Whether Google Publisher Tags is detected - Whether the UID2 or EUID provider ID is registered - Whether `getAdvertisingTokenAsync` is available - The registered collector function code -- A status banner indicating whether the Secure Signals configuration is complete ### Storage Tab From 0263639c39af767be06360d814ede1f875f9bf25 Mon Sep 17 00:00:00 2001 From: eiman eltigani Date: Tue, 31 Mar 2026 12:40:07 -0600 Subject: [PATCH 04/25] update config tab details --- docs/ref-info/ref-uid-verify.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index fd98df287..04449bdf1 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -70,9 +70,8 @@ The **Config** tab provides a snapshot of the integration's current state, inclu **Prebid.js integrations:** -- Whether Prebid.js is detected and the UID2/EUID module is active -- The user ID configuration from `pbjs.getUserIds()` -- Token validity status +- The current UID2 token from `window.pbjs.getUserIds().uid2` +- The Prebid.js configuration parameters from `window.pbjs.getConfig().userSync.userIds` (for example, `uid2ApiBase`, `subscriptionId`, `serverPublicKey`) **Google Secure Signals integrations:** From eb170ef13f835332843ac4f8a181cb6254dd6a04 Mon Sep 17 00:00:00 2001 From: eiman eltigani Date: Tue, 31 Mar 2026 12:49:03 -0600 Subject: [PATCH 05/25] udpate storage tab descriptions --- docs/ref-info/ref-uid-verify.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index 04449bdf1..e25044215 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -84,18 +84,17 @@ The **Config** tab provides a snapshot of the integration's current state, inclu The **Storage** tab shows the raw identity data stored in the browser for the current integration. -**For SDK integrations:** +**For SDK and Prebid.js integrations:** | Field | Description | |---|---| | Storage Type | Whether the identity is stored in a cookie or `localStorage`. | -| Storage Key | The name of the cookie or `localStorage` key (`__uid_2`, `__euid`, `UID2-sdk-identity`, or `EUID-sdk-identity`). | -| Stored Value | The raw identity JSON with syntax highlighting. | -| Validity | Whether the stored identity is currently valid or opted out. | +| Storage Key | The name of the cookie or `localStorage` key. For SDK integrations: `__uid_2`, `__euid`, `uid2-sdk-identity`, or `euid-sdk-identity`. For Prebid.js integrations: `__uid2_advertising_token` or `__euid_advertising_token`. | +| Stored Value | The raw identity JSON, including `advertising_token`, `refresh_token`, `identity_expires`, `refresh_expires`, `refresh_from`, and `refresh_response_key`. | +| Valid Identity | Whether the stored identity is currently valid. | +| Optout Identity | Whether the identity reflects an opted-out user. | -**For Prebid.js integrations**, the tab shows the Prebid token storage location and current value. - -**For Google Secure Signals integrations**, the tab shows the cached Secure Signals value (stored under `_GESPSK-uidapi.com` for UID2 or `_GESPSK-euid.eu` for EUID) and whether the signal was sent via the SDK or Prebid. +**For Google Secure Signals integrations**, the tab shows the status of the secure signal and the current UID2 advertising token. If no signal has been generated yet, it indicates that neither a cached signal nor an SDK advertising token is available. Once the token is available, it confirms that Prebid will include it in bid requests to Google Ad Manager via `encryptedSignalSources`. ### Callbacks Tab From e139a8dce95562bd045c6c4074535ee455512ff1 Mon Sep 17 00:00:00 2001 From: eiman eltigani Date: Tue, 31 Mar 2026 14:04:16 -0600 Subject: [PATCH 06/25] update broken link and remove inaccurate line --- docs/ref-info/ref-uid-verify.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index e25044215..b40f4b838 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -10,9 +10,9 @@ import Link from '@docusaurus/Link'; # UID Verify Chrome Extension -UID Verify is a browser extension for debugging UID2 and EUID integrations. It inspects the UID2 or EUID implementation on the current page in real time, surfacing SDK configuration, identity storage, event history, and errors — without requiring any code changes to the page. +UID Verify is a browser extension for debugging UID2 and EUID integrations. It inspects the UID2 or EUID implementation on the current page in real time, surfacing SDK configuration, identity storage, event history, and errors. -The extension supports integrations using the UID2 JavaScript SDK, Prebid.js, and Google Secure Signals. +The extension supports integrations using the UID2 JavaScript SDK, Prebid.js, and Google Secure Signals. ## Overview @@ -27,7 +27,7 @@ UID Verify requires: - **Google Chrome** or **Microsoft Edge** browser - A web page that has a UID2 or EUID integration — one of the following must be present on the page: - The UID2 JavaScript SDK (`window.__uid2`) or EUID JavaScript SDK (`window.__euid`) - - Prebid.js with a UID2 or EUID user ID module configured + - Prebid.js with a UID2 or EUID user ID module configured - Google Publisher Tags (GPT) with a UID2 or EUID Secure Signals provider registered If more than one integration type is detected, you can switch between them using the integration type tabs at the top of the popup. If neither a UID2/EUID SDK, Prebid.js, nor Google Secure Signals integration is detected, the popup displays a message indicating that no supported integration was found. From a98c8a08123b26a3349294a63d8b118490092933 Mon Sep 17 00:00:00 2001 From: eiman eltigani Date: Wed, 1 Apr 2026 09:30:54 -0600 Subject: [PATCH 07/25] update uid-detective to uid-verify in chrome store link --- docs/ref-info/integration-sample-sites.md | 2 +- docs/ref-info/ref-uid-verify.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/ref-info/integration-sample-sites.md b/docs/ref-info/integration-sample-sites.md index 29a508726..2e9064d0a 100644 --- a/docs/ref-info/integration-sample-sites.md +++ b/docs/ref-info/integration-sample-sites.md @@ -138,7 +138,7 @@ This tool is for developers or clients validating data preparation, such as hash UID Verify is a Chrome browser extension for debugging UID2 and EUID integrations. It inspects SDK information on websites, tracks events and event history, and monitors storage (cookies and local storage). The extension supports integrations using Prebid.js and Google Secure Signals. -- Site: [UID Verify on Chrome Web Store](https://chromewebstore.google.com/detail/uid-detective/cfpjjmdagnkmmolcddnoagffeoekkmle) +- Site: [UID Verify on Chrome Web Store](https://chromewebstore.google.com/detail/uid-verify/cfpjjmdagnkmmolcddnoagffeoekkmle) - Code: [uid2-detective](https://github.com/IABTechLab/uid2-detective) - Doc: [UID Verify Chrome Extension](https://unifiedid.com/docs/ref-info/ref-uid-verify) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index b40f4b838..ab1a7d583 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -36,7 +36,7 @@ If more than one integration type is detected, you can switch between them using Install UID Verify from the Chrome Web Store: -1. Go to the [UID Verify listing](https://chromewebstore.google.com/detail/uid-detective/cfpjjmdagnkmmolcddnoagffeoekkmle) in the Chrome Web Store. +1. Go to the [UID Verify listing](https://chromewebstore.google.com/detail/uid-verify/cfpjjmdagnkmmolcddnoagffeoekkmle) in the Chrome Web Store. 2. Click **Add to Chrome**. 3. When prompted, click **Add extension**. 4. Pin the extension to your toolbar for easy access: click the Extensions icon in your browser, then click the pin icon next to UID Verify. From d6741d8e00d162f5c8877e5d5056ce5540574ef7 Mon Sep 17 00:00:00 2001 From: eiman eltigani Date: Wed, 1 Apr 2026 14:31:01 -0600 Subject: [PATCH 08/25] Remove code link and update integrations sample tools page --- docs/ref-info/integration-sample-sites.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/ref-info/integration-sample-sites.md b/docs/ref-info/integration-sample-sites.md index 2e9064d0a..3e614ac8d 100644 --- a/docs/ref-info/integration-sample-sites.md +++ b/docs/ref-info/integration-sample-sites.md @@ -136,10 +136,9 @@ This tool is for developers or clients validating data preparation, such as hash ### UID Verify Chrome Extension -UID Verify is a Chrome browser extension for debugging UID2 and EUID integrations. It inspects SDK information on websites, tracks events and event history, and monitors storage (cookies and local storage). The extension supports integrations using Prebid.js and Google Secure Signals. +UID Verify is a Google Chrome browser extension for debugging UID2 integrations. It inspects UID2 SDK information on websites, tracks events and event history, and monitors storage (cookies and local storage). The extension supports integrations using Prebid.js and Google Secure Signals. - Site: [UID Verify on Chrome Web Store](https://chromewebstore.google.com/detail/uid-verify/cfpjjmdagnkmmolcddnoagffeoekkmle) -- Code: [uid2-detective](https://github.com/IABTechLab/uid2-detective) - Doc: [UID Verify Chrome Extension](https://unifiedid.com/docs/ref-info/ref-uid-verify) :::note From 63a8e41d27ccc62bdb30b70ec3331158e94f9d3d Mon Sep 17 00:00:00 2001 From: eiman eltigani Date: Thu, 2 Apr 2026 08:03:05 -0600 Subject: [PATCH 09/25] remove EUID reference per Gens feedback --- docs/ref-info/ref-uid-verify.md | 26 +++++++++++++------------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index ab1a7d583..1bbb0084e 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -1,6 +1,6 @@ --- title: UID Verify Chrome Extension -description: How to use the UID Verify Chrome extension to debug and inspect UID2 or EUID integrations on any web page. +description: How to use the UID Verify Chrome extension to debug and inspect UID2 integrations on any web page. hide_table_of_contents: false sidebar_position: 03 displayed_sidebar: docs @@ -10,27 +10,27 @@ import Link from '@docusaurus/Link'; # UID Verify Chrome Extension -UID Verify is a browser extension for debugging UID2 and EUID integrations. It inspects the UID2 or EUID implementation on the current page in real time, surfacing SDK configuration, identity storage, event history, and errors. +UID Verify is a browser extension for debugging UID2 integrations. It inspects the UID2 implementation on the current page in real time, surfacing UID2 SDK configuration, identity storage, event history, and errors. The extension supports integrations using the UID2 JavaScript SDK, Prebid.js, and Google Secure Signals. ## Overview -When integrating UID2 or EUID, it can be difficult to tell whether the SDK is initializing correctly, whether tokens are valid, or where in the lifecycle an error is occurring. UID Verify solves this by reading the SDK state, storage, and event stream directly from the page and presenting it in a structured, searchable interface. +When integrating UID2, it can be difficult to tell whether the SDK is initializing correctly, whether tokens are valid, or where in the lifecycle an error is occurring. UID Verify solves this by reading the SDK state, storage, and event stream directly from the page and presenting it in a structured, searchable interface. -The extension detects whether a page uses the UID2 SDK directly, Prebid.js, or Google Secure Signals (or a combination), and adjusts the displayed information accordingly. It supports both UID2 and EUID deployments. +The extension detects whether a page uses the UID2 SDK directly, Prebid.js, or Google Secure Signals (or a combination), and adjusts the displayed information accordingly. ## Prerequisites UID Verify requires: - **Google Chrome** or **Microsoft Edge** browser -- A web page that has a UID2 or EUID integration — one of the following must be present on the page: - - The UID2 JavaScript SDK (`window.__uid2`) or EUID JavaScript SDK (`window.__euid`) - - Prebid.js with a UID2 or EUID user ID module configured - - Google Publisher Tags (GPT) with a UID2 or EUID Secure Signals provider registered +- A web page that has a UID2 integration — one of the following must be present on the page: + - The UID2 JavaScript SDK (`window.__uid2`) + - Prebid.js with a UID2 user ID module configured + - Google Publisher Tags (GPT) with a UID2 Secure Signals provider registered -If more than one integration type is detected, you can switch between them using the integration type tabs at the top of the popup. If neither a UID2/EUID SDK, Prebid.js, nor Google Secure Signals integration is detected, the popup displays a message indicating that no supported integration was found. +If more than one integration type is detected, you can switch between them using the integration type tabs at the top of the popup. If no supported integration is detected, the popup displays a message indicating that no supported integration was found. ## Installing the Extension @@ -43,12 +43,12 @@ Install UID Verify from the Chrome Web Store: ## Using UID Verify -1. Navigate to a web page that has a UID2 or EUID integration. +1. Navigate to a web page that has a UID2 integration. 2. Click the **UID Verify** icon in your browser toolbar to open the extension popup. 3. The extension detects the integration type on the page and displays the appropriate tabs. :::note -If both a UID2 and an EUID integration are detected on the same page, the extension displays an error. A page should use either UID2 (for North America and parts of Asia) or EUID (for Europe and other GDPR-applicable regions), not both. +UID Verify supports both UID2 and EUID. A page should use either UID2 (for North America and parts of Asia) or EUID (for Europe and other GDPR-applicable regions), not both. If both are detected on the same page, the extension displays an error. ::: ## Interpreting Results @@ -76,7 +76,7 @@ The **Config** tab provides a snapshot of the integration's current state, inclu **Google Secure Signals integrations:** - Whether Google Publisher Tags is detected -- Whether the UID2 or EUID provider ID is registered +- Whether the UID2 provider ID is registered - Whether `getAdvertisingTokenAsync` is available - The registered collector function code @@ -89,7 +89,7 @@ The **Storage** tab shows the raw identity data stored in the browser for the cu | Field | Description | |---|---| | Storage Type | Whether the identity is stored in a cookie or `localStorage`. | -| Storage Key | The name of the cookie or `localStorage` key. For SDK integrations: `__uid_2`, `__euid`, `uid2-sdk-identity`, or `euid-sdk-identity`. For Prebid.js integrations: `__uid2_advertising_token` or `__euid_advertising_token`. | +| Storage Key | The name of the cookie or `localStorage` key. For SDK integrations: `__uid_2` or `uid2-sdk-identity`. For Prebid.js integrations: `__uid2_advertising_token`. | | Stored Value | The raw identity JSON, including `advertising_token`, `refresh_token`, `identity_expires`, `refresh_expires`, `refresh_from`, and `refresh_response_key`. | | Valid Identity | Whether the stored identity is currently valid. | | Optout Identity | Whether the identity reflects an opted-out user. | From a4e0b2001147ea3bf63f98148a3d51d842abd9d9 Mon Sep 17 00:00:00 2001 From: eiman eltigani Date: Thu, 2 Apr 2026 09:51:27 -0600 Subject: [PATCH 10/25] change siidebar location to match euid --- docs/ref-info/integration-sample-sites.md | 2 +- docs/ref-info/ref-uid-verify.md | 36 +++++++++++++---------- sidebars.js | 2 +- 3 files changed, 22 insertions(+), 18 deletions(-) diff --git a/docs/ref-info/integration-sample-sites.md b/docs/ref-info/integration-sample-sites.md index 3e614ac8d..0cec89d0a 100644 --- a/docs/ref-info/integration-sample-sites.md +++ b/docs/ref-info/integration-sample-sites.md @@ -136,7 +136,7 @@ This tool is for developers or clients validating data preparation, such as hash ### UID Verify Chrome Extension -UID Verify is a Google Chrome browser extension for debugging UID2 integrations. It inspects UID2 SDK information on websites, tracks events and event history, and monitors storage (cookies and local storage). The extension supports integrations using Prebid.js and Google Secure Signals. +UID Verify is a Google Chrome browser extension for debugging UID2 integrations. It inspects UID2 SDK information on websites, tracks events and event history, and monitors storage (cookies and local storage). It also supports Prebid.js and Google Secure Signals integrations. - Site: [UID Verify on Chrome Web Store](https://chromewebstore.google.com/detail/uid-verify/cfpjjmdagnkmmolcddnoagffeoekkmle) - Doc: [UID Verify Chrome Extension](https://unifiedid.com/docs/ref-info/ref-uid-verify) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index 1bbb0084e..bf11878ac 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -12,25 +12,29 @@ import Link from '@docusaurus/Link'; UID Verify is a browser extension for debugging UID2 integrations. It inspects the UID2 implementation on the current page in real time, surfacing UID2 SDK configuration, identity storage, event history, and errors. -The extension supports integrations using the UID2 JavaScript SDK, Prebid.js, and Google Secure Signals. +The extension supports integrations using the SDK for JavaScript, Prebid.js, and Google Secure Signals. ## Overview -When integrating UID2, it can be difficult to tell whether the SDK is initializing correctly, whether tokens are valid, or where in the lifecycle an error is occurring. UID Verify solves this by reading the SDK state, storage, and event stream directly from the page and presenting it in a structured, searchable interface. +When integrating UID2, it can be difficult to tell whether the UID2 SDK is initializing correctly, whether tokens are valid, or where in the lifecycle an error is occurring. UID Verify helps debug this by reading the UID2 SDK configuration, identity data, and event stream directly from the page and presenting it in a structured, searchable interface. -The extension detects whether a page uses the UID2 SDK directly, Prebid.js, or Google Secure Signals (or a combination), and adjusts the displayed information accordingly. +The extension detects whether a page uses the UID2 SDK directly, Prebid.js, or Google Secure Signals (or a combination), and displays the relevant information for each integration type. ## Prerequisites UID Verify requires: -- **Google Chrome** or **Microsoft Edge** browser +- **Google Chrome** browser - A web page that has a UID2 integration — one of the following must be present on the page: - - The UID2 JavaScript SDK (`window.__uid2`) + - The SDK for JavaScript is loaded on the page (accessible via `window.__uid2`) - Prebid.js with a UID2 user ID module configured - Google Publisher Tags (GPT) with a UID2 Secure Signals provider registered -If more than one integration type is detected, you can switch between them using the integration type tabs at the top of the popup. If no supported integration is detected, the popup displays a message indicating that no supported integration was found. +If more than one integration type is detected, you can switch between them using the integration type tabs at the top of the popup. + +:::note +Server-side integrations are not currently supported. UID Verify works by reading client-side signals such as browser storage and UID2 SDK globals, which are not present in a server-side integration. +::: ## Installing the Extension @@ -57,10 +61,10 @@ UID Verify supports both UID2 and EUID. A page should use either UID2 (for North The **Config** tab provides a snapshot of the integration's current state, including status banners for successful token generation, errors, opt-out identities, and other configuration states. The information displayed depends on the integration type: -**SDK integrations:** +**UID2 SDK integrations:** -- SDK version -- SDK initialization options +- UID2 SDK version +- UID2 SDK initialization options - The current identity object, including: - Advertising token - Refresh token @@ -84,25 +88,25 @@ The **Config** tab provides a snapshot of the integration's current state, inclu The **Storage** tab shows the raw identity data stored in the browser for the current integration. -**For SDK and Prebid.js integrations:** +**For UID2 SDK and Prebid.js integrations:** | Field | Description | |---|---| | Storage Type | Whether the identity is stored in a cookie or `localStorage`. | -| Storage Key | The name of the cookie or `localStorage` key. For SDK integrations: `__uid_2` or `uid2-sdk-identity`. For Prebid.js integrations: `__uid2_advertising_token`. | +| Storage Key | The name of the cookie or `localStorage` key. For UID2 SDK integrations: `__uid_2` or `UID2-sdk-identity`. For Prebid.js integrations: `__uid2_advertising_token`. | | Stored Value | The raw identity JSON, including `advertising_token`, `refresh_token`, `identity_expires`, `refresh_expires`, `refresh_from`, and `refresh_response_key`. | -| Valid Identity | Whether the stored identity is currently valid. | +| Valid Identity | Whether the stored identity is currently valid — that is, the advertising token has not expired and the user has not opted out. | | Optout Identity | Whether the identity reflects an opted-out user. | -**For Google Secure Signals integrations**, the tab shows the status of the secure signal and the current UID2 advertising token. If no signal has been generated yet, it indicates that neither a cached signal nor an SDK advertising token is available. Once the token is available, it confirms that Prebid will include it in bid requests to Google Ad Manager via `encryptedSignalSources`. +**For Google Secure Signals integrations**, the tab shows the status of the secure signal and the current UID2 advertising token. If no signal has been generated yet, it indicates that neither a cached signal nor a UID2 SDK advertising token is available. Once the token is available, it confirms that it will be included in bid requests to Google Ad Manager. ### Callbacks Tab -The **Callbacks** tab is available for SDK integrations only. It displays the source code of all callback functions registered with the SDK, with syntax highlighting. This is useful for confirming that the correct callbacks are wired up and identifying where events are being handled in the page code. +The **Callbacks** tab is available for UID2 SDK integrations only. It displays the source code of all callback functions registered with the UID2 SDK, with syntax highlighting. This is useful for confirming that the correct callbacks are wired up and identifying where events are being handled in the page code. ### Event History Tab -The **Event History** tab shows a searchable, real-time log of SDK events as they occur on the page. Each row in the table includes: +The **Event History** tab shows a searchable, real-time log of UID2 SDK events as they occur on the page. Each row in the table includes: | Column | Description | |---|---| @@ -113,6 +117,6 @@ The **Event History** tab shows a searchable, real-time log of SDK events as the Use the search bar to filter by event type or token value. -This tab also includes an **Error Log** when errors are detected. The extension captures several categories of errors: failed network requests to the UID2 operator, failed resource loads (such as the SDK script), `console.error` calls from SDK code, and errors thrown by SDK methods. +This tab also includes an **Error Log** when errors are detected. The extension captures several categories of errors: failed network requests to the UID2 operator, failed resource loads (such as the UID2 SDK script), `console.error` calls from UID2 SDK code, and errors thrown by UID2 SDK methods. For known error patterns, the extension displays contextual troubleshooting guidance alongside the error. diff --git a/sidebars.js b/sidebars.js index fe94f0457..3aaa9a2a3 100644 --- a/sidebars.js +++ b/sidebars.js @@ -369,11 +369,11 @@ const fullSidebar = [ 'getting-started/gs-normalization-encoding', 'ref-info/ref-preparing-emails-and-phone-numbers-for-processing', 'ref-info/ref-token-validator', - 'ref-info/ref-uid-verify', 'getting-started/gs-opt-out', 'ref-info/ref-operators-public-private', 'ref-info/ref-integration-approaches', 'ref-info/integration-sample-sites', + 'ref-info/ref-uid-verify', 'ref-info/ref-tokens', 'ref-info/ref-how-uid-is-created', 'ref-info/ref-server-side-token-generation', From 590c7a257a6bd75ca8996f64f414b8e1e97fc967 Mon Sep 17 00:00:00 2001 From: eiman eltigani Date: Thu, 2 Apr 2026 09:55:09 -0600 Subject: [PATCH 11/25] improve definition for gss variable --- docs/ref-info/ref-uid-verify.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index bf11878ac..79d916efe 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -82,7 +82,7 @@ The **Config** tab provides a snapshot of the integration's current state, inclu - Whether Google Publisher Tags is detected - Whether the UID2 provider ID is registered - Whether `getAdvertisingTokenAsync` is available -- The registered collector function code +- Whether a collector function is registered (the function that passes the UID2 token as an encrypted signal to Google Ad Manager) ### Storage Tab From eba0df83734c43108cb1769458818a9f214ca8ca Mon Sep 17 00:00:00 2001 From: eiman-eltigani-ttd Date: Mon, 6 Apr 2026 09:16:42 -0600 Subject: [PATCH 12/25] Apply suggestion from @genwhittTTD Co-authored-by: Gen Whitt <107279666+genwhittTTD@users.noreply.github.com> --- docs/ref-info/ref-uid-verify.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index 79d916efe..dbbc86895 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -38,7 +38,7 @@ Server-side integrations are not currently supported. UID Verify works by readin ## Installing the Extension -Install UID Verify from the Chrome Web Store: +To install UID Verify from the Chrome Web Store, follow these steps: 1. Go to the [UID Verify listing](https://chromewebstore.google.com/detail/uid-verify/cfpjjmdagnkmmolcddnoagffeoekkmle) in the Chrome Web Store. 2. Click **Add to Chrome**. From df08680959d8a7fb3f2fc5d06051b2ee35c9e0a4 Mon Sep 17 00:00:00 2001 From: eiman-eltigani-ttd Date: Mon, 6 Apr 2026 09:17:02 -0600 Subject: [PATCH 13/25] Apply suggestion from @genwhittTTD Co-authored-by: Gen Whitt <107279666+genwhittTTD@users.noreply.github.com> --- docs/ref-info/ref-uid-verify.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index dbbc86895..294bf8b55 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -49,7 +49,8 @@ To install UID Verify from the Chrome Web Store, follow these steps: 1. Navigate to a web page that has a UID2 integration. 2. Click the **UID Verify** icon in your browser toolbar to open the extension popup. -3. The extension detects the integration type on the page and displays the appropriate tabs. +2. Click the **UID Verify** icon in your browser toolbar to open the extension popup. + The extension detects the integration type on the page and displays the appropriate tabs. :::note UID Verify supports both UID2 and EUID. A page should use either UID2 (for North America and parts of Asia) or EUID (for Europe and other GDPR-applicable regions), not both. If both are detected on the same page, the extension displays an error. From 2dab41c06c4b7e1785794e1a8fde7b93119d4f4f Mon Sep 17 00:00:00 2001 From: eiman-eltigani-ttd Date: Mon, 6 Apr 2026 09:17:17 -0600 Subject: [PATCH 14/25] Apply suggestion from @genwhittTTD Co-authored-by: Gen Whitt <107279666+genwhittTTD@users.noreply.github.com> --- docs/ref-info/ref-uid-verify.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index 294bf8b55..32b3941b3 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -60,7 +60,7 @@ UID Verify supports both UID2 and EUID. A page should use either UID2 (for North ### Config Tab -The **Config** tab provides a snapshot of the integration's current state, including status banners for successful token generation, errors, opt-out identities, and other configuration states. The information displayed depends on the integration type: +The **Config** tab provides a snapshot of the integration's current state, including status banners for successful token generation, errors, opt-out identities, and other configuration states. The information displayed depends on the integration type, as shown in the following sections. **UID2 SDK integrations:** From a11599940c793b52714fd93cde6327865a2379ce Mon Sep 17 00:00:00 2001 From: eiman-eltigani-ttd Date: Mon, 6 Apr 2026 09:17:25 -0600 Subject: [PATCH 15/25] Apply suggestion from @genwhittTTD Co-authored-by: Gen Whitt <107279666+genwhittTTD@users.noreply.github.com> --- docs/ref-info/ref-uid-verify.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index 32b3941b3..6719bffdf 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -89,7 +89,9 @@ The **Config** tab provides a snapshot of the integration's current state, inclu The **Storage** tab shows the raw identity data stored in the browser for the current integration. -**For UID2 SDK and Prebid.js integrations:** +**UID2 SDK and Prebid.js integrations** + +SDK and Prebid.js integrations include the fields shown in the following table. | Field | Description | |---|---| From f4419c24f8b5eb77dc04ad5b0cf4496da7192836 Mon Sep 17 00:00:00 2001 From: eiman-eltigani-ttd Date: Mon, 6 Apr 2026 09:17:37 -0600 Subject: [PATCH 16/25] Apply suggestion from @genwhittTTD Co-authored-by: Gen Whitt <107279666+genwhittTTD@users.noreply.github.com> --- docs/ref-info/ref-uid-verify.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index 6719bffdf..f8dc0af1a 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -95,7 +95,7 @@ SDK and Prebid.js integrations include the fields shown in the following table. | Field | Description | |---|---| -| Storage Type | Whether the identity is stored in a cookie or `localStorage`. | +| Storage Type | Indicates whether the identity is stored in a cookie or `localStorage`. | | Storage Key | The name of the cookie or `localStorage` key. For UID2 SDK integrations: `__uid_2` or `UID2-sdk-identity`. For Prebid.js integrations: `__uid2_advertising_token`. | | Stored Value | The raw identity JSON, including `advertising_token`, `refresh_token`, `identity_expires`, `refresh_expires`, `refresh_from`, and `refresh_response_key`. | | Valid Identity | Whether the stored identity is currently valid — that is, the advertising token has not expired and the user has not opted out. | From 0314d848175f93ce1fb42d3d778215acfccaa40d Mon Sep 17 00:00:00 2001 From: eiman-eltigani-ttd Date: Mon, 6 Apr 2026 09:17:48 -0600 Subject: [PATCH 17/25] Apply suggestion from @genwhittTTD Co-authored-by: Gen Whitt <107279666+genwhittTTD@users.noreply.github.com> --- docs/ref-info/ref-uid-verify.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index f8dc0af1a..19f6f4da3 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -98,7 +98,7 @@ SDK and Prebid.js integrations include the fields shown in the following table. | Storage Type | Indicates whether the identity is stored in a cookie or `localStorage`. | | Storage Key | The name of the cookie or `localStorage` key. For UID2 SDK integrations: `__uid_2` or `UID2-sdk-identity`. For Prebid.js integrations: `__uid2_advertising_token`. | | Stored Value | The raw identity JSON, including `advertising_token`, `refresh_token`, `identity_expires`, `refresh_expires`, `refresh_from`, and `refresh_response_key`. | -| Valid Identity | Whether the stored identity is currently valid — that is, the advertising token has not expired and the user has not opted out. | +| Valid Identity | Indicates whether the stored identity is currently valid — that is, the advertising token has not expired and the user has not opted out. | | Optout Identity | Whether the identity reflects an opted-out user. | **For Google Secure Signals integrations**, the tab shows the status of the secure signal and the current UID2 advertising token. If no signal has been generated yet, it indicates that neither a cached signal nor a UID2 SDK advertising token is available. Once the token is available, it confirms that it will be included in bid requests to Google Ad Manager. From 5a0183efdeefedf1003490654d2622b81c6fdeb2 Mon Sep 17 00:00:00 2001 From: eiman-eltigani-ttd Date: Mon, 6 Apr 2026 09:17:58 -0600 Subject: [PATCH 18/25] Apply suggestion from @genwhittTTD Co-authored-by: Gen Whitt <107279666+genwhittTTD@users.noreply.github.com> --- docs/ref-info/ref-uid-verify.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index 19f6f4da3..0fea7530f 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -109,7 +109,7 @@ The **Callbacks** tab is available for UID2 SDK integrations only. It displays t ### Event History Tab -The **Event History** tab shows a searchable, real-time log of UID2 SDK events as they occur on the page. Each row in the table includes: +The **Event History** tab shows a searchable, real-time log of UID2 SDK events as they occur on the page. It includes the columns shown in the following table. | Column | Description | |---|---| From 775020044fa6e836496a93c795bc83f4cf977f42 Mon Sep 17 00:00:00 2001 From: eiman-eltigani-ttd Date: Mon, 6 Apr 2026 09:18:08 -0600 Subject: [PATCH 19/25] Apply suggestion from @genwhittTTD Co-authored-by: Gen Whitt <107279666+genwhittTTD@users.noreply.github.com> --- docs/ref-info/ref-uid-verify.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index 0fea7530f..74cbd7ce2 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -99,7 +99,7 @@ SDK and Prebid.js integrations include the fields shown in the following table. | Storage Key | The name of the cookie or `localStorage` key. For UID2 SDK integrations: `__uid_2` or `UID2-sdk-identity`. For Prebid.js integrations: `__uid2_advertising_token`. | | Stored Value | The raw identity JSON, including `advertising_token`, `refresh_token`, `identity_expires`, `refresh_expires`, `refresh_from`, and `refresh_response_key`. | | Valid Identity | Indicates whether the stored identity is currently valid — that is, the advertising token has not expired and the user has not opted out. | -| Optout Identity | Whether the identity reflects an opted-out user. | +| Optout Identity | Indicates whether the identity reflects an opted-out user. | **For Google Secure Signals integrations**, the tab shows the status of the secure signal and the current UID2 advertising token. If no signal has been generated yet, it indicates that neither a cached signal nor a UID2 SDK advertising token is available. Once the token is available, it confirms that it will be included in bid requests to Google Ad Manager. From 23ccd2c165374641f821d770fc2127a755ee3998 Mon Sep 17 00:00:00 2001 From: eiman eltigani Date: Mon, 6 Apr 2026 11:33:37 -0600 Subject: [PATCH 20/25] update package to fix vulnerability --- package-lock.json | 6 +++--- package.json | 3 ++- 2 files changed, 5 insertions(+), 4 deletions(-) diff --git a/package-lock.json b/package-lock.json index e0bdabdfd..d2f586544 100644 --- a/package-lock.json +++ b/package-lock.json @@ -10624,9 +10624,9 @@ } }, "node_modules/lodash": { - "version": "4.17.21", - "resolved": "https://registry.npmjs.org/lodash/-/lodash-4.17.21.tgz", - "integrity": "sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==" + "version": "4.18.1", + "resolved": "https://registry.npmjs.org/lodash/-/lodash-4.18.1.tgz", + "integrity": "sha512-dMInicTPVE8d1e5otfwmmjlxkZoUpiVLwyeTdUsi/Caj/gfzzblBcCE5sRHV/AsjuCmxWrte2TNGSYuCeCq+0Q==" }, "node_modules/lodash.debounce": { "version": "4.0.8", diff --git a/package.json b/package.json index 5fdd57ef7..3628715f0 100644 --- a/package.json +++ b/package.json @@ -60,7 +60,8 @@ "serialize-javascript": "^7.0.3", "svgo": "^3.3.3", "node-forge": "^1.4.0", - "picomatch": "^2.3.2" + "picomatch": "^2.3.2", + "lodash": "^4.18.0" }, "browserslist": { "production": [ From 78510e3332d8933907fb004c4852033853b823fe Mon Sep 17 00:00:00 2001 From: eiman eltigani Date: Mon, 6 Apr 2026 11:36:00 -0600 Subject: [PATCH 21/25] add lead-in copy and fix duplicate step in uid-verify doc --- docs/ref-info/ref-uid-verify.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index 74cbd7ce2..ec98a5054 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -47,10 +47,11 @@ To install UID Verify from the Chrome Web Store, follow these steps: ## Using UID Verify +Once installed, follow these steps to inspect a UID2 integration: + 1. Navigate to a web page that has a UID2 integration. 2. Click the **UID Verify** icon in your browser toolbar to open the extension popup. -2. Click the **UID Verify** icon in your browser toolbar to open the extension popup. - The extension detects the integration type on the page and displays the appropriate tabs. +3. The extension detects the integration type on the page and displays the appropriate tabs. :::note UID Verify supports both UID2 and EUID. A page should use either UID2 (for North America and parts of Asia) or EUID (for Europe and other GDPR-applicable regions), not both. If both are detected on the same page, the extension displays an error. @@ -58,6 +59,8 @@ UID Verify supports both UID2 and EUID. A page should use either UID2 (for North ## Interpreting Results +The following sections describe the information available in each tab of the UID Verify popup. + ### Config Tab The **Config** tab provides a snapshot of the integration's current state, including status banners for successful token generation, errors, opt-out identities, and other configuration states. The information displayed depends on the integration type, as shown in the following sections. From 06c383f9d56e0a2e5babf76d87f7543a82ec7953 Mon Sep 17 00:00:00 2001 From: eiman eltigani Date: Mon, 6 Apr 2026 11:46:57 -0600 Subject: [PATCH 22/25] add lead in sentence and clarify content section for gss --- docs/ref-info/ref-uid-verify.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index ec98a5054..4ada4224c 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -59,7 +59,7 @@ UID Verify supports both UID2 and EUID. A page should use either UID2 (for North ## Interpreting Results -The following sections describe the information available in each tab of the UID Verify popup. +The following sections describe the information available in each tab of the UID Verify popup. The content of each tab varies depending on the integration type detected. ### Config Tab @@ -104,7 +104,7 @@ SDK and Prebid.js integrations include the fields shown in the following table. | Valid Identity | Indicates whether the stored identity is currently valid — that is, the advertising token has not expired and the user has not opted out. | | Optout Identity | Indicates whether the identity reflects an opted-out user. | -**For Google Secure Signals integrations**, the tab shows the status of the secure signal and the current UID2 advertising token. If no signal has been generated yet, it indicates that neither a cached signal nor a UID2 SDK advertising token is available. Once the token is available, it confirms that it will be included in bid requests to Google Ad Manager. +For Google Secure Signals integrations, the tab shows the status of the secure signal and the current UID2 advertising token. If no signal has been generated yet, it indicates that neither a cached signal nor a UID2 SDK advertising token is available. When the collector function has run successfully, the extension displays a "Secure signal is cached" status message and shows the cached value stored under `_GESPSK-uidapi.com`. The cached signal is in the format `[providerId, advertisingToken, expiryTimestamp]`. The current UID2 advertising token is also displayed separately. ### Callbacks Tab From a14a7fd113394156f32667a9016753e89abf57a9 Mon Sep 17 00:00:00 2001 From: eiman eltigani Date: Mon, 6 Apr 2026 11:54:09 -0600 Subject: [PATCH 23/25] use more precise wording to explain callbacks --- docs/ref-info/ref-uid-verify.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index 4ada4224c..25c5c793f 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -108,7 +108,7 @@ For Google Secure Signals integrations, the tab shows the status of the secure s ### Callbacks Tab -The **Callbacks** tab is available for UID2 SDK integrations only. It displays the source code of all callback functions registered with the UID2 SDK, with syntax highlighting. This is useful for confirming that the correct callbacks are wired up and identifying where events are being handled in the page code. +The **Callbacks** tab is available for UID2 SDK integrations only. It displays the source code of all callback functions registered with the UID2 SDK, with syntax highlighting. This is useful for confirming that the correct callbacks are registered and identifying where events are being handled in the page code. ### Event History Tab From f99feb74fbf8b67aa3e728f00cfb7bcfbfd6cd67 Mon Sep 17 00:00:00 2001 From: eiman eltigani Date: Mon, 6 Apr 2026 12:25:29 -0600 Subject: [PATCH 24/25] seperate example errors into bulleted list --- docs/ref-info/ref-uid-verify.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index 25c5c793f..e910dd62b 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -123,6 +123,11 @@ The **Event History** tab shows a searchable, real-time log of UID2 SDK events a Use the search bar to filter by event type or token value. -This tab also includes an **Error Log** when errors are detected. The extension captures several categories of errors: failed network requests to the UID2 operator, failed resource loads (such as the UID2 SDK script), `console.error` calls from UID2 SDK code, and errors thrown by UID2 SDK methods. +This tab also includes an **Error Log** when errors are detected. The extension captures several categories of errors: + +- Failed network requests to the UID2 operator +- Failed resource loads (such as the UID2 SDK script) +- `console.error` calls from UID2 SDK code +- Errors thrown by UID2 SDK methods For known error patterns, the extension displays contextual troubleshooting guidance alongside the error. From 9b40f2973e7c1d51713fea28f9024d58a0074644 Mon Sep 17 00:00:00 2001 From: eiman eltigani Date: Mon, 6 Apr 2026 12:28:28 -0600 Subject: [PATCH 25/25] include wording to make it clear error list is not exhaustive --- docs/ref-info/ref-uid-verify.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/ref-info/ref-uid-verify.md b/docs/ref-info/ref-uid-verify.md index e910dd62b..86e7ae4a5 100644 --- a/docs/ref-info/ref-uid-verify.md +++ b/docs/ref-info/ref-uid-verify.md @@ -123,7 +123,7 @@ The **Event History** tab shows a searchable, real-time log of UID2 SDK events a Use the search bar to filter by event type or token value. -This tab also includes an **Error Log** when errors are detected. The extension captures several categories of errors: +This tab also includes an **Error Log** when errors are detected. The extension captures errors from several sources, including: - Failed network requests to the UID2 operator - Failed resource loads (such as the UID2 SDK script)