-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Comments
@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.
Not understanding this -- the user object is outside the imp object. |
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. |
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. |
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?
The text was updated successfully, but these errors were encountered: