You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The alwaysUseBid setting appears to be broken. Instead of always sending the bid to the ad server, it does nothing. I think this functionality was accidentally removed in the prebid.js refactoring prior to 0.9.0: 2ad8150#diff-f8e049a1b6d4f9aa96fca41d2f7aa11dL286
To reproduce, add a custom bidder setting to pbjs.bidderSettings in pbjs_example_gpt.html, such as:
When brightcom responds with a bid, we'd expect the custom_test_key key to be part of the targeting object when you call pbjs.getAdserverTargeting(). However, it is not.
If you redo this test on the commit for the 0.8.1 release, custom_test_key is part of the targeting as expected.
I'm working on a fix for this and should have a PR soon.
The text was updated successfully, but these errors were encountered:
* Add test for `getAdserverTargeting`.
* Add test for `getBidLandscapeTargeting`.
* Move winning bid targeting result to fixtures.
* Add test for ad server targeting when bid landscape reporting is on.
* Add function to get targeting for bids with `alwaysUseBid` set to `true`.
* Fix unsetting `enableSendAllBids`.
* Update ad server targeting to include custom keys of `alwaysUseBid` bids.
* Move `getAdserverTargeting` tests to test against public API.
* Move `alwaysUseBid` targeting test to module level.
* Add checks for ad server targeting keys.
* Remove unneeded exports.
* Remove public function to disable sendAllBids.
* style updates (@protonate)
The
alwaysUseBid
setting appears to be broken. Instead of always sending the bid to the ad server, it does nothing. I think this functionality was accidentally removed in the prebid.js refactoring prior to 0.9.0: 2ad8150#diff-f8e049a1b6d4f9aa96fca41d2f7aa11dL286To reproduce, add a custom bidder setting to
pbjs.bidderSettings
inpbjs_example_gpt.html
, such as:When brightcom responds with a bid, we'd expect the
custom_test_key
key to be part of the targeting object when you callpbjs.getAdserverTargeting()
. However, it is not.If you redo this test on the commit for the 0.8.1 release,
custom_test_key
is part of the targeting as expected.I'm working on a fix for this and should have a PR soon.
The text was updated successfully, but these errors were encountered: