Clew

See how it works
before you make an account

The seven Clew formats below run on this page, through the same code a visitor to your site would get. Press any of them.

Start free

Free plan, no card, and no cap on visitors

These are not screenshots: if a format breaks, this page breaks with it

+ New reportExportShare
12,480visitors
$8,132revenue
64%completion
ReportOwner
Weekly summaryyou
Sign-ups by channelyou
Churn by planyou

Pick a format

It runs over the mock on the left. Close it with the cross, the Esc key, or by pressing the button again.

Onboarding should be changed by the person who sees the problem, not by the person with release access.

What changes in the work

A wording fix ships today, not next release

Step text is edited in the editor on your live page. No developer, no branch, nothing to deploy.

A step that cannot find its element is skipped

The widget looks for the element for five seconds, retrying. If it never appears the step is skipped and the tour carries on. A broken last step does not mark the tour as seen, so the visitor gets it again.

You see which step loses people

A funnel per step rather than one number for views. Plus a list of steps that lost their element, so you hear about a break before your users do.

The data can stay with you

Our EU cloud, or self hosted on your own servers. The widget pulls in no third party dependencies.

How it goes on your own site

One line on the page

A tag in the head, or through your tag manager. The code is never touched again.

Build by clicking on the live page

Open your site with the editor, click an element, write the tooltip. Exactly what you just did on the mock above.

Publish, then read the funnel

Rules for pages, delay, visit number and audience properties. Then the per step numbers.

Which format, and when

Each format is right for one case and wrong for the rest. If we told you all seven were equally good, you would learn nothing.

Tooltip tour

Walk somebody through the screen without taking them off it. The right format when you are explaining an interface rather than announcing something.

Modal

When there is one important thing to say and it does not matter where they were looking. It interrupts, so it is expensive: spend it once.

Modal with a picture

When one picture explains faster than three paragraphs: a new screen, a report cover, a diagram. The image is linked by https — the file stays yours.

Announcement bar

The quietest format: a strip at the edge of the screen that covers nothing and asks for no reaction. For a deadline, or an announcement meant for everyone.

Checklist

When the value is several steps away and people come back for them on different days. It lives in a corner and remembers the progress.

Rating

Ask for a score once the value has landed, then branch: a happy customer gets the review link, an unhappy one gets a box to tell you instead of telling a review site.

Survey

When analytics shows that people leave but not why. Up to three questions, one per screen, and the answers sit apart from the analytics.

Free tools

The arithmetic happens in your browser and no signup is needed. Built by the same team.

What people ask before signing up

Do I need a developer?

Once, to put a line in the head or add a tag in your tag manager. After that tours are built by clicking on the live page and the code is not touched again.

What happens when our markup changes?

The widget looks for the element for about five seconds, retrying, so one that renders late is still found. If it never appears, that step is skipped and the tour carries on. If the missing one was the last step, the tour ends quietly and is not marked as seen, so the visitor gets it again. Every miss appears under Health with the selector and the page.

Is it free?

Yes on the free plan: one site, tooltips and tours, no cap on visitors and no card. The popup formats — modal, bar, checklist, rating, survey — come with a paid plan, and every new account gets a trial with all of them.

Will the widget slow the site down?

It is one script with no third party dependencies, loaded asynchronously, and it does not block rendering.

Where does the data live?

In our EU cloud, or on your own servers in the self hosted edition. The widget adds no third party trackers and sends nothing to anybody else.

What about a single page app?

The widget follows route changes itself and re checks the display rules. There is nothing to call by hand.

Can I show a tour to only some users?

Yes: by page, delay, scroll, visit number, and by properties you pass through Clew.identify().

How is this different from a tour library?

A library leaves you the targeting, the analytics and the editing, and a wording change is a release. Here the change is made by whoever noticed the problem.

Build one on your own site

One line on the page, then tours are built by clicking. The free plan has no visitor cap and asks for no card.

Start free

Free plan, no card, and no cap on visitors

Product tours, popups and onboarding in the age of AI

7 patterns with step counts, copy rules and what to measure, what AI changes, and a checklist before you publish. PDF, 2 pages. What is inside →