Widget installation

Install the Site snippet

<script defer src="https://cdn.stand.chat/widget/stand.js" data-stand-id="YOUR-SITE-ID"></script>

• Open the Site, expand Installation snippet, and copy the generated script without changing its Site identifier.
• Add the generated deferred script once through the website’s shared page template, code, tag manager, or builder custom-code area. The document head is suitable; placing it before the closing </body> tag also works.
• Publish the change to the real visitor-facing domain; a saved draft or local preview does not verify production installation.
• Visit the published page so the widget performs its Site lookup, then return to Sites and confirm Installed status.

Pending and installed status

Domain and Site-ID matching

• The data-stand-id selects one Site record and its configuration.
• The page domain must normalize to the Site’s saved domain. Preview and staging hostnames need their own matching configuration when they should run Stand.
• Protocol, path, and a leading www. are removed for the Site-domain comparison.
• Path-specific behavior and Stand-in specialization are evaluated only after the Site and domain match succeeds.

Missing Site ID and demo mode

A page that loads stand.js without a Site ID runs in demo mode instead of showing no chat. Stand Chat’s demo Stand-in answers on any domain. It identifies itself as Stand Chat’s demo assistant, not as the website, explains that the snippet has no Site ID, and describes how to get one.

Developers can set data-stand-id="demo" to choose demo mode explicitly and try client-side integration code before registering: openChat with a greeting, visitor message, or private prompt; identify; stand-button; stand-card; and stand-chatbox.

<script defer src="https://cdn.stand.chat/widget/stand.js" data-stand-id="demo"></script>

• Only the demo Stand-in answers. Demo chats are not routed to human reps, so show-when="rep" entry points stay hidden, and demo chats show the Powered by Stand footer.
• Configuration saved in Stand cannot be tried in demo mode: behavior rules, site instructions, configured greetings, knowledge bases, skills, integrations, branding, and your own reps and Stand-ins require your own Site.
• Demo conversations, including private page context and page-known identity sent with them, are handled by Stand Chat. They do not appear in any customer’s Chats or History and do not use a customer’s chat quota.
• When a page switches between demo mode and a real Site ID, a chat saved in the visitor’s browser from the other mode is discarded instead of restored.

If the widget does not become available

• If the chat introduces itself as Stand Chat’s demo assistant, the published script has no Site ID or uses demo. Replace it with the Site’s generated snippet.
• Confirm the copied snippet was published in the active template or tag-manager container, not only saved as a draft.
• Inspect whether cache or CDN output still serves the previous page.
• Confirm the page hostname matches the Site rather than a preview or alternate domain.
• Check that the Site is enabled and Chat widget status lists an eligible rep or Stand-in.
• Review Chat widget behavior for a delayed, scroll-based, manual, or suppressed reveal, and check whether the page hides the launcher with data-stand-hide-button or StandChat.initiallyHideChatButton(), before assuming installation failed.

Security and lifecycle boundaries

• The public Site identifier selects configuration but is not a customer secret or rep authentication credential.
• The stable snippet does not need to change when owners edit runtime Site behavior.
• Removing the snippet stops future page loads from initializing Stand but does not delete the Site record or prior conversations.
• Installing the snippet does not give Stand permission to bypass the website’s own authentication or read private backend data.

Related features

• Site management — A Site is Stand’s installation and routing boundary for one named website context. It owns the stable embed snippet, normalized domain, enablement, Site instructions, fallback language, behavior rules, coverage diagnostics, and usage scope.
• Chat routing and match status — For every new website conversation, Stand builds an eligible set from the matched Site, organization capacity, Available reps, and enabled AI Stand-ins. It routes to an Available rep first; when Stand-in coverage is active, enabled Stand-ins can cover chats when no rep is Available or every eligible rep is at capacity.
• Stand JavaScript API — The public window.StandChat API lets a website reveal its own chat entry points, inspect responder availability, open Stand with page-specific context, and identify a signed-in visitor.