-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
GA Plugin and GDPR #4976
Comments
To know if the user is browsing from EU, we'd have to use an IP Geolocation service. I don't know any that's free. |
No @sebastienfi I don't think this is Gatsby's responsibility at all. This must be left at the owner's choice. Gatsby should just give control to the owner whether the plugin is enabled or not and allow to enable it at run time, rather than built time. I could start by adding an enabled/disabled flag on the plugin. How does that sound? |
We use a specific CDN for Europe and another set of CDN for the rest of the world. Is what you propose to integrate an option in the plugin to activate the check on whether Send your PR, and I'm happy to review :) It would be welcome to have an example site like |
Btw. using google analytics is OK (even in Europe) if you anonymize IPs and also disable cross session (bad) cookies. With this config tracking should be fine:
Ofc. you lose cross-session user tracking feature of analytics, but it might be good for many developers who jsut want to do basic tracking and don't care about GDPR. Currently plugin allows to anonymize IP, but doesn't allow (cannot see option) to enable session only cookies - As I understand (don't take as lawyer advice) whole GDPR (no consent) compliant code might be:
|
@jurosh Thanks, that's very helpful! Looks like cokies_expires is now also available as |
Hi, Maybe it can help others facing the same difficulties. First, I imported tarteaucitron into the scripts folder of my static folder.
}} And that's it. Hope it can help |
I published this a couple months back for GDPR compliance: Cookiehub looked way nicer than tarteaucitron. |
Yes, it does, but it's not as customizable as Tarteaucitron :(
And I needed some services other than GA, that Cookiehub doesn't support! But I tried your plugin when I started working on my project and it worked as expected :)
Le 16/01/2019 à 14:43, Michele Memoli a écrit :
… I published this a couple months back for GDPR compliance:
https://www.gatsbyjs.org/packages/gatsby-plugin-cookiehub/
Cookiehub looked way nicer than tarteaucitron.
—
You are receiving this because you commented.
Reply to this email directly, [view it on GitHub](#4976 (comment)), or [mute the thread](https://github.com/notifications/unsubscribe-auth/AGf4XQVVVwJr2teYVYLSCiZPeWcJfUtFks5vDyyTgaJpZM4TUg6_).
|
Hiya! This issue has gone quiet. Spooky quiet. 👻 We get a lot of issues, so we currently close issues after 30 days of inactivity. It’s been at least 20 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open! Thanks for being a part of the Gatsby community! 💪💜 |
Hey again! It’s been 30 days since anything happened on this issue, so our friendly neighborhood robot (that’s me!) is going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error, I’m Thanks again for being part of the Gatsby community! |
I can't seem to find the widget ID on cookie hub, would you mind telling me where to look for it? |
Description
Google's new EU user consent policy states that Google's products, such as Google Analytics must have user's consent in order to work in a page. That means that a website must take the user's consent and then enable the Google Analytics plugin. With that in mind, I would like to see some sort of a toggle to enable/disable the Gatsby Google Analytics plugin on demand.
Expected result
I would like to be able to have Google Analytics plugin disabled by default. Then ask the user's consent and only then enable it.
Here are some references on GA tracking code:
The text was updated successfully, but these errors were encountered: