UID2-7375 Reference UID Verify from publisher web integration guides#1037
UID2-7375 Reference UID Verify from publisher web integration guides#1037sunnywu wants to merge 2 commits into
Conversation
Add tips pointing to the UID Verify Chrome extension reference page from the publisher web integration resources and the individual supported web guides, so it's discoverable beyond its standalone ref page. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Extract the repeated tip into _snpt-uid-verify-debug-tip.mdx and import it into all seven consuming pages instead of duplicating the callout text. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
genwhittTTD
left a comment
genwhittTTD
left a comment
There was a problem hiding this comment.
Left some comments. The tip copy itself is great but I'm suggesting different placement -- a separate section, below the "Integrating with single sign-on (SSO)" section which is in many docs -- no Tip tag, don't include it in the main intro and overview pages. Those are my suggestions.
| To use the UID2 Google Ad Manager secure signals integration, if you are using an SDK you must have your UID2 integration already set up. This does not apply if you are using server-side integration. For a summary of all the integration options available, see [Integration guides: Summary](summary-guides.md). | ||
| ::: | ||
|
|
||
| <SnptUidVerifyDebugTip /> |
There was a problem hiding this comment.
visual issue here -- a Note immediately followed by a Tip, better not to do.
Suggest have the content here without the Tip tag?
Another possibility is to add it as an item in the Troubleshooting article (https://unifiedid.com/docs/guides/integration-google-ss#troubleshooting).
Or we could change the preceding Note into a prerequisites section.
There was a problem hiding this comment.
change note to prerequisites is better - Adding a Troubleshooting section at the bottom may be overlooked.
| - Automatic refreshing of UID2 tokens | ||
| - Automatic storage of UID2 tokens in the browser | ||
|
|
||
| <SnptUidVerifyDebugTip /> |
There was a problem hiding this comment.
I don't love the placement here -- between the SDK features and the summary of steps to implement, which I think flow well one to the other. Perhaps it could go after the summary of steps? But keep it here if you prefer.
| If you are using Google Ad Manager and want to use the secure signals feature, first follow the steps in this guide and then follow the additional steps in the [Google Ad Manager Secure Signals integration guide](integration-google-ss.md). | ||
| ::: | ||
|
|
||
| <SnptUidVerifyDebugTip /> |
There was a problem hiding this comment.
Again, here, it's added in right below another admonition. We avoid consecutive admonitions if possible. And in this case there is even another one before that, with only one line of copy between. So we have Tip, one line, Note, then this new Tip.
I had an idea. What about having a separate section directly after the "Integrating with single sign-on (SSO)" section in applicable guides, and calling it "Using UID Verify Chrome Extension"? That would mean consistent placement in all applicable docs.
| As long as you generate the token and keep it refreshed, you can also use other options for passing the UID2 token into the bidstream. | ||
| ::: | ||
|
|
||
| ## Debug your integration |
There was a problem hiding this comment.
Here it's a separate section, which I think is good.
How about we call it "Using UID Verify Chrome Extension"? Or, "Inspecting with UID Verify"? Or some other name you're comfortable with for the instances in the other guides so that in all instances it could be a separate section. Yours is better, actually, because it says what it does. But right at the top of the other docs is too soon to introduce debugging info.
Whatever you settle on for the title, remove the "tip" tag. We should not have a whole section with only a tip in it and no other copy.
There was a problem hiding this comment.
Yeh i think "Inspecting with UID Verify Chrome Extension" is good.
| | Server-side integration | [Publisher integration guide, server-side](../guides/integration-publisher-server-side.md) | A guide for publishers who do not use the [SDK for JavaScript](../sdks/sdk-ref-javascript.md). | | ||
| | Publisher/SSP integration with GAM | [Google Ad Manager Secure Signals integration guide](../guides/integration-google-ss.md) | A guide covering the additional steps needed for publishers using UID2 with the Google Ad Manager Secure Signals feature (previously known as Encrypted Signals for Publishers, ESP). | | ||
|
|
||
| <SnptUidVerifyDebugTip /> |
There was a problem hiding this comment.
_snpt-publisher-implementation-resources is used in a couple of overview-type docs including the main Publishers overview/intro page. I think that it's better not on those pages. It's debug info. Better to just have it as a heading on the pages for the specific docs is my though, with the separate heading as suggested in earlier comments (and no Tip tag).
2 participants
Summary
UID Verify (the Chrome debugging extension) was previously documented only on its standalone reference page (
ref-info/ref-uid-verify). It was not referenced from the publisher integration guides.This PR adds a shared snippet (
docs/snippets/_snpt-uid-verify-debug-tip.mdx) with a:::tippointing to the UID Verify reference page, framed as a debugging/inspection aid (not a token-generation integration option), and imports it into:Hub pages:
docs/snippets/_snpt-publisher-implementation-resources.mdx— renders on Publisher integration resources and the Publishers overviewdocs/guides/integration-options-publisher-web.md— new "Debug your integration" sectionIndividual web guides (the three integration types UID Verify supports):
integration-javascript-client-side.mdintegration-javascript-client-server.mdintegration-prebid-client-side.mdintegration-prebid-client-server.mdintegration-google-ss.mdThe tip text lives in a single snippet so it stays consistent across all pages. Additions only; no existing content changed. Pure server-side guide is excluded (nothing client-side for UID Verify to inspect). Japanese i18n mirror left for the docs team to translate separately.
Jira
UID2-7375
Related
EUID-docs companion PR: European-Unified-ID/EUID-docs#425
🤖 Generated with Claude Code