4 ms·
> Server side logs aren’t an accurate way of doing analytics ... Based on what? Server side logs records what the server itself sent. That sounds like it sho
by justinclift 6y ago
> Server side logs aren’t an accurate way of doing analytics ...
Based on what? Server side logs records what the server itself sent. That sounds like it should offer far more accuracy than what a JS only solution would do.
That being said, if the code for analysing the server logs is lousy, it's not going to help. :)
- JackWritesCode 6y agoBefore looking at accuracy, you already have compliance challenges with logging IPs / user agents and using it for analytics purposes.
- justinclift 6y agoPlease don't try and change the goal posts. You said: > Server side logs aren’t an accurate way of doing analytics... What is your thinking behind that statement, as it sounds incorrect?
- ivanche 6y agoWhat compliance is challenged by logging user agents?
- snowwrestler 6y agoThe identifier in server logs is IP address, which is useless for distinguishing users. On the corporate side, NAT hides all the visits of many people behind a single IP. On the consumer side, ISPs change IP addresses all the time so a single person will show up as multiple IP addresses. Note that I'm just talking about distinguishing people, not identifying or tracking. A basic question like "how many people came to my website today" is more accurately answered with client-side analytics than by analyzing web server logs.
- justinclift 6y ago> A basic question like "how many people came to my website today" is more accurately answered with client-side analytics than by analyzing web server logs. How can client side analytics be more accurate, when ad blockers stop visits from even being registered by client-side analytics?