Launchers can be configured to match your use case and brand guidelines. In this article, we will detail the main aspects of this configuration, by covering:
How to create a new Launcher
What are the main components that can be customized.
How to define where and to whom the Launcher should appear.
To create a new Launcher, you can either:
Click the Create a Launcher button in the top-right corner of your Dashboard's Launchers page.
Open the Chameleon Builder directly in your app and create a Launcher from there.
Once you create a new Launcher, you'll be presented a list of pre-configured templates, which can be used for the common use cases. These templates are:
Help / Training widget
Feature release / Updates log
You can hover over these templates to see a preview of the Launcher on the right-hand side before picking one.
Once you've selected your template, your Launcher will be created with a placeholder name and you'll be taken directly to the editing view, where you can access all the configuration options.
There are a number of key aspects you can customize when configuring your Launcher:
The icon with which the user interacts to open your Launcher.
The Launcher's body, which will present a list of items to your users.
Location and position
The rules which will determine in which pages your Launcher will show, and whether a specific element should exist on those pages and where on the page it will be located.
The Launcher Widget is the icon or interface with which your users will interact to open the Launcher Menu.
You can configure the following aspects of Launcher Widgets:
Trigger: whether a user needs to click or hover over the target to open the Menu
Widget Type/Target: you can choose a default icon, upload your own, set custom text, or select an existing element on your page, to open the Menu
Position: this is available if you use an icon for the Widget. If you choose an 'Element on page' then there is no positioning needed.
Axis adjustment: you can manually adjust the position of the icon, by using px or % values
Colors: if you selected an icon then you can change the colors for this
Tip: You can also use our Launchers API to trigger the opening of the Menu without the need for a widget at all.
The Launcher Canvas is the actual Launcher's body which contains your list of items, which can be Tours, Microsurveys, hyperlinks, search bar, dividers, etc.
You can configure the following aspects of the Launcher Menu:
Content: you can click into the Menu title to directly edit the Header copy
Widget and Height: you can set the width and maximum height for the Menu window. The window height will resize to fit the number of tours displayed until the maximum is reached.
Colors: for the background and text
Checklist: you can choose to show checkmarks adjacent to Tours once they have been completed
Search: you can decide whether to show the search bar in the Menu or not. This is great if you have a lot of Tours, as the search will return matches for any content from these (Tour title, Step body text, etc.).
When all your Launcher items are configured to be hidden when completed, you can determine whether:
The Launcher will also be hidden
The Launcher will remain on the page and an Empty State will be shown.
Opting for the latter, all you need to do is to add an Empty State item and configure how your empty state should look like.
COMING SOON: Launcher items will soon be marked as complete when their success condition has been met, regardless of whether the user has clicked the item within the checklist or not.
Similar to other Chameleon Experiences, you'll also have to ensure your Launcher is showing on the correct areas of your product.
The right way to do this is by leveraging:
URL Rules (under "Display Rules"): Here you can define in which URLs your Launcher will show.
Element Rules (under "Display Rules"): Here you can require a given element to be present on the page for the Launcher to show.
Position (under "Design"): Indicate in which area of the screen your Launcher should show.
Launchers can also be targeted to a specific Segment of users.
This gives you the possibility to create multiple Launchers that fit different use cases. For example, you can leverage a Target Audience of users that are currently in the onboarding phase and targeting a Help Launcher to them.
Targeting Launchers is similar to targeting other Chameleon Experiences. You can define the Launcher's Target Audience from the configuration view on the Chameleon Builder.