Analytics Are Made Easy With Kolahawk.

To activate Chat, simply click the Chat Availability button on the right side of the main navigation bar. This button allows you to toggle between "available" and "unavailable." Master Accounts and Operators are both unavailable by default. To better visualize what a Chat Operator and visitor sees at any one time, see the Chat Status Cheat Sheet.

Keystroke Logging Limitations

Password field data and other sensitive data like credit card numbers  is never recorded or transmitted. No matter what. Even if you add the LoNotSensitive class name to a password field. Kolahawk has no need for others' passwords, and neither should you.

Note: Kolahawk also scans for certain input fields with names that denote their contents as potentially containing sensitive information, such as ccn, card-number, cvv2, etc. As with password fields, these fields are internally marked as sensitive, and cannot be overridden.

Kolahawk loads code asynchronously and defaults to loading after the load Javascript event fires on the page. This means that your page should fully load first and then Kolahawk will download the required resources and start running. So, Kolahawk should not slow down your site at all.

Some of our features such as Live Views & Recordings require sending data to our servers even after the page fully loads. These are also asynchronous requests and are sent in batches, but are required for the tool to be able to collect the data needed. However, these are sent in the background and do not affect the performance of your page or slow down the user experience.

Some page load time systems will include ongoing pings and make it look like your page load time is quite high. From the user perspective the page load time is the same as without having Kolahawk installed, but because we are constantly sending data, the other page load measuring systems (such as Pingdom) might show a much higher page load time.

Some other analytics tools (e.g. Google Analytics) might show a different number of live visitors compared to Kolahawk. If a visitor isn't being shown in the Live Visitors tab or in Recordings, it may be due to one of the following reasons:

1. The Kolahawk script can take up to 8 seconds to load. If the visitor bounces quickly, some analytics may pick up on this visitor, but Kolahawk will not as our code never had a chance to load. This will also prevent you from using a pageview on a visitor that did not provide any actions on site.
2. The visitor has blocked themselves by visiting our privacy policy and disabling Kolahawk tracking.
3. You have not placed the Kolahawk tracking code on ALL pages of your site.
4. An administrator has blocked the visitor's IP (Settings » Blocked IP Addresses).
5. The browser they are using does not allow for javascript to run.
6. The visitor is actually a bot, such as a web search engine. Bots are ignored.
7. They had some sort of add-on installed that blocked Kolahawk from tracking them.
8. The browser was too old to work with Kolahawk.
9. The visitor is on a page of your site that doesn't have the Kolahawk tracking code installed.