Subdomains and session continuity
Understand the difference between visitor context and authenticated conversation history.
Same installation across subdomains
Use the same widget key and widget origin on each host, and allow each host in widget settings. Conversation continuity follows the widget-origin session storage and the browser’s storage policy. Signed identity is the supported way to recover authorized history when a new session is created.
Optional first-party visitor cookie
cookieDomain configures an optional non-secret first-party visitor-context identifier on the host site. It does not copy the iframe bearer token into your website and does not authorize conversations. Browser cookie restrictions and private browsing still apply.
window.TruComWidgetConfig = { cookieDomain: '.example.com' };
// Use on example.com and its allowed subdomains.Separate sites and apps
A cookie cannot share an authenticated session between unrelated domains or app WebViews. Issue a fresh signed identity proof for the authenticated customer instead. If storage is unavailable, the widget can keep an in-memory session for that page; subsequent pages may start a new one.