Live data from Hacker News

Using analytics on my website

azan-n.com

11–20 of 61 posts

Re: Using analytics on my website

#11

[flagged]

> Just use GoAcces for fuck's sake. You don't need more than access logs. What are you going to do with that analytics data anyway? How much can you even trust that it's real and not bots that are getting better every day?

I can provide you a very simple example. You have a blog, with articles. On a multi-thousand word article, you know that traffic that spent You get the point, I hope. Access logs are useless for this kind of basic information.

Another very good example - there was a blog from someone involved in the UK GDS initiative, that described the case of a woman sitting with a handheld console in the waiting room of a government office. Initially you think she's just playing, but peeking over her shoulder, you see she's filling an application for unemployment. The browser on the handheld is horribly outdated, but she probably doesn't have another choice. Therefore knowing your audience, and adapting to it is crucial. From them:

> people now access GOV.UK in many different ways - 16,500 visits came from games consoles in the last month (Xboxes/PlayStations/Nintendos) - including 65 sessions from a handheld Nintendo 3DS (this is in 2015 https://gds.blog.gov.uk/2015/11/20/2-billion-and-counting/)

It entirely depends on what your website is doing if you need analytics or not. But a lot of orgs and people actually do, and can and should make use of them.

Re: Using analytics on my website

#12
post #8

I went the other way entirely: no analytics, 100% static site, no logging. It's super fast and it takes away one more thing to monitor and keep up, it's not as if I'm running an e-commerce site.

Good idea - one "analytic" is to put your email on the site, and see how many people say hello!

Re: Using analytics on my website

#13
post #8

I went the other way entirely: no analytics, 100% static site, no logging. It's super fast and it takes away one more thing to monitor and keep up, it's not as if I'm running an e-commerce site.

This is the way. However, if you do want to view some stats about your site, you can get them by checking the domain on Google Search console [0].

[0]: https://search.google.com/search-console/about

Re: Using analytics on my website

#14

[flagged]

> It's bad enought that marketing departments has convinced 99% of companies (or has overruled product / engineering) that it's good to track and make websites slower in the process.

Because there are no product tools and analytics to track and make websites slower in the process?

Re: Using analytics on my website

#15
post #8

I went the other way entirely: no analytics, 100% static site, no logging. It's super fast and it takes away one more thing to monitor and keep up, it's not as if I'm running an e-commerce site.

I've done exactly the same. I must admit, there's a sense of FOMO — if I weren't hosting on GitHub Pages, I would 100% do some analysis of server logs to learn something about site traffic. However, on balance, this is still the best option!

Re: Using analytics on my website

#16
I’ve been looking to add some analytics to the endoflife.date API (JS obviously doesn’t work) and my no-JS options are:

1. Netlify analytics, which I’ve tried in the past and found under-powered

2. CloudFlare analytics (yes, there’s a No-JS variant in the Pro plan)

3. get your raw access logs from your host, and throw them at GoAccess/…. BunnyCDN seemed like the simplest provider for this with access to raw logs in the standard tier. Both CloudFlare and Netlify restrict this to the Enterprise tier.

Re: Using analytics on my website

#17

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 simpl…

I feel like the blog post confused domain registration and DNS on the root domain. CloudFlare absolutely demands the latter by asking you to change your name server on your root domain. The only way out is on the enterprise plan.

Re: Using analytics on my website

#18
I suggest using analytics that you can self-host, like https://www.goatcounter.com/ and renting a cheap vm to run it on along with your blog. It is way better, you have more control and you can be sure that javascript tracking is working for 100% of people using the site since you have full control over it not getting blocked by adblockers.

Re: Using analytics on my website

#19
Hi HN, PostHog employee here. I'm working on our Web Analytics product, which is currently in beta. It's fun to see us mentioned here :)

I should mention that we have a ton of SDKs (see https://posthog.com/docs/libraries) for back end frameworks and languages, so if you wanted to use PostHog without any client-side JS you could send pageviews and other events manually, but for the vast majority of people it makes more sense to use our JS snippet.

Hijacking this comment to share the roadmap for web analytics https://github.com/PostHog/posthog/issues/18547. It's very much in the launch-early-and-be-embarassed phase, but I would love to hear any feedback or suggestions that people have, particularly if you're already a PostHog user.

Post reply on HN