Forum Moderators: DixonJones
For example:
User goes from page 1 to page 2. Server log sees the request for both pages. User hits the back button and returns to page 1. Because page 1 is cached the server doesn't see a request and so it doesn't show up in the server log. It does in my files because the tracking is done client side, not server side. I get 10-20% higher figures by catching this cached traffic.
Duration:
Server logs measure the time of a request. If a user goes from page 1 (5 seconds) to page 2 (10 minutes) and then leaves the site then the server log tells me that the session length was 5 seconds, because it can't measure the unload of page 2. Mine does, which gives me accurate duration data - priceless.
I could go on but I won't bore you ;-)
PS: I use Clickstream by the way.
This is especially important on development pages (and yes, I use noindex,nofollow), because development pages will mirror the Real Site, and you want to avoid want dupe content penalties.
Hosted tracking is tracking done by an ASP who hosts the enormous amount of data that can be collected for you. Typically, the data gathered by the tracking system (say an ISAPI filter or module on your webserver) is streamed or FTPed do the Service Providers IP address where it is ingested into a server farm for you. You then access your report via a web interface which you log in to.
Another option is to purchase software that will analyze your server access logs. I like doing it that way, myself.