Skip to main content
A website tour helps a visitor decide whether the product is relevant. It should answer a specific question and lead to a sensible next action; it does not need to reproduce an entire sales presentation.

Design the journey

Choose a visitor and a single promise. For example, a reporting product might show how a team finds an issue and assigns follow-up. Start near the useful result, then show only the actions needed to understand it. Use representative data and write guides in the visitor’s language. A simple structure:
  1. Orient: State the problem or outcome in one sentence.
  2. Show: Guide the viewer through the key action and its result.
  3. Invite: End with a next action that fits the page, such as starting a trial or exploring another relevant workflow.
For multiple audiences, use branches only when each choice leads to a coherent, independently understandable path. Test all choices, including the ending.

Example: turn a claim into a tour

Suppose the page says “Find delayed orders before they become escalations.” A useful tour could start on an order list, ask the visitor to select the late filter, show the filtered result, and open one order. The closing step can invite the visitor to start a trial or explore another workflow. Each screen should make the original claim easier to judge. Replace this example with a real product workflow and approved sample data. Avoid a welcome screen that repeats the marketing headline without showing anything; the surrounding page can provide the introduction. If the tour is embedded beside text, make its first screen understandable even when someone arrives directly through a shared link.

Publish and place it

Publish the demo and use Share → Embed to choose an inline, full-page, or pop-up format. Put the tour near the claim it demonstrates and give it enough space to be usable. On the actual page, test loading, phone layout, navigation, and the link or CTA at the end. Keep a text introduction and a direct link available for readers who cannot use the embed. Choose inline when the demo is part of the page’s main explanation; a pop-up can work when a visitor deliberately opens a longer tour. Check the experience in the page, not only in the editor: a narrow container can make an otherwise clear guide difficult to read. If the final CTA takes the visitor elsewhere, verify the destination and make sure it matches the surrounding page’s next step. See embed troubleshooting if the player does not load or fit.

Improve it

Choose a question before looking at analytics: for example, “Are visitors reaching the result?” Compare the step funnel and completion rate over a useful period, then watch the path yourself. A drop is not automatically a broken step; the visitor may have found what they needed. Change one element, publish, and compare a later period while accounting for traffic changes and small samples.