Tours

Tours are interactive guided experiences that walk users through your product features and interface, helping them discover functionality and reach key insights. Unlike static content, tours provide step-by-step visual guidance that highlights elements, shows videos, and explains features in context.

How Tours Work

Tours are delivered as overlay experiences that appear directly on your website, guiding visitors through interactive walkthroughs of your product. They combine visual cues, explanatory text, and optional video content to create engaging onboarding or feature discovery experiences that adapt to your site's design. Tours can span multiple pages, automatically navigating visitors between pages as they progress through each step.

Triggering Tours

Tours can be triggered by various events and conditions such as page visits, user interactions, time-based rules, or custom events. The Trigger button on the tour page opens these settings. For tours the Page rules are left out of that panel — the tour's Start URLs take their place. For detailed information about configuring tour triggers, see our comprehensive trigger documentation.

Trigger Configuration

Learn about all available trigger options and how to configure them for your tours.

The Tours List

Click Add Tour to create one: choose New Item to start from scratch, or pick one of the ready-made templates.

The Tours list opens as a table with one row per tour, and two buttons at the top right switch between List view and Card view (Yaplet remembers your choice in this browser). A strip of numbers above it shows how many tours are Live and how many are Drafts, plus Shown · 30 days. The All, Live and Draft buttons narrow the list by state, and you can search, filter by widget and sort.

Each row shows the priority arrows, a tile with the number of steps, the tour name and its start URL, a switch with a Live or Draft badge (flip it to put the tour live or turn it off right from the list), the widget, Shown for the last 30 days, the creation date, a Reports button, an Edit button and a ⋯ menu with Edit, Reports, Duplicate and Delete. Card view shows the number of steps and start URL, the name, widget, a Live/Draft badge, the creation date, one line with how many people the tour was shown to in the last 30 days (or a note that nobody saw it in that period), and small Allow close and Back button tags when those options are on.

Unlike banners, chat messages and surveys, tours show only the Shown figure. Their Clicked and Rate columns show a dash, and hovering it says Tours don't report when a visitor finishes them — nothing in Yaplet records how far a visitor got through a tour, so a percentage would be invented rather than measured.

Priority is not set inside the editor. On the Tours list, use the up and down arrows at the start of each row — or, in Card view, the two arrow buttons beside the Priority number in the card footer. Hover them for Increase priority and Decrease priority. When several tours qualify for the same visitor at the same moment, only the heaviest one starts.

Tour Settings

Open a tour from the list to edit it. The page header has Reports and Trigger buttons and the save controls: Unsaved changes appears with Discard and Save changes as soon as you edit something, and leaving with unsaved edits asks first. Under the header, a Flow card holds the tour's steps, and a Settings section ("Who gets the tour and what visitors can do in it") holds the rest.

The Flow Card

The Flow card says how many steps the tour has (or No steps added). It lists the Start URL (or URLs), then every step in order — click a step to see its type, mode, selector, content, page and fallbacks — with a Navigate to page marker wherever the tour moves to another page, and Tour ends at the bottom. A tour with no steps shows No tour steps yet and a Start building tour button. Once it has steps, the card offers Edit flow and Clear flow.

If a tour has more than one link step, or a link step that isn't the last one, a yellow warning says so, and saving asks you to confirm.

Start Tour Setup

Start building tour and Edit flow open the Start tour setup dialog. It holds the tour's start URLs:

Start URLs
string[] required
One or more page URLs where the tour can trigger — the tour triggers when a visitor is on any of these pages. By default, URLs are matched exactly. Use * as a wildcard to match any text:
  • https://example.com/dashboard — matches this exact page only.
  • https://example.com/dashboard/* — matches all subpages under /dashboard/.
  • https://example.com/*/edit — matches any edit page (e.g. /products/edit, /settings/edit).
Trailing slashes are ignored during matching. The tour triggers when the visitor is on any of the listed URLs (OR logic). Press Add URL to add as many as you need. When you save the tour, these URLs become its page rules.

The dialog's Start tour builder button opens the builder (see below); Cancel closes the dialog.

Settings

Name
string required
A descriptive title for your tour. Only your team sees this name.
Widget
string required
Which chat widget this tour belongs to — and therefore which website it appears on. A brand has at most one chat widget, so in practice you are choosing the brand.
Published
boolean
Whether the tour is active and can be triggered for visitors. Visitors only get the tour while this is on.
Visitors can close the tour
boolean
Shows a close button, so visitors can leave the tour before it ends.
Show a Back button
boolean
Visitors can go back to the previous step. The tour's buttons (Back, Next, and Close on the last step) are labeled in the brand's language, set under Brand settings → General.

Tour Builder

The tour builder provides a visual interface for creating interactive guided experiences. It opens in a separate window on your own website and allows you to build step-by-step tours directly on your pages. A bar along the bottom of that window holds the builder's controls: buttons to add a step (Add post, Add pointer, Add video and Add redirect), the timeline of your steps, Navigate and Save.

Step Types

Tours support multiple step types to create rich, interactive experiences:

Text-based steps that display messages and information without highlighting specific elements.

Pointer and video pointer steps also have an interaction mode (Select interaction mode): Default or Click. With Default, the highlighted element is only a spotlight that the visitor cannot click, and they move on with the tooltip's next button. With Click, the visitor can click the highlighted element and has to click it to continue (that step has no next button), and the Flow card shows Click required on that step.

