Five-minute install
Be live in minutes. Add one snippet to your site, or use the browser extension — and Wakeline works with any tech stack, on any framework.
One snippet
Paste it once and you're connected.
Or the extension
No site change needed — build straight from your browser.
Any stack
Modern frameworks or plain HTML — it doesn't matter.
Live in three steps.
Grab your snippet
Copy it from your dashboard.
Add it to your site
Or install the browser extension.
You're live
We confirm the moment it's detected.
Snippet in, detected, identified — the whole install.
The install is deliberately boring: one snippet, one identify call, one green banner. Here it is end to end for a typical React app.
Paste the snippet
Copy it from the Install page into your HTML before </head>. It loads wakeline.js asynchronously — your page never waits on it — and initializes with your publishable key.
Identify after login
Where your auth resolves, call Wakeline("identify", user.id, { name, email, plan }). Every trait you add becomes a targeting attribute; name or email makes analytics show people, not IDs.
Watch the banner flip
The Install page polls live: amber "waiting for the first request" flips to green "Installation detected" the moment the SDK phones home from your app.
Clear the usual suspects
Not detecting? The page has not deployed, a Content-Security-Policy is blocking (the Install page lists the two directives to add), the key belongs to another project, or an ad blocker is interfering — in that order.
What to expect: Live in minutes, on any stack — the snippet is framework-agnostic. The publishable key is safe in the browser: it only reads published flows and writes events, and you can revoke and reissue it anytime.
When not to use five-minute install.
No pattern fits every job. Here’s where we’d point you at something else — sometimes ours, sometimes not.
Waiting for a sprint slot
This is not an integration project — it is a paste. If the snippet is stuck in a backlog, use Quick preview mode to build your first guides against a sample app meanwhile, so launch day is publish day.
Installing on pages you will never guide
You can scope the snippet to the app surfaces where guides run. A marketing site with no guides gains nothing from carrying the SDK.
Skipping identify()
Technically optional, practically the difference between targeting people and targeting browsers. Without it: no traits, no segments, no cross-device memory. Ship it with the snippet, not "later".
How long does installation actually take?
Minutes: paste the snippet before </head>, deploy, and watch the Install page flip to "Installation detected". The identify() call after login is one more line where your auth already lives.
Does the snippet slow my site down?
It loads asynchronously, so it never blocks rendering — and the SDK is built deliberately small. If Wakeline ever fails to load, it fails silently: your app is unaffected.
Is the publishable key safe to expose?
Yes — it grants read access to your published flows and event writes, nothing else. Keys are managed under Settings, where you can mint and revoke at will if one ever leaks into the wrong repo.
We have a strict Content-Security-Policy — will it work?
Yes, with two directives: script-src and connect-src entries for the Wakeline origin, both shown on the Install page. A CSP block is the most common cause of "not detected", and the browser console names it plainly.
Which frameworks are supported?
All of them — the snippet is plain JavaScript. React, Vue, Angular, Rails, Django, static HTML: if it renders a page, guides run on it. Single-page-app route changes are handled; login-gated builds use the browser extension.
See it on your own app.
Ship your first guide in minutes. Free to start — no credit card.