In addition to setting which page a step should show on, you can configure the step to show after a user action, such as a click, hover, or delay.

This can be a great way to add interactivity to your Tour and improve engagement and conversion. There are some examples of how you can use this below. 

You can add such triggers from the Actions menu, under the on-page trigger option.

Trigger types

There are the following trigger types:

  1. None [default]: no user action required; step shows when URL (and element) matches.
  2. Page element click: when a user clicks on an element on the page.
  3. Page element hover: when a user hovers over an element on the page.
  4. Icon click: when a user clicks on a Chameleon icon added to the page
  5. Icon hover: when a user hovers over a Chameleon icon added to the page.
  6. Timed delay: User is on the page for a set period of time.

To do this, click the "Adjust" option:

In this you can configure other options, such as position. 

When you've added a "user action" trigger then this will also be required when you are previewing or testing the step / tour, so that it reflects the behavior for your end users. 

Persistent icons

When using Chameleon icons (for example, a hotspot), you can also decide whether it should remain when the step shows or not. To cause it to remain showing, choose Yes for Icon trigger persists.

If you choose No, the hotspot will disappear while the step sis showing. 

Note: Although you may choose an element to attach the hotspot to, this is not the element the step is attached to. The trigger element can be different to the step position element. Learn more about positioning your steps.

Example uses

Some ideas which you could explore include:

  • [Delay]: Delaying a user onboarding tour starting by 20 seconds to give a user the chance to first absorb the new interface before they are offered help / guidance
  • [Page element click]: Showing a user help after they've clicked some advanced functionality
  • [Page element click]: Showing help with a user clicks on a confusing element (where they hoped to accomplish something other than the actual functionality)
  • [Icon click]: Help up-sell users by highlighting and explaining functionality that is not available to them, but would be with a different plan
  • [Icon click]: Using a "painted door" test to offer potential new functionality, and assess whether users click. Upon clicking the idea can be explained and you can get their feedback, using our Typeform integration. 
  • [Page element click]: Congratulating users for discovering some a cool feature when they first hover over it (to encourage them to explore it further)
  • [Icon click]: Using a hotspot for a custom one-time help tips as a user is learning new functionality

User actions in Manual Tours

For any Tours that are set to be delivered manually any user actions set on the first step will be ignored. 

This will prevent a broken experience where the user starts the Tour (from a link, or Launcher item, or button in another Tour/Survey, etc.) but nothing appears because the first step is awaiting a second user action. 


Did this answer your question?