-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Create an opt-in to Google Analytics Tracking on gohugo.io websites #106
Comments
I think there should be analytics. Having that data helps determine how people use the site, and thus can be useful for design. What's more, for the long-term viability of a an open source project, there should be a measure of users, and I think web traffic is a better measure than stars. However, I agree, opt-in is appropriate. We have that capability now (in the internal ga template). I haven't done that myself, being U.S.-centric, but happy to tackle it. |
Yes we had work done to this end in the GDPR update back in May 2018. Some kind of opt-in banner is needed so that when a user clicks: Yes ---> The GA script loads Also once a choice is made the banner shouldn't appear again for an X amount of time. Thanks for offering to tackle this. |
Perhaps rename the issue to reflect just opt-in. And that assumes others agree. |
Done. |
A quick easy-win which helps with protecting users privacy (and GDPR compliance) a bit would be to add IP address anonymization to the Google Analytics config for all users. Just add: |
This helps a bit with #106 (see comment #106 (comment))
This helps a bit with #106 (see comment #106 (comment))
I noticed that currently Google Analytics tracking is enabled across the board on all gohugo.io websites.
See: https://github.com/search?q=org%3Agohugoio+UA-7131036-4&type=Code
Please consider disabling it.
If you see value in tracking visitors then maybe there should be an opt-in or opt-out banner.
Personally I am not in favour of tracking visitors for an Open Source Project but then again this is not my call.
cc: @bep @budparr @digitalcraftsman @regisphilibert @kaushalmodi @moorereason
The text was updated successfully, but these errors were encountered: