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

Interactive Product Tours: How to Structure Them and Measure Step Completion

Interactive product tours work when each step asks for one action and you measure the outcome. Structure rules, keyboard accessibility, five events to track and a computed six-step completion funnel.

Chen Yu Published Nov 21, 2026 11 min read Product News
Sample data: 33.0% complete the tour. Making step 4 optional and lifting its pass rate to 80% would raise completion to about 44.4%, a hypothesis to test.Sample data

An interactive product tour is a short guided sequence in which the user performs actions step by step instead of reading, used inside a product to reach a first useful result. It works when each step asks for one action and success is judged by the outcome, not by clicks on Next. Below: structure rules, keyboard accessibility, five events to track, a computed six-step funnel and how to tell whether the tour really helped.

What you will learn

  • One goal, one action per step, value early, a visible skip: about 3 to 6 steps by our working rule
  • Send an event per step and read the funnel from the biggest drop: step 4 lost 40.6% in the example
  • Judge the tour by the outcome with a before-and-after or holdout comparison, not completers against non-completers

What is an interactive product tour?

An interactive product tour is a short guided sequence that asks the user to do something in the product, step by step, instead of only reading about it. Two things are called tours, and they have different goals:

  • In-product tours run inside the live product and help a new user reach a first useful result. Success is activation.
  • Interactive demos are sharable replicas of the product used before sign-up, on a website or in a sales email. Success is the visitor reaching the end and taking the next step. For that use see product demos.

This guide is about the first kind, with one measurement approach that works for both. For the term, see product tour. TapCub does not build or show tours. It measures them: you send an event for each step and read the step-by-step completion in a funnel, as the last section shows.

How should a tour be structured?

Nielsen Norman Group's research on instructional overlays (coach marks) in mobile apps gives rules that carry over to web tours: show one tip at a time, avoid chains of back-to-back tips (people dismiss them faster and the product seems more complicated), keep text minimal, make the overlay look different from real controls so people do not try to tap it, and limit content to key tasks or unusual interactions. Turn those into a structure.

PartRuleSample copy
GoalOne goal per tour, written as an outcome"Create your first report"
StepsOne action per step; 3 to 6 steps for one goal"Click New report"
CopyUnder about 25 words, verb first"Pick the date range, then press Apply"
OrderThe step that produces value comes earlyShow a result by step 3
ExitA visible Skip and a way to resume later"Skip tour" / "Resume from the Help menu"
TriggerStart when the user reaches the relevant screen, not on every first loadStart on the empty reports page

The 3-to-6 range is our working rule, not a published standard. What is worth checking is your own data: where, in the funnel below, people leave.

Make a step an action step (the user must click or type to continue) when the action is the point; make it an information step (a Next button) only when there is something to read first. Action steps give a cleaner signal, because completing one proves the user did the thing.

PartRuleSample
GoalOne goal per tour, written as an outcomeCreate your first report
StepsOne action per step; 3 to 6 stepsClick New report
CopyUnder about 25 words, verb firstPick the date range, then press Apply
OrderValue-producing step earlyShow a result by step 3
ExitVisible Skip and a way to resumeSkip tour / Resume from the Help menu
TriggerStart on the relevant screenEmpty reports page

The 3-to-6 step range is our working rule; check your own funnel.

What does accessibility require?

A tour is an overlay on top of a product, so it can break keyboard use. WCAG 2.2 success criterion 2.1.1 (Keyboard, Level A) requires that all content functions can be operated through a keyboard interface. In practice, for every step:

  1. Reach and operate with the keyboard. Next, Back and Skip are focusable and respond to Enter and Space.
  2. Move focus into the step when it opens and return it to the element you are explaining when it closes.
  3. Do not trap focus in the overlay with no way out; Escape closes it.
  4. Do not hide the thing you are pointing at behind the overlay, and do not rely on colour alone to show the highlighted area.

Test it once with only a keyboard before launch; it takes five minutes and catches the common failures.

Which events should you track?

Without events you only know whether the tour was shown. Send five, with the tour name and the step number as properties:

EventWhen it firesProperties
tour_startedTour appearstour, version
tour_step_viewedA step is showntour, step
tour_step_completedThe user does what the step askedtour, step
tour_skippedSkip is pressedtour, step
tour_completedLast step donetour, version

Then add the outcome event the tour exists for, for example report_created. A call looks like tapcub.track('tour_step_completed', { tour: 'first-report', step: 3 }). Name the events once and keep them: renaming splits the history.

Worked example: a step-completion funnel

Sample data: 1,000 new users start a six-step tour. The number who complete each step:

StepWhat it asksUsers% of start% of previous stepDrop
1Start the tour1,000100.0%
2Click New report82082.0%82.0%18.0%
3Choose a data source69069.0%84.1%15.9%
4Invite a teammate41041.0%59.4%40.6%
5Pick a date range37037.0%90.2%9.8%
6Save the report33033.0%89.2%10.8%

Read it from the biggest drop. Step 4 loses 280 people (40.6%), more than twice any other step. It asks something different from its neighbours (leave the report and invite a person), so the cause is probably the step itself, not the tour's length. If step 4 were made optional or moved after the report is saved, and its pass rate rose from 59.4% to 80%, completion would be 690 × 0.80 × 0.902 × 0.892 = about 444, a completion rate of 44.4% instead of 33.0%, with the later steps' pass rates unchanged. That is a hypothesis to test, not a promise.

