There are a variety of ways to test SessionCam using your own processes or third party software. We’ve outlined our recommended approach to testing below:
How to test recording
You can view the calls that SessionCam makes using any browser’s developer tools. E.g. Firebug or DevTools etc.
Open the developer tools and select the Network tab
Sessioncam.recorder.js confirms that the SessionCam tag has been added to the page currently loaded in the browser.
If SessionCam recording is enabled and functioning correctly, you should also see the following calls:
- JS call: The SessionCam tag has been added to the page currently loaded in the browser
- Config call: This decides the config options for SessionCam — whether to record or not, which fields to mask out and other config options. If the config specifies that recording should start then we'll carry on, if not there will be no more activity.
- Get PageID call: Sends the page HTML and is usually only called once per page
- Save Events Call: These are generally sent every second while there are events being monitored. Save events confirm that SessionCam is recording.
How to test replay
Once you have seen that recording is working correctly, you can check that sessions are available in the SessionCam console.
You can do this by browsing/using your website, and then checking the console for the session recording.
The simplest way to do this:
- Log into SessionCam, then select the Recordings tab
- Click on Advanced Filters & then Select A SessionCam Filter drop-down menu
- Choose IP Address & enter your IP (Note - if SessionCam is masking part of your IP, enter 0 for the last 1 or 2 octets)
- Press Apply to see any recorded sessions for the applied filter
Note that if you do not see your site’s assets, you may need to allow our IP addresses.
If you encounter a problem during testing, contact our support team who can investigate and resolve the problem for you.