-
Notifications
You must be signed in to change notification settings - Fork 758
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
Keeping stored-request ID, targeting in floors #2292
Comments
Discussed in PBS committee. It was brought up that publishers may have input on this proposal. Here's a summary of the question for pubs: "would it be ok for Prebid Server to surface stored-request-ids as a stand-in for adunits?" A stored-request ID is a key used in app and AMP scenarios that indexes into a set of bidders and parameters. There's also been some interest in Prebid.js to utilize server-side lookup of bidders. Currently, the stored-request ID is not available to bid adapters and modules, but we're proposing that it would be useful in scenarios where there's not some other kind of adunit information like GPID or PB ad slot. Specifically, the first use case will be for floor optimization, but there could be other use cases for bid optimization. |
Discussed today with the publisher task force. There was no concern about sensitivity of having this value available to downstream code. The only comment was that it's possible, like gptSlot, storedRequest might not be granular enough to truly use as |
This was done with PBS-Java 1.101 |
Early feedback on the floor feature is that being able to target floors by adslot would help publisher performance. However, we don't often get the 'gptSlot' or 'pbAdSlot' in App and AMP scenarios.
But we do almost always get a storedrequest.id, which is a pretty good stand-in for adunit.
So I propose that Prebid Server should keep the storedrequest object instead of removing it. i.e. modules and adapters could look in
imp.ext.prebid.storedrequest.id
Alternately, we could push this burden to the contents of the stored request entry. i.e. push the problem to the host companies to remember to add this value to each DB entry. But since that value could get out of sync with reality, it's safer to have PBS keep the actual value used.
Either way, we'll then create a new 'adUnitCode' floors targeting to use this hunt path:
Finally, we'll deprecate the "pbAdSlot" floors targeting parameter -- adUnitCode is what used in client-side floors module.
The text was updated successfully, but these errors were encountered: