However
That's the keyword. So no one can have a definitive answer to this question. And no one is taking risks.
All this will remain blur until the publication of the ePrivacy Regulation [
webmasterworld.com...] (the evolution of the EU cookie law), which "should" (hmm) discharge web publisher for cookie consent, and make web browsers in charge of handling this.
(Also, in the upcoming ePrivacy regulation, they say "The proposal also clarifies that no consent is needed for non-privacy-intrusive cookies improving internet experience", which sounds like what the cookie for non-personalized ads is doing).
Now, to "try" to answer your question, and as I said several time in the dedicated topic [
webmasterworld.com...] . I "understand", that non-personalized ads produce a non-tracking cookie, with no personal information attached. "If" this is right, then it's no longer related to the GDPR, but still addressed by the EU Cookie Law.
The EU Cookie Law requires to obtain the consent of a user BEFORE dropping a cookie (it's unclear which kind of cookie really requires this or not!) . But 99.9% of sites are not obtaining the consent before a cookie is written. Web publishers adopted "themselves" an approach where displaying a banner, to inform the user about cookie, with links to information, would be enough. Legally it's not, but since everybody is doing this... (also, legally, it's the one dropping the cookie which has to obtain the consent, so in the case of Adsense, this is supposedly Adsense which has to obtain this consent, and not the web site publisher).
That being said, what I am doing is :
- non-personalized ads for EU visitors
- sticky cookie banner, information that third parts are using cookies, with link to my privacy policy page, where where I explain who does what, and how to control cookies
- on this banner, I have two choices, accept or refuse. If a user click refuse, I disable ads , and replace them with self promotional content. (this is not a modal banner, so most of people ignore it and do not make choice).
I think this "should" be fine, until the moment all this will be handled by web browsers themselves.