Every SST Web Design and Hosting customer has access to AWStats to view and analyze their web site traffic. Some customers also elect to have us install Google Analytics on their site for additional insight. What are the differences between AWStats and Google Analytics? One of the main differences is they generate their data using different methods, and each has its advantages and disadvantages. This is why they sometimes generate very different traffic results. Below are some of the reasons for this.
AWStats (AWS) uses log based tracking. Every time users perform actions on your website, the server records or logs details of those actions. AWS puts together log data into a meaningful format.
- It tracks things like PDF downloads, images, Flash files, and documents. GA can't do this.
- It tracks failed requests, which GA can’t do if the user aborts the page before it gets loaded. This is really important if you want to optimize your website.
- The data is on your server in standard format so you don't rely on a third party's (Google’s) server.
- If a returning user has file caching enabled on his web browser (usually the case), the request for the file he already viewed will not be sent to the web server and he will view a local copy. So sometimes AWS will not detect multiple visits, because a page drawn from a user’s cache may not result in an HTTP request to the server. This reduces the number of page views reported by AWS.
- A single page in a browser is frequently a conglomerate of several different files. These ‘include’ files are assembled invisibly via PHP, AJAX and any number of other web technologies. From the server’s perspective (which is where AWS gets its data) each of these requested files is a “page.” The server has no way of knowing that a client-side AJAX script is actually assembling the requested files into a single viewable page in the user’s browser. So AWS reports on every HTML (or PHP) file requested as one ‘page’. The end result is a vastly inflated number of “page views” in AWS.
- It only has the IP address (and HTTP_USER_AGENT data) to go on, and anyone behind a shared connection or forward proxy will not get counted as a unique user. Same for different users, each with a separate login, on the same PC.
It can report events that do not involve a request to the web server, such as Flash action scripts.
- AWS shows information that still needs to be interpreted into business value. GA attempts to communicate business value up front. The executive may favor GA reports over AWS reports.
- GA has a fantastic ability to collect data from inside the webpage itself. With careful configuration you can analyze form completion/ abandonment rates (plus where the form got abandoned). You can also define a ‘path’ through your website that comprises your preferred sales process, and look at entry/exit points along this path.
- User data is collected in real time, and this adds a small but often noticeable delay to the load times of your web pages.
- The bottom line is that it gets complex, and the only way around it is to make assumptions as to what constitutes a unique user or visitor, and simply accept that inaccuracies are inevitable. Google Analytics reads low, AWStats reads high, and that’s the way it is.
When you're ready to discuss your needs, please call your sales representative or Sidney McSwain at (800) 967-1412, ext. 225 to arrange a no-cost initial consultation.