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

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 access this from within the "Trigger" menu when editing a step, from the Chameleon editor topbar:

User action options

You can require one of the following user actions to occur before that step is shown:

  1. Immediately [default]: no user action required; step shows when URL (and element) matches
  2. On click: when a user clicks on: an element on the page; a Chameleon hotspot; or a custom icon
  3. On hover: when a user's cursor hovers over: an element on the page; a Chameleon hotspot; or a custom icon
  4. After delay: User is on the page for a set period of time

When using the "On click" or "On hover" options, you can select a specific element on the page as the subject of this action, or you can use a Chameleon hotspot (pulsing dot) or upload your own custom icon / image. 

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 hotspot

For example, when using the hotspot, you can also decide whether the hotspot should remain when the step shows or not. To cause it to remain pulsing, choose "Yes" for "Hotspot trigger persists".

If you choose "No", then the hotspot will disappear upon step 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. Set where the step is positioned in the "Focus" section. Learn more here.

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
  • [On click - element]: Showing a user help after they've clicked some advanced functionality
  • [On click - element]: Showing help with a user clicks on a confusing element (where they hoped to accomplish something other than the actual functionality)
  • [On click - custom icon]: Help up-sell users by highlighting and explaining functionality that is not available to them, but would be with a different plan
  • [On click - custom icon]: 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. 
  • [On click - element]: Congratulating users for discovering some a cool feature when they first hover over it (to encourage them to explore it further)
  • [On hover - hotspot]: Using custom one-time help tips as a user is learning new functionality

Ignored for first Step 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?