Advanced Setup

The Advanced Setup section allows you to fine-tune the definitions of the dataset.

Alternate domain names for web server: Enter each of the domain names or addresses that may be used to access this website. E.g. www.domain.com, domain.com, 127.0.0.1.

It may be accessed by SSL (i.e. https protocol), enter that as well, e.g. https://www.domain.com.

Server Side Scripting: Select the scripting language used by your website, if any.  If your site is flat HTML or a scripting language not listed, select 'none'.  If your site uses more than one of the listing scripting languages, select the one that is most predominant in the site.

Default Pages: Enter the Default Pages used by the web server when only a directory is specified, not a particular page. e.g. index.html, default.html,

index.php, etc.

Case Sensitive URLs? If your web server is running on an operating system that distinguishes between filenames where only the case of the letters is different (i.e. upper-case vs. lower-case), you should select Y.

Microsoft Windows™ is not case-sensitive, but most other operating systems, including Unix™ and Linux, are case-sensitive.

Case Sensitive URL Parameters? If your scripting technology (e.g. PHP, ASP) distinguishes between two URL parameters values when the case of those values is different, select Y, otherwise select N.

What URL parameter is used to distinguish between different links to the same page? If you have the same link twice on one web page (e.g. Contact Us at the top and bottom of your page), you can help ClickTracks™ distinguish between the two by adding a "dummy" URL parameter with different values for each of them. This parameter should not be used by your system.

Session Tracking: Choose whether you will use 1st Party or 3rd Party cookies to track customers through your website(s).  Using 1st Party cookies has an advantage in that you don't risk security issues, such as browsers or adware checkers blocking the cookies.  When set to 1st Party, cookies dropped by the JDC are considered to be from the same source as cookies dropped by the main website itself.  This is generally the preferred setting.

If you host your JDC on a separate domain (e.g. jdc.domain2.com vs. www.domain.com since 'domain' is different from 'domain2'), you can not use 1st Party cookies.  The typical scenario for this is that you are using the JDC to track a large number of different websites.  Another common scenario is that a given website uses a third-party site (with a different domain) for doing something like ecommerce transactions.

Note: choosing 3rd Party Tracking + 1st Party Cookies tracks your customers with 3rd Party cookies, but also records your 1st Party cookies for analysis.

Enable Exit Tracking? With Exit Tracking enabled, the JDC will add JavaScript that will track where your users go when they leave your web site. This information will then be displayed within the Browser View of the Navigation Report.  Any links on your website that go to an external website will have the overlay bar with the number and percentage of visitors who left your site for this external site.  With Exit Tracking turned off, you will only see a bar with the word 'External' on these links. 

Enabling exit tracking will make the JavaScript code load slightly slower, but it a matter of a few milliseconds of load time, so it shouldn't affect your page performance or accuracy.

Note: test this carefully with your existing JavaScript to make sure there are no unintended effects.