About Demo Documentation Downloads Links Thanks Wishlist
 
 Your stats
browser :unknown
major v. :
minor v. :
OS :unknown
OS vers.:
country :unknown
language :unknown
 News & Releases
I've just released the third beta of the core package. This version fixes one small bug (reported by Ben Hines) in OmniWeb browser detection. If you already use phpWebStats, then simply run this patch (one SQL command).

As I've found a short time ago, some design changes will make many features possible and some actual features much faster. So I've decided there won't be any final version right now, rather small bugfixes to the existing betaversion.

These new features are for example - actions logging, OS and arch presumptions, much better referer stats, etc. You can see the details in the wishlist.

Do you miss some feature? Have you just found a bug in phpWebStats? Do you have some recommendations? Contact me! (e-mail: dracula007@atlas.cz, more contact options below)
 Project stats
total clients in db : 0
search engines : 0
mail collectors : 0
countries : 0
languages : 0
 Contact details
ICQ: 69663249
e-mail: dracula007@atlas.cz

Welcome,

you've just entered the site devoted to phpWebStats, an Open Source (GPL) project, based on PHP and an arbitrary SQL database (at present only MySQL is supported, but it should be really easy to add support for different SQL databases with regular expressions support), whose objective is to develop a web traffic statistics package.

There are two main goals of this project. The main purpose is to collect as much information about the traffic on your site as possible, and these information should be available on the fly. There are several excellent packages that do the same thing by analysis of the log files (for example AWStats), but these packages have several disadvantages from certain point of view:

  • You need access to web server log files, which is not possible on most freewebs and cheap commercial services.
  • These information are not available at runtime, so you can't use them when sending the pages to the clients.

This project should solve these problems, because all you need is PHP and MySQL support, which is a common configuration even on freewebs. The information is available on the fly, meaning for example you can customize the pages by the browser (you can use different CSS style sheets/Javascripts for different browsers, block mailcollectors, etc.) And furthermore the installation is pretty simple - in fact all you need to do is to

  • run two SQL scripts to create the database structure and import data
  • set the database information (host, user, password and database name)
  • include the correct library (.php ) into your script and set database information
  • assign an unique IDs to visitors
  • call one function that does all the logging

Sure, on the web there's nothing you can trust absolutely. The client can provide you incorrect or incomplete information (the client can modify it, not to send you some optional information, some sort of proxy or anonymizer can be used, etc.), in which case you won't get correct and/or complete information. And of course usually it's impossible to detect which of the users sent you correct information and which of them don't. But hopefully overwhelming majority of visitors will give you correct information.

The package is divided in two main parts - the core and the visualisation part. The core is the main part which identifies all the important information about the visitor, does all the logging, and provides methods for retrieving RAW data from the database. The visualisation part does the presentation - shows the data retrieved by the core as a chart (line, pie, 3D,...), as a HTML table, simple text etc.

Actually the package is made public as a beta version, and should give you the following information (if available):

  • client (browser/search engine/etc.) name and version (major and minor)
  • operating system (including version if available), architecture (x86, Power PC, etc.)
  • is it a search engine?
  • is it a mail collector? (so you can block it, if you want)
  • country (the client is connecting from)
  • preferred language (set by the client in the browser)

You can find much more information in the documentation.