The following cookies are set when a visitor navigates to a website that has SessionCam recording enabled...
1st party permanent cookie: sc.UserId:
Used to identify an individual unique visitor (set for one year). The SessionCam reporting console can re-sort recorded sessions by a unique visitor. This means that multiple visits from the same unique visitor over a selected date/time range can be aggregated.
1st party session-expiry cookie: sc.Status:
Used to store the recording status through the visitor's session. This cookie is set on the first load of SessionCam. It stores whether SessionCam is to record the session or not. This cookie also stores data for whether ServiceTick web surveys are configured to launch for given hostname.
1st party session-expiry cookie: sc.ASP_NET_SESSIONID:
Used to identify the individual user session. This cookie provides the details needed to compile a recording showing multiple pages visited during a visitor’s unique visit to a website.
3rd party session cookie: sc.ASP_NET_SESSIONID:
Only used when a visitor goes across multiple domain names belonging to the same client within a single visit
This cookie is always set but only used in the specific situation of SessionCam users who have websites where the content and functionality is distributed across multiple domain names. This cookie enables the SessionCam reporting console to maintain a view of a visitor’s session across multiple domain names.
1st party SessionCam Test cookie: SessionCamTestCookie:
Deleted after being set. This cookie is set when SessionCam initialises and is only ever used to ensure we can read and write cookies. Once this cookie has been set it is deleted immediately and if the cookie fails to set, SessionCam will not attempt to record.
1st party permanent cookie: sc.OptOut:
New session creation cookie: sc.InTg:
The main endpoint that is used to 'ingest' the data we record uses the hostname https://ws.sessioncam.com. This is where the session records to when the sc.InTg cookie's value is 'a'. When the sc.InTg cookie's value is 'b', that session is one of a few that is being processed on the new code. The endpoint used for these is https://b.ws.sessioncam.com. Neither of these hostnames are a third party. All the sessions are processed through SessionCam and presented on the console. The cookie is created when a brand new session starts and is simply used to keep sessions recording consistently to the same hostname (endpoint) from start to finish. If we don't use this cookie then we would not get complete sessions running on the new code.