Forum Moderators: DixonJones
That said, log files on their own can't answer some important questions people want to know - Flash support, screen size, etc. And their ability to track user sessions depends on how good your analytics package is, and whether you embed session cookies in your log files. That's why Javascript-based page tagging exists - to enhance (not replace) log files.
Bottom line, it's not an either or situation. You'll always have log files. Javascript-based page tagging just enhances those log files - they put additional information in them that your analytics package can use to better digest the log file. If you use an external service like Google Analytics the extra information is put in their log files, not yours - but one way or another it's being put in a log file somewhere.
Log files, report, accurately, requests to the http server. And that is ALL.
In simple terms, most companies use a router between their LAN and the Internet. So while every work station in the company has its own IP address, this IP address is local. To the Internet, all stations go through a single router with its own, single IP address, presenting to destination web sites requests (if they get that far and don't get handled by ISP caches along the way) of requests made by a single IP address, which many misleading packages reveal as a single user.
With complex cookies you can do some tracking of run-of-the-mill users, but technicaly savvy users may disable cookies or even delete them during a session, so again results are not to be relied upon.
Matt
Read the library thread [webmasterworld.com...] for more info.