No-code product tour builder
Open your live product inside Wakeline and build right on top of it. Point, click, and place every step on the real page — no code, no staging site, no waiting on engineering.
Click here to spin one up.
Build on the real thing
Your actual app loads inside Wakeline, so what you design is exactly what your users will see.
Point and click
Select any element to anchor a tooltip, drop in a modal, or place a banner — then configure it in a side panel.
Preview before you publish
Step through the whole experience live on your own page, then publish in seconds.
Live in three steps.
Open your site
Enter your URL and your app loads right inside the builder.
Place your steps
Click elements to anchor them, pick a template or start blank, and write your copy.
Publish
Go live instantly — your changes reach users in seconds.
A welcome tour, built on the live page.
Say you want every new signup to create their first project before they wander off. Here is the whole build, start to finish — no ticket filed, no code shipped.
Open your app in the builder
From Flows, choose "On my website" and enter your URL. Your real dashboard loads inside Wakeline, exactly as users see it.
Anchor the steps by clicking
Click your "New project" button and attach a tooltip: "Everything starts here." Set it to advance when the user clicks the real button — not a Next button.
Set the audience and trigger
In Configuration, target logged-in users, trigger on page load, and set frequency to "until completed" so people who finish never see it again.
Preview, then publish
Step through the whole tour on your own page with live preview. Publish, and it is in front of new signups in seconds.
What to expect: The flow's Reports tab shows started, completed, and a step funnel from day one — so a week in, you will know exactly which step loses people, if any.
When not to use on-site builder.
No pattern fits every job. Here’s where we’d point you at something else — sometimes ours, sometimes not.
Your key screens are behind a login wall
If your app blocks embedding (many do, via frame protections), the on-site builder can't load it. That is exactly what the browser extension is for — same builder, running on your signed-in pages.
You want to try Wakeline before touching your site
Use the "Quick preview" mode in the new-guide wizard instead. It builds against a sample app, so you can learn the editor without entering a URL at all.
The change belongs in your product, not on top of it
If the fix is a clearer empty state or a better button label, ship that instead. Guides layered over confusing UI are a patch, not a cure — we would rather you fix the screen.
You need pixel-perfect brand layouts
The builder composes steps from structured content — title, body, media, buttons — styled by your theme. If you need a fully bespoke, hand-coded layout, this is deliberately not a page builder.
Do I need a developer to use the on-site builder?
Only for the one-time install: someone pastes the Wakeline snippet before </head> once. After that, building, editing, targeting, and publishing guides is entirely point-and-click — no code, no deploys, no engineering tickets.
Does building on my live site change my site?
No. The builder loads your page inside Wakeline and draws on top of it. Nothing is written to your site — guides are stored in Wakeline and rendered by the SDK at view time, isolated from your code and styles.
What happens if my app redesigns and an element moves?
Each step anchors to a CSS selector. Small changes usually keep working; if an anchor disappears, the step's "if element does not appear" behavior decides whether to skip it or wait, so a missing element never strands the tour.
Can I see a guide before users do?
Yes — live preview steps through the whole flow on your real page before you publish, and every flow starts as a draft. Nothing is visible to users until you explicitly publish it.
Which sites does the builder work on?
Any web app where you can install the snippet — React, Vue, Angular, Rails, anything. For pages that refuse to load in an iframe (common with strict security headers), use the browser extension instead; it is the same builder in a different wrapper.
See it on your own app.
Ship your first guide in minutes. Free to start — no credit card.