1. Knowledge Base
  2. Web SDK questions

Cross-domain functionality

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

When the customer navigates to a separate domain which doesn't has the web SDK set up the co-browsing connection will be temporarily lost until they redirect back.

You can avoid this by enabling full device mode as the session begins. The agent will then be able to guide the customer to complete their task even on a 3rd party domain. For more information on full device mode check the article: https://support.cobrowse.io/3rd-party-websites-with-full-device-mode.

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.