You lose all the ones with a blocker, all the ones with JS turned of.
Of course it’s not the biggest percentage, but still.
So you’re right, it depends of what the website is. It’s easier to follow individuals with a JS solution.
You lose all the ones with a blocker, all the ones with JS turned of.
Of course it’s not the biggest percentage, but still.
So you’re right, it depends of what the website is. It’s easier to follow individuals with a JS solution.
Instead we now have disable GA or all JS in order to not be tracked. GA is a huge privacy issue, and I have no idea why no one is looking at this more closely than some of the other things I see as trivial.
Google controls most of the web's search. It controls a huge chunk of the browser market. And a huge chunk of the websites out there use GA if not google-ads. Between Google and Facebook, we are constantly being tracked and monitored for maximum benefit/profit.
Case in point: Even without GA, I recently browsed a blog that had a Disqus comments section embedded on it. The embedded Disqus script did a post to "https://accounts.google.com/o/oauth2/iframe" that had a referral header telling google exactly the page I was at, and it included a few other potentially-tracking tokens. Bad? You decide. But this is not what we should be allowing the players on the web to do, and we shouldn't feel like conspiracy-theorists for being bothered by it.
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.
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.