It’s all about asking the right digital analytics questions.
Sure, in the right context, you can probably get by doing what Avinash Kaushik refers to as “data puking,” but you won’t excel as an analyst or marketer that way.
In addition, you’ll consistently come up short on bringing true business value to your company.
In any field, it’s important to be critical. But in digital analytics, it’s crucial.
Don’t Blindly Report; Be Critical and Ask Questions
According to Tim Wilson from Analytics Demystified, “Most analyses don’t turn up wildly surprising and dramatic insights. When they do – or, when they appear to – my immediate reaction is one of deep suspicion.”
Similarly, Ronny Kohavi, Distinguished Engineer and GM of the Analysis and Experimentation team at Microsoft, stresses following Tywman’s Law: Any figure that looks interesting or different is usually wrong!
Yet in the vast majority of digital analytics cases, we simply accept the numbers without questioning them.
The mark of a good analyst isn’t an advanced knowledge of a tool’s interface, though that does help. And it’s not about running down a checklist to appease a manager, though processizing things can be valuable.
It’s being able to step back and think critically, ask important business questions, and answer them with a high enough degree of precision in order to take action.
Why focus on business questions? Because the problems a business faces can be surprisingly unique, and trying to apply a formula or best practice tends to have the illusion of begin insightful, but in reality is just the easy way out. Here’s how Avinash Kaushik put it:
With that in mind, there are a few questions that, in the hands of the right analyst, will consistently bring value to an analytics practice.
They’ll make you step back and reflect on how your organization is using data, and how you can improve on your data culture…
1. Is this data accurate? Can we trust it?
If no one trusts your data, it’s essentially useless.
That’s why doing an analytics audit is so important: it forces you to question the integrity and quality of your data, and you’re required to have important conversations about what you’re collecting in the first place.
There are plenty of things at the account level in a given analytics system that should be subject to question.
For instance, is your Google Analytics data sampled?
This is a simple question to answer, but the answer determines how you deal with your data. Maybe it doesn’t matter much to you, but maybe it does. Maybe your data is directionally important and the precision isn’t as important. But it’s important to ask the question.
For what it’s worth, there are many ways to get around the sampling issue in Google Analytics. But to begin thinking about solutions, you need to have the conversation first.
There are many other considerations with Google Analytics data integrity, which is why we recommend doing a full exploratory Google Analytics Health Check.
At the highest level, this involves going through your account report-by-report and questioning whether or not the data makes sense on an intuitive level.
Do you have a 100% bounce rate – or a 0% bounce rate? It’s very likely you have some issues with double pageview tracking or incorrect use of event tracking (e.g. you’re using interaction events when you shouldn’t be).
The solutions for these problems tend not to be difficult, yet finding the problems in the first place isn’t easy. Doing a full sweep analytics health check isn’t common. Do this once and you’ll discover a ton. More importantly, never stop questioning the integrity of your data, and it’s likely you’ll continue to find and fix these quirks.
Does my data line up with other systems?
Another important point to make here is that you can usually approach data from multiple angles. Doing so allows you to answer the question, “do my data sources line up?”
For instance, it’s not uncommon for your Google Analytics ecommerce data to be slightly different than that of your ecommerce software. This could be for a variety of reasons, but you want to make sure it’s within a reasonable degree of accuracy (e.g. 95%+ similar).
Tim Wilson calls this triangulation, and he emphasizes that you can do this for more than just ecommerce data:
This is the same reason we recommend to integrate your testing tool with your analytics data. That way, you can get another view of the numbers to sanity check whether things line up or not.
2. What’s missing? Do we have the full picture?
You may be able to trust your data to a certain extent, but that doesn’t mean it includes the full picture.
This starts at the highest levels and goes all the way through your GA set up. For example, there are a variety of questions to explore within your property settings:
- Is the default URL set up correctly?
- Are your referral exclusion settings configured correctly (e.g. you use PayPal to process payments)?
- Is enhanced link attribution turned on?
- Have you enabled demographics and interest reports?
- Is Google Webmaster Tools linked properly?
- AdWords Integration
- Is it configured correctly?
- Is PPC data showing in Google Analytics?
- Are the resulting clicks and sessions being recorded properly?
For example, I could listen to Spotify’s web app all day every day. I could be a power user, a paying customer, and yet, I still may want to wander over to their developer’s site every once in awhile because I want to discover the most depressing Radiohead song using their API.
Sadly, Spotify sends this data to another Google Analytics property. This means that I’m a completely new user according to their developer’s site, and my user journey has become fractured from their point of view. There’s no way, now, for them to track all of my behavior on their website.
You can tell this by using GA Debugger, a free Chrome extension that is useful for doing analytics audits without even opening up the GA interface.
Here’s the homepage (spotify.com):
And the developer’s page: (developer.spotify.com):
Different tracking IDs there.
Another area you might be missing some granularity is with campaign tagging. Campaign tagging, at least in Google Analytics, is done with parameters in your URL. They usually look something like this:
There are five UTM tags used by Google Analytics:
The “medium” and “source” tags are required. It’s recommended you use a “campaign” tag as well, so you can track individual marketing campaigns. “Content” is used to differentiate between multiple content versions in a campaign (as in A/B testing messaging). Finally, the term “tag” is used to identify paid search terms that led to clicks.
While many platforms, including ad platforms like AdWords or email services like Mailchimp, will automatically append UTM tags to your URLs, some of them don’t. So you may be missing a huge part of your data that gets absorbed into Direct traffic or another channel.
Finally, the picture of your user can be fragmented because of many standard technical issues that, again, are relatively easy to fix but hard to spot. Here are a few we tend to look for when doing a GA Health Check:
- Missing tracking code on some pages, resulting in self-referrals or visits not recorded.
- Missing tracking code on 404 pages and server 500 pages.
- setDomainName missing on blog.mydomain.com, resulting in referring keyword lost and 2 visitor sessions.
- iFrame banner tracking resulting in double cookie.
- Missing eCommerce category.
- Site Search using static URL or mod-rewritten URL, thus q=keyword not extractable.
- Quotation marks not escaped or ansi characters not encoded in eCommerce category or item names.
- Missing manual tags in emails and newsletters & RSS, social, Google products, Google News.
- Violating Google’s terms of service by accidentally collecting personally identifiable information
- URL fracturing in behavior reports.
That’s just a small part of what you should check for in your audit. For more information on Google Analytics audits, check out these articles:
- Google Analytics Health Check: Is Your Configuration Broken?
- 20-Step Google Analytics Audit: The Key To Improving Performance At Every Level
3. Is this data meaningful?
If you’re in an organization where you’re just ordered to build reports and not to question what you’re actually trying to answer, well, then I’m not sure I can help you. But if you have a small amount of autonomy and a little bit of curiosity, simply step back and ask, “what does this mean for the business?”
Often times, you’ll come to the sad conclusion that you weren’t going to be able to act upon the data you’re pulling anyway. This isn’t to negate the power of exploratory data analysis. It’s simply to question the inherent value that certain metrics hold.
To use an extreme example, take how Buffer performed an “A/B test” on their tweets.
There’s a lot wrong with this, of course (different times of day, cherry picking data, etc.). But inherent in this is a question of, “so what?” Are retweets your metric of choice – why? Maybe they are the most important leading indicator, and I’m out of line here, but it seems to be grasping at straws here.
Buffer isn’t a lone offender; we all do this. It’s really easy to, without digging deeper, overestimate the importance of a given micro-conversion or micro-metric. That’s why it’s so important when we question the importance of metrics – especially when everyone seemingly agrees with their importance.
When questioning the importance of metrics, the pendulum tends to swing. “Bounce rates are super important” leads to “bounce rates are useless.” The truth usually lies somewhere in the middle.
4. What can we measure and analyze to get more meaningful results?
How can we get more out of our data?
The process of asking these digital analytics questions is the process of slowly moving up the digital analytics maturity curve.
You’re moving from asking foundational questions like, “can I even trust these numbers,” and “does this mean what I think it means,” to “what tracking should be in place for optimal insights and actionability,” and “is this data usable and accessible by the teams that can take action upon it.”
Some questions that you might be asking at this level include:
- Have you mapped out meaningful events you’d like to track for a great view of customer behavior?
- Do you have defined outcomes/conversion points, KPIs, dashboards?
- Do you do segmentation, merchandising, and campaign optimization?
- Have you built data-driven or behavioral personas upon which you can take action – with targeting or otherwise?
- Are your data sources merged in a way that you can view a larger part of the full customer journey?
- Are you using behavioral targeting?
- Are you using predictive analytics?
Of course, there’s a point of diminishing returns when you begin “tracking everything,” so don’t think that’s the answer to move up the maturity curve. Unless your organization is set up for it, you may introduce an element of unmanageable complexity to your data. Your data is only useful so long as you can take action upon it.
Tracking every single thing can bring confusion to a team that may have otherwise been better served by conservatively mapping out key events and focusing on those. But, if you’re too conservative with your tracking, you may be missing a larger picture of customer behavior. It’s a balancing act, and by no means a copy/paste recipe.
5. Have I Done Proper QA?
QA is important for everything you do (not the least of which is A/B testing).
That means it’s important for analytics and reporting, too. Tim Wilson from Analytics Demystified puts it well:
Every time you QA your reports, start by using simple common sense: do the numbers look weird? Remember, there’s usually something fishy about numbers that are too surprising or different. Never take them at face value; always question these numbers.
In addition, just as you should proofread your blog posts, you should proofread your reports. Tim Wilson walks through his standard process for proofreading:
- Pull up each query and segment in the tool you created it in, then walk back through what’s included.
- Re-pull the data using those queries/segments and do a comparison with wherever you wound up putting the data to do the analysis
- Proofread the analysis report – no need to have poor grammar, typos, or inadvertently backwards labeling.
Being good at analytics is about asking good questions. It’s not about “data puking,” or blindly reporting metrics without questioning their accuracy, integrity, importance, or actionability.
The moral of the story here is that, with data, taking the extra minute to question things may bring nonlinear value to your program. More data isn’t always a good thing; if it’s poor quality data, you may just be more confident in making bad decisions. Take the time to ask critical questions, and your program will improve with time, as will your clarity and business decisions.