There's a lot to do around privacy, GDPR and website analytics tools like Google Analytics.
As a Digital Experience Agency, we think it is very important to have a clear vision on these topics. In this article, we summarize some important evolutions and take a look at the future and what we think it will look like.
Read on and discover…
- A concise summary of what exactly the GDPR-problem was with Google Analytics
- Which settings in Google Analytics are an issue in terms of GDPR
- Other tools you can use to replace GA
- Why we believe current legislation is doing more harm than good
Let's dive into it...
The current situation in Google Analytics land
It seems like every month a new article is published about some authority that has issued a ruling related to GDPR legislation.
In these last couple of years, Austria's DSB, Franse's CNIL, Italy's GPDP, and several other data protection authorities issued verdicts about websites needing to stop using Google Analytics.
If we take a moment to translate the complex legal texts and rulings into human language, in most cases it boils down to this:
- The websites in question collect data which is considered personal information
- This information was collected without prior consent
- All this website analytics data ends up on U.S. servers
Given the data is physically stored on servers in the US, US authorities (such as the NSA) could also access it.
And that's exactly what the problem was until recently: Google could not guarantee the privacy required by the GDPR because U.S. law overruled it anyway.
Solution: the Data Privacy Framework (DPF)
In July 2023 the so-called Data Privacy Framework went into effect. This agreement was set up specifically for the aforementioned GDPR-issue and is in practice the successor to the "Privacy Shield", which was deemed invalid in 2020.
Thanks to the Data Privacy Framework, companies based in the European Union can once again store personal data on US-servers without automatically violating the European GDPR.
How personal is personal data?
It should clear: the collection of personal data, ánd the storage of that data on American servers is at the root of a lot of fuss.
“But Wouter, our website doesn't collect personal data!”
Are you sure?
After all, according to the GDPR's definition, a lot of (seemingly small) things are being categorized as "personal..."
As soon as someone can be directly or indirectly identified in any way, that data is considered "personal" data. Not only do we have the usual suspects such as birth dates and email addresses, there's also things like IP addresses or anonymized IP addresses in combination with browser data, screen resolution or type of device your visitor uses.
If Google Analytics assigns a unique identification number to a visitor and this same identification number is used when that visitor visits your website from a different device (because they are logged into their Google account for example) then this is also considered to be personal data.
Indeed, if data in Google Analytics can be combined with data from other tools and this can somehow lead to identifying a person, then this too is a form of personal data.
How to ensure that you collect as little "personal" data as possible depends on the tool you use:
- Google Universal Analytics: switch to GA4 or an alternative tool as soon as possible
- Google Analytics 4 (GA4): follow the privacy-friendly setup in the following section
- Matomo Analytics: configure according to their own guidelines
- Piwik Pro: configure according to their own guidelines
- If you use another tool: have it reviewed by your DPO
A privacyfriendly Google Analytics 4 setup
If you use Google Analytics 4 on your website, it's best to set it up so that no personal data is stored or shared with third parties.
Setting up GA4 in a privacy-friendly way is done as follows:
- Google Signals: turn off
- User ID: turn off
- User-provided data capabilities: don't allow
- Granular location and device data collection: turn off
- Advanced Settings to allow for Ads Personalization: turn everything off
- Data Sharing Settings (can be found at account level): turn everything off
- Manage default consent settings for data collection: select "No. Do not automatically mark this data as consented."
- If you use custom events (for example click tracking of email addresses and phone numbers) make sure the data can't lead back to one single person. You could enable the option "redact data" to automatically anonymise email addresses before they are sent to Google Analytics.
And of course: only send data to Google Analytics after your website visitor has given explicit permission to collect statistical data. Read more about how you can make your website GDPR-compliant.