Product tours

Walk new users through one workflow, step by step

A tour is an ordered set of steps. Each one points at a button, menu or field in your app and explains it in a sentence or two.

Довіряють понад 200 SaaS-компаній, що зростають

  • FreshTricks
  • Geek Dynamic
  • Kiteframe
  • Morrowbit
  • Ochreline
  • Tandemly

What you get

  • Steps on your real interface

    Each step points at an element by its CSS selector. A step without an element shows in the middle of the page, which works well as a welcome.

  • Shown to the right people

    Tours start on their own for people who match the audience rules, on the pages you choose. You can also start one from your own "Take the tour" link.

  • See where people drop off

    Analytics show how many people started, how far they got per step, and how many finished, skipped or closed the tour.

How it works

From an idea to live guidance, without waiting on a release.

  1. Set the start page

    Give the tour a name and a URL pattern, such as /app/*. See URL patterns.

  2. Add steps

    For each step, pick the element with the Chrome extension or paste a selector, then write a short title and message.

  3. Choose audience and frequency

    Decide who sees it, how often, and whether it starts now or on a schedule.

  4. Preview on site, then publish

    Check the draft on your real page. People using your app only see it once you publish.

What's included

Targeting
Match by role, plan, company, custom attributes, events, or whether someone finished other content. Save groups as segments. See Who sees it.
Frequency and schedule
Show once, every visit, every N visits or every N days. Start right away or at a set date and time. See When and how often.
Goals and experiments
Set what success means, like a page visit or an event, and compare against a control group. See Goals and experiments.
Translations
Translate each step, fill in machine drafts, or export a CSV or XLIFF file for translators. See Languages.
Broken step alerts
If a step's element goes missing after a release, Cueston records it under Analytics, Issues, so you can repoint the step.
Versions
Every published version is kept in History, so you can see what changed and put an earlier one back. See Versions and rollback.

Questions

Three to seven steps on one workflow work best. A tour that tries to explain everything gets skipped.

See it on your own product

Get a short walkthrough of Cueston on your app, or start free and build your first one today.