Sitemap
Viewing Personally Identifiable Info in Google Analytics: Right or Wrong?

The reason you can't is probably why you shouldn’t.

4 min readSep 18, 2014

--

Marketers and consumers have had a contentious relationship since the dawn of analytics and advanced practices were brought to bear by the digital marketing industry to better understand and influence user behaviors.

Since the birth of these very powerful digital surveillance tools (aka Analytics), marketers have abided by the ethos that we would study the data in aggregate, without surveying any one user in particular. And I believe that this is the careful balance we've crafted as marketers and consumers.

This concept is known as ‘Personally Identifiable Information’ or in shorthand, ‘PII data.’

We — as marketers—respect your individual privacy and don’t collect PII data. You — as consumers — will share more and more behavior with us so long as we don't creep you out or overstep your boundaries along the way.

Google formalized this policy in their industry-standard and free solution, Google Analytics. Google strictly forbids piping in PII data to your analytics suite. If they catch you with PII data in GA, they will shut you down for good and you'll be blacklisted. There’s really no coming back from that offense.

And while there are some analytics suites that build their value proposition around PII data, I'm looking at you Kiss Metrics, it’s not our industry standard.

Our industry standard is analysis in aggregate, not in singularity.

We get absolutely no value from looking at the behaviors of one identifiable individual. We don't need that power; just like school districts don't need tanks. But that’s an entirely different blog post.

Get Matt Browne’s stories in your inbox

Join Medium for free to get updates from this writer.

While Google doesn't allow PII data, they do allow anonymized user IDs that you could tie back to individuals if you wanted to. And while there’s some privacy exposure there, it’s a nice balance between surveillance and privacy. This is what a proper implementation of anonymized data looks like:

Press enter or click to view image in full size

You can see individual behaviors can be dissected in amazing detail, but we're not actually viewing an individual’s name or email address (PII data).

Enter our segment on ‘the reason why you can't is probably why you shouldn’t.’

The reason you can't view PII data in Google Analytics is long. I'd imagine at the top of that list is Google fearful of overzealous marketers freaking customers out with creepy practices. Another good reason for not collecting this data in this manner is that it’s illegal in many countries in Europe. And finally, what value do I get as a marketers by spying on a specific user? Google is clearly erroring on the side of caution here and frankly I think it’s the right call from a company that has a blemished track record with user privacy.

But that long list of reasons hasn’t stopped someone from developing a simple Chrome solution that will circumvent Google and drop in PII data in your Google Analytics reporting without Google knowing.

This developer invented a clever work around for himself and then developed into a commercially viable extension.

Here you can see him overlaying PII data into the GA platform.

If you search the Chrome store for marketing apps, this is one the more readily accessible extensions in the marketing category. However, it flies in the face of protecting individual user privacies and Google should remove it from their store.

(To avoid inadvertently promoting his Chrome extension, I have chosen not to link to it or reference it.)

If I marketer wants to develop and hack their own reports, so be it. But when you start distributing these techniques to the mainstream, you have to bear the responsibility of ‘just because you can, doesn't mean you should.’

You ought to share and extend the ethos of the Google Analytics terms of use and not seek to redefine them. As an industry, lets not give consumers more reasons to be wary of us.

What do you think? Should Google step in here and remove the extension? Or is this the future of marketing intelligence? As both a user and marketer, I sure hope the latter is not true.

--

--

Matt Browne
Matt Browne

Written by Matt Browne

Technology renaissance man and sucker for a good ristretto espresso.