I use Uservoice to manage tickets for Porthole, AirVLC and other Danger Cove apps. While doing helpdesk, I usually notice that some questions get asked more than once. That’s when I try to wrap the answer in a knowledge base article. First and foremost because it will help people out even faster than I can respond via email. Questions like: “Will this work on my Mac?” and “If I buy Porthole, how will I get it?” are perfect for a knowledge base entry. The answer is similar for everyone and it’s something that you want to know now, instead of in an hour. The huge downside however, is that I don’t get the chance to interact with my customer. This goes double for questions that have similar solutions for everyone, but when asked a lot might indicate an underlying problem that could be fixed in an update.
This means that when the knowledge base expands, I need a way to track how often each article is read. Seeing the amount of support calls drop (good), but not knowing when everybody encounters the same problem and silently discards your app (pretty bad) is a very uncomfortable feeling. Trust me. Uservoice has some built-in analytics that provide general statistics, but because I chose to show knowledge base articles on the product pages as well, I need something extra.
_gaq.push(['_trackEvent', 'Support', 'Open article_107729', 'article_107729']);
Or if you prefer to make the call inline.
<a href="#" onclick="_gaq.push(['_trackEvent', 'Support', 'Open article_107729', 'article_107729']);">Article title</a>
These events fire every time someone opens (or closes; I log that separately) an article.
What I end up with is a nice overview of which topics get consulted the most! This still doesn’t beat communicating via email, but it makes sure that I can at least determine where to focus my attention (and sleep at night).