Mostly from this list: https://privacyfocusedanalytics.info/. Our analysis is restricted to open source web analytics solutions that don’t use cookies.
- Ackee
- Backend: NodeJS, DB: Mongo
- No bounce rate
- MIT license
- Goatcounter
- Backend: Go, DB: SQL
- README mentions backend integration with server?
- EU Public License
- Kindmetrics
- Backend: Crystal, DB: Clickhouse
- Pretty full data
- MIT license
- Plausible
- Backend: Elixir, DB: Clickhouse for stats, postgres for general data
- Pretty full data
- AGPL License
- Pirsch
- Backend: Golang, DB: Postgres
- Pretty full data
- Seems like it requires your static site to be served by a Golang binary to properly get tracking data.
- AGPL License
- Counter.dev
- Backend: Golang, DB: Redis
- No bounce rate, no IPs, pretty limited
- Seems like it requires your static site to be served by a Golang binary to properly get tracking data.
- Also, AGPL license, which might mean you’d need to make that HTTP server open source
Some others: Matomo and Open Web Analytics, both PHP-based
Example of types of data collected (from Pirsch README):
- unique visitor count per day, path, and hour
- session count
- bounce rate
- view count
- growth (unique visitors, sessions, bounces, views, average session duration)
- average time on page
- average session duration
- languages
- operating system and browser (including versions)
- referrers
- countries
- platform
- screen size
These are only my findings after a cursory review of each tool's site and Github README. It may contain inaccurate or incomplete information, so I'd love feedback.
Another idea: convert this into a table or JSON file, maybe even contribute back to the privacy-focused-analytics repo.
Pirsch doesn't require "your static site to be served by a Golang binary to properly get tracking data". It's just that they have a backend integration as well, in case you don't want frontend integration (embedding scripts).