Session based pages

Some web pages rely on the visitor's session state to display the proper information or protect the content of the site.

Session state is the data your webserver keeps on each user. This data is kept internally (private) or in session cookies and is not accessible to ClickTale during the standard caching phase of the recording.

As a result you will see a different content during playback than expected (the login screen) or you might see a warning message saying that caching has failed (404 or 302 HTTP errors).

An example of such a site would be an e-commerce site where the cart page changes as a result of what the visitor decided to buy.

Another example would be a login to a "Members Only" section of the site where the authentication details of the visitor are stored as a session variable/cookie.


 * If you are using PHP you may want to use our PHP integration module which will solve this issue for you.
 * If you are using ASP.NET the ASP.NET integration module would solve this issue for you.
 * If you are using JSP the J2EE integration code will allow ClickTale to support JSP session state. Another option is the J2EE integration module. Please investigate both before deciding.
 * If you are using ColdFusion you may want to try our ColdFusion integration code.
 * If you are using Classic ASP you may want to try our Classic ASP integration code.
 * If you are using Ruby On Rails you may want to try the Ruby On Rails integration module.
 * If you are using custom cookies of your own with our FetchFromWithCookies API (not for HttpOnly cookies, as these are delivered by the server and cannot be fully utilized by javascript).

If you are using some other webserver/programming language combination you are welcome to port the samples and post them in the forum or contact support.

Another option is to use our API to pass various additional data(including static versions of the pages) to our caching process via the ClickTaleFetchFrom variable.

Finally, you can use the ClickTaleUploadPage method from the API to record the content directly from the client side. This option will put a small additional stress on the client side and is therefore less favorable if User Experience is a primary concern.