Architecture of Version 5.x
   

The ClickTracks Server component is a Windows service that runs on a machine dedicated to retrieving/downloading logfiles from one or more web servers. The usual method for this retrieval is FTP; however, the software also supports reading physical files from the file system over the network or locally on the same machine. The software uses a schedule to determine when to make a connection and begin the process of downloading and processing the remote logfiles.

After each file is downloaded and processed, the result is a normalized .NLF logfile, which is then written to the dataset folder. The dataset folders can be located either on the same machine or elsewhere on your network. The dataset folder is where the ClickTracks Professional client will access data. In a typical case, the dataset folder is located on a shared network drive, making easy access for ClickTracks Professional clients running on other computers. Other data access methods are direct HTTP or HTTPS from the same machine, or data can be mirrored to another server, typically a remote web server, again for clients to access. (See Mirroring Data to Another Server.)

Analyze on Server (v5.1)

The concept of Analyze on Server was introduced with the ClickTracks Server (v5.1). It was designed to take the burden of the log data Analyze phase off the client and put it onto the server. This option can only be enabled or disabled at the server. You can select Analyze on Server when creating a new dataset, in the New Dataset Wizard, or later when setting the properties of an existing dataset.

After the ClickTracks service has completed processing the logfiles and created .NLF files, a second phase of analysis and visitor counting (auto-analyze) will take place. This phase, which is started by the server, processes the dataset's existing and new .NLF files and generates .BIN files ("refined" data files) per day of data. The Pro Client can then use these files directly for further analysis and reporting. (See Analyze on Server Processing.)

The server administrator can then configure this dataset (by clicking on the green icon next to the dataset) for all clients to receive global labels, import campaigns, and configure revenue. (See Configure Client - Analyze on Server Datasets.)


JDC Dataset Support (v5.1)

As of version 5.1, the Pro Server can handle JDC datasets from the ClickTracks Hosted service. A configuration can be created to retrieve the JDC dataset from the hosted machine and make this data available to desktop client machines, just as is done with any other server dataset. (See New JDC Dataset Wizard.)


System Overview Diagram



clip0032


The ClickTracks Server can read logfiles from multiple web sites, load balanced servers and multiple subdomains.


The major user configurable components of the Server UI are:


Datasets

Datasets represent the top level configuration layer of the ClickTracks server. A dataset will be configured to define the base properties for the server which include a descriptive dataset name, the local location of the stored data, the server polling frequency, and scheduled start time. A dataset can contain 1, or more, domains, which define the properties of the web site.

Additional dataset properties are:
 
Dataset Mirroring  
 
The ClickTracks server can replicate the current dataset to a remote FTP server for access by other ClickTracks Professional Client applications that may not be able to access the dataset via a file system, or network share. The ClickTracks Professional Client will use FTP, or HTTP/HTTPS protocol to access this mirrored dataset.  
 
 
Cookie Tracking  
 
The special cookie tracking option should only be enabled when your site is using persistent cookies, and you wish to analyze data for ad campaigns. When this option is enabled, the ClickTracks server generates additional data files used by the client software. It also takes additional time and memory for the server to process the logfiles.  
 
Url Pruning (v5.1)  

URL Pruning is a way to have the ClickTracks Server delete a portion of a URL which you don't want to analyze. This feature can be useful to normalize various URLs in your logfiles. It can delete a fixed string or a regular expression portion of a URL  


Domains

Domains represent the secondary level of configuration of the ClickTracks server. A domain will be created under a named dataset and will define the properties of the web site. Depending on the structure and function of your web site, 1 or more domains can be defined under a dataset. In turn, domains can contain multiple web servers.


The Domain properties are:


General Properties

Case Sensitivity  
 
This property tells the server if the files on the web server are case sensitive or not. UNIX web servers are case sensitive so the page index.html and INDEX.HTML are different. Windows web servers are not case sensitive and treat all pages without regard to case.  

Server Scripting  
 
This property tells the server what server-side scripting technology the web server is using.  


Advanced Properties

File Inclusions:  
 
Include only certain directories when processing logfiles.  
 
File Exclusions:  
 
Exclude certain directories from the Included directories.  
 
Host Exclusions:  
 
Host IP addresses can be excluded from the logfile processing.  
 
URL parameters are case-sensitive  
 
This property will inform the server to treat URL parameters with case-sensitivity to differentiate between them.  
 
URL parameter used to distinguish between links on the same page:  
 
This property defines a particular parameter that can be used to differentiate between multiple links to the same page so that a user can see the differences in clicks to the links.  
 
Default pages  
 
This is the list of pages to treat as a default loading page when a web browser opens up a directory name.  



Web Servers

Web server represents the lowest level of configuration of the ClickTracks server. The web server configuration will tell the server how to retrieve logs, and which logfiles to process. One, or more, web server configurations can be defined under a domain.

Logfile Retrieval Method - Logfiles can be retrieved by either the FTP protocol, or from a local file system, or network share.

FTP  
 
Logfiles are downloaded via the FTP protocol from the remote server. A valid set of FTP login parameters are required to use this method.  
 
File System  
 
Logfiles are retrieved from a local file system, or network share directory for processing.  
 
 
Logfile Settings
 
 
Logfile directory  
 
The directory name on the FTP, or file system where the logfiles reside.  
 
File exclude mask  
 
Use this file mask pattern to exclude files from being processed by the server.  
 
File include mask  
 
Use this file mask pattern to include only the logfiles specified to be processed by the server.  
 
Logfile index of Server IP:  



New Dataset Wizard