Moving between pages, tours and app actions

Each step has a When they click Next setting, in the builder's panel and in the step form.

Go to the next step

The default. The next step shows on the same page.

Go to a page

Enter a path such as /reports or a full address. When the person presses Next, that page opens and the tour carries on there with its next step, as long as they stay in the same browser tab. On the last step, the tour finishes and then opens the page.

To build the steps on the other page, open it in the builder with Use the page, then pick its elements.

Start another tour

This tour finishes and the one you choose starts. It has to be published, and the person has to be among the people it is shown to.

Run an in-app action

Runs a function your app registered with the widget, then shows the next step. Use it to open something a step explains, such as a drawer or a menu: the next step waits a few seconds for its element to appear.

Your app registers the function under a name:

Announcer.onAction('open_report_builder', function () {
  openReportBuilder();
});

Then add the action under Sigo AI › Actions, of the in-app kind, with the same name. A page that didn't register it just moves on to the next step.

The tour never clicks elements for your users. Your own code opens what needs opening, so it always does exactly what your app does.

Moving on with a click on the element

If Go to the next step when they is set to Click this element, the step has no Next button: the element is the button. If that click loads another page, the tour continues there.

Starting a tour from a link or from your code

• Add ?usersignal_tour=ID to any address in your app. The editor shows the tour's ID under How often. Use it for a checklist step that starts a tour.
• Call Announcer.startTour(ID) from your app's code.