June 25, 2005
Web Reporting is More Than Page Views and Visits
For the longest time I've been wanting to put together a better set of reporting for the websites I build. I, like many others, have been a slave to page views and hit numbers, knowing that there was more to the site than these base stats. The "big project" forced me to dig much deeper than I have before, and look to resources on the web to create a better web report.
Eric Peterson Leads the Web Designer to Water
I've read numerous posts, articles, and ideas on how to start gauging return on investment, but all have been theory or just vapor. That is until I found a wonderful book with a horrible title "Web Analytics Demystified".
Once you get past the corny title, you find a very succinct review of:
- Web traffic reporting tools
- Typical types of reports
- Best of all, how. He presents a litany of possible Key Performance Indicator (KPI) metrics to create statistically valid gauges on website performance, and how to put them together
Finally a "how-to" book! I was thinking "Great, we'll read the book, get our statistics in-line and we're done!" Of course, things are never as easy as they look.
The Really Real World of Wildly Scattered Data
Shortly after reading the book, we started investigating how we could put these reports in place. We already had WebTrends OnDemand but found that we needed more data than was available in our trusty statistics program. So we started listing out all the possible points of data (here are a couple of examples):
- Our sales data had to come from the mainframe because not all of our sales are processed online
- WebTrends OnDemand can't track exception reporting all that well so we're reliant on our trusty old log analyzer for that and other server-based data
The list actually goes on to about 7-10 possible datasources and no easy way to consolidate them except manually. We still haven't figured out how to solve this problem but we are trying to make up for some of it by automating as much of the data gathering as we can.
Not Everyone Wants to See All Your Stats
Try putting a bunch of numbers depicting visits and pageviews in front of most business managers and you'll get a blank stare, or worse they will equate those numbers to sales. To tell the true story of web performance you need to go back to the basics: the goals and objectives for the website.
When setting out the objectives for your site you should have been wording it in a way that qualifies it for measurement. Instead of "Increase traffic to the site" it should read "Increase searches on the website that convert to sales". Get to what you want your site to do, then figure out how to gauge it. These are your key performance indicators.
To tell a complete story, you need to consolidate the following into a compelling story:
- Research and Surveys (how users perceive your site)
- Usability Test reporting (how users actually use your site)
- Data on traffic and usage of the site
However, it takes a lot of time to pull all this information together, so for more frequent reports its best just to compile key metrics into a quick report. Again the book came to our rescue by providing a wonderfully simple format, KPI Worksheets. Using these handy little sheets, we can now put reports together quickly and in a language that is much easier to understand.
Still Going
And that's how far we've gotten. The team has put together our first monthly report and are working on our second. Its taking time figuring out how much we can automate and schedule, but its really coming together and for the first time in my career I feel the report I'm handing to my boss really means something.
- Posted in:
- Business of Web

Comments
1
Xavier Casanova:
7 to 10 sources... that's ugly. Good luck with your KPIs and if you have something to share, please shoot!
Posted: June 29, 2005 at 11:45 PM MT