The Tracker does lots of work behind the scenes automatically. It prepares the requested reports, archives the reports, removes the old statistical data, renews the visitors geo data, browsers and operating systems data, processes the tracking requests that were logged when Delayed tracking was enabled.

We strongly advise to setup the cron script right after you finish the tracker's installation.

When a user requests a report in Tracker and decides to add it to the preparation queue – the report will be prepared as soon as the command line script will launch again on the server. That’s why it is preferred to launch the script with smaller intervals.

The cron script setting will require your skills of server configuration (or presence of a person who knows how to configure your server).

It is not enough just to check the “Enable the cron script” option in the settings. It is also necessary to add a record to the crontab of your server (if it is Linux, FreeBSD or any other Unix-based server) or setup Scheduler in Windows.

Setting up Scheduler on Windows might be challenging but without it Tracker will be rather restricted in its capacities.

It is necessary to setup the script intervals so that it is launched every minute. It does not mean the script will do something every minute, since it has built-in logic which decides if any new tasks have to be done. But if the script is launched every minute it has the best chance to do all the new tasks in time.

In the section “Administration / Cron Settings” you will find the line to be added to the crontab. However, the line may differ a bit for your particular server. In the very beginning of the line there is a 'php' command which tells the server that it is necessary to launch PHP interpreter. It is possible that your server needs to have '/usr/bin/php' or similar command instead. Please consult your system administrator if the default suggested line doesn't work for you 

On the same page you can see if the cron script is enabled or not. Under the main program menu you will find a message “The cron script was last launched at…”

The second important setting is “Maximum CPU Load”. Based on this setting Tracker will be taking care of not overloading the server by its operations. And if the load exceeds the specified value,  Tracker goes to a sleep mode for a while, until the load is below the critical level again. This works for all processes – Caching, Archiving, Old statistics removal, XML libraries processing.

The load limit you specify depends upon your server. We advise you to use the value equal to the total sum of processor cores of your server. That is, if you have Dual Xeon, for example – put “2” in the form field.

It is also possible to set the load limit on Windows servers. You should install the free of charge package LoadAverage that gives an opportunity to see average load parameters in Unix style on Win32 systems. 
In the corresponding field you should specify the complete path to GetLoadAvg.exe, so that Tracker could run the program and get the current load information from it. Path example: 'C:Program FilesArkane SystemsLoad AverageGetLoadAvg.exe'.

You can also specify the time of day when the cron script should better not be working. It will be launched but will not perform any tasks.


For the command line script to work properly, it should be executed with PHP working in a CLI mode (command line interface). Depending on your version of PHP this might require using a special PHP executable (php-cli.exe, cli/php.exe, etc). Please refer to the documentation on the PHP site for the details related to the version of the PHP installed on your server (the location of the PHP CLI executable differs in different versions of PHP as well as on different platforms):

Alternatively, you can ask your hosting company about the exact location of the PHP CLI executable on your server.

You can check if the php executable that you are currently using is a CLI version by running it with a “-v” parameter like this:

php –v

or like this:

/usr/bin/php –v

The output should look similar to this:

PHP 5.0.5 (cli) (built: Jan 5 2006 16:25:09)
Copyright (c) 1997-2004 The PHP Group
Zend Engine v2.0.5, Copyright (c) 1998-2004 Zend Technologies

If you will see “cli” in the brackets immediately after the PHP’s version then you are running a CLI executable – just what you need! If, however, you don’t see “cli” in the output then you are running a wrong PHP executable and you need to find its CLI version.

The main advantages of PHP CLI:

  1. PHP doesn’t output any default HTTP headers (which do not make any sense when the script is run from the command line).
  2. Several limitations from the php.ini file are ignored, like max_execution_time, for example. If you will notice that the command line script fails to finish the work and is killed by PHP because the maximum execution time configured in php.ini is exceeded – then you are NOT using PHP CLI and should correct this.


The cron script logs its operations.  There are three types of logs available to you:

  1. Report preparation log
  2. Statistics removal log
  3. Statistics archiving log

In each of the three you will find useful information about Tracker operations in a background mode, how long they took and what the server load was.

Cron Processes Monitor

Starting from version 3.0.1 there is a special tool available to you that monitors background processes. The list of processes includes all the cron script runs no matter if it performed tasks or not.

There is a button “Complete” next to uncompleted processes. By pressing it you’ll force the process to finish. If the process is really running, indeed, it will stop as soon as it completes the current operation. If the process has already finished (probably with an error which caused the process to be still marked as uncompleted in the log) then within five minutes such process will be marked as complete automatically.

Personal $79.95
Merchant $129.95
Agency $299.95