Install it
1
Allow your domain
Under Allowed domains, type the domain you will serve the widget from — for example
example.com — and press Add.Only listed domains may load the widget. An empty list allows nothing, which is the
safe default but a silent one: a snippet pasted before a domain is added shows nothing
at all. Subdomains are not included automatically, so list shop.example.com as well if
you serve the widget there.2
Copy the snippet
Install snippet holds the snippet with your own widget key already filled in. Press
Copy.Copy it from the product rather than from here — the key is yours and the loader address
follows your workspace.
3
Paste it on your site
Into your site’s HTML, just before the closing
</body> tag, on every page you want the
widget to appear on. Most sites have one template that covers all of them. The script
loads asynchronously and does not hold up your pages.Pasting the snippet twice is harmless — the loader refuses to start a second widget.4
Wait for the first load
The channel is marked live the moment Watx sees the widget load from an allowed domain.
Open your own site to make that happen. Channel Settings then says Web widget is
live, with Last seen underneath.
If the widget does not appear
The channel’s status message in the sidebar names the likely cause. In order of how often it is the answer:
The widget is deliberately loaded inside its own frame, so nothing on your site can change
how it looks and nothing it does can break your layout. The launcher is a frame too, which
is why there is no element on your page for your CSS to catch.
Controlling it from your own page
The loader exposes a small API for opening the chat from your own buttons:The two keys
Channel Settings → Keys holds both.
Both are confirmed before they rotate. Rotate the widget key if it has been pasted on a
site that is not yours; rotate the secret if you believe it has leaked.
Every request that touches a conversation needs a signed session token as well as the
widget key, so somebody copying your key out of your page source cannot read or write
anyone’s chat.