Webalizer vs. Google Analytics

Has anyone noticed a difference between webalizer stats and google analytics?  I am finding significant varience between "unique visitors" in webalizer vs. google analytics.  I undertsand that webalizer is parsing log files, whereas google is being passed info via a script.
Who is Participating?
cogboxerConnect With a Mentor Commented:
With Google Analytics visitors with cookies disabled will not be tracked. Because Google Analytics uses first party cookies (cookies set and read by the same domain currently shown in your address bar) the number of real users that will block these cookies is small. And, at the same time this prevents Google Analytics from tracking visits from automated spiders and other systems that don't interpret JavaScript.

Webalizer will show all requests of the server recorded in the server logs. It doesn't actually interact with the browser at all. One benefit of this is that you can see how often certain elements of a page have been accessed--such as particular images, css files, PDFs, includes, and other non-page elements.

Whether Webalizer or Google Analytics would be lower would depend upon the assumptions set up in Webalizer. Personally, for a figure like unique visitors, I think Google Analytics will yield the more accurate figure.

I've found that clients can often find it frustrating when you can't give them a very simple "we generated X unique visitors to the site last month". So, I would pick a standard that you will rely on, then whenever possible implement that tracking tool early in any design/redesign/marketing process. Your before and after stats will be comparing apples to apples.

Here's a Google Analytics page that discusses this issue:
PhilHowConnect With a Mentor Commented:
Unique over what period of time?  24 hours?, 10 days? 30 days?

Are the time slices calculated form the same time zone?  It the GA code on every page (it won't report 403, 404, or 500  errors as a hit unless you have custom error pages with the GA code.  Webalizer reports everything in the log.  There are many other variables.

The changes of getting the same result from both is just about zero.  They are two totally different approaches to stats generation.  Comaring them to confirm trends is about the only reconciliation that is possible.
tmateosian1Author Commented:
I'm not looking for the exact cause, nor do I expect them to match, but rather looking for the reasons they can vary.  For instance I know that some script blockers will cause the GA script to not report.  Good call about the 403, 404, 500!  Please list as many *possible* reasons as you can think of.  Thanks.
Webalizer, being a log file analyzer, has to make certain assumptions about what is actually a unique visitor using time of request, IP address, UserAgent (browser, OS) etc.

Google Analytics, being a web-beacon type tracker, can actually cookie individual visitors, giving a much better "unique visitor" number. So, it's not surprising that they have significantly different numbers.
tmateosian1Author Commented:
Yes that's a good point.  What happens if someone has disabled cookies?  I guess what I'm getting at is that webalizer provides a more favorable (i.e. higher) figure and I am looking for ways to explain the difference.  SO far I have some reasons why GA would be lower, and also some reasons why GA would be more accurate about uniqueness for those visitors it can track.  
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.