-
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
TCF2 denied 'fetchBids' for 'bidder' #12534
Comments
They do.
If OMGZero and AdForm are the same entity for the purposes of TCF, you can set the
What happened on nov. 26? Maybe some change in the CMP? |
Hi and thanks a lot - There hasnt been any changes in the CMP which is the odd part. As far as i know we have the aliasBidder in place, but it seems that is not working anymore for OMGZero (OMGZero is the same entity for purposes as Adform ), but i am not sure if the script needs to be changed somehow: pbjs.que.push(function () {
Do you think it would help if we rolled back to a prior version of Prebid? |
Do you think we can add reuse_gvl_id: true to make it work? pbjs.aliasBidder("adform", "omgzero", {reuse_gvl_id: true}); |
The option is called |
try |
Yes thanks - it worked thanks - we are back in business :) |
I am not sure if these warnings we get in the debug https://borsen.dk/?pbjs_debug=true is mere warnings or do they actually effect the stop of sending bid request to the bidder as being the error.
TCF2 denied 'fetchBids' for 'bidder.omgzero'
and
WARNING: Alias 'omgzero' will NOT re-use the GVL ID of the original adapter ('adform', gvlid: 50). Functionality that requires TCF consent may not work as expected.
We seem to have an issue with an alias bidder and error is we stopped sending bidrequest to the bidder.
I can see there is a few prior cases to this TCF2 denied 'fetchBids' for 'bidder' but i am not sure what the solution is to fix it?
We run prebid version: Prebid.js v9.16.0 and that was updated a month ago, but issue with not sending any bid request forbidder OMGZero started nov. 26-27.
The text was updated successfully, but these errors were encountered: