Using connectOnPageLoad comes with some trade-offs that you should consider. When set to true, the live chat functionality remains unaffected, and all features like conversion tracking and proactive triggers work as expected. However, setting it to false means these features might not function as intended since the connection is deferred until user interaction.
This setting can improve performance by reducing the load on your website, but it also means you might miss out on monitoring visitors who haven't interacted with the widget. It's essential to weigh these trade-offs based on your specific use case and website traffic patterns.
The connectOnPageLoad setting can significantly impact the performance of your Web Widget. By default, the Web Widget connects to live chat services as soon as the page loads, which can slow down your website, especially if you have high traffic….
Adding the connectOnPageLoad setting to your web pages is straightforward. You need to modify the source code of each page where the Web Widget is embedded. Insert the connectOnPageLoad setting above the Web Widget code snippet, specifying either…
Yes, you can use connectOnPageLoad even if you're not utilizing chat features. This setting is primarily beneficial for managing performance in the Chat dashboard, especially when handling a large number of chat requests. If your Web Widget is only…
If the Web Widget doesn't display when connectOnPageLoad is set to false, it could be due to the widget not being triggered by user interaction. This setting defers the connection until a user interacts with the widget, so if there's no…