/Docs
Start free

Webflow

Add the chat widget to a Webflow site through the project's custom code, in the footer, so it publishes with the site.

Where it goes

On Webflow the snippet lives in Site settings, Custom code, in the Footer code box. It is one script tag; it loads asynchronously and never blocks the page.

index.html
<script>
  window.sellioSettings = { widgetKey: "your-widget-key" };
  (function (w, d) {
    w.SellioWidget = w.SellioWidget || [];
    var s = d.createElement("script");
    s.src = "https://sellio.chat/widget/embed.js";
    s.async = true;
    d.head.appendChild(s);
  })(window, document);
</script>

Replace your-widget-key with the key from Settings, then Install. The key is public and safe to commit: it names the workspace and carries no permissions.

Steps

  1. 1
    In Sellio, open Settings, then Install, and copy the snippet with your widget key.
  2. 2
    In Webflow, open the project's Site settings, then the Custom code tab.
  3. 3
    Paste the snippet into Footer code and click Save changes.
  4. 4
    Publish the site. Custom code only runs on the published site, not in the Designer preview.
  5. 5
    Open the published site; the launcher should be in the bottom corner.
ℹ
Site-wide custom code needs a paid site plan. On the free Starter plan you can add the snippet to one page's settings under Custom code instead.

Identify visitors

When your site knows who is signed in, tell the widget so the inbox shows a name and email instead of a visitor id. Safe to call before the loader has finished; commands queue until it is ready.

identify.js
window.SellioWidget = window.SellioWidget || [];
window.SellioWidget.push(["setVisitor", {
  id: "your-user-id",
  name: "Ada Lovelace",
  email: "ada@example.com",
}]);

To stop anyone spoofing a name, sign the id on your server and pass it as userHash; see Identity verification.

Verify

Open the live site, send a message from the launcher, and check your inbox. If the launcher does not appear, the usual causes are a cache that still serves the old page, a visibility rule in Settings, then Visibility that hides it on this page or device, a domain missing from Allowed domains under Settings, then Install, or a snippet pasted into a page-level box rather than the site-wide one.

Updated . Something wrong or missing? Tell us.