ag Manager, anonymizing

[kexej28769@nongnue]

To ensure that you are using Analytics in compliance with GDPR, a good place to start is to audit all the data you collect to make sure that it is all relevant to its intended purpose and that you are not accidentally sending Personally Identifiable Information (PII) to Google Analytics. Sending PII to Google Analytics was already against its terms of service, but it often happens accidentally when information is passed along in the URL of a page. If it turns out that you are sending PII to Analytics, you will need to talk to your web development team about how to fix it because using filters in Analytics to block it is not enough — you need to make sure that it has never been sent to Google Analytics in the first place.

PII includes anything that could potentially be used belgium number data identify a specific person, either by itself or in combination with other information, such as an email address, home address, date of birth, zip code, or IP address. IP addresses weren’t always considered PII, but GDPR classifies them as an online identifier. Don’t worry, though – you can still get geographic insights into who visits your site. All you have to do is turn on IP anonymization and the last part of the IP address will be replaced with zeros, so you can still get a general idea of where your traffic is coming from, although it will be a little less accurate.

If you use Google T IP is very easy. Simply open your Google Analytics tag or its settings variable, select "More settings" and select "Fields to set". Then, select "anonymizeip" in the "Field name" box, enter "true" in the "Value" box, and save your changes.



If you don't use GTM, talk to your web development team about modifying the Google Analytics code to anonymize IP addresses.

Pseudonymous information such as user IDs and transaction IDs are still acceptable under GDPR, but need to be protected. User and transaction IDs need to be alphanumeric database identifiers, not written in plain text.