-
Notifications
You must be signed in to change notification settings - Fork 6
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
Privacy site measurements #254
Comments
add docs gbif/jekyll-hp-base-theme@6909d3a |
There is some confusion in the GBIF North America region over whether or not Google Analytics are permissible for portals that are hosted on GBIF servers in Denmark. In #16 it seems like Google analytics might be acceptable under certain circumstances, but I had heard from Abby Benson that this was not the case. Since #16 is a bit old, and both of these issues are still open, would you mind trying to summarize where we stand with using Google Analytics on hosted portals? Tagging @dbloom for awareness. |
I'll defer to @MattBlissett and @kcopas on that. |
The issues were with Google Universal Analytics. The changes and customization available through Google Analytics 4 appear* to enable it to be run in compliance in Denmark, provided that site owner:
|
Thanks @kcopas! At the end of the day, GA would be a convenience for us to learn about our portal users, but I want to ensure that I don't put GBIF in a bad light as the host of our portal. I will look into this a bit more. If I decide to implement GA, I will share my plan before I do anything to make sure I haven't misinterpreted anything. |
Hi @sformel-usgs |
Thanks @timrobertson100. I had explored that option, and Plausible seems like a good service, but it's a bit more complicated than that on my end. USGS uses GA and isn't willing to pay for Plausible as a new service. I'm going to see what I can do with GA. |
Add instructions for using e.g. Plausible
And possible inform participants abou the new EU laws that impact the use of e.g. Google Analytics
The text was updated successfully, but these errors were encountered: