One reason I am not convinced by the new User Explorer report in GA is that it is a bit oversold – you cannot monitor activities of an identifiable user, since the report is still anonymous. It’s not just Google’s own TOS that forbid storing personal info, there is also a bit of a legal issue which at least applies in Europe. If you store personally identifiable information you need to obtain permission by, and must be able to delete the data at the request of, the person in question. The former thing is not quite feasible and the latter is not at all possible. Storing user based data (with their permission) rather is the domain of Customer Relationship Management systems. Yet you can emulate at least some features of a CRM system with the feature set Google offers for free.
The first part of this series introduced the problem – wanting to track to 2 different GA properties without double-coding the tracking calls – and the second part proposed a solution, using a GA plugin to amend GA’s sendHitTask to send a copy of the payload to an additional property. This part explains one of the caveats of that idea and how to overcome it.
The first part introduced the problem – sometimes you need to track a website to two different properties, and usually this would require you to do all your tracking calls twice, and that it sort of cumbersome. Wouldn’t it be nice if you just could pass in a second property id and have the data send to both properties.
David Vallejo ak.a. “thyngster” is, much like me, a web analyst who keeps a blog and likes to share information with others – to that effected he has started a “hackathon” , an opportunity for programmers to work together on a piece of code. The idea is to create a plugin for the Universal Analytics tracking code that allows data to multiple properties.
The very first article in this blog was about how Google Analytics does not do user level reporting and how it doesn’t make sense anyway. Promptly Google tries to make me look foolish by releasing the new user explorer, a report that allows user level reporting.