Yehoshua Coren, founder of Analytics Ninja, tackles Google Analytics success tactics, analytics data challenges, and the future of digital analytics.
First and foremost, I strive to understand what business questions need to be answered so that I can make sure that we’re collecting data to answer those questions.
Next, I do my best to hammer home the importance of analytics being a part of the process of any “campaign” / “project” / “dev cycle” etc. It’s sometimes difficult to change a common aspect of company culture where people build new pages/components/content and only after launch do they ask for analytics. I want analytics to be a “line item” for any project or campaign. I’ve seen this happen across a number of large organizations that we’ve worked with and it is very fulfilling to see analytics no longer treated as an afterthought.
Additionally, I work with development teams to have a technical framework through which they can adhere to having a data layer and HTML5 data-* attributes within markup on the page. In this manner, Dev Teams will be able to build analytics into their infrastructure in a consistent manner.
Lastly, having a dashboard or report planned after launch will help product teams and other business owners have visibility into their efforts. They’ll be able to see the “fruits” of having analytics be a part of their day-to-day business requirements.
To leverage GA successfully, you need to have careful strategic planning of your data collection. Using custom metrics in addition to traditional event tracking makes a big impact on how well GA functions as a tool.
There are a few. Sometimes it is a lack of care and investment in what is required to maintain and use a data collection pipeline. Other times it is a naive belief that analytics is either “plug-and-play” or that you can just buy some fancy, expensive tool that has a Google Analytics connector, and then your analytics is turnkey.
Even with good processes in place at an organization, it is critical to recognize that you need people to make it happen. That’s the other big challenge; a lack of highly qualified analytics professionals to fulfill the data demands that exist in the business world.
To leverage GA successfully, you need to have careful strategic planning of your data collection. Using custom metrics in addition to traditional event tracking makes a big impact on how well GA functions as a tool. Honestly, though, I think that companies should focus on how to use GA to “go beyond” GA. Databases and cloud computing resources are a great place to get your data ‘out of GA’ so you can do more with it.
I think that is one of Google’s biggest moves by re-platforming to the App+Web platform. They want people to use BigQuery. I think it is a smart move by Google, even though the current iteration of App+Web is still very “beta” and the data collection limits of the platform are pretty ridiculously rigid and limited.
I’m not fully convinced I agree with the premise of the question. That data should be turned into insights. I.e. We have all of this data!! Tell me what to do with it. Rather, I think that the primary role of data is to answer business questions. Tell me what your questions are and the business problems we are trying to solve for, and then use data to help answer questions.
That said, some of the low-hanging fruit will always be measuring the users’ browsing experience. Doing a behavioral analysis based upon Device Category and Browser generally tends to lend insights into how a particular experience (for example, Mobile / Desktop) translates into whether or not a user was able to accomplish what they were trying to do on a website.
I think that the primary role of data is to answer business questions. Tell me what your questions are and the business problems we are trying to solve for, and then use data to help answer questions.
Having accurate (or even more pointedly - precise) data coming into Google Analytics will lead to greater usage and adoption of the data. If stakeholders don’t trust the data, they won’t use it. Trusting data and having the adoption of using the data within an organization is critical.
Knowing HOW the data flows from the website into analytics (technically) is needed.
Psychology. We must always remember that analytics is not about HITS, it is about people using a website. Sometimes analysts will over-trust their data. It’s also important to trust your brain, as well as to be able to extrapolate what that data is saying about human behavior.
We must always remember that analytics is not about HITS, it is about people using a website.
More and more tagging is going to be “first party”, in other words creating/maintaining your own analytics pipeline using internally owned cloud infrastructure. As browsers try to lock down privacy, analytics is going to be pushed server-side. Machine learning and AI applications are going to be layered upon analytics data to try to automate the discovery of insights.