Site Profiles

Tracker doesn't have a limit for the number of tracked domains inside one site profile. So in theory inside one site profile you can aggregate statistics for any number of domains and sub-domains.

However, this can prove to be inconvenient if you need to view the aggregated statistics of different sites and projects separately. For this you can use site profiles, which effectively are just containers for the aggregated data.

Site Domains

After a certain period of gathering statistics you may find out that the list of site domains contains some records of unknown origin or unwelcome nature.

These may be IP addresses of search engines, or your local domains that you use for site creation, or domains of sales systems on whose 'thank you' pages youve put a sales tracking code. And so on.

Therefore we advise you to enable the option "Gather statistics only for the selected domains. Every new domain which is not specified in the list of allowed domains will be ignored. You can make up your own list of specified domains on the site editing page.

Please note that If a visitor arrives from a referrer whose domain is registered as a domain of the current site, the tracker will not consider it to be entry from a referrer.

Removal of unwanted domains can be done on the company editing page, in the list of sites.

Please pay special attention to sales system domains (i.e. Yahoo store, ShareIt, etc). For the sales to be tracked their domains should be included in the list of allowed domains.

Cookie Domain

In the site settings you can specify on what domain the tracker should set the tracking cookies. It is important in case you use different tracking code types on different site pages.

For instance, you might be using Javascript tracking on, PHP tracking on, and Tracker itself is installed on

By default the tracker will set cookies without specifying a domain, and they could only be read back on in case of Javascript , HTML and ActionScript tracking types. In case of PHP tracking, the current domain will be, and the cookies could only be read back there.

Thus one and the same visitor may be identified as two different visitors in case he/she loaded pages with different tracking code types on different sub-domains.

In order to avoid that in the above scenario you should place '' (without quotes, with a point at the beginning) in the corresponding cookie domain field. Then the tracker will set cookies that could be read back on all the sub-domains of site.

Site Text ID

This option is added for your convenience and is especially useful when you integrate Tracker with various content management systems. In the tracking code you can use a text ID of the site instead of numeric one (if the text id has been specified in the site settings).

Instead of the variable nsSiteId in the tracking code you should put the variable nsSiteTextId, and the tracker will identify the site using the specified text ID.

More details on parameter settings can be found in the tracking code article.

Personal $79.95
Merchant $129.95
Agency $299.95