To ensure an even more contextual delivery to your users, you can time your Chameleon Experiences to your brand efforts. Use our Scheduling feature to control exactly when your Experiences should start displaying or stop appearing to your users.


Note: This feature is available for Tours and Microsurveys.


How can I schedule Experiences?

Creating an Experience and setting it up for success are two different things. Scheduling is a core activity in your configuring workflow.

As you build your Tour or Microsurvey from the Chameleon Dashboard, access the Scheduling options in the final step of your configuration, under “Review & publish”. With each Experience, you’ll find helpful options to control how to display it to your users.

With Tours you’ll have a few core options when controlling the display time:

  • Publish your Tour right away.

  • Schedule your Tour to go live at a custom date in the future.

  • Set your Tour to be displayed forever.

  • Unpublish your Tour at a custom date in the future.

scheduling options for Tours

Combine these options to fit the timing and specific goal, so your Tour always hits the right spot.

For Microsurveys, you’ll have a key action to help hone in the right feedback: unpublishing after receiving a specific number of responses.

To make sure you keep the feedback high-signal use the unpublishing option to cover just the right amount of respondents for you.

Once you've configured your Experience display life you will also see a confirmation on top, next to its name.

scheduling confirmation message

How to get the best out of Scheduling?

Scheduling Experiences helps you save time while coordinating in-product adoption efforts. Here's some advice from us to get you started:

  • Align your Tour or Microsurvey with active promotions, campaigns, or new feature launches.

  • Control the relevancy of your content by always aligning it to your product roadmap.

💡 Keep in mind that any brand efforts are relevant to your users when they are fresh and relatable.


Up for more?

Did this answer your question?