It is self hosted, has support for desktop apps, mobile apps and web apps at the same time.
[1] https://count.ly
[2] https://marketplace.digitalocean.com/apps/countly-analytics
171–180 of 320 posts
It is self hosted, has support for desktop apps, mobile apps and web apps at the same time.
[1] https://count.ly
[2] https://marketplace.digitalocean.com/apps/countly-analytics
I still can't see any solid reasons why a site owner would not use GA. Other products: - Objectively lack features - Potentially incur extra costs in money/time - May be a small barrier in m&a - May carry additional risks/attack vectors if self hosted Trying to ween off big tech is commendable, but likely detrimental to a business. Relatively high risk, low reward. I'm happy to have my mind changed. I can see a case…
GDPR compliance. GDPR is the European privacy law. It protects European citizens so it applies not only to European companies but any company that does business in Europe (having offices or advertising/selling there). Google does not give much assurance regarding their GDPR compliance... their text on that subject is mostly CYA and then they make it your responsibility to decide how to use it in compliance (if at all…
The GDPR does not discriminate based on citizenship.
It applies if the organisation providing the service is in the EU/EEA* OR if the user of the service is in the EU/EEA* (to the extent that the data reference their activity in the EU/EEA).
And the UK, but thanks to brexit there's a parallel UK GDPR in place so... take that in to account.
In my blog I started using Netlify's analytics which are server based and cost $9 per month (up to a number of views) and I gotta say they are extremely basic and lackluster. I paid for the subscription for one month but I don't think I will keep on paying. Edit: Also it doesn't seem to be tracking referrers correctly.
Yes, Netlify Analytics are bad. Try Fathom.
I moved to Netlify analytics from Goat counter because I liked the idea of having server side analytics, but at $9 per month these are extremely overpriced.
I think I will just go back to Goat counter.
Earlier quoted context omitted.
Server side Analytics are far from reliable. Go and try Netlify, then you’ll see how unreliable they really are. For us nerds, we can always block things using DNS level blocking but Fathom’s custom domain feature has done really well for the majority: https://usefathom.com/blog/custom-domains-embed-code
Good adblockers do DNS lookup to see if subdomain points to tracking server anyway. Only completely self-hosted (your domain, your tracking server) solutions are resilient to adblocking
I'd like to ditch google analytics for a new small side project I'm building. I live in a small country in Europe and for me the most important feature of these alternatives is the cookieless tracking and the lightweight scripts. However, the pricing is too steep for a project that won't gain more than thousands users. Fathom analytics and simple analytics cost ~100$/year. Plausible costs ~50$ I really liked and almo…
https://github.com/usefathom/fathom https://github.com/plausible/analytics
Earlier quoted context omitted.
I find time spent on page is a great way to measure performance of redesigns on page. There are numerous actionable points.
Unless your page is google.com, where more time spent on page means the experience is worse, not better.
Countly [1] is another open source alternative to Google Analytics - suggest you try it on Digital Ocean [2] or deploy on your own [3]. It is self hosted, has support for desktop apps, mobile apps and web apps at the same time. [1] https://count.ly [2] https://marketplace.digitalocean.com/apps/countly-analytics [3] https://github.com/countly/countly-server
I use Ackee, also a simple and open source alternative https://ackee.electerious.com/
There's no UI for my signals application, but it should give me raw access to all the GA metrics people typically look for (pages, referrers, user agents, etc). Storage could be pain point. Compute might also turn out to be, but if that ever becomes a problem, then I'll probably have much more to think about...
What am I missing here?
I have my own self-hosted Matomo instance [1]. Via Docker & docker-compose it's quite easy to install and keep up to date and Matomo is open source, well maintained, very well behaved and pretty hands off. And I configured it on my websites with cookies turned off [2] and with IP anonymization [3]. In such an instance you don't need consent, or even a cookie banner, because you're not dropping cookies, or collecting…