Plausible Analytics VS GoAccess

# Function to get Plausible Analytics timeseries data def get_plausible_timeseries_data(): # Calculate the date range for the last 90 days date_to = datetime.today().strftime('%Y-%m-%d') date_from = (datetime.today() - timedelta(days=90)).strftime('%Y-%m-%d') # Setting the metrics we want to look at metrics='visitors,pageviews' # Actually pulling the data we want url = f"https://plausible.io/api/v1/stats/timeseries?site_id={site_id}&period=custom&date={date_from},{date_to}&metrics={metrics}" headers = { "Authorization": f"Bearer {api_key}" } response = requests.get(url, headers=headers) data = response.json() # Putting the data into a dataframe we can use for analysis results = data['results'] df = pd.DataFrame(results) # Adjusting the date field so we can avoid future warnings and be more accurate df['date'] = pd.to_datetime(df['date']) return df

I’m building an Open Source multi-tenant email newsletter tool [1] and the project is entirely AGPLv3 licensed. I have automatic builds from the `main` branch that I deploy to the SaaS version while public Docker images are available only for tagged releases.

There is currently no difference between the self-hosted and the SaaS version, but I am planning two things:

1) An env variable `IS_SELF_HOSTED` which, when set to `false`, toggles certain features like billing (currently enabled via a separate env variable and theoretically available to self-hosters) and includes hard-coded stuff like a footer with links to the official project website and our ToS.

2) Add a registration feature for self-hosters who make a donation. I haven’t fully planned out this feature, but if a self-hosted instance is registered by a paid supporter, it will most likely remove a call for becoming a supporter (that is yet to be added) or give them a supporter badge.

Choosing the AGPLv3 has been partially inspired by Plausible’s very successful model [2]. They’re also using a `SELFHOST` env variable to differentiate between their "Enterprise Edition" and the "Community Edition" [3].

[1] https://www.keila.io

[2] https://plausible.io/blog/open-source-licenses

[3] https://github.com/plausible/analytics/blob/baa99652f612f50b...

I think a single Google Analytics alternative is pretty hard to pick considering that GA can be used to very much varying extents.

For simple and "detailed enough" insights, I enjoyed using Plausible (https://plausible.io/) in the past.

For more in depth analytics that give you a detailed view into your own product, PostHog.com seems to be by far the best and most popular option out there.

I could do the same exercise with Google Analytics and Google Tag Manager, but luckily I don't need to, since Plausible already did. A piece of advice, rip out Google Analytics and use Plausible instead. It first of all doesn't destroy your website, and secondly it doesn't violate the GDPR - So you can embed it on your site without having to warn your visitors about that they're being spied on by Google.

Also, currently we are using https://plausible.io/ for analytics. No other bugs.

I just swapped out Google Analytics with Plausible for AINIRO.IO. It’s only been a week, but so far I am super jazzed about it. First of all, Plausible doesn’t use cookies, so I can completely drop all cookie disclaimers and popups I had because of GDPR. Second of all, the site scores significantly better on load time. This results in a 10x better user experience for my website visitors, while making sure the website is still 100% conforming to GDPR laws.

No clue what you mean, browser cache might even clear itself without you doing anything manually. This thing makes no sense.

Nowhere ever did it say Tech Demo anywhere, not in the HN headline, not on the page itself. No, thanks. And even as a tech demo, there is nothing impressive going in. It is stores shit to local storage, I guess. Lol, I just looked this up, and it was in Firefox on 2009 already? WHAT? https://developer.mozilla.org/en-US/docs/Web/API/Window/loca... I never used it myself directly, but I remember reading about some API that kind of is the new version of cookies that can store more and better and I think that is it. 2009, I would swear what I think about was newer, maybe I am mixing something up, maybe not.

It has unnecessarily tracking from the comment above, not sure if it even sends all your notes to https://plausible.io, and I do not care. For me, this fails as a tech demo or whatever the fuck It's supposed to be. Sorry to not get all excited about everything posted here. In 2009 it for sure would ;)

If you already use Posthog, Web Analytics has been in Public Beta for quite some time.[1]

If I remember correctly, CloudFlare Analytics does not need you to register your domain with them. I personally feel keeping domain registration coupled with your DNS provider is not a good idea.

Plausible[2] has an Open Source self-hostable version but is not so updated in sync with their SaaS version.

Umami[3] is another simple, clean one. And, of course, as many have suggested, Matomo is the other well-established one. If you want to avoid maintaining a hosting routine, a lot do the hosting out of the box these days. PikaPods[4] was good when I tried and played around for a while.

1. https://posthog.com/docs/web-analytics

2. https://github.com/plausible/analytics

3. https://umami.is

4. https://www.pikapods.com

Plausible - Open Source Alternative to Google Analytics

There are many good, lightweight, and open-source alternatives to Google Analytics, such as Plausible, Matomo, Fathom, Simple Analytics, and so on. Many of these options are open-source, and can be self-hosted.

Not forgotten by any means but goaccess is nice and simple to use

https://goaccess.io/

If one wants server-side metrics with a little more info than the author's "hacky little script", there's always goaccess [1], which functions in broadly the same way. I even use it with Firebase Hosting-hosted sites via [2] (which I wrote).

[1] http://goaccess.io/

[2] https://github.com/Silicon-Ally/gcp-clf

> Just use GoAcces for fuck's sake.

GoAccess seems pretty cool and is probably a good task for the job, when you need something simple, thanks for recommending it: https://goaccess.io/

Even if you have analytics of some sort already in place, I think it'd probably still be a nice idea to run GoAccess on your server, behind some additional auth, so you can check up on how the web servers are performing.

That said, I'd still say that the analytics solutions out there, especially self-hostable ones like Matomo, are quite nice and can have both UIs that are very easy to interact with for the average person (e.g. filtering data by date range, or by page/view that was interacted with), as well as have a plethora of different datasets: https://matomo.org/features/

I think it can be useful to have a look at what sorts of devices are mostly being used to interact with your site, what operating systems and browsers are in use, how people navigate through the site, where do they enter the site from and how they find it, what the front end performance is like, or even how your e-commerce site is doing, at a glance, in addition to seeing how this changes over time.

People have also said good things about Plausible Analytics as well: https://plausible.io/

Maybe, if it's just local and need just information, maybe https://goaccess.io is an option.

I run goaccess on a cron job and have paired it with a MaxMind GeoIP database so that you can see where people are coming from etc.

https://goaccess.io/

file on GitHub.

There is small programm for linux https://goaccess.io/

I heard about https://goaccess.io/ (and even tested it) but first, nothing about tracing logs, and I think that the provided HTML dashboard isn't enough security-oriented for me but it's more about monitoring your customer volume... It does -partially- fit my case.

Loved AWStats! Still can be useful — but bots, client side caching, CDNs, and did I mention bots..? have made the data hard to rely on for much. A while ago I switched from AWStats to GoAccess (https://goaccess.io/) for this kind of thing. I prefer its interface, and it's way way faster to churn through big log files (C vs. Perl).

matomo and goatcounter are nice, but there are even solutions which don't need any extra CPU or any extra client request:

• https://goaccess.io/

• https://www.awstats.org/

Both of them are free/open-source.