Last week I attended my 8th GA Summit in Mountain View (the first one had just 10 people in the room! Four of that original group where there this year*). For a change, I summarise the highlights – and why I consider them important to you the GA user – as an infographic
Its good to know the limits of your Google Analytics implementation. All software has it limits and Google Analytics is no exception. From Google’s viewpoint, setting boundaries and limits prevents errors and system overload, and it ensures that other users of the service are not affected by the processing of someone else’s data. For example, a website with a relatively low amount of traffic data should not have its reports delayed due to the processing of another user’s data from a site that has more traffic.
The table below lists the limits set for the free version of Google Analytics.
Following a recent period of renewed media debate (I use that term loosely!) about the legality of tracking website visitors with Google Analytics, Sara Andersson, founder of Search Integration AB and the blog No Ketchup (hence the reference in my title), interviewed me about my opinions on this last week and what the debate should really be about. As always, I would be interested in your feedback…
- Can you give me your thoughts on how Google look at this product and how they handle data internally?
- The latest discussions on Google Analytics being illegal and the fact that they propose that people should not use GA on their sites, what is your reaction to this? Are the concerns legitimate at ALL?
- The latest EU privacy law is trying to stop people from tracking individual information. What is your thoughts on this in relation to Google Analytics as a product?
- Why does Google Analytics get all the focus in the debate about privacy? Are there other services and tools that in your opinion, website owners should be aware of when it comes to tracking sensitive data?
- What can website owners do in order to clarify to their visitors how they handle data?
- Beyond looking at the concerns of website owners, what should the privacy debate be about?
What do you see as the future direction of analytics?
I enjoy sticking my neck out on future predictions, so I reproduce my answer to this question here…
Not really! The eye catching headline form the following article is actually very misleading (I used Google translate). In fact, this is a classic example of poor/misleading journalism on this subject…
As I wrote in my last article on this subject: Google Analytics and the new EU privacy law #3, if you use Google Analytics to collect personal identifiable information (PII) without the explicit consent of each visitor, then yes you are breaking the privacy laws in each of the 27 EU member countries. That is the same with any tracking tool/methodology. It also breaks the Terms of Service of GA.
In my post form last week, I commented on Econsultancy’s 5th Online Measurement and Strategy Report 2012. An area that stood out for me in that report was the 8% market share of GA Premium, the paid version of Google Analytics. In this post I wanted to spend more time sharing my thoughts on the wider points raised by this report…
I am a big fan of Econsultancy because of the quality of the work these guys do. In case you missed it they published their 5th Online Measurement and Strategy Report 2012 today. As with the previous reports, it’s fascinating snapshot on where web analytics is right now – both as a process and as an industry.
But what got my attention are the GA Premium numbers… [...]
As you may be aware, last May (2011) a new EU privacy directive came into force – officially known as Privacy and Electronic Communications Regulations (PECR), though often referred to as the “EU cookie law” as it implies that setting website cookies without a visitors consent would be illegal in all 27 EU member countries.
Contrary to what has been reported (and even enacted on some sites), you do not need to seek explicit consent to set an anonymous, benign first party cookie. [...]
If you manage a Google Analytics account, then understanding regular expressions – and how to set them up – is a key part of your job. This tutorial is intended to jump start novice users into the world of regular expressions – specifically from a Google Analytics point of view. [...]