Merging two Guides

Learn triggering guides from another guide's step or a hotspot.

Gabriel avatar
Written by Gabriel
Updated over a week ago

Overview

In UserGuiding, guides can be butt spliced. In other words, you can start a different guide from a running guide's final step.

Or, they can be ramified if you give an option to users to trigger another guide from the intermediate steps of the Guide.

In addition to the above, guides can be placed into and triggered by hotspots. To configure any of the above:

  1. You can use the "Guide List" component within the guide steps.

  2. Or, use Custom Buttons set to the action of Trigger a Guide within guide steps.

Guide List

You can select the Guide List component from the new component menu to add Guides to your guide steps and hotspots.

This way, you can use a Guide step or a hotspot as a medium to trigger another guide.

If you add more than one Guide, you can ramify the user experiences through guides. This action allows end-users to decide on which Guide they want to launch.

  • After clicking on the Guide List component, the unit will be automatically added just above the green +ADD button.

  • To select a guide to be added, click on the white area.

  • It will open the section from which you can select and add guides.

Guide List Items: Here, you can add new guides to your list or extract existing ones from your list.

If you're showing custom guides to specific user segments, turn on the "Hide if segments don't match."

The linked Guide can't be displayed for an end-user who doesn't meet your segment rules. So when choosing a Guide to be added, be sure to check the segment rules for the List's Guide as well.

Above, from left to right, respectively, you can find:

  1. Guide List Items

  2. List Item Properties: Roundness, Height, Font Size

  3. Surrounding Paddings

  4. Delete

Once your Guide or Hotspot is published and a user clicks on a Guide in the List, the current Guide or Hotspot will be automatically dismissed, and the listed Guide will be activated.

If you choose a guide that can't be activated on the current page, the current Guide will only be dismissed.

Custom Buttons set to the action of "Trigger a Guide"

Customs buttons are components you can add to a guide's step or a Hotspot. To add a Custom Button to a guide's step

  • First, click on +Step on the step editor and choose a step type.

  • Once you select a step, find it on the page, click on +ADD in green to open the New Component Menu, and select the Button.

  • Once you select the Button, a template button saying GO will be added as a new component. You can change its text simply by clicking and typing.

Each time you click on the button, a new one will be added. You can change their location with the actions of drag and drop. As you can see in the following example:

  • We've selected two buttons,

  • Change one's text to DISMISS and put them side by side,

  • We've also canceled the requisite default buttons in Chrome Extension.

Now it is time to set the "GO" button to a custom action: What will happen when end-users click on it?

Then click on a button to open the setting menu, from left to right containing the following items:

  1. Text alignment

  2. Surrounding Paddings

  3. Button Properties

  4. Action ---> is what happens when you click on this button.

  5. Delete

  • If you click on the arrow icon on the above image, you'll see that the default action is Go to the Next Step - click on it and see what your options are:

  • You will select the Trigger a Guide.

Trigger a Guide

When you choose this option, you will be prompted to select your desired Guide from a dropdown list of guides.

To merge two guides for creating an uninterrupted end-user experience, you can trigger a new guide on the last step of another one.

Through intermediate steps containing custom buttons that can trigger other guides can make your content branch out intelligently.

Did this answer your question?