Practical Analytics
Often when reading blogs and articles on web analytics there is lots of use of the term "Actionable". Well I'd like to talk about something else. Something that should please the developers in IT that support your site and just maybe help to improve what can sometimes be a tenuous relationship between IT and Marketing. Practical Analytics.
What does Practical Analytics mean? Here is my spin on it:
Practical Analytics is the process of using web analytic data to help guide infrastructure, features, and support of a web site or web based application.
Really it comes down to makes changes on your site that make it easier to manage and maintain, not necessarily changes that make it a better experience for the end user of the site itself. The data used to make these changes is not hard to get to, nor does it require any deep analysis. Most of the time it is data contained in the most basic, canned reports available in almost every tool.
So what? Well as a career developer, I can not tell you the number of times I would have killed to have had the type of usage data I have now to not only help guide change, but to be able to use this data to help convince the HiPPOs out there that these changes needed to be made.
This is extremely important to me right now, as I am knee deep in a major redesign effort. As part of the planning process for the redesign there have been countless decisions made based on analytic data we had, and over the next few blog posts I will be highlighting some of my favorites.
Practical Analytics: Use Case #1 - Kill the old, tired, busted, outdated pages.
I am sure this is hardly news to anyone, but as a company constantly adds content to their site to keep it fresh and current, there is often a multitude of old outdated pages that never quite seem to get deleted. Perhaps the thought is that they need to be kept for SEO, or someone may have a bookmark to the page, or more than likely a new page version with a new name was published and the old file was never deleted.
So use your web analytics tool of choice and pull a list all the web pages with any traffic at all for the last six months. The most basic of reports. Then get a list of all the files currently on your server. Apply a little excel magic and you will get a list of pages on your site with zero traffic in the last six months. These are the first ones to go, no one will miss them at all.
The next step would be to look at the ones that are really lagging far behind. This will take a bit more time to go through that list and see if these pages need to go, or need to be improved. Either way, you have made the maintenance of your web site a bit easier by removing the pages with little or no traffic.
If you are truly concerned about users that might have a bookmark to one of those old pages, then you could easily modify your 404 process to send users to a search results page or some other custom 404 solution.
This is simply one of many practical applications of analytics data that will not only help you clear out old content, but should make the overall task of site maintenance easier. This should please even the most obstinate of curmudgeon developers out there!
Review: User Driven Change – Give Them What They Want
A few months back I was lucky enough to get a copy of "User Driven Change: Give Them What They Want" by Carlos del Rio & Jeff Noethen. When it arrived I set it on a stack of other books in my ever growing pile of books to read. To be honest I had forgotten about it until I received a nice "nudge" on twitter asking what I thought of the book.
Well, I finally got around to reading it. I was blown away! Not only was it a nice fast read, but the information was broken down in great examples. The book starts off with how to make a site quick to use and engaging, and breaks that down into the following points:
1. Site Speed
2. Short Action Process
3. Intuitive Design
4. Clear Messaging
5. Compartmentalization
6. Third Party Integration
Impressively, the authors take their own advice and apply most of these points to the book, making it both quick and engaging!
1. Site Speed: The book is only 130 pages and can easily be read in one sitting, although I am sure that I will be re-reading it with a highlighter and note pad in hand. It does not get bogged down in useless information.
2. Short Action Process: With each section of the book, there are examples/suggestions to put the topic into action on your own site.
4. Clear Messaging: No fluff. Straight to the points and to the real meat of the content.
5. Compartmentalization: Each section is broken down into small items that can be taken and used on small sections on your site or as part of a larger project.
While this book is not written for someone new to the measure space, there are great insights in this book than can be leveraged by people at all skill levels. After reading through a few very technical books, it was nice to have a light, quick read that is still packed with useful information in an easily digestible format. I would recommend this book to anyone looking for more insight on improving the site experience for your users, and I am looking forward to their next book!
Jive + Omniture + Automation = Happiness
I am a true believer in automation, so the last thing I want to do is create a process or work flow that I or someone else has to baby sit. When I began working on a project to see what type of data I could get from Jive, an online community application, and into Ominture I wanted to make sure that the solution could be automated.
Before we get into it, there is a key point I want to make about the data. The data base that you get from Jive is not your typical clickstream data set. It is an activity database. You will not get pagenames, or visitor session information. What you will get is an activity logged for everything a users does on the community site. Views/creates/modifies a thread, blog post, question, poll, etc.. If the user is logged in, you get their user id, name, etc.. If the user is not logged in, they all show up as a single user. Even with this limitation, there is still plenty of useful data to be found.
Why I joined the Web Analytics Association
Recently in the great twittersphere there has been a lot of chatter on the value of a Web Analytics Association (WAA) membership. After thinking on it for a few days, I wanted to offer my my 2/5's of nickel on why I joined the WAA and what value I have received as a result of joining.
Let me start with saying that I think true value of a membership in the WAA, or any user group like this, is dependent on what you are willing to put into it. Membership is not a passive experience. My personal goals in joining the WAA were:
- Education
- Networking
- Collaboration
Education:
As I become more and more immersed in the world of analytics, I am constantly looking for way to expand my knowledge. As part of this process I wanted to be able to participate in the WAA committees, forums, peer reviews, webcasts, etc.. Being able to join the committees and not only participate in the discussions, but to learn from the experiences of the other members of great value to me.
Networking:
I love being able to interact with others that are passionate about web analytics. To share experiences, challenges, failures, and successes and to build relationships with others in the industry is great. It is true that this can be done without the WAA, but for me, it has opened up another set of people to interact with that I had not yet, or might not have the had the opportunities to.
Collaboration:
The developer in me loves standards. Love, love, love, love... Standards. So the opportunity to be part of a group/committee that discusses and helps shape those standards is a very exciting offer. I am still getting my feet wet in this area, but I look forward to becoming more active in this area.
Based on these goals alone, I do feel that I get a great value for my membership in the WAA!
There are other great groups and projects out there, like the Analyis Exchange where you could accomplish these goals, but I do not feel that participation in one group should preclude you from participating in the other. I love talking about analytics with whomever will listen and through these conversations, this engagement, and healthy debate on ideas true innovation happens. There is something great about taking an idea and throwing it out for the world to see, comment on, and mold into something new.
IQWorkForce Interview
I wanted to take a moment and say thank you to Corry Prohens, President of IQWorkForce. A few weeks back I had the opportunity to talk with Corry about staffing related issues in Web Analytics, when he was a guest on the Beyond Web Analytics Podcast.
Since then IQWorkForce has launched one of the most engaging facebook fan pages I have ever seen, and just this week I was asked to be interviewed by Corry about the Beyond Web Analytics podcast. I jumped at the chance! I have to admit that I am really geeked out seeing the interview posted. So thank you Corry, for not only being a guest on the podcast but for the interview as well!
To read the whole interview, which I highly recommend
, visit the IQWorkForce site.




