-
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
Criteo bid adapter: Bump fastbid version #10696
Conversation
Just wanted to ask what is a reason for this bid adapter to have external .js loaded. After checking many other bid adapters I haven't found any other DSP bidAdapter using this technology. If prebid.js is generaly running on a fair "max CPM wins policy" this could also violate some Prebid policy / or use internal prebid.js calls hidden to all other adapters? |
hi @DemekaParis Thanks for raising this, you will want to follow progress on #10653 that will address your very concern around loading external files. This feature is legacy design and allowed Criteo to run some features not available in Prebid.js by the time (Criteo ID Module, timeout stats and other minor things). Criteo team is confident and committed to address this with Prebid 9.0 or even before. Please also notice that today it is already possible to optout from this feature. Allan |
We're not bumping fastbid any longer |
@DemekaParis see also #4031 (comment) and #5804 as useful background. |
Reopened as the Fastbid changes are minor bug fixes that I reviewed, awaiting board approval before this merge. |
I believe making the repository at https://github.com/Prebid-org/prebid-js-external-js-criteo/tree/master/dist public would be mutually beneficial at this time, especially until the anticipated PR for prebid 9 is implemented. If there are no proprietary elements involved, I see no issue with this approach. Alternatively, consider presenting it as an opt-in feature for publishers, as I am confident you can effectively communicate the advantages directly to them. I would like to express my concern about the current opt-out mechanism, as it seems impractical. Referring to Prebid.js/modules/criteoBidAdapter.js Line 27 in 61d299e
Also this opt-out/opt-in should be written in https://docs.prebid.org/dev-docs/bidders/criteo.html where there is no mention of opt-out. I appreciate your consideration of these points and believe addressing them would contribute to a smoother user experience. |
hi @DemekaParis these instructions are build-time instructions. A runtime optout is also possible, it is explained on our integration guides but we will also document on https://docs.prebid.org/dev-docs/bidders/criteo.html 👍
|
Ad discussed with the criteo team, this bug fix is the final bump |
Type of change
Description of change
Bump fast bid version to ensure the latest fix is available