Before installing an AIUNIFY Chat Agent on a website, confirm that:
Open the Agent's Settings page and locate Embed on your site.
The Settings page displays the Agent-specific installation snippet and provides a Copy snippet action.
If the Agent is still Draft, the Settings page warns that you must publish the Agent before the snippet can run for visitors.
The launch snapshot also reports whether widget installation is available.
The generated snippet is a one-line asynchronous script loader containing the Agent's ID.
The deployment pattern is equivalent to:
<script src=".../widget/widget.js?..." data-agent-id="AGENT-ID" async></script>
Always copy the generated snippet from the Agent rather than manually inventing an Agent ID or widget URL.
The interface instructs you to paste the snippet before:
</body>
on every webpage where that Agent should be available.
If your website platform supports a global footer, global code injection area, theme layout, or shared template, the snippet can normally be placed there so it loads across eligible pages.
Restricted Paths can then prevent the widget from mounting on selected areas.
Installing the script does not override the Agent's Allowed Origins. The website origin must still be authorized.
If the script exists in the page but the Agent does not initialize, review Allowed Origins first.
Even on an allowed origin, the widget will not mount on URL paths matching the Agent's Restricted Paths configuration.
The generated widget URL includes a version/hash query value. AIUNIFY Chat generates this value so browsers and cache layers can retrieve updated widget builds rather than remaining indefinitely on an older cached bundle.
After installation:
Check the Agent's publication state, Allowed Origin, Restricted Paths, installation location, and copied snippet before changing application code.