Step-by-step Cobrowse Session Workflow
When a cobrowse session starts, Cobrowse.js sends a StartCobrowse request to the Glance Cloud infrastructure. Cobrowse.js passes your Glance group ID, and receives a unique session ID, a Cobrowse session server assignment, and the list of masked fields.
The session id consists of three components: 1) your group ID, 2) a session key, and 3) a random number for uniqueness.
Cobrowse.js stores the session ID and the set of masked fields in a browser session cookie, and proceeds to start uploading session data to the designated Cobrowse session server (CServer). It also sends session resources that the agent might need. These resources are files referenced in the session HTML such as font files, style sheets, icons, and images.
The CServer posts a message to the Glance web server and informs it that a session has started. Both group id and session key are required to join a session. Once logged in, the group id can be determined based on the agent’s Glance group membership.
As for the session key, there are several ways it might be specified on the agent side. The session key might be a randomly assigned string, or might be some piece of information associated with the visitor, such as user id or a tracking cookie id embedded in your web page.
The agent might enter the session key manually, or it might be extracted automatically for the agent from data in a CRM record.
Either way, the result is that the agent opens a browser window to the URL:
The CServer sends only HTML markup for the browsing session to the agent browser. Resources referenced by the session HTML, such as images or style sheets, are downloaded by the agent directly from the your website when possible.
If downloading those resources is not possible (maybe due to CORS restrictions) AgentView.js requests them from the CServer to ensure the agent's view of your website is displayed appropriately.