For the complete documentation index, see llms.txt. This page is also available as Markdown.

Overview

Add the Limio chat agent to any website with a script tag

The chat embed puts your Limio AI agent on any page: your marketing site, a campaign landing page, a CMS you don't control the build for. You paste a script tag; the widget handles the rest.

It is the same ready-made chat widget your Limio shop pages use, with the same agent configuration, theming and launcher branding. The embed changes where it runs, not what it is.

Embed, panel or custom surface?

You want
Use

The floating chat widget on a site outside Limio

The chat embed (this section). A script tag; no code.

The floating chat widget on your Limio shop

Nothing to install. Configure the agent in the admin; see Limio Agents.

An in-page chat surface on a Limio page

The Chat Panel component in the Page Builder.

Your own chat UI, any behaviour, any look

A custom surface built on the client SDK; see Getting Started.

The embed surfaces the widget as-is. If you need different markup or behaviour, that is a custom surface, not an embed option.

How it works

The snippet loads a small bootstrap script (about 2 kB). The bootstrap creates a chat session with your Limio tenant, then lazy-loads the widget itself, React and all styles included; there is nothing else to install. Styles are scoped to the widget, so they don't affect your page and your page's CSS doesn't affect the widget.

Visitors chat as guests by default. Each guest gets a session that persists across page navigations on your site. If your site knows who the visitor is, you can pass that identity to the widget so the same person gets the same conversation history on any device; see Identifying visitors.

What you'll need

  • Your Limio shop domain (it serves the embed script), from your Limio contact

  • Your site's origin on the tenant allowlist: Limio configures which websites may start chat sessions for your tenant (https://www.example.com, scheme and host, no path). Requests from other origins are rejected.

  • An HTTPS site: the identity features require a secure context

  • A configured chat agent in your Limio environment

Pages in this section

  • Setup: paste the snippet and allow your origin

  • Identifying visitors: recognise logged-in users with a signed assertion

  • JavaScript API: control the widget from your own code

Last updated

Was this helpful?