TapCub is live — analytics, insights and live chat, free on one platform
Glossary

What is a product tour? Types, metrics and how to judge one

A product tour is a short in-app guide that walks users through key steps. Types of tours, the metrics that matter, and an example showing why completers doing better does not prove the tour works.

Sophia Bennett Reviewed by Oliver Reed Also called product walkthrough Last updated Nov 19, 2026 Glossary

Quick answer

A product tour is a short guided sequence inside a product that walks a user through a few key steps, using pointers, tooltips or modals. Judge it by how many users complete it and reach the target action, not by how often it is shown.

Formula: Tour completion rate = users who finished the last step ÷ users shown. Step completion = users reaching step N+1 ÷ users reaching step N. Lift = outcome rate (shown) − outcome rate (holdout).

What is a product tour?

A product tour is a short, guided sequence shown inside a product that walks a new or returning user through a few key steps, usually with pointers, tooltips or modal windows. Amplitude defines tours as guided walkthroughs that introduce users to the main features and workflows of an app, most useful during onboarding. Intercom describes its version as an interactive, multi-step guide that shows customers how to use the product.

A tour is a means, not a result. Its job is to move a person toward a moment of value, such as creating the first project or sending the first message. A tour that is shown 10,000 times and completed by nobody has done nothing, however good it looks. That is why the useful question is not "how many people saw it?" but "how many finished it, and did they do the thing it was supposed to lead to?" The sections below turn that into numbers. For the wider design of the first minutes of use, see onboarding flow and app onboarding; the first-use experience itself is covered at FTUE. This page is the definition and how to judge a tour, not a tool comparison.

Types of product tours

Amplitude groups tours into styles that differ in how much they ask of the user:

TypeWhat it isBest used forMain risk
Interactive walkthroughA multi-step sequence where the user acts on each step before moving onTeaching a core workflow to new usersLong sequences lose people at every step
Feature calloutA tooltip or pop-up on one new or underused featureAnnouncing a feature at the moment it is relevantInterrupts someone who is mid-task
ChecklistA task list users complete in any order and at their own paceSetup that has several independent partsEasy to ignore if it is not tied to value
Embedded visualA short image, video or animation that explains a screen and can be dismissedExplaining something that is hard to describePassive; users watch and still do not act

There are also two delivery styles. A linear tour shows every user the same fixed steps in order. A contextual tour appears based on what the user does or has not done, for example only after they have been on an empty dashboard for a minute. Contextual tours cost more to design but interrupt fewer people.

Metrics: judge a tour by completion and outcome, not views

Amplitude lists completion rate, time to value, a guided versus unguided comparison, and A/B results as the main measures. Written as rules you can compute:

MetricFormulaWhat it tells you
Start rateUsers who started ÷ users shownWhether the first card is worth a click
Step completionUsers reaching step N+1 ÷ users reaching step NWhich step is losing people
Tour completion rateUsers who finished the last step ÷ users shownWhether the tour is the right length
Dismissal rateUsers who closed it early ÷ users shownHow much it annoys
Outcome rateUsers who did the target action within a window ÷ users in the groupWhether the tour achieved its purpose
LiftOutcome rate (shown) − outcome rate (not shown)The effect of the tour, if the groups are comparable

The last two rows matter most. Completion tells you the tour is bearable; only the outcome and the lift tell you it is worth having.

Worked example: a five-step tour

Sample data: a project tool shows a five-step tour to 1,000 new users. The target outcome is creating a first project within 7 days.

StepUsers reaching itStep completion (vs previous step)Share of those shown
1. Welcome card1,000—100%
2. Create a project720720 ÷ 1,000 = 72.0%72.0%
3. Invite a teammate540540 ÷ 720 = 75.0%54.0%
4. Open the board410410 ÷ 540 = 75.9%41.0%
5. Finish330330 ÷ 410 = 80.5%33.0%

Tour completion is 330 ÷ 1,000 = 33%. The biggest single loss is the very first card (280 of 1,000 never got past it), so the opening, not the length, is the first thing to look at.

