-
Notifications
You must be signed in to change notification settings - Fork 50
UID2-7375 Reference UID Verify from publisher web integration guides #1037
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,6 +12,7 @@ import Link from '@docusaurus/Link'; | |
| import SnptIntegratingWithSSO from '../snippets/_snpt-integrating-with-sso.mdx'; | ||
| import SnptPreparingEmailsAndPhoneNumbers from '../snippets/_snpt-preparing-emails-and-phone-numbers.mdx'; | ||
| import SnptExampleClientServerSendUid2ToSdk from '../snippets/_snpt-example-client-server-send-uid2-to-sdk.mdx'; | ||
| import SnptUidVerifyDebugTip from '../snippets/_snpt-uid-verify-debug-tip.mdx'; | ||
|
|
||
| # Client-server integration guide for JavaScript | ||
|
|
||
|
|
@@ -43,6 +44,8 @@ For integration scenarios for publishers that do not use the SDK for JavaScript, | |
| 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 /> | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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. |
||
|
|
||
| ## Integrating with single sign-on (SSO) | ||
|
|
||
| <SnptIntegratingWithSSO /> | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -13,6 +13,7 @@ import Tabs from '@theme/Tabs'; | |
| import TabItem from '@theme/TabItem'; | ||
| import SnptIntegratingWithSSO from '../snippets/_snpt-integrating-with-sso.mdx'; | ||
| import SnptPreparingEmailsAndPhoneNumbers from '../snippets/_snpt-preparing-emails-and-phone-numbers.mdx'; | ||
| import SnptUidVerifyDebugTip from '../snippets/_snpt-uid-verify-debug-tip.mdx'; | ||
|
|
||
| # Client-side integration guide for JavaScript | ||
|
|
||
|
|
@@ -37,6 +38,8 @@ UID2 provides an SDK for JavaScript (see [SDK for JavaScript reference guide](.. | |
| - Automatic refreshing of UID2 tokens | ||
| - Automatic storage of UID2 tokens in the browser | ||
|
|
||
| <SnptUidVerifyDebugTip /> | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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. |
||
|
|
||
| To implement, you'll need to complete the following steps: | ||
|
|
||
| 1. [Complete UID2 account setup and configure account](#complete-uid2-account-setup-and-configure-account) | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -8,6 +8,7 @@ displayed_sidebar: sidebarPublishers | |
|
|
||
| import Link from '@docusaurus/Link'; | ||
| import SnptPreparingEmailsAndPhoneNumbers from '../snippets/_snpt-preparing-emails-and-phone-numbers.mdx'; | ||
| import SnptUidVerifyDebugTip from '../snippets/_snpt-uid-verify-debug-tip.mdx'; | ||
|
|
||
| # Publisher web integration overview | ||
|
|
||
|
|
@@ -138,3 +139,7 @@ The following table shows integration options that support passing UID2 token in | |
| :::note | ||
| 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 | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 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.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeh i think "Inspecting with UID Verify Chrome Extension" is good. |
||
|
|
||
| <SnptUidVerifyDebugTip /> | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,4 +1,5 @@ | ||
| import Link from '@docusaurus/Link'; | ||
| import SnptUidVerifyDebugTip from './_snpt-uid-verify-debug-tip.mdx'; | ||
|
|
||
| The following resources are available for publishers to implement UID2: | ||
|
|
||
|
|
@@ -27,6 +28,8 @@ For a detailed summary of web integration options, see [Publisher web integratio | |
| | 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 /> | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. _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).
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. sounds good |
||
|
|
||
| ### Mobile integrations | ||
|
|
||
| The following resources are available for publisher integrations supporting Android or iOS devices. | ||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| :::tip | ||
| You can use the [UID Verify Chrome extension](../ref-info/ref-uid-verify.md) to inspect and debug your UID2 web integration directly in Chrome. UID Verify supports the SDK for JavaScript, Prebid.js, and Google Secure Signals. | ||
| ::: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change note to prerequisites is better - Adding a Troubleshooting section at the bottom may be overlooked.