Skip to main content
The widget is configured in Dashboard → Widget and installed with one script tag. The console generates the exact CDN URL and public key for your deployment.

​
Install

Place the snippet before </body> or through your tag manager after consent rules permit support chat. The loader infers the CDN origin from its own src and fetches public configuration from the gateway.

​
Configuration areas

Set light/dark theme, welcome message, visual pattern, logo, brand treatment, and launcher placement.

​
Domain and page security

Verify the domain where the widget runs, configure ALLOWED_DOMAINS, and keep the public API/CDN origins consistent. Page rules accept absolute HTTP(S) URLs or paths beginning with /, with up to 50 rules in the current validator.
Host DOM access lets the loader read semantic page text and pass a bounded snapshot to the iframe on request. Enable it only on sites you trust and only when contextual support justifies the privacy exposure.

​
Session and SPA behavior

With DOM access enabled, the loader maintains a stable anonymous visitor ID and reports URL/title changes from History API navigation. With DOM access disabled, it uses an ephemeral visitor ID. Device and page visibility rules are evaluated before rendering.

​
Troubleshoot

Confirm the generated script has data-InteraOne-public-key, the public config endpoint can find that widget, and the API URL baked into the bundle is correct.
Check browser console origin errors, CDN iframe assets, Socket.IO reachability, reverse-proxy WebSocket support, and widget-token creation.
Review page rules against the full current URL and SPA navigation. Ensure the saved showWidget and selected-page settings match your intent.
Last modified on July 17, 2026