When speaking at events I am sometimes accused (light heartedly) of drinking too much of the Google Koolade – meaning I endorse the good parts and skip/skim the pitfalls. However this post is a criticism of Google for what I consider to be a flawed thinking with their recently announced support of multiple currencies in Google Analytics.
SEO is getting harder! If you are active with search engine optimisation (SEO), then you will be aware of the issue of not provided showing in your Google Analytics reports for organic visits. This post updates the situation plotting the growing impact over time and the differentiation of tech-savvy versus tech-savvy web users.
A busy day…
– Tag Management Systems (panel)
– Privacy Q&A with the UK data privacy authority
I have been to all of the London events (I think) since 2004 so its been interesting to see how things have changed over the years. Here’s my thoughts:
Talking about cookies i.e. deletion rates
Feature wars – tool X has 10,000 “must have” features Beauty Parades – vendors lined up to pitch their products
KPIs – How to select/choose your key performance indicators
Data accuracy questions
Big data – we all now have it
Tag Management – the CMS of third-party script placement
Privacy – good/practise, how does Google fit in
Case studies – more examples of what works, what does’t, search marketing and content optimisation
A very quick poll to help me understand book sales. This is to help me understand how to approach future editions, the value of an ebook, and how updates can be managed.
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 with comparisons to GA360 where applicable.
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?
I was recently interviewed by CMSWire. Apart from pointing you to the full article, I thought the questions, expertly posed by Siobhan Fagan, were very relevant. I particularly liked:
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.