Forum Moderators: martinibuster
What does EU GDPR means for Adsense?
Looks like I will have to buy the expensive plan of CookiebotA basic cookie notification script shouldn't cost anything, there are lots out there. You can then tweak it to reflect your own preferences. I suggest moving the script and the css file over to your own server to make it faster and to safeguard against 3rd party downtime.
but does anyone know if it's mandatory to anonymize IPs in Analytics?Google sent an email notifying Analytics users that they are GDPR safe. I don't use GA but I think there's a setting to anonymize IPs. If so, I would certainly do so... then you know you're safe.
It's so goofy that publishers would be expected to provide a site-based "cookie opt out" functionality when that very functionality already exists in every single web browser worth its salt.
Perhaps a link to a tutorial on how to use their own software would suffice? It would in any sane world. But then, that's the GDPR in a nutshell.
fretfull: " Also considering that I'm thinking about giving up Adsense altogether since it's not worth the hassle, why do I even care?"
Why does the policy require consent for cookies, even if used for purposes other than personalization, such as ads measurement?
Cookies or mobile identifiers are used to support personalized and non-personalized ads served by Google to combat fraud and abuse, frequency capping, and aggregated ad reporting. Our policy also requires consent to the use of cookies or mobile identifiers for users in countries in which the EU ePrivacy Directive’s cookie provisions apply. We understand that regulatory guidance on ePrivacy laws is not consistent across Europe, which is why our policy calls for consent to cookies or mobile identifiers “where legally required.”
What choices do I need to present to my users?
Google’s policy does not dictate the choices that should be offered to users. Some publishers may want to present a choice between personalized and non-personalized ads; others may wish to present different choices to their users.
Why do we need consent to ads measurement — isn’t that legitimate interests?
Google uses cookies or mobile ad identifiers to support ads measurement. Existing ePrivacy laws require consent for such uses, for users in countries where local law requires such consent. Accordingly, our policy requires consent for ads personalization and ads measurement where applicable, even if ads measurement can, for GDPR purposes, be supported under a controller’s legitimate interest.
Do I need the consent before the tags fire or can the consent come afterwards?
Our understanding of GDPR requirements is that consent for personalized ads should be obtained before Google’s tags are fired on your pages. The ePrivacy Directive requires consent for the placement of, or access to, cookies but the regulatory guidance on ePrivacy laws is not consistent across Europe, which is why our policy calls for consent to cookies or mobile identifiers “where legally required.” Some regulators have issued guidance specifically requiring user action prior to setting of cookies, while others have permitted consent concurrent with the setting of cookies.
Regulatory guidance indicates that the GDPR will affect the consent required for cookies under the ePrivacy Directive, but there isn’t clear guidance on how these laws will interact. We await more guidance from regulators and will update our support materials accordingly. In the meantime, for those customers not seeking consent to personalized ads, we will continue to apply national standards for cookie consent, and we are not requiring changes to current cookie consent implementations.
We are also developing a consent solution for DFP and AdSense that will become available more widely soon.
You require to obtain your users' consent to the use of cookie
Turning off interest-based ads inside Adsense + telling people by using the site they're accepting cookies + telling them how they can disable/delete cookies stored in their browser = more than enough.