Replay Technical Details

Details on data transfer and replay architecture

This article provides a high-level overview of how Replay data is captured, compressed, and transferred to ForeSee servers for processing to create the Replay movies in the CX Suite.


1. SDK Execution

The SDK code is executed in the browser and on ForeSee servers. So the flow of activation starts with the Web SDK running in the browser during the client experience. Data is stored within the browser during session capture in either or optionally session storage. All information is spooled until a trigger condition occurs that causes the data to be released to the ForeSee servers.

ForeSee does not otherwise transmit information to a clients server, nor does ForeSee need to run anything on a client's infrastructure. ForeSee code is loaded on the web page and this is sufficient since all of the capture and transmission logic is in the browser.

ForeSee uses both AJAX requests and Web Beacon requests to send this data from the client browser directly to ForeSee servers.

2. Triggers

The trigger is either an accepted invitation or a feedback badge click. Data continues to be sent to ForeSee servers from that point on until the end of the browsing session. Data transfer typically happens on page unload or once a message size hits a memory limit. This triggers a chain of processing of the data on ForeSee servers.

3. Masking & Asset Collection

All data is censored in the browser for sensitive personal information prior to transmission to ForeSee servers.

On the server side, most of the data required to reproduce the session is contained in the data sent from the browser directly to ForeSee's servers. But ForeSee needs CSS and image assets, which is retrieved in the traditional way with HTTP Get requests to your servers from ForeSee servers. All this information is stored in the cloud.

4. Movie Creation

Currently, ForeSee only process movies for those sessions which submit a survey or leave Feedback by way of the Feedback badge. ForeSee recreates the session by playing back the DOM mutations within a browser. While the session is playing, ForeSee records the browser playback and generates an MP4 movie file. Once the movie file is created, it is stored within ForeSee's database for the CX Suite or AAP to load.