All website navigations on different routes of the same top-level domain work out of the box! An example is moving from cobrowse.io to cobrowse.io/pricing. Just make sure our web SDK is set up correctly!
Sometimes you also need to navigate to different subdomains or top-level domains in order to complete your tasks. We have a few options to cover these situations.
Navigating to a (sub-)domain that you control
Example: moving from cobrowse.io to docs.cobrowse.io (which we control!)
We support this using the cross-domain feature of our web SDK: https://docs.cobrowse.io/sdk-features/advanced-features/web/cross-domain-session-support. Simply add the needed code to each of your required (sub)domains! This retains the full functionality of the web SDK.
Navigating to a (sub-)domain that you do not control
Example: moving from cobrowse.io to github.com/cobrowseio
This depends on whether or not the customer will return to the domain on which the co-browsing session was initiated. The use cases are outlined below.
- End user navigates to a third-party top-level domain temporarily:
- Option 1: Begin the session, enable full device mode, guide your customer to complete their task, they return to the original domain, then you can deactivate full device mode.
- Option 2: Begin the Cobrowse.io session, do not enable full device mode, you customer navigates to a separate domain momentarily (e.g. for a log in and redirect). When the customer is away from the original domain, the co-browsing connection will be temporarily lost until they redirect back.
- Navigate to a third-party top-level domain and do not return: simply enable our full device mode and let the customer navigate to the third party domain.
Technical information for implementing full device mode can be found in our documentation: https://docs.cobrowse.io/sdk-features/full-device-capabilities. This includes enabling full device mode by default. Be sure to check the agent controls during full device mode on web.