Completers do better, but that does not prove the tour works. Of the 330 who finished, 198 created a project within 7 days (60%); of the 670 who did not finish, 134 did (20%). That is a 40-point gap, but people who sit through five steps were probably going to do the task anyway.

A holdout is the fair test. Suppose the team keeps a random 20% of new users from seeing the tour. Sample results:

GroupUsersCreated a project within 7 daysOutcome rate
Shown the tour800336336 ÷ 800 = 42.0%
Holdout (not shown)2007272 ÷ 200 = 36.0%

The lift is 42.0 − 36.0 = 6.0 points, much smaller than the 40-point completer gap. A two-proportion z-test on these numbers gives z ≈ 1.54, which is a p-value around 0.12, so with a holdout this small the 6 points could still be chance. Larger holdouts, or a longer run, are needed before deciding. See holdout group for how to size one.

Common mistakes

  • Reporting impressions. "The tour was shown 50,000 times" says nothing about completion or outcome.
  • Comparing completers with non-completers and calling it lift. Selection does the work, as the 60% versus 20% gap shows. Use a random holdout.
  • A tour that explains every button. Five short steps toward one outcome beat fifteen steps that cover the whole interface.
  • Showing it at the wrong time. A tour on first load, before the user has seen the empty state, answers questions nobody has asked yet.
  • Never retiring it. When the interface changes, an old tour points at buttons that moved. Review tours when a release touches the screens they cover.
  • No way out. Always give a visible skip or close, and treat dismissal as data, not failure.

Measuring a product tour in TapCub

Take the five-step tour above. The tour itself is built in your own tool or code; TapCub is where you check whether it worked.

  1. Send the tour's moments as events. From the tour's code, call tapcub.track for tour_started, tour_step_viewed with a step property, tour_completed and tour_dismissed with the step it was closed on. Add them to All-platform analytics › Data › Tracking plan so the names are agreed before release.
  2. Build the funnel. In All-platform analytics › Behavior › Behavior analysis, make a funnel from tour_started through each step to tour_completed, which reproduces the table above and shows where users drop.
  3. Measure the outcome. Add a second funnel from tour_started to your target event, for example project_created, within 7 days, and compare it with the same funnel for users who never started the tour.
  4. Save the groups. In All-platform analytics › Users › Segments & tags, create a rule segment for "completed the tour" and use it as a cohort to compare retention.
  5. Record the variant. If your tour tool assigns a holdout, send the assignment as an event property such as tour_variant, then break the outcome down by it.

TapCub does not build product tours and does not randomise users into a tour or a holdout. It only measures. Do the assignment in your tour tool, and read the lift in TapCub.

See also: What is a walkthrough? Meanings, how to run one and how to measure it.

Sources

Was this explanation clear?

We use your answers to fix and expand this page.

Sophia Bennett

Product Adoption Consultant

Explores customer onboarding, live conversations, and self-service, turning common usage questions into practical guidance and improvements.

FAQ

Questions people ask

Short answers to the follow-up questions that come up most.

Still have a question?

Chat with the team behind TapCub — we usually reply within a few hours on business days.

What is the difference between a product tour and a walkthrough?

The words are used interchangeably. Some teams use walkthrough for a tour where the user must act on each step, and tour for a passive sequence of pointers.

How do you measure whether a product tour works?

Track completion step by step, then compare the rate of the target action between users who saw the tour and a randomly held-out group that did not. Comparing completers with non-completers overstates the effect.

How long should a product tour be?

As short as it can be while reaching one outcome. Look at step completion in your own funnel: if a step loses far more people than the others, shorten or move it.

Does TapCub build product tours?

No. TapCub measures tours with events, funnels and segments you send from your own tour tool or code, and does not build tours or randomise users into groups.

See this number on your own site

Add one script tag for web and apps, and the first reports fill in within minutes.

See your data clearly. Find your growth.

Every click, backed by data. Install one line of code and see your first numbers in a minute.

No credit card · Free plans for analytics and chat · Cookieless analytics