Multi-Page Tours

Tours can span multiple pages. Each step can target a specific page URL — when the visitor progresses through the tour, it automatically navigates between pages as needed. In the builder, use the Navigate button to switch to a different page and add steps there. Steps are grouped by page in the timeline for easy overview.

If your start page can be reached via different URL variants, add them as additional Start URLs. Use wildcard matching (e.g. https://example.com/app/*) to cover an entire section of your site, or enter the full URL for specific pages.

Responsive Element Targeting

Pointer and video pointer steps have a built-in fallback system that handles cases where the target element isn't visible — for example, a sidebar menu item that becomes a hamburger menu on mobile. The system provides three layers of resilience: fallback selectors, fallback steps, and skip-if-hidden.

Adding Fallback Selectors

Pick Your Primary Element

Select the main target element as usual: click the crosshair button (Click to select element) at the top of the step editor, then click the element on your page.

Add a Fallback Selector

Once a primary element is set, an Add selector button appears under Fallback selectors. Click it to enter picker mode again and select an alternative element (e.g., the mobile equivalent).

Manage Your Fallbacks

Each fallback appears as a numbered row (#1, #2, …). You can reorder them with the up/down arrows or remove them with the X button. Add as many fallbacks as needed.

How It Works at Runtime

The SDK tries to display the step using this priority order:

  1. The element you picked — the main (primary) target
  2. Fallback selectors — tried in order, top to bottom (same message, different target)
  3. Fallback steps — tried in order, first match wins (completely different step with its own message and target)
  4. Skip or centered message — if nothing matches and Skip if hidden is enabled, the step is silently skipped. Otherwise, the step displays as a centered popover

The first visible match at each layer is used. Fallback selectors preserve the original step's message but point to a different element. Fallback steps are entirely independent — they have their own type, selector, and message.

A pointer targeting a desktop sidebar link might not exist on mobile where the navigation is collapsed into a hamburger menu. Add a fallback selector targeting the mobile menu equivalent so visitors on smaller screens see the pointer on the correct element.

Fallback Steps

While fallback selectors point to a different element with the same message, fallback steps let you define entirely different steps that are shown when the primary element isn't visible. Each fallback step has its own type (pointer or post), selector, and message content.

This is useful when the mobile version of your site has a fundamentally different layout — not just a different selector for the same element, but a completely different interaction flow.

Adding Fallback Steps

In the step editor, the Fallback steps section appears below the fallback selectors for pointer and video pointer steps. Click Add pointer or Add post to create a fallback step. For pointer-type fallbacks, the element picker opens automatically so you can select the target element. Use the pencil icon to edit the fallback step's message content.

Example Use Case

Your tour highlights a "Settings" button in the top navigation bar. On mobile, there is no top nav — instead, users access settings through a bottom tab bar icon. A fallback selector won't help here because the mobile element has completely different surrounding context. Add a fallback pointer step targeting the mobile tab bar icon with a message tailored to the mobile layout.

Skip if Hidden

Tick the Skip if hidden checkbox, next to the Fallback steps heading on any pointer or video pointer step, to silently skip it when neither the primary element, fallback selectors, nor fallback steps produce a visible match. Without it, unmatched steps display as a centered popover message.

Use Skip if hidden for steps that only make sense in certain contexts — for example, a step highlighting a desktop-only feature that has no mobile equivalent at all.

Builder Workflow

Step 1: Setup Starting Page

In the Start tour setup dialog, add one or more Start URLs and press Start tour builder. The tour builder opens the first URL in a new window. If the first URL contains a wildcard (*), you'll be asked Which page should the builder open? — enter the full address of a specific page in Builder URL.

Step 2: Add Tour Steps

Use the buttons in the builder bar to add a step — Add post, Add pointer, Add video or Add redirect — and click an element on your website to point at it. Use the + buttons between steps to insert at a specific position.

Step 3: Navigate to Other Pages

For multi-page tours, click Navigate to switch to another page and continue adding steps. The builder preserves your progress across page navigations.

Step 4: Configure Step Content

Click a step in the timeline to open its editor: add explanatory text, an optional video, and the interaction mode, then press Done. Post and link steps can be assigned to any page via the Page selector.

Step 5: Preview & Refine

Test the tour flow, adjust step order via drag-and-drop, and ensure smooth navigation between steps and pages.

Step 6: Save Tour

Press Save in the builder bar. The builder window closes and your steps appear in the Flow card on the tour page, with the message Tour flow updated locally. Save the tour to persist changes. The builder's Save does not write the tour by itself — press Save changes on the tour page to keep it, then switch Published on.

Link steps redirect to a URL and end the tour — use them only as the final step. For mid-tour page transitions, use the Navigate feature to add steps on different pages instead.

Preview & Testing

Use the built-in preview feature to see how your tour will appear on your website. The tour builder provides real-time preview of steps and interactions.

Testing engagement campaigns

Learn how to safely test your campaigns before letting them reach live visitors.

Always test your tours across different devices and screen sizes to ensure proper element highlighting and step progression work correctly. Use fallback selectors, fallback steps, and skip-if-hidden on pointer steps to handle responsive layouts where elements may not be visible at all breakpoints.

© 2026 Yaplet. All rights reserved.