Earlier quoted context omitted.
Server logs can't do this job well. If the system is designed well, in a lot of cases the users won't be receiving the resource from your server, they will be receiving it from a) their browser cache, b) their local network cache, c) their ISP's cache, or d) a CDN. Your server logs might be showing several thousand hits while the number of times a page is actually shown to somebody might be tens of thousands of hits.…
Is it possible to add a basic ping that pings your server whenever a page loads (cached or not) to get around this?
Safari now blocks Google Analytics on sites, new Privacy Report feature shows
51–60 of 117 posts
Re: Safari now blocks Google Analytics on sites, new Privacy Report feature shows
#52What's a good tool for doing server side analytics? Like for a small site I've made for fun. The only way I can easily know how many users visit is via Google analytics. Well easily that is.
Re: Safari now blocks Google Analytics on sites, new Privacy Report feature shows
#53Re: Safari now blocks Google Analytics on sites, new Privacy Report feature shows
#54Re: Safari now blocks Google Analytics on sites, new Privacy Report feature shows
#55Earlier quoted context omitted.
Here's another suggestion: Learn how to configure Google Analytics properly. https://support.google.com/analytics/answer/1011397?hl=en "If all [data sharing] settings are OFF, your Analytics data is only used to provide and maintain the Analytics service."
Weill, this only "works" for you if you trust google. Given multiple security incidents in the past I am certainly not one of those people.
Re: Safari now blocks Google Analytics on sites, new Privacy Report feature shows
#56I have no love for Google Analytics, but as a small-scale publisher, I have serious questions about what tools can replace it: 1) Which analytics can a website employ that is not geared toward enriching the analytics platform developer by violating site visitor privacy? 2) Do those analytics mechanisms have any kind of aftermarket, such that third-party developers integrate it into publishing platforms that publisher…
You can turn off the cookies too, anonymize IPs (the default actually) and if you do that you don't even need GDPR consent or cookie banners.
Re: Safari now blocks Google Analytics on sites, new Privacy Report feature shows
#57Earlier quoted context omitted.
Is it possible to add a basic ping that pings your server whenever a page loads (cached or not) to get around this?
Yes, with Cache-Control, and then if you turn that product into a SaaS so that not every website has to run a copy, you get Google Analytics.
Re: Safari now blocks Google Analytics on sites, new Privacy Report feature shows
#58Earlier quoted context omitted.
Server logs can't do this job well. If the system is designed well, in a lot of cases the users won't be receiving the resource from your server, they will be receiving it from a) their browser cache, b) their local network cache, c) their ISP's cache, or d) a CDN. Your server logs might be showing several thousand hits while the number of times a page is actually shown to somebody might be tens of thousands of hits.…
Oh yes they do, and why would you want to break network caching to spy on your users? You can always add some little js to ping your server (logs! Again!) or a non-cacheable tracking pixel.
Re: Safari now blocks Google Analytics on sites, new Privacy Report feature shows
#59Suggestion: the access logs your web server collects are enough for basic analytics, and if you are curious for more, you can manually instrument your site a little. You don't need to give Google the power to spy on your users.
You can setup some sort of pixel that's never cached and that transmits the page via query params, but then the implementation isn't reliable and a PITA.
If you have your own server, something like Matomo.org works better.
Re: Safari now blocks Google Analytics on sites, new Privacy Report feature shows
#60Federated analytics soon? - Google gives you a docker container and an API key to run that collects metrics on your public/own cloud, that gets slurped up to Google and you still get your demographic info.