add docs for SharedID #1923
add docs for SharedID #1923
Conversation
|
@jdwieland8282 - I assume there will be updates to this after yesterday's conversation about adding 3rd party? |
| @@ -604,6 +605,70 @@ pbjs.setConfig({ | |||
| }); | |||
| {% endhighlight %} | |||
|
|
|||
| #### SharedID | |||
|
|
|||
| The SharedId UUID is a native Prebid identity service. SharedID has been designed to minimize its footprint on publishers pages, and optimized for the most common identity use case, interest based advertising. SharedID writes a simple 1st party ID in the publisher's domain. The first 48 bits represents the UUID’s birthdate, followed by 80 bits of random characters. Yes, a user will have a unique SharedID identity for each publisher they visit. However, since each UUID is available to all bidders who integrate with this identity service, we expect an open & transparent graph of users to emerge. Delegating this task to the community, and supporting it with this simple, efficient 1st party identity is beneficial to all parties participating in the RTB ecosystem. | |||
There was a problem hiding this comment.
The comma is not needed here:
SharedID has been designed to minimize its footprint on publishers pages, and optimized for the most common identity use case, interest based advertising.
Suggested minor edits:
Yes, a user will have a unique SharedID identity for each publisher they visit. However, since each UUID is available to all bidders who integrate with this identity service, we expect an open & transparent graph of users to emerge. Delegating this task to the community, and supporting it with this simple, efficient 1st party identity is beneficial to all parties participating in the RTB ecosystem.
should be:
A user will have a unique SharedID identity for each publisher they visit. Since each UUID is available to all bidders who integrate with this identity service we expect an open & transparent graph of users to emerge. Delegating this task to the community, and supporting it with this simple, efficient 1st party identity is beneficial to all parties participating in the RTB ecosystem.
There was a problem hiding this comment.
Sorry, didn't notice this, suggested edit:
SharedID has been designed to minimize its footprint on publishers pages and is optimized for the most common identity use case, interest-based advertising.
|
I'm curious...how is this any different than pubcommon? I also haven't seen any PRs in https://github.com/prebid/Prebid.js/pulls for this, I assume that's coming separately? |
| @@ -67,7 +68,7 @@ of sub-objects. The table below has the options that are common across ID system | |||
| {: .table .table-bordered .table-striped } | |||
| | Param under userSync.userIds[] | Scope | Type | Description | Example | | |||
| | --- | --- | --- | --- | --- | | |||
| | name | Required | String | May be: `"britepoolId"`, `"criteo"`, `"digitrust"`, `"id5id"`, `identityLink`, `"liveIntentId"`, `"parrableId"`, `"netId"`, `"pubCommonId"`, or `"unifiedId"` | `"unifiedId"` | | |||
| | name | Required | String | May be: `"britepoolId"`, `"criteo"`, `"digitrust"`, `"id5id"`, `identityLink`, `"liveIntentId"`, `"parrableId"`, `"netId"`, `"pubCommonId"`, `"SharedID"`, or `"unifiedId"` | `"unifiedId"` | | |||
There was a problem hiding this comment.
shouldn't this be "sharedId" (lowercase "s" and "d")?
| | name | Required | String | May be: `"britepoolId"`, `"criteo"`, `"digitrust"`, `"id5id"`, `identityLink`, `"liveIntentId"`, `"parrableId"`, `"netId"`, `"pubCommonId"`, `"SharedID"`, or `"unifiedId"` | `"unifiedId"` | | |
| | name | Required | String | May be: `"britepoolId"`, `"criteo"`, `"digitrust"`, `"id5id"`, `identityLink`, `"liveIntentId"`, `"parrableId"`, `"netId"`, `"pubCommonId"`, `"sharedId"`, or `"unifiedId"` | `"unifiedId"` | |
|
closing in place of #2031 |
No description provided.