-
-
Notifications
You must be signed in to change notification settings - Fork 106
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
Sunsetting the Google Analytics services #550
Comments
I don't think there's a real decision point here between the two. We know we want privacy-friendly data from Plausible, we just don't want a gap in data. As soon as Plausible is working well and we have similar quality data to what we now get from Google Analytics, then we can drop Google Analytics. |
Deprecating Google Analytics in numpy.org as per discussion in #550.
Thanks for finishing this @jarrodmillman! Now that we have switched to only Plausible, it would be good to post the current data of both Google Analytics and Plausible, so we have a data point showing how the visitor numbers compare. That way we can normalize future numbers, otherwise we're probably going to see them as a drop in visitor numbers. Here is the Google Analytics data as of right now: Now ~150,000 users/month vs. ~100,000 a year and a half ago (see #269 (comment)) seems about right. As noted in that discussion, the Cloudflare numbers are way higher, more like ~2,000,000/month. |
@jarrodmillman can you post what you're seeing from Plausible? |
Per the discussion in #546, we are temporarily trying both google analytics and plausible. Once we decide whether to use google analytics or plausible, we will need to either:
Remove google analytics (see #549)
Remove the following files
as well as this line
in
config.yaml.in
.Remove plausible analytics (see #546)
Remove
from
config.yaml.in
andfrom
README.md
.Why use plausible?
The theme will only support plausible going forward, so using it will involve less customization for numpy.org. For more information, see https://plausible.io/vs-google-analytics.
The text was updated successfully, but these errors were encountered: