Widget options

Script tag attributes of the ASE widget, how it detects language and page context, Shadow DOM isolation, Content-Security-Policy and single-page apps.

The script tag

<script src="https://app.ase.support/widget/ase.js" data-key="pk_YOUR_KEY" defer></script>
data-keyRequired. The widget key for this domain and agent.
data-apiOptional. API base URL; defaults to https://app.ase.support. Only needed for self-hosted or staging setups provided by ASE.
data-platform-srcOptional. URL of a platform helper script (used by store integrations) that the widget loads after itself.

Load the tag once per page, before </body>. defer keeps it from blocking rendering.

What the widget sends

On open, the widget starts a session with the page URL, title, meta description and page language, so the agent knows which page the visitor is on. Each message then goes to the chat endpoint with the session ID and the visitor's language. Nothing is sent until the visitor opens the widget.

Language detection

The interface language comes from the page's <html lang>, falling back to the browser language. The agent's reply language is decided by the agent's language mode (Auto: the visitor's language).

Isolation

The widget renders inside a Shadow DOM. Your page's CSS does not leak into it and its CSS does not touch your page. The floating bubble and panel use a high z-index; if another element covers them, lower that element's z-index.

Content-Security-Policy

If your site sets a CSP, allow:

script-src  … https://app.ase.support;
connect-src … https://app.ase.support;

Single-page apps

Include the tag once in the HTML shell. The widget stays mounted while your router changes views; the session continues. The page context sent at session start reflects the page where the visitor first opened the chat.

Embedding inside the page

To render the chat in a container instead of a floating bubble, use the Page Embed plugin; for a centred modal on desktop, Overlay Mode.