-
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
Prebid.js sends wrong gdpr flags to prebid-server #6414
Comments
As an example of a typical response one can see on wsj.com
@wqi1972 as potentially affected |
Nice analysis @rsnigel - care to open a PR to fix? |
Linking the blame, @jaiminpanchal27 added this to avoid empty string errors #2766 #2530 introduced |
closing with merge of #6429 |
Fyi @rsnigel usersync if ambiguous default is changing with prebid/prebid-server#1786 @SyntaxNode do you agree with OPs concern around legality? |
prebid/prebid-server#1786 is now on hold as the legality is being called into question. One one hand, all publishers impacted by GDPR should be sending GDPR signals by now, and seems that small publishers with no EU presence should not be forced to send gdpr signals to confirm that the gdpr does not apply. On the other hand, not knowing if a user is in the EU does not absolve us from following the GDPR if the user actually is in the EU. |
Prebid.js is interpreting
__tcfapi
incorrect and sending wrong flags to prebid-server when GDPR does not apply.When GDPR applies, the handling is correct.
If GDPR does not apply, https://github.com/prebid/Prebid.js/blob/master/modules/prebidServerBidAdapter/index.js#L192 checks for
if (typeof gdprConsent.consentString !== 'undefined')
which is incorrect.A certified IAB CMP does not need to return a valid
tcString
outside of GDPR. Typical CMP's only returngdprApplies = false
.Example of typical CMP response:
If there is a
__tcfapi
available, the linepayload.gdpr = (gdprConsent.gdprApplies) ? 1 : 0;
is enough and the if should be removed.What is the result of this bug. Prebid-server does not get a gdpr=0 flag and if
usersync_if_ambiguous=false
, prebid-server rejects all user syncs which breaks prebid-server completely outside of gdpr. The workaround is to setusersync_if_ambiguous=true
which is questionable from a legal point of view.The text was updated successfully, but these errors were encountered: