The SessionCam Tag & Recording Events Sequence

We provide the following generic recording tag:

<!-- SessionCam Client Integration v6.0 -->
<script type="text/javascript">
//<![CDATA[
var scRec=document.createElement('SCRIPT');
scRec.type='text/javascript';
scRec.src="//d2oh4tlt9mrke9.cloudfront.net/Record/js/sessioncam.recorder.js";
document.getElementsByTagName('head')[0].appendChild (scRec);
//]]>
</script>
<!-- End SessionCam-->

We recommend that the tag is located as close as possible to the closing body statement on the page… If you're using a tag management solution to achieve this we recommend setting your solution to fire the tag when a page is ‘DOM Ready’ - this ensures that the DOM tree has fully exposed its contents before we begin to record.

Events Sequence

1. A visitor lands upon a page where the above tag is deployed (either by tag manager or hard coding)
2. The tag fires and appends the SessionCam recorder JS link (https://d2oh4tlt9mrke9.cloudfront.net/Record/js/sessioncam.recorder.js) to the header of the page - this is the main SessionCam recorder code; If this process is successful you can see the network event ‘sessioncam.recorder.js’ within dev tools, with a 200 status
3. sessioncam.recorder.js then initiates the ‘config.aspx’ event to confirm the recording configuration of the page
4. If the configuration of the page is set to record sessioncam.recorder.js initiates the ‘GetPageId’ event in order to facilitate a copy of the page HTML; if the page is not set to record you will see no further SessionCam events in the network call list
5. sessioncam.recorder.js then begins recording the visitor's input as ‘SaveEvents’ - these are bundled together and sent, asynchronously, in irregularly sized packets to AWS
6. The asset grabbers facilitate copies of the pages CSS during post-recording processing

See here for more on Post-Recording Processing