ADVADS / cookies and GDPR

Hi Paul,

Yes, something is going to change. Thanks to the many feedback, I already made a plan how this might work, including a mockup for the settings.

I would appreciate more feedback on the fallback behavior, though.
What should happen, if a cookie is not there? Let’s take a few scenarios:

1. ad popup should stay closed for 1 day; but without cookies, this would mean it pops up for that user with every page impression

2. a large Leaderboard ad should show up for visitors on large screens only. No cookies would mean it might also show on mobile and disturb the user experience.

2b: it is a small ad, enabled for small devices only. It would fit on desktop though

I am a huge fan of useful defaults. How should the use cases above behave out of the box if the feature is broken without a cookie?

It is not a rhetorical question, I would really appreciate a few opinions about it.

Thanks
Thomas

GDPR compliance is a multi-dimensional challenge. And, as always, Google is not making this easier for webmasters and publishers. The cookie case is one part, and Adsense (among other ad networks) consent is another.

Given your proposed scenarios, ad popup (assumes a site wide opt in within a lightbox effect) is abrupt, irritating, yet offers a most compliant use case. Every impression will attach until optin (optin incl. close box). Desktop/mobile supported. AMP support would be most helpful.

Given my interest is with scenario 1, scenario 2a is most similar to my version of scenario 1, so no need to codify 2a

As I see it, 2b is another variation of scenario 1, except the size / type of effect

Thus, advanced ads product question is (incl pro): how many options should be built for GDPR. Or does advanced ads work within another cookie notice framework?

And what about other scripts/cookies like Google Analytics? what framework should control what?

Ideally, a framework should include a cache smart geolocation option via _SERVER req var cfcountry.

If advanced ads pro included GDPR support, a leverage point for version of pro product.

> GDPR compliance is a multi-dimensional challenge

Couldn’t agree more. If it would be simple then I would have a solution already. I also don’t like to add additional consent messages to the frontend, if most webmasters already have them for Analytics, Cookies, etc., hence I opened the discussion here.

My scenarios were not solutions for a consent message. They were ad setups that could break if we don’t use cookies at all. I wanted to know how you would expect these cases to be handled if a user didn’t opt in to cookies yet.

> _SERVER req var cfcountry

What are you referring to with that?

Thanks
Thomas

Thanks for the important clarification. And with me, GDPR compliance had been occupying too much of my time recently. And the original support inquiry here was ADVADS cookies and I quickly concluded EU consent was primary.

The reason I brought up geolocation / cfcountry was user experience. If a fraction of traffic (EEA countries) needed special cookie handling, then at least, a fraction of visitors would be affected, minimizing risk and ad revenue.

For ADVADS, if no cookies, nor consent, then ADVADS features could be disabled / skipped. It really is a troubling situation.

I do not see how ADVADS can be separated from EU consent. They are tightly coupled.

Example of a tight coupling is MonsterInsights Pro. It now has a EU compliance addon to anonymize IP, forms handling, etc. It also will read cookie optin from Cookie Notice and CookieBot. My testing has shown this Google Analytics solution does not fully work because the initial request is still tracked (cookies set). And attempts to block/delay functional scripts has not worked for me.

Yes, pop up it’s not good, aslo for mobile, why don’t use banner like here :

https://ps.w.org/ad-blocking-advisor/assets/screenshot-1.png?rev=1282924

Make easy GDPR adsense implementation can explose your sell, if so, i hope you’ll lower the price, because if you’ll win a lot, with gdpr we’ll lose a lot with this stupid low ??

Thanks for all your feedback.

I will update this tutorial for a custom GDPR-notice and pushed our GDPR feature already into development. Practically, you could already use the Cookie condition in Pro do disable / enable a specific ad if a cookie from any consent tool is set / not set.

Thomas

Not sure I understand all of the above (pretty sure I don;t understand a lot of it). Since this is about GDPR, I will ask my question here.

At this moment I use a plugin with a cookie notice, but the advancedad-plugin, still loads. Is there an option in which it is possible to load the plugin (and thus the ads and stuff) AFTER the visitor has given their yes on cookies and stuff?

(Or maybe there is a plugin that loads a page before all of the rest that only allowes you to continue when you accept the cookies, and then the whole paga including the plugin for ads will load)

Hi Troel,

I am just preparing the next update (hopefully ready today) which comes with support for various consent-gathering plugins.

Best regards,
Thomas

PS: please open a new thread if you have more questions, so that the original other author does not get all the notifications.