Noise or Music?

A key recommendation for GDPR compliance is to use the Google Analytics feature anonymizeIP, also known as “aip”. As the name suggests, this simple switch drops the last 3 digits from your visitor’s IP address. For example, if a visitor has a public ip of 215.113.40.184, then Google will obfuscate this to 217.115.40. (and all other visitor ip addresses) when it processes your Google Analytics data. No ip address data is stored. That’s good for GDPR compliance because ip data is considered PII in Europe.

So if the last 3 digits of an IP address are removed, does that impact geolocation data?

The answer is of course yes, but how much of an impact, and should you worry about it..?

GDPR means that organisations need to keep records of all personal data, be able to prove that consent was given, show where data is going, what its being used for, and how it is being protected.

But what defines personal data…? And how is PII different…?

I must admit that the new Google Analytics documentation about the GDPR specific Data Retention setting is confusing! The assumption from many clients is that ALL data older than NN months is going to be deleted i.e. a cliff-edge effect where any report older than say 26 months is going to be empty. The setting is important, […]

In this post I address a key question that is troubling many a website owner using Google Analytics (the “Controller” in GDPR terminology): Is explicit consent required before I can track my visitors?

I am going to assume you are aware of GDPR (who isn’t? And Facebook have successfully heightened the awareness in the US). You should also be aware that even though I work in the data industry, I have been a strong privacy advocate for many years now. I approach the subject as an end-user would. Let’s face it, for many years now the data/tracking industry has a bad reputation in general…

It is interesting to note that although GDPR has been 10 years in the making, Google Trends shows that since the start of 2018, the volume of searches for the term “GDPR” is now more than double that at any period the previous year i.e. this is important:

My challenge: As with viewing any information containing charts, tables, diagrams etc. reading content in COLOUR is very important to me, more so than the purchase price. Hence, why the book Successful Analytics was in colour – by necessity it uses better quality paper and hopefully by using colour, the points are clearer as well as easier to remember. However colour printing is expensive – it always was. So I need your feedback via this 2 second poll – it will help me to decide what to do with the next version of Successful Analytics.

My extension to the GTM Tips post by Simo Ahava (Tip 64!). Essentially, I extend the regex for more rigorous email checks and add prevent other PII types getting in to Google Analytics. You don’t need to ask why this is so important in today’s GDPR compliance world…

If you haven’t gotten around to reading my latest book: Successful Analytics – or want get one for a colleague/client, here is a great opportunity… I am running a one-time sale of 50% OFF all paperback orders – for 1 month only (hard stop of 13-Aug-2017). There is limited stock, so its a first come […]

Google Analytics is now removing personal info from collected data. So far only for query term “email”.

Surveying to your customers is obviously a good thing, BUT the key to obtaining a good participation rate and accurate results, is the timing and mechanism of your survey. Unfortunately these are so often forgotten. The result is poor quality data masquerading as “feedback” that can also be damaging for your brand!

In this post I discuss why surveys often end up being a silent brand killer that also produce skewed data, as well as how to increase survey participation without damaging your brand….

If you have a transactional site, then of course you will want your transactional and product data as measured by Google Analytics, to match the real sales numbers that your back-end system collects. However in reality, these never exactly match due to a number of issues. These include:

1) Processing time differences; 2) Returns; 3) Blocked tracking; 4) Cross-domain tracking issues – the most problematic.

I discuss these next, but first…