Open ian-lr opened 4 years ago
You're right, it goes under user, not user.data. Fixed.
As for timeline, we'll discuss in this week's Prebid Server committee meeting with the aim to mark as 'ready-for-dev'. Then anyone in the community could contribute the code to either code base.
Otherwise, this is not likely to be a high priority for any of the main project teams to build, so might take a while unless the Prebid Publisher committee makes a special request.
Hi @bretg ,
I see this was moved to "ready for dev" which I take it as good news :) To clarify what you said last time, now that it is "ready to dev" it means that either someone from community (for example me) does the dev and make a pull request, which will be reviewed and eventually validated and it is done. If nobody form community volounteer to do the code, then main projects teams could evaluate doing it, but it is unlikely to take priority compared to other projects already in scope.
Correct?
@jdelhommeau - correct. Your pull request would be welcome.
It is not currently possible to pass userIds (e.g. user.ext.eids) to Prebid Server via AMP. While cookie-based syncs are enabled with the
amp-iframe
, this limits the information available to bidders processing requests from AMP pages. Given the growing popularity of both userIds and AMP, this seems like a good opportunity to extend Prebid Server capability.Acceptance Criteria
amp-ad
.Note, as AMP-RTC does not support eids , userIDs will likely need to be added to the query string or through some other Prebid-specific interface. A potential strawman follows.