Skip to content
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

Migrate off of Google Analytics #3

Closed
amanahuja opened this issue Jun 25, 2021 · 7 comments
Closed

Migrate off of Google Analytics #3

amanahuja opened this issue Jun 25, 2021 · 7 comments
Assignees
Labels
feature new feature request

Comments

@amanahuja
Copy link
Owner

I'd like to move away from Google Analytics for web privacy and tracking reasons.

While I'm aware of alternatives like Matomo, I haven't yet investigated these options. If you are knowledgeable about these things, your input would be welcome.

@amanahuja amanahuja added the feature new feature request label Jun 25, 2021
@amanahuja amanahuja self-assigned this Jun 25, 2021
@amanahuja
Copy link
Owner Author

amanahuja commented Feb 11, 2022

My criteria at the moment:

  • no cookies (required)
  • privacy forward (required)
  • GDPR /CCPA, PERCe... compliant (required)
  • open source (required)
  • data portability (required)
  • ability to manage at least 3 domains (required)
  • features required: basic counter of visits, bounce rate
  • features nice-to-have: info about browser, screen size, links followed

Expected traffic for my purposes is probably like... 100 visits per month. I should be able to find an option that is free or close to free, although I'm happy to pay/donate to support. I don't mind technical work to set things up, I guess, but a hosted solution would be nice so I don't have to worry about maintenance, updates, etc.

Here are two useful lists

Looking through that list for hosted solutions that have free tiers, then:

  • splitbee
  • beampipe
  • micro-analytics
  • counter.dev
  • Swetrix

@amanahuja
Copy link
Owner Author

It's apparent that some of my naive "nice to have" features are not privacy-respecting. For example, many of the privacy-forward analytics software track only the landing page and not all the pages loaded. This is better for the user. Thus "top pages" are not available, but "top landing pages" are.

Cookie-less analytics has limitations, and I'm fine with that.

counter.dev's documentation states:

Counting unique users is achieved with a combination of relying on sessionStorage facilities, the browser's cache mechanism and inspecting the referrer. Using this technique considerably reduces the complexity and load on the server while improving data privacy at the cost of knowing less about users. We can't and don't want to be able to connect single page views to an user identity.

@louispotok
Copy link

I use self-hosted Matomo on a digital ocean droplet for louispotok.com -- I believe it meets all your criteria except cookies.

This blog post with a setup for basic server-side analytics may also be useful.

@amanahuja
Copy link
Owner Author

I've setup Matomo as a new resource on my utility server (pafnuty.com), and I'm testing out the integration. Should be good to go soon.

@amanahuja
Copy link
Owner Author

I had some problems with the js tracker, but now resolved. For posterity: https://forum.yunohost.org/t/matomo-tracker-redirects-fail/20576/4

Marking this as done.

@amanahuja
Copy link
Owner Author

Confirmed tracking is working after some months.

@louispotok
Copy link

FWIW I have been using plausible.io for work stuff and I quite like it -- paid and hosted, but very privacy conscious and the design is a lot simpler/nicer than matomo, which has a bunch of stuff I never use

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature new feature request
Projects
Development

No branches or pull requests

2 participants