Avinash Kaushik (yes I think he’s pretty sharp!) mentions in his Web Analytics 2.0 book that for web metrics, you should focus on some “critical few” questions. If the bridge/platform is burning, what are the key things that can drive real action and offer the strongest results for the effort? This can be translated as well into an overall strategic plan. For me, it boils down to this, three questions that are customer focused, and a fourth that is internal to the business:
Customer-focused
What are customers looking for? Capture their search keywords, both external (organic search) and on your web site.
Can they find it? Web metrics will give you a pretty good idea here.
Does it solve their issue/problem? Feedback mechanisms; short surveys, ratings, track sharing, etc.
Internal-focused
Can we measure Service Request deflection and/or cost savings from implementing self-service and 1 to many strategies? The Holy Grail, the justification for the senior staff in your company for all your efforts. I don’t have a magic formula (yet), it must be a combination of measures to show the trend and likelihood, but difficult to conclusively prove.
So what do you think? What are your critical few questions?
I am working my way through Avinash Kaushik’s excellent latest book, Web Analytics 2.0 – the Art of Online Accountability and Science of Customer Centricity. I have been looking for a crash course in web metrics to quickly render me an analysis ninja, and this is definitely fitting the bill so far. He writes in a very personable style, easy to understand – highly recommended. Avinash also donates 100% of the proceeds to two charities, so deepen your knowledge while helping those in need!
One thing he highlights in Chapter 3 as he talks about different web metrics is Bounce Rate, which is when a visitor comes to a single page on your site and then leaves with no further interaction. He describes this as almost always bad, as the user is not interacting with the site. The one exception he cites is for blog posts, where it is expected that the regular blog reader will just go to the post, leave and then exit. He further mentions a way to review site exits is to contrast Bounce Rate (mostly bad) with Exit Rate, which is how many people left the site from a particular page (not bad or good, hard to measure why). If a Bounce Rate is low but the Exit Rate is higher, then in general users are just leaving from this page, but it is not strongly negative.
For those of us in Technical Support, however, both Bounce and Exit Rates are valuable metrics; if we have a Knowledge Base which is well-indexed by search engines, and the article is well-written to solve a particular issue (and has no other links), we would expect a successful article to have a high Bounce Rate. This means the customer who was searching for an answer found our article through web search, and it answered their issue. A high Exit Rate would show that the user was searching on our site for an answer and once again, found the article and left, problem solved.
Of course there is always the chance they became frustrated and just chose to leave, but in most cases I believe we can assume they would refine their search, looking for a satisfactory answer before giving up and leaving. This also highlights the need for KB articles to have a tool for customer rating and/or feedback.