In UserGuiding, you can manage your guides through their settings page. In this article, we explain all of the subsections falling under guide settings.
To have detailed information about each of them, you can use directory links given throughout the article.
As the name implies, here you can change the status of a guide. It can be active or inactive. To display guides for end-users, its status should be active. And to make it invisible, you can change it as inactive.
The Guide ID: It is next to the Status Field on top.
Guide Name: This is the section where you can edit a guide's name and description.
Targeting is the process that you determine on what page or pages you want a guide or some other content to display.
A target is composed of A Rule and a URL bit and, its functioning is depicted as it is read from left to right.
Let's all look at the guide's targeting that is shown us here below:
If a page's URL equals to https://userguiding.com/, this means the sample guide will be displayed on it.
To have in-depth information, see also: What is Targeting?
Segmentation is a feature that helps you to create end-user segments or groups. Created segments are used throughout UserGuiding to filter users and target them for guides, hotspots, and checklists.
If a visitor meets all rules of a segment, they will be included in that segment which is used for targeting a guide or, etc.
With Audience Segmentation, you can set the right coupling in the guide's settings page, and make sure your guides are visible for the right audience.
You can set user segments to guides, hotspots, checklists, help centers, and NPS.
To learn how to create user segments and more, read What is Segmentation?
Here, you can define a triggering method for your guides. This will be the predefined behavior of a guide to display for end-users.
Auto is the default triggering method of a guide. It means that if end-users match the segmentation condition of a guide when they arrive on the targeted page(s), the guide will automatically show up.
Other methods besides auto-trigger all considered as custom. If you choose any of the following custom triggering methods, your guide won't show up unless people trigger them with the way you set.
Custom triggering method examples are:
- Triggering a guide via Checklist or Help Centers.
- Triggering a guide by using its hyperlink.
- Events and triggers in Google Tag Manager.
- Any prerequisite action that you can define to trigger a guide.
Important: The Guide ID is located under the Guide's Settings Page right next to the Status Field on top.
Always means that your guides will be shown to end-users of the correct segment each time they arrive on the targeted page.
Only Once means that your guides will be shown to end-users of the correct segment only once when they arrive on the targeted page.
Each content you create such as guides, hotspots, checklists, etc. should be placed inside the embedded container code, to be displayed within you we app.
At first, a guide is set to your default container. By changing its container, you can take a guide from one embed code and place it to a different one.
To have in-depth information, see also: What are the Containers?
Guides that you create with UserGuiding can look native-like, if you set a custom theme to them, befitting your web application.
To learn how to create a custom theme for your guides, you can read: Creating Themes
To preserve and publish the current setting of a guide or any other content, always remember to Save and click on the green publish changes button.
Publishing changes will make your guide's final state visible on your webpage.