Do Not Track, maybe
To opt out of tracking scripts on websites, you can set the “Do Not Track”-setting available in some browsers. Activating it adds a “please do not track me”-signal to all your HTTP-requests. Unfortunately, third parties are not required to honor that wish. They don’t have to stop collecting data about you. Some might, many will not.
Before GDPR went into effect, I removed Google Analytics from my portfolio. I do not currently know if people are reading my articles at all. When it comes to tracking, I would rather fly blind than invade my visitors’ privacy.
As long as I can recognize trends, the behavior of individuals is completely irrelevant to me. You keep your privacy, I still get some usage statistics. I won’t get the same level of detail a Google Analytics would give me, which is fine. Netlify, where I am currently hosting my site, is offering exactly the kind of analytics I am looking for. Their documentation sounds super promising: Analytics by Netlify
This will still leave blind spots in my statistics, so I would like to compile a list of pros and cons of this approach. What are you using your analytics for that this will not give me?
Running Google Analytics is the most obvious reason for showing a consent form to visitors. There are many less obvious ones you also need consent for.
I had my expectations of how software is used challenged last week when talking to the CTO of a med-tech startup.
Without a specified target audience in mind, the content we create ends up being for nobody instead of being for everyone.
When we need to gather statistics or other logs from our projects, we don’t always need to use full, privacy-invading analytics solutions.