Bugfix: returnCreative handling by cache type - #4898
Open
MichaelErmer wants to merge 3 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem observed
We observed successful banner bids that could not render after moving traffic to PBS-Go. The bidder raw OpenRTB response contained adm, but the final PBS-Go response did not. At the same time:
This made the auction look successful in GAM, but without adm there was no creative to render. As a result, impression trackers contained in the creative were never executed and the bidders recorded no impressions.
The request did not ask PBS to suppress banner creative. It only configured ext.prebid.cache.vastxml.returnCreative=false, which should affect cached VAST for video bids.
Root cause
PBS-Go collapsed cache.bids.returnCreative and cache.vastxml.returnCreative into one global boolean before building the response. When vastxml.returnCreative was false, makeBid therefore cleared adm for every returned bid, including banners.
This also made it impossible to vary returnCreative by media type as described in #2584.
Expected behavior and PBS-Java parity
PBS-Java keeps the two cache targets independent when deciding whether to include adm:
This means the observed request keeps banner adm while still removing video adm. Combined bids and vastxml settings now follow the same precedence as PBS-Java as well.
The corresponding PBS-Java behavior is implemented in BidResponseCreator and covered by its cache functional tests.
Fix
Fixes #2584
Testing