Presence / 1-Click Requirements
Presence allows agents to cobrowse with visitors instantly. Visitors do not need to click a link or type a hot key sequence, and do not need to read a session key over the phone.
The following requirements must be met in order to take advantage of Presence:
Agents must be using Glance for Salesforce or a custom integration.
data-presence="on"to the Cobrowse script tag.
Specify a Visitor ID on every page from which a Cobrowse session can be started. The Visitor ID must:
Be known to the agent side CRM.
Be unique to each individual who may be browsing your website at any given time. If two individuals are browsing the website with the same Visitor ID, the Presence Service cannot distinguish between those individuals.
Adhere to the requirements of a Session Key listed here.
Agents must have a valid Presence subscription.
Agent CRM must be integrated with the Glance Presence service via the Glance Presence API. Glance's Salesforce application is Presence capable.
More information about the Glance Presence API can be found under Customizing.
Disable Console Logs
NOTE: The ability to disable console logs is supported in Cobrowse version 4.9 later.
To suppress console logs due to presence, you must include
If you use an ad blocker that uses the EasyPrivacy list, you may need to make changes to your ad blocker to enable Presence. The EasyPrivacy list includes the
When the script is blocked, the Join button will not light up in Salesforce, even if a visitor is viewing a properly tagged customer web page.
To remediate this, turn off the ad blocker, white-list the customer site in the ad blocker, or unsubscribe the ad blocker from the EasyPrivacy list.
This list is on by default in the uBlockOrigin extension. It is not on by default in AdBlock or AdBlock plus.