Landing Pages: Standard vs Custom
You have already read about a Standard Landing page. In addition, you have the option to create your own Custom Landing Page(s) using the Surfly widget, offering a plethora of customization possibilities through front-end coding. Check out our tutorial for technical details.
Below table lists some commonly valued highlights of the two:
Standard Landing Pages | Custom Landing Pages | |
Skills | Zero code implementation | Simple front-end coding skills required |
Timeline | Few minutes. | Few hours/days. |
Most Common Use Case | Ideal for Proof of Concepts (POCs) where the customer needs to be the default host, but obtaining resources and approvals for integrations might cause delays | Suitable for cases where branding and customization are essential, and the go-live process can be managed along with resource and approval alignment |
Branding & Customisations | Limited URL customization, e.g., https://app.surfly.com/landing/customizable-part/ | Complete control over the URL, e.g., https://assistance.yourcompany.com |
Communicating over a call can be complicated | Communicating over a call will be easier | |
Sessions start with settings configured in your dashboard. | Sessions can be started with different settings by specifying them through code. This is an advantage if you plan to use different approaches for session start and require different settings to apply for them. | |
Further customizations like displaying a pop-up with a message or terms of service for the customer are not possible | Extensive customization options available, allowing you to display an assuring message, terms of service agreements, or customer information input fields (e.g., name, email) before the session starts |
Browsers like Safari (in regular mode) and Chrome (in Incognito mode) implement policies to limit or control third-party cookies usage, impacting the way sessions start and function on websites using widget. Please read about it here.