Since #GDPR and the rise of privacy awareness, keeping trackers on your website is like betting climate change won’t impact you.
Google Analytics is already weakened by Brave browser, ad blockers, browsers extensions… Later this year, a single change in Safari (this one: https://fosstodon.org/@markosaric/104392496830100166) will impact keep away much more users (https://canistop.net/b/ios_saf) from Google data harvesting!
At work we’re self-hosting Matomo: 1) higher numbers (less blocking) 2) GDPR+privacy 3) you win clients because they love 1 and they fear messing with 2.
Our manager was already dealing with GDPR compliancy. So connecting the dots between GDPR and Matomo was common sense and convinced him.
Always ask yourself why you want the data and what they enable. If they don’t enable anything, they’re just noise and vanity, and you’re probably already sending too much JS to the user.
It’ll be hard. Sometimes you’ll win, sometimes not, but it’s worth doing it (step by step).
Also, you’ll have to educate people inside of your company (and yourself). A lot.
Example: our social media dpt. unilaterally decided today that I had to urgently tenfold the JS payload by adding a Facebook pixel tracker and a LinkedIn one on the company’s website.
Lost cause: as I know they’re always last minute, I told them it couldn’t be done before end of months. “So let’s forget it for now.” But it means I’ll have to discuss why they want this, what it enables… Which is already boring. :p
Ceci est l'instance du site NintendojoFR. Elle est réservée aux membres de la rédaction et à nos chers lecteurs qui souhaitent avoir un compte.