Also read the overall number: 33.0% completed. A low completion rate is not by itself a failure. If most of the people who leave have already reached the first useful result, the tour has done its job early.

app.tapcub.com

Six-step tour: users completing each step

1,000 users started

1 Start the tour

1,000

2 Click New report

820

3 Choose a data source

690

4 Invite a teammate

410

5 Pick a date range

370

6 Save the report

330

Step 4 loses 280 people, more than twice any other step, and it asks something different from its neighbours.
Sample data
Sample data: 33.0% complete the tour. Making step 4 optional and lifting its pass rate to 80% would raise completion to about 44.4%, a hypothesis to test.

Did the tour actually help?

The tempting comparison is completers against non-completers. Sample data: of the 330 completers, 224 activated (67.9%); of the 670 others, 208 did (31.0%). "The tour doubles activation" is the headline. It is wrong in the same way the chatted-versus-not comparison is wrong: people who finish a six-step tour are the keen ones, who might have activated anyway.

Use a comparison that does not depend on who finishes:

  1. Before and after, same length. Sample data: the 1,000 users before the tour activated at 38%; the 1,000 after at 44%. The gap is 6 points. Standard error of the gap = √(0.38 × 0.62 ÷ 1,000 + 0.44 × 0.56 ÷ 1,000) = 0.0220, so the 95% interval is 6 ± 4.3 points: 1.7 to 10.3 points. It excludes 0, which supports a real change, but the lower end is small. Check that nothing else changed in that period (a pricing change, a campaign).
  2. A holdout (some new users never see the tour) is stronger, but needs an experimentation tool; TapCub does not split traffic.
  3. Outcome, not completion. Judge the tour by the outcome event (activation, retention at week 4), not by how many clicked Next.

The method for the interval is the one in how to calculate a confidence interval; the two-proportion comparison follows the NIST/SEMATECH handbook.

How do you improve a tour with this data?

  1. Fix the biggest drop first. In the example, step 4.
  2. Make the step optional, move it later or split it if people leave the page to do it.
  3. Cut steps that no one fails only if they add nothing; a step with a 98% pass rate costs little.
  4. Trigger by behaviour. Start the tour when the user reaches the screen it explains.
  5. Compare versions. Add a version property and break the funnel down by it.
  6. Re-measure with the same outcome after each change and keep the old numbers.

Common mistakes

  • Counting "tour shown" as success. Count outcomes.
  • Too many steps, all information. Chains of tips are dismissed.
  • Comparing completers with non-completers. Selection bias again.
  • No skip. Forced tours teach people to dismiss overlays.
  • Keyboard-hostile overlays. Test with a keyboard.
  • Renaming events between versions. It splits the history.
  • Reading small cohorts. A cohort of 30 swings by several points on one person.

Measuring a tour in TapCub

Take the six-step example. TapCub does not build the tour, so you add the events in the product and read the results here.

  1. Send the events. In the product's code, call tapcub.track for each event in the table. A name is required (cut at 100 characters), and you can send up to 20 properties per event.
  2. Build the funnel. In All-platform analytics › Behavior › Behavior analysis, make a funnel from tour_started through each tour_step_completed (at most 20 steps), with a window long enough for people to finish (the default is 7 days). It shows count, rate versus step one and versus the previous step, drop-off and median time from the previous step, and marks the largest drop.
  3. See who dropped. Click a step to see the people who arrived or dropped there, and open one in All-platform analytics › Users › People to read their timeline.
  4. Compare versions. Break the funnel down by the version property; the breakdown keeps the 10 groups with the most entries.
  5. Judge the outcome. Build the same funnel to the outcome event, and build a segment in All-platform analytics › Users › Segments & tags of people who did tour_completed. Use annotations (Configuration › Annotations) to mark the day a new tour version shipped, so the before-and-after comparison is dated.

Know the boundary: TapCub does not build or display tours, run A/B tests or split traffic. A holdout needs a separate tool; TapCub measures what happened.

FAQ

What is an interactive product tour?

A short guided sequence in which the user performs actions step by step instead of reading, used inside a product to reach a first useful result or on a website as a clickable demo. Its success is measured by the outcome, such as activation.

How many steps should a product tour have?

Our working rule is 3 to 6 steps for one goal, one action per step, with the value-producing step early and a visible skip. Check your own funnel: a step that loses far more people than the others, like the 40.6% drop in the example, is the one to redesign.

How do you measure product tour success?

Send an event for each step and for the outcome, build a funnel of step completion, and judge the tour by the outcome (activation, week-4 retention) rather than by completion. Compare before and after, or against a holdout, not completers against non-completers.

What is a good product tour completion rate?

There is no universal figure. In the sample, 33.0% completed, and that can be acceptable if people who leave have already reached the first useful result. Look at where people leave and what outcome they reached.

Are product tours accessible?

They can be if every step works from the keyboard: WCAG 2.2 success criterion 2.1.1 (Level A) requires content to be operable through a keyboard interface. Make Next, Back and Skip focusable, move focus into each step, never trap it, and let Escape close the tour.

Sources

Filed underProduct News

Was this article helpful?

We use your answers to fix and expand this page.

Chen Yu

Technical Engineer

Focuses on tracking code, SDKs, and API integrations, with practical guidance on implementation checks and troubleshooting.

Measure every step of your tour

Send one event per step and read completion, drop-off and time between steps in a funnel, then judge the outcome.

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