WEB/DOC: use Plausible for analytics (using Scientific Python server) #53984
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stefanv
reviewed
Jul 3, 2023
| gtag('js', new Date()); | ||
| gtag('config', 'G-5RE31C1RNW'); | ||
| </script> | ||
| <script defer data-domain="pandas.pydata.org" src="https://views.scientific-python.org/js/script.js"></script> |
There was a problem hiding this comment.
Is it necessary to have this snippet in addition to the theme's analytics?
There was a problem hiding this comment.
Yes, this is for the website pages, which uses a different tool/theme/layout compared to the docs (which uses pydata-sphinx-theme)
lithomas1
approved these changes
Jul 8, 2023
There was a problem hiding this comment.
This LGTM but I would defer to @datapythonista for final review.
|
This pull request is stale because it has been open for thirty days with no activity. Please update and respond to this comment if you're still interested in working on this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This proposes to switch from our current usage of Google Analytics to Plausible.
(currently it fully switches, but could also first add it in addition so we have both for some time)
Plausible is a privacy-friendly and open source alternative for Google Analytics (https://plausible.io/).
The server we are using here is a self-hosted one by the Scientific Python team (using one from plausible.io costs some money). But the disclaimer I got from @stefanv is that it's a small server without professional sysadmin support and is currently not automatically backed up (but we could set up a cron job to query the data and dump them somewhere). I think, given that this is also being used by other projects (numpy, scipy, scikit-learn, ..), that this is fine, and if there come up problems, we will be able to look for solutions together.
The main advantage is that privacy-friendly (not collecting data for a big corporation ..). I think our current usage of Google Analytics is actually not correct (I assume we should have a pop-up to ask for permission).
The consequence of that is that Plausible cannot track "unique visitors" over time (only per day), for example per month (https://plausible.io/data-policy#how-we-count-unique-users-without-cookies).