Planning Your Experience
Last updated
Last updated
Determine when your experience becomes active with options for immediate launch or scheduled activation:
Set a Starting Date: Schedule the start by selecting a date and time in the future.
By default, the time is prefilled with the date of creation. Set the date to 'Now' by clicking on the cross "X" to activate the experience immediately.
Set an Expiration Date: This option is perfect for timed campaigns or feature releases. By default, experiences are published indefinitely, but you can add a date on which it will be automatically paused.
You can pause and restart published experiences anytime from your Dashboard.
Control the repetition frequency to manage how often an experience is presented to users.
Once: Ideal for one-off announcements or welcome messages. Once the user has seen the flow, it will not reappear. This depends on a user seeing or completing the first step of the flow, and behavior can vary slightly depending on whether the first step is a modal, snippet, tooltip, or hotspot.
It is the default and recommended option to make sure not to overwhelm users who skipped the experience.
Every Time: The experience will display every time a user meets the trigger conditions. Suitable for persistent guidance or reminders.
A very useful option to test but don't forget to switch it back, it may bother your users to have a constantly reappearing pop-up.
Custom Time: Set a custom recurrence schedule by specifying the frequency that suits your campaign needs.
You currently can set the frequency only in days. It's really useful to set reminders for surveys or already-known recurrent announcements.
Manage user exposure to avoid overwhelming them with multiple experiences:
Rate Limiting: Toggled by default, this option enforces display frequency rules. It helps you maintain a great experience for your end-users and prevent them from being overwhelmed by too many experiences.
Be careful it might cause you not to see your experience live, you can disable it while you are testing, but as for the "every time" recurrence don't forget to switch it back.
It's a project-wide parameter, go to your settings to set the maximum number of in-app experiences a specific user can see within a specific time range.
Check out our notice about it
Prioritize the order in which multiple live experiences appear:
Priority allows you to define an order between live experiences when there is a conflict, usually multiple experiences published on the same URL. (Higher values are displayed first.)
For example, a Poke with a priority of 10 will be displayed before a Poke with a priority of 9.
->
