Common terms on the topic of co-browsing

Yes! Surfly is designed with integration in mind. We offer a range of options that will empower you to create exactly what you need. Find out more on the integrations overview page.

Embeddable tools work by adding a piece of JavaScript code to your web pages. Functionality added this way is limited and applies to the amended pages only. Our technology is fundamentally different - it works everywhere.

You can go anywhere with no reduction in features, no workarounds, and no change in experience. All of this can be achieved without adding a single line of code, with Surfly.

Pixel based co-bowsing is essentially a video stream and therefore suffers all the latency problems that come with it. Video is also fixed - you can't change anything as it's streamed. Surfly shares web content - not pixels.

Surfly's univeral co-browsing is lightweight and rendered locally by each participant, giving a faster experience with way more control and countless of possibilities for creating collaborative journeys.

Screen sharing is powered by WebRTC, which is essentially a video stream. That's why screen sharing is the same thing as pixel based co-browsing, which is completely different from what Surfly offers.

Surfly differs both in its quality of actual the co-browsing experience as well as its ability to serve different use cases - Surfly offers vastly more possibilities.

Surfly's webhooks and APIs are available to all customers. Read more about using webhooks with Surfly here.

Surfly has servers located all over the world. You can pin your traffic to one or multiple regions to ensure all of your data in transit doesn't leave them. You can also opt to deploy Surfly on your own cloud servers, or even choose to deploy on-premise.

You can see all regions currently supported in our public cloud here. Every server location is available for use by all customers on our public cloud deployment.