Online businesses live and die through conversion rates and task success rates. Most of my customers can tell me what their key metrics are at any point in time. And they know that when they see a sudden change in conversion rates or other success rates, they need to investigate why right then.
The vast majority of the ebusiness leaders that I talk to have invested in web analytics and/or other tools to give them a top-level view of the health of their ebusinesses and to stay on top of site trends. Web analytics tools do a great job of ‘slicing-and-dicing’—helping you to find the customer segment that’s most representative of a change. You can look at differences across specific products or product categories; new versus existing customers; geographic region; day of the week; where the customer came from (for example, from Google versus from a banner ad); and virtually any other segment that you define in the tool.
However, web analytics tools don’t tell you why customers in these segments behaved differently. That’s where a customer experience management solution comes into play—in supplementing this quantitative data with qualitative data for full customer behavior analysis. (Note: if you want to delve more into how customer experience management tools and web analytics complement each other and where they overlap, read the white paper “Customer Experience Management and Web Analytics: From KPIs to Customer Transactions” by Eric Peterson of Web Analytics Demystified, Inc.)
Also, in my experience the customer experience problems that are hardest to understand are ones that involve factors that the ebusiness is not tracking—and therefore not tagging for web analytics. No ebusiness can tag every component of its customer experience for web analytics; but it is the things that aren’t being tracked that are often the most likely to go wrong because no one is thinking about them at all.
Here’s an example. A major automotive retailer noticed a high number of abandonments on the last step of the checkout process but had no way to determine what was causing the problem with its existing site tools. When the company replayed a few of these abandoned sessions in Tealeaf, they recognized a pattern: no debit card user was able to complete a transaction successfully. Further analysis showed that its web application was not built to handle debit cards and their required PINs. Because debit cards were accepted in the company’s stores, they were automatically added to the list of payment options on the site. However, a form field and logic to accept PIN numbers had been overlooked. This is the kind of unanticipated problem that you can’t tag for; and therefore can’t be analyzed or even identified using web analytics tools.
To implement all of the best practices for investigating changes or differences in conversion rates, you should deploy both a web analytics tool and a customer experience management tool in order to get the full picture of what is happening on your sites and why.
Here are the steps that you should take:
- Define what constitutes a significant change to each of your key task completion rates by analyzing the existing benchmarks you have in place and define a process for monitoring these KPIs on a regular basis.
- Put in place processes for investigating any significant change immediately and to investigate any unexpected, significant difference in task completion rates between segments. Always ask why.
- Use your web analytics tool to isolate the difference to as small a customer segment as possible. Enlarging the percentage difference in task completion rates between segments will make it easier to identify the problem.
- Use a customer experience management tool to replay a sample of sessions in the problem segment to visualize the customer experience and look for unexpected behavior. (See my previous blog entry, “Where Do I Start Customer Behavior Analysis? I Have So Many Sessions!” for guidance on estimating the number of sessions to view).
- Look at the complete user sessions, not just the step where the problem occurred. Often, a problem occurs long before it results in an abandonment.
- After gaining visibility into the problem from replay, the qualitative data you see may give you insights on how to refine the problem. By searching for other sessions where the same thing went wrong you can refine problems with the type of variables that web analytics do not track, as in our retailer example above (searching for the type of credit card).
- Once you have insight into the problem and have refined it, quantify the impact of it. The impact of the problem should correlate with the overall change in conversion rate.
These best practices are how you turn your key metrics into action: you must go from which and where to discovering why.
-- John Dawes, Vice President, Product Management
