It's a general best practice to allow users to delay or exit your Experiences if they're not ready to engage with them. In Chameleon, you can configure whether a user should dismiss an Experience and, if so, what should happen next.
š¤ You should avoid interrupting a user who's focused on using your product. Instead, allow them to dismiss an Experience they're not ready to take and learn more later.
Availability & Usage
š Available for all plans
š Ready to enable better Tours, Microsurveys, Embeddables, Launchers
āļø Configure from the Builder
Configuring your Dismiss
With any Tour, Embeddable, or Microsurvey you create, you can enable users to exit or snooze it by using the "Dismiss" option. Find it in the Interactions section of the Builder and access multiple configurations, such as:
Choosing a dismiss Type: cross or text.
Setting its Position: outside right, or left; inside right, or left
Adjusting its Color and size: select from a palette pulled from your page, or insert a HEX code; change the size for both types of dismiss.
Configure a Timed Dismiss: adding a timed delay (in seconds) to your dismiss with the possibility to display the timer.
Action: exit or snooze the Experience.
āØ You can use both the Dismiss component, as well as buttons to allow users to snooze or exit your Experience. For example, you can set the Dismiss to exit a Tour and the button as a "Remind me later" that snoozes it. This way, you create better user expectations around what happens after they engage with your Tour. Learn more about using buttons in Chameleon.
ā¹ If you set both the buttons & the Dismiss to snooze your Experience, the configurations you set will be shared between these components.
When adding a dismiss option, there are two things to configure: the action and its appearance.
Dismiss action
This setting will ultimately depend on your expected outcome -- do you want your users to go through this Experience later on, or do you want it to be exited altogether? You have both options here:
Exit
Users will not see that Experience again, even if they match all the remaining conditions (e.g. URL rules, being part of a user Segment, etc.).
āSnooze
Users will see that Experience again after a set period of time. You can define this period and, optionally, indicate how many times it should reappear until it stops showing altogether. When a Snooze expires on a Tour, the segmentation will be reassessed, and the Tour only shows to users that currently match the Segment conditions.
ā
Timed Dismiss
You can also set the Experience to be dismissed after a set number of seconds, with the option to show the time progression to your users as well. This creates better expectations for users.
With timed-dismiss users will stop the timer if they engage with your Experience, in any way, like clicking or hovering on the Experience, or typing in the input field.
š Snoozing is separate from Recurrence, which defines the frequency you automatically display a Tour to a user. Read more about how 'snooze' takes precedence over Recurrence settings.
Dismiss appearance
Configuring the appearance of your dismiss option involves altering the dismiss type, position, and color:
Type
You can choose between having a cross or custom text for your dismiss option. Custom text can be helpful to set expectations when snoozing an Experience; you can, for example, set the text to "later", "not now", or "remind me tomorrow".
āPosition
You can set the Dismiss to show on the outside right/left or inside right/left side of your canvas.
Size
Change the size of your dismiss cross or text.
Color
You can change the color of your dismiss option by selecting from a palette pulled from your page or inserting a HEX code.
How do I let end-users dismiss a Launcher?
Beyond the Welcome State below, you can let end-users remove the Launcher itself so it stops showing up for them. Enable Dismiss on the Launcher's default state in the Builder (its appearance and re-show rule depend on how the Launcher is placed).
Floating Launchers (the default, widget-based placement) show a fixed white round control with a cross on the outside top-right corner of the Widget. Its only setting isĀ Color, which recolors the cross; while the Launcher has aĀ ThemeĀ assigned, this color is locked to the Theme's dismiss color, and becomes editable once you detach the Launcher from its Theme.
Embedded Launchers keep the dismiss control inside the panel, with the same Type, Position, Text, and Size options described above.
When an end-user dismisses a Launcher, it stops showing to them until your rule brings it back. Launchers don't use the Snooze/Exit choice described above for other Experiences: instead, open recurrence settings from the Dismiss card in the Builder and choose whether the Launcher never comes back, reappears on the end-user's next page load, reappears after a set period (a week, month, quarter, half-year, or year), or reappears once they complete a specific event.
ā¹ If your Launcher opens automatically on page load, Dismiss gives end-users a way to opt out. Read about configuring this in Creating a Launcher in Chameleon.
Dismissing a Launcher Welcome State
In the case of Launchers, your users can dismiss the Welcome State that introduces the menu of items that await them. From the Builder, you can configure the:
style
position
color
size
ā¹ If your Launcher uses a Theme, the Welcome State's dismiss color follows the Theme's dismiss color by default. You can update it to a different color from the Builder on the specific Launcher you are building.
š” Dismissing the Welcome State counts the same as completing its CTA: your users won't see the Welcome State again, and the Launcher opens on its items from then on. To let users close the Launcher itself, see the dismiss section above.
Showing another Experience upon dismiss
You can also configure another Experience to show when a user exits a given Experience. This could be useful, for example, to show a CSAT Microsurvey to measure your user's satisfaction with an onboarding Tour. To do this:
Create the Experience you wish the user to see upon dismissing this one
In the user Segment for that Tour, add a "Chameleon Tour Events" or "Chameleon Microsurvey Events" filter
In that filter, select the name of this Tour, and set the operators as "Was" and "Exited".
