Analytics awstats how to#
Analytics awstats code#

Analytics awstats code#

Most search engine crawlers and spiders do not run Javasript code and hence Google Analytics doesn’t treat them as website traffic while AWStats does.

From the server logs AWStats can generate reports and graphs and thus AWstats goes by the title of log file analyzer. They rely on passively tracking server logs - a single data source - to generate their metrics. AWStats/Webalizer on the other hand work on the website’s hosting environment.

Analytics awstats how to#

Again, this applies to a very small number of users as knowledge on how to opt out of Google Analytics tracking is very limited.

Also, users who have opted out of Google Analytics are not considered. If any user happens to have disabled JavaScript functionality or Cookies in their internet browser – which is extremely rare these days - their visits are not counted as the relevant code does not run to communicated with Google. User count takes place via the output code generated by combining the on-page Javascript with client-side Cookies. Google Analytics gathers information at the visitor/source level, by using a JavaScript code that must be placed on every single page you want to track.But the stats shown by them can differ due to the following reasons: Both give detailed reports regarding which pages are garnering the most visits, from which sources, at what times of the day, what the average visit duration is, among many many other things. In a nutshell, one can say Google Analytics is more user centric while tools like AWStats and Webalizer are used more to monitor and optimize server performance and speed of content & web service delivery. awstats allows a configurable stylesheet, making theming quite simple (especially if you just borrow from kogakure’s gitweb theme like I did.) The breadcrumbs are accomplished by using a form of str_replace('',$breadcrumbs) which is lazy but works fine.Īccessing the result requires SSL and basic auth credentials.Google Analytics and AWStats are both tools used to measure website traffic and related site visitor metrics, which can then be analyzed to optimized your digital marketing, user experience and server performance / content distribution strategies. My server also stores all of the “database text files in the same directory key by their subdomain, so I settled on a config.json file to specify which to process and how to map them to their actual domain name. With that sorted out, it was a short script to generate static copies of the reports, get the paths right for the assets (icons, css, etc) and putting them somewhere web accessible. Manually building the awstats reports was a bit tricky to figure out, as the nf files must be in the same directory as and the working directory must be the location of the script. I accomplished this first by merging the “databases” with AwstatsParser, then by generating static reports. Once they were summarized though, I needed a quick way to access them preferably without a CPanel session and without checking HTTP and SSL separately. After much deliberation, I realized that the awstat “databases” (text files) already had the required SiteVisit and SiteVisitor counts, so it was only a few lines of code to read and combine them. Multisite summary was something I craved. (SSL is also tracking separately from non-SSL, which was annoying.)

My server already stores access logs and processes them with awstats every day, but I found it painful to log into CPanel then check site by site. Themed multisite summary dashboard for awstats