Skip to content
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

UserId module OpenrRTB user.ext.eids #3790

Closed
pm-harshad-mane opened this issue Apr 29, 2019 · 4 comments
Closed

UserId module OpenrRTB user.ext.eids #3790

pm-harshad-mane opened this issue Apr 29, 2019 · 4 comments
Labels

Comments

@pm-harshad-mane
Copy link
Contributor

Type of issue

Suggestion: If UserId module passes information of supported partners in ORTB user.ext.eids format then it will be easier for ORTB supporting bidders like PubMatic to support all userId partners without making changes for every partner.

Description

ORTB.user.ext.eids has a provison to pass external user ids in ORTB, which can be easily supported. f UserId module passes information of supported userId partners in ORTB user.ext.eids format then it will be easier for ORTB supporting bidders like PubMatic to support all userId partners without making changes for every userId partner. Then an ORTB supporting bidder will simply copy the userId object into payload.user.ext.eids, this will avoid the repeating efforts for each provider getting added in userId object like TTD, DigiTrust and new ones coming.

Also rather than duplicating the userId object in every bid object can we send userId object along with validBids separately?

@bretg
Copy link
Collaborator

bretg commented Apr 30, 2019

@pm-harshad-mane - the current design places all IDs under user.ext.tpid (which stands for third party ID). This seems sufficient for you're asking -- just copy that object which could contain an array of IDs.

{
  "user": {
    "buyeruid": "...",
    "ext": {
         "tpid": [ 
          { 
            "source": "tdid",
           "uid": "11111"
        }
      ]
    }
  }
}

Also rather than duplicating the userId object in every bid object

Not understanding this -- the user object is outside the imp object.

@stale
Copy link

stale bot commented May 14, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label May 14, 2019
@stale stale bot closed this as completed May 21, 2019
@bretg
Copy link
Collaborator

bretg commented Jun 28, 2019

I believe we addressed this with #3900 and #3935

@pm-harshad-mane
Copy link
Contributor Author

We can ask User Id submodules to decide the format they want to use, if adapter wants to change the format then the adapter can make changes in adapter code.
Now, adapters like PubMatic, Rubicon, Pulsepoint need to create the OpenrRTB user.ext.eids object and need to make code changes to support each new userId submodule

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants