Too many people blocking that script. I have about 20 different sites using it that I manage in some form bit cannot couch for it anymore.
Too many people blocking that script. I have about 20 different sites using it that I manage in some form bit cannot couch for it anymore.
Fighting this fight at the moment:
marketing folk - "we're seeing more responses from old people than young people, we should focus on that market"
technical folk - "Are we allowing for the fact that older people are less likely to be blocking GA and therefore most of those untracked clicks are likely to be younger?"
marketing folk - "well, no, but we don't have any information on those, so we can't make any decisions about them."
technical folk - "but we know GA is blocked by ad-blockers. And we know that ad-blockers are used more by younger, more tech-savvy people. And we know that approx 60% of the visits to our site are not registering on GA. So... can we include that in our analysis?"
marketing folk - "...."
technical folk - "...."
marketing folk - "I don't know how to change the pretty graph that GA produces to include that."
I'm also personally shocked at how FEW people relatively end up using ad blockers. Its a night and day difference
And this is 2 years ago so I assume it's even higher now. It's a lot more than I expected for sure. They only count consumers though.. Perhaps companies don't always allow it, but I always use uBlock at work.
Marketing folk - "Wait...if we're getting more responses from old people than young people and old people are more likely to run adblockers than young people, let's increase our spend on Google Ads because only people without adblockers will see them."
Technical folk - Get into woodworking.
Edit - If the technical folk push back, that's when marketing folk will say that 'the law of really big numbers' means that 40% of a big market is still worth a lot. Trust me, woodworking....:)
That's the problem, accurate visitor tracking wasn't on the web design goals.
But if you want an independent track to verify your JS report, the server logs have almost an almost completely disjunct set of problems.
https://developers.google.com/analytics/devguides/collection...
Did you write your own scripts to use your proxy URLs with the same API?
Besides, I was talking about my server directly sending data to Google Analytics without JavaScript on the client side. GA has strong adherence to GDPR so there's no legal or privacy issues I can see with that.
This assumes you self-host analytics.js and proxy GA API requests through your domain without changing path/query. If you manage to reverse engineer analytics.js and change the path/query AND proxy through your own domain, then this likely wouldn't be detected. But there's a chance that Google will make changes to analytics.js that aren't compatible with your reverse engineering it, and your setup breaks.
We now record key metrics just through our backend. No tracking, no cookies, just aggregate numbers.
Consult `man 1 grep` for information on how to query it.
Or something like goaccess to get nice charts.
I go out of my way to not use any Google services and I don't like when websites negate that choice by using Google analytics, Facebook pixels etc.