3 ms·
The author is wrong. You just do what google does and ask for consent before providing access to the site. The user doesn’t need to log in to consent. Once con
by ec109685 9y ago
The author is wrong.
You just do what google does and ask for consent before providing access to the site. The user doesn’t need to log in to consent. Once consented, the site can set a cookie. Then that user becomes part of your “Full interaction users” bucket.
- r00fus 9y agoWhat if they don't consent? Will you have not do analytics for that user? You can't block that user as per GDPR if they are simply answering no to the consent.
- ec109685 9y agoYes you can block. See the YouTube example. As long as you have a valid reason to collect the data for the benefit of the user experience, you can make that a requirement to use the site.
- mgiannopoulos 9y agoYou can argue that GA is critical to the existence of the site, so you are allowed to block non-consenting users. I hope anyway :)
- mgiannopoulos 9y agoSounds good to me but that would be only needed if you’re sending personal data (like usernames) to Google Analytics, right? If you’re anonymising IP and have no personal data in your URLs, there is no need for consent for GA tracking I think.
- ec109685 9y agoIt doesn’t have to be personally identifying info to qualify. If you are storing data on behalf of the user, you have to get consent from the user.
- mgiannopoulos 9y agoWhich pages were visited is not information stored on behalf of the user though. It is information stored for business analysis.
- ec109685 9y agoWhich is used to enhance the product, so it's okay to collect and require for consent.
- PeterStuer 9y agoWhat if the user doesn't consent? As I understand it you can make no difference in your service to those that do not 'opt-in' to your tracking.