-
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
Multiple Video adUnit requests result in the same identical winner tag (AppNexus module) #2282
Comments
@paooolino |
Hello Matt, it's my pleasure. |
well in the standard banner workflow when we set keys we mark the bids as used but that doesn't work great for video because we don't get a callback letting us know the bid won. |
One more thing that's not clear to me. Why does it work if the adunit code is different? When I remove the adunit and add a new one with the same code, it shouldn't be enough? |
@paooolino I guess that happens because while the adUnit is destroyed, the associated bids are not. So when you add back the adunit with the same code, the bids are associated with it again. |
Hi @mkendall07 , We're currently running into the same issue where we would like to mark a video advertisement as "consumed". We’re using the IMA3 SDK and can string up the “consumed”-call to one of the events fired. Regarding “Have you thought about what that API would look like?”, a global-scoped function to mark an video-advertisement would do. We can extract the hb_cache_id or hb_adid from the original call to DFP, so something like this:
What do you think? P.S. We don't know if the video-ad actually played (it might have lost to another campaign). If we want that, then we’ll need something more elaborate. We could get the cache_id during the vast-parsing process (check if a call is made to prebid-cache) or afterwards by swapping out the vast-tag with a vpaid script (player within a player style). |
@mkendall07 @jaiminpanchal27 So current TL;DR; There needs to be some way to flag a video-bid as used on pages which run multiple videos (ex. Single page applications). Bid-cache breaking options:
Bid-cache maintaining options:
I think both of these are outside of the current scope of Prebid. I might be able to help the development, but I need to know which solutions are possible and preferred. |
@mkendall07 Sure thing, we’re actually already running a test with #1. First result suggests it fixes our issues (poki@36843ac). I’ll read the contribution guide and send a pull-request somewhere in the upcoming days. |
@mkendall07 Here you go, see if you like it. |
Merged #2777 |
Type of issue
Bug?
Description
Consecutive requests issued to prebid.js Video results in the same identical VAST winner tag with AppNexus. The adServer consequently does not compute a lot of valid impressions.
The problem was NOT happening in v.1.0.0 or before. I verified it happens with 1.3.0, 1.4.0, 1.5.0.
The workaround I found consists of changing the videoAdUnit code appending a progressive integer to any new request.
Steps to reproduce
Test page
http://sftnetwork.com/prebid-same-tag-proof/index.html
workaround: http://sftnetwork.com/prebid-same-tag-proof/index-workaround.html
Expected results
the "s=" parameter should be different for each request.
Actual results
the prebid-1.5.0 version results in the same tag with the same "s=" parameter multiple times.
Platform details
Windows 10, Chrome 64.
prebid version 1.5.0 (but also tested with 1.3.0, 1.4.0), AppNexus module
Other information
none
The text was updated successfully, but these errors were encountered: