Don’t forget “this works in chrome so every other browser is wrong”, or “I tested in chrome, edge, opera, …” which are all just chrome with different skins.
Ad-blockers and tracking prevention block your script from loading (enabled by default on many browsers today).
Well yes, all your “free” analytics tools are literally just spyware for the purpose of tracking. That they tell you some of the information they get from the spying you are fundamentally using an unnecessary “tool” for which the overriding goal is spyware.
Every person using this kind of garbage analytics needs to acknowledge that that is what they’re doing and stop pretending otherwise.
Garbi | 5 hours ago
"Testing only on Chrome" infuriates me.
olliej | 2 hours ago
Don’t forget “this works in chrome so every other browser is wrong”, or “I tested in chrome, edge, opera, …” which are all just chrome with different skins.
olliej | 3 hours ago
Well yes, all your “free” analytics tools are literally just spyware for the purpose of tracking. That they tell you some of the information they get from the spying you are fundamentally using an unnecessary “tool” for which the overriding goal is spyware.
Every person using this kind of garbage analytics needs to acknowledge that that is what they’re doing and stop pretending otherwise.
max-headroom | 4 hours ago
Maybe you'll get the message eventually.
fazalmajid | 8 hours ago
JS-heavy SPAs should be the exception, not the rule, but in any case it is a good idea to sanity-check your analytics against web server logs.