Use plausible analytics #546
Conversation
|
✔️ Deploy Preview for numpy-org ready! 🔨 Explore the source changes: 092e10d 🔍 Inspect the deploy log: https://app.netlify.com/sites/numpy-org/deploys/61faa3c52e319900080d0b25 😎 Browse the preview: https://deploy-preview-546--numpy-org.netlify.app/reports/lighthouse |
|
Thanks Jarrod! Could I get an invite? More importantly, I don't think it's working well, these numbers are definitely way too low, especially for the docs (should be O(100,000/day):
|
|
Two things: (1) we currently only track |
|
Hmm yeah, I'd expect many/most people to use AdBlock (how can you tolerance browsing without it?). Kind of a strange decision, because this has nothing to do with ads. Any way to change that behavior? Statistics should improve when we have Plausible integration in a release rather than only in For the record, this is what Cloudflare says for
|
|
We can host the plausible script on scientific-python.org, which would be unlikely to be blocked (https://plausible.io/docs/proxy/introduction#are-you-concerned-about-missing-data). I can set that up tomorrow. |
|
that sounds good, thanks |
|
Looks like we're already doing that, so I'll have to check why adblock picks it up; could be the naming of the script. |
|
EasyList contains: So will have to rewrite the JavaScript name. |
|
@jarrodmillman @stefanv First of all, thank you for finding an open source alternative to GA! As someone who used to spend a lot of time on this type of analytics, I would be curious to compare results from both platforms for the next 2-3 months. |
|
The analytics server had to be renamed to avoid uBlock, so now it is located at https://views.scientific-python.org. I also added a rewrite rule to serve the Javascript from a more innocuous location, and the hugo theme has been updated accordingly. This should take care of most adblock issues. |
jarrodmillman
force-pushed
the
plausible
branch
from
23cfb60 to
59bc1af
Compare
InessaPawson
left a comment
InessaPawson
left a comment
There was a problem hiding this comment.
The PR looks good to me. I’m just thinking, maybe, we should keep Google Analytics for another month or two. In the past, regardless of the analytics platform, it took at least a month for new accounts to get more reliable data on website traffic.
jarrodmillman
force-pushed
the
plausible
branch
from
59bc1af to
ea1f556
Compare
jarrodmillman
force-pushed
the
plausible
branch
from
ea1f556 to
092e10d
Compare
|
I added back google analytics. Since the theme no longer supports this, I added the necessary files to this repo (see #549). If this PR is merged, I will create an issue to make sure we don't forget to clean up this "temporary" fix when (or if) numpy.org decides to stop using google analytics. @InessaPawson Do you have access to the google analytics (I don't)? If not, do you know who does? |
|
I decided to merge this as it doesn't remove anything, everyone is interested in trying it out, and we need to merge it to compare it with google analytics. If this causes any issues, I will fix them or undo this change. To make sure we don't lose track, I created #550 where we can continue the discussion. |
Sounds great!
Yes, I do. @rgommers is another web team member who has it. |
|
@jarrodmillman May I have an invite to the numpy.org plausible account? |
4 participants
Trying plausible analytics. We are using this for scipy.org, docs.scipy.org, and scientific-python.org. If this PR is merged, you will be able to view the analytics for numpy.org at https://views.scientific-python.org/numpy.org. The page is currently private, so you will need to create a plausible account and let @stefanv or me know what address you registered.
I don't know who currently has access to the google analytics, but we should make sure whoever is currently monitoring the google analytics is OK with using plausible.