Signal developer docs

Signal reads what a visitor does on a website, asks one short question when the answer would change what to offer, and offers the next step that fits: a booking link, a call back, WhatsApp, a guide by email, matching products, or a chat with the team. These docs cover everything you can build on.

Quick start

In the dashboard, open Settings → Install and copy your snippet. It looks like this:

<script type="module"
  src="https://app.try-signal.com/sdk/signal-auto.js"
  data-signal-key="sig_pk_live_…"
  data-signal-api="https://app.try-signal.com"></script>

Paste it on every page, just before </body>.
Add your website's domain under Settings → General → Allowed domains (exact host names, e.g. www.example.com and example.com).
Open your site. Settings → Install turns green when the first visit arrives.

That's all most sites need. The popup, questions and offers come from your configuration, which the setup wizard writes for you.

What's in these docs

Page	For
Install	The script tag, its options, platforms, smart forms, testing safely
JavaScript API	`window.signal`: tracking events, identifying visitors, listening to Signal, drawing your own UI
Consent and storage	Cookie banners, storage modes, turning analytics or personalisation off
Configuration	Signals, questions, routes, offers, forms, follow-ups, privacy and brand
Webhooks	Sending ready leads to Zapier, Make, your CRM or server, and verifying signatures
Server API	Publishing configuration, reporting won deals, exporting and deleting visitor data

Keys

Every project has two kinds of key:

Publishable keys (sig_pk_…) go in your website. They only work from your allowed domains and can only do what a visitor can do.
Secret keys (sig_sk_…) are for your server. They are shown once when created (Settings → Install → New secret key). Never put them in a web page.

Keys contain the environment: dev, stg or live.

For AI assistants

A plain-text index of these docs is at /llms.txt, and the full text at /llms-full.txt.