News for hackers. Stuff that matters.
Re:Using GoAccess for self-hosted web analytics by tyingq on Friday December 27, 2019 @07:17AM (#21890908)
GA does support using Google Tag Manager and a NOSCRIPT iframe for recording visits from people with JavaScript disabled.

You can also either proxy GA through your own domain, or use server side APIs to track those with blockers. Both support passing the browser IP as a parameter.

Also, fwiw, just noting both are technically possible. I'm not speaking to whether either is okay ethically.

Re:Using GoAccess for self-hosted web analytics by joshyi on Monday December 30, 2019 @09:59AM (#21913693)
I think a big problem with Google Analytics is accuracy, especially with the now so popular adblockers. Log analysis such as GoAccess should be able to track these down fine since it works at the server level.

I believe tracking visitors at the client level deflates the actual number of visitors. On the other hand, server-side tracking gives you a more accurate number at the cost of not knowing for sure if the client is a human behind a browser.

Re:Using GoAccess for self-hosted web analytics by tyingq on Monday December 30, 2019 @10:03AM (#21913726)
You can programmatically send hits to GA from your server, and get the benefit of the nice UI.
Re:Using GoAccess for self-hosted web analytics by adamzochowski on Friday December 27, 2019 @12:14PM (#21892521)
FYI: Paranoid adblockers / privacy protectors will block iframe to remote domains. For example: uMatrix by gorhill (same author as uBlock Origin) does this.