This form (Settings -> Statistics) is used to customize the system-wide settings of the Statistics module.
|Time to send the next statistical report by e-mail||This field contains the time that the statistical report will be sent. Henceforward, the report will be sent on a daily basis at the specified time. If you leave the field blank, no report will be sent.|
If the site runs on a Windows-based server, the filed is blank by default. This is due to the Windows operating system peculiarity that protracts sending e-mail messages.
|On-line visitor interval||This field specifies the value that is used in the Online visitors subsection. This subsection displays sessions of visitors appeared active for the last N seconds. This field contains the value N.|
|Maximum number of records in tables||The Statistics module subsections display various tables containing the information retrieved from the database. Any retrieval is characterized by a number of the selected records. The more this number is, the more system resources and time is required by a server to accomplish the request and format the output. This parameter allows limiting the number of records and accelerating the process of building the statistical reports by specifying a reasonable value of records. If wish to avoid limitation, you can set any large value, for example, 100 000 000. As a rule, such values are rare to achieve, even if the site traffic puts a heavy load on the server.|
|Graphs weight||Width of graphs displayed in the statistical reports, in pixels.|
|Graphs height||Height of graphs, in pixels.|
|Pie charts diameter||Diameter of pie charts, in pixels.|
|Size of the TOP list in statistics summary||Number of elements (adv. campaigns, events etc.) displayed in reports on the Statistics summary form.|
|Size of the TOP list in the ad campaign detail view||Number of elements displayed in reports on the Advertising campaigns form.|
|Extra processing for visitors not accepting cookies||The Statistics module is capable of interacting with browsers or other software that do not accept inter-session or session cookies. This is achieved by storing the session data in a special table. The specific user (visitor) is recognized by applying a hash function (md5) to a range of environment variables peculiar to this very user. This flag allows enabling or disabling this feature.|
|Optimize tables when cleaning||The system automatically optimizes MySQL tables after it has deleted the outdated statistical information (fields Days to keep...).|
|Base currency (all the financial data will be stored in this currency)||If the Currencies module is installed, you can select a base currency for the Statistics module to store the financial showing. If the option Convert all financial showing is checked, all the values will be converted into a new base currency using the rate of exchange for the present day.|
You can protect your site from mass downloads by using this form. If you do not want your site to be available offline or just to limit the number of concurrent connections from a single IP address, specify appropriate values in this form. You can customize the PHP and HTML code of the page that is sent to a user in case the traffic limit is exceeded.
|Disable||If checked, the excessively active clients are blocked.|
|for||Period of time during which a client receives the HTTP error 503 (or other error specified in the template) in response to all requests.|
|if during the period of||A client must not make more hits than specified in the next field within this period; otherwise the client will be refused.|
|generated more than||Maximum allowed number of hits within the specified period of time.|
|Save the section and page traffic statistics||This flag enables or disables tracking the traffic statistics of the site sections and pages. This information is available in the Site traffic subsection.|
|Collect data for the "Site Paths" report||If enabled, the statistics module registers events and other information required to display the site path report.|
|Max path length to keep for this site||Maximum number of clicks to be kept within one path.|
|Important page parameters||Page parameters (those passed in URL as ?param=value¶m=value...) to be stored.|
|Use advertising campaign with referer1=NA, referer2=NA by default||Set this flag to apply a default advertising campaign to ordinary users that visit the site under no advertising campaign. The default advertising campaign has the following identifiers: referer1=NA, referer2=NA.|
|Automatically create ad. campaigns for URL'a with referer1 and referer2||If this option is enabled, and if referer1, referer2 are present in URL but no adv. campaign matches these parameters, the system creates a new campaign with these parameters.|
|Synonyms for referer1||This field contains aliases for the advertising campaign identifierreferer1. By default, the synonym for referer1 is r1 and referrer1.|
|Synonyms for referer2||This field contains aliases for the advertising campaign identifierreferer2. By default, the synonym for referer2 is r2 and referrer2.|
|Synonyms for referer3||This field contains aliases for the advertising campaign identifierreferer3. By default, the synonym for referer3 is r3 and referrer3.|
|Default event display mode in the advertising campaign report||The rightmost column in the advertising campaign report shows information on visitor events who hit upon the site under the advertising campaign. This parameter sets the default display mode if this column.|
|Wildcard for the browser UserAgent (used to automatically detect search engines as exceptions)||This field allows you to specify the UserAgent wildcards. All software reporting this UserAgent will be excluded from the Autodetect (see the Autodetect subsection). The wildcard allows the following operators:% - 0 or more characters; _(underscore) - any one character. If you specify the inexact UserAgent string, you should enclose it with the operator %.|
|Encode the event additional parameter||This flag enables or disables the base64-encoding of the events auxiliary parameter.|
|Short site identifier (used in the auxiliary parameter when loading events manually; without dots and spaces)||A short site identifier is used in the auxiliary parameter when loading the external events manually. This parameter had been introduced to allow distinguishing the auxiliary parameters of different sites, having these sites built with the Bitrix Site Manager CMS only.|
|Path to additional handlers for manual event loading||Path to the folder with scripts (relative to the site root) which can be used when loading events for CSV file preprocessing. Files from this folder are displayed in the Loading events form as a CSV file processors list from which a desired processor can be selected.|
|Referring sites and search phrases|
|Save the statistics of the referring sites and search keywords||This flag enables or disables tracking the statistics of external referrer hits, including search engines. This information is available in the Site traffic and Search keywords subsections.|
|Do not erase top domains from the referring||This field specifies the first N most active domains that will not be erased when cleaning the referring domains table. If set to 0, a common rule applies: the table is cleaned after the number of days specified in the field Days to keep the referring domains after the last visit from any domain occurred.|
|Save hits||Enables or disables storing addresses of the loaded pages. This information is available in the Visitor hits subsection.|
These parameters allow to specify the maximum period of time during which each event is stored. Each parameter field is equipped with the clear checkbox which, if marked, clears the corresponding piece of information upon clicking Save.
|Days to keep history of the section and page visits||Information on the section and page traffic (in fact, number of hits per section or page) is stored in a special table. This field specifies number of days that the table is cleaned after the last hit occurred.|
|Days to keep the site path dynamics||For each path, the system keeps path clicks for every day. These data are stored in a special table which is cleared after number of days specified in this field passed after the last click.|
|Referring sites and search phrases|
|Days to keep search keyword hits||Any visit under a search phrase is recorded in a special table. This field specifies number of days that the table is cleaned after the last visit of such kind occurred.|
|Days to keep referring page hits||This field specifies number of days that the referrer hit table is cleaned after the last hit of such kind occurred.|
|Days to keep each event||The Statistics module makes provision for the event types. The system stores all events, both internal and external, in a special table. This field specifies number of days that the table is cleaned after the event occurred.|
|Days to keep the event type dynamics||The system keeps the history for each event to store the number of events on a daily basis. This field specifies number of days that the table is cleaned after the event occurred.|
|Days to keep history of the advertising campaign visitors||The system stores the hit history of all visits under advertising campaigns. The history is stored in a special table. This field specifies number of days that the table is cleaned after the last visit.|
|Days to keep advertising campaign dynamics||The system keeps the unique history table for each advertising campaign to store the information on a daily basis. This field specifies number of days that the table is cleaned after the last event of any type occurred under this advertising campaign.|
|Days to keep search engine dynamics||The system keeps the history for each search engine to store the number of indexed pages on a daily basis. This field specifies number of days that the table is cleaned after the last indexing operation occurred.|
|Days to keep search engine hits||A hit of a search engine is the address of the indexed page. The system keeps the unique history table for each hit. This field specifies number of days that the table is cleaned after the last indexing operation occurred.|
|Days to keep the country-based dynamics||For each country, the system keeps visits and other information. These data are stored in a special table which is cleared after number of days specified in this field passed after the last visit from a specific country.|
|Days to keep visitors||Each visitor that hits the site is assigned own profile. All profiles are stored in a special table. This field specifies number of days that the table is cleaned after the last visit occurred.|
|Days to keep sessions||Information on the visitor sessions is stored in a special table. A session has a number of parameters; one of them is the date of the last hit within a session. This field specifies number of days that the table is cleaned after the last hit occurred.|
|Days to keep hits||The system keeps the unique history table for each hit, that is, stores addresses of all pages transferred to a visitor. This field specifies number of days that the table is cleaned after the last hit occurred.|
This tab allows to set parameters describing rules used to exclude certain visitors from statistics.
|Use the following rule||Defines the method by which visitors are excluded:
|User groups to be excluded from statistics||Information (hits, sessions etc.) on users who are members of the selected groups will not be recorded.|
|IP address range(s) to be suppressed||Information on visitors whose IP addressed match the specified IP
address ranges will not be recorded.|
This form allows to assign access permissions to all available site users except administrator who always has full access. By altering the default access level, you can easily change the access permissions for all users at once who have the Default level.
The form allows to assign the following permissions to site visitors.
|Default||Changes the default access level thus affecting all user groups that have the default access level.|
|[User groups]||Changes the access level.|
The form allows to recreate both the index and file with the IP address database used to lookup the country name by the visitor IP address. You can set the time slice in seconds (Step field), if the operation fails to complete within the assigned time on your server.
The form can be used to clean all the statistics tables, except for the search engine tables (counters only will be reset) and IP-to-country tables.
The form is used to optimize the MySQL tables of the Statistics module.
|© 2001-2005 Bitrix||Bitrix Site Manager - Content Management & Portal Solutions|