|
|
|
||||||||
|
|
|
||||||||
|
|
|
Site Log Analysis Case
Study
As mentioned before, the client's hosting company provides monthly server log reports created by a server-based WebTrends solution. Although we found out that the hosting company would change the default settings if asked, no one had bothered to do so. What a waste! A lot of very useful data was lost forever. Here are some tips you can follow for customizing your own server log analysis tool. Whether you use WebTrends, Analog, or any of the other useful tools out there, these tips are general enough to help you out, as well. Apply
Filters Wisely Any reporting tool worth its exhorbitant licensing fee will allow you to exclude "noise"-causing data from the reports. I recommend you set your exclusion lists to filter out at least the following: 1.
Extraneous files 2.
Inapplicable referrers Unfortunately, reporting tools aren't terribly smart. If the user is on one page in your site, then clicks on a link to any other page in your site, the reporting tool will count the first page as a referrer. So set the reporting tool to ignore any referrer URLs beginning with "www.yoursite.com". Be sure to add "yoursite.com" minus the "www" as, again, reporting tools are dumb. 3.
Irrelevant users Reporting
Numbers In addition to filtering out the bad stuff, you want to make sure you have enough of the good stuff. WebTrends, for example, only tracks the 10 most popular pages in your site by default. Well, what if your site is moderately sized with over 500 pages? A list of 10 popular pages would be way to short to do your forensics investigation much good. Depending on the size of your size, you might benefit from having your report list the top 100 or even 500 pages! Here is a list of the types of stats your reporting tool is probably capable of creating. For the modestly-sized consumer product site I studied, I would have customized the report for the next reporting period to include 50-100 items each.
Other Links in this Case Study
|
|||||||
|
|
|
|