Administration Interface / Menu / Definitions  

Menu

Definitions

Sites

This menu allows you to define the sites you are going to get statistics on. You can add, edit, and remove sites. Each site can be added to a group. Site groups are used to apply a set of rules (access, parameters, marking) to more than one site. By default, each site belongs to the "default" group with ID=0.

When the ActiveStat scripts record visit information, they can add a site by themselves if such site hasn't been defined before. A name for the added site will be generated as "A/I.YYYYYMMDDHHMMSS", where "YY..SS" is a current timestamp. You can restrict ActiveStat from gathering information about unknown (non-defined) sites by setting the $stat_write_unk_site constant to 0 in the stat.cfg.php file. In this case you will have to explicitly define a site to start gathering information on it.

By default, the ActiveStat is configured in a way that the application is used on a single site with ID=1 assigned.

You can delete a site and/or the information on it using the "DB Maintenance/Delete Info" menu item.

Actions

This menu allows you to administer actions to be tracked on your sites. A feature can be any event (e.g., a user's click) you want to give a name to and then get statistics on. If you define some "action name", an ID will be assigned to it. Then, if you decide to track the action, you'll have to use the given ID. For example, we've defined two actions: "Search1_(home)" - search feature usage on the first page of the site, "Search2" - search feature usage on the other pages:



Having added the actions, we get their IDs: 1 and 2 respectively. Then we need to embed the sslogres() function calls to gather statistics on the actions:

<!-- track search option 1 using its ID -->
<a href="search.php" onclick="return sslogres('ssfn', 1)"><img src="/search.gif"></a>

<!-- track search option 2 using its NAME -->
<a href="search.php" onclick="return sslogres('ssfn', 'Search2')">Search</a> now!

Now we can get reports on our "actions". For example:



Then we can group both searches to get summary information on search usage, or, if we had other "actions", we would be able to filter by "search" group to compare the two searches to see which search feature was more usable.

You won't be able to remove an action via the menu if the database already contains statistic information on it. To make sure the removal is available, you need to delete the referring information (mark rules, visits) first.