Hi @carol.hutchinson ,

Dialogs are a special case of Guides (single step Guide = Dialog) and hence we recommend using Guides new editor to create Dialogs and be able to use all the functionalities of Guides in the Dialog step. Hence, we did not develop the Snooze button for Dialogs and there are no plans either.

Please let us know if there is any specific Dialog functionality which you feel is not available in Guides new editor then we will look at providing that in new editor and not vice versa.
 

Thanks,

Abhilash

Hi Abhilash, 

Thank you for confirming. We haven’t been using the new editor but managed to use the Guide to have a Dialog Engagement with the Snooze button included using the old editor. 

Unfortunately when we were testing with the Qualification Scope set to display the Engagement again at Intervals (set at a minute apart for testing) the Engagement wasn’t displayed to us again as expected when choosing the Snooze button.

Is there particular settings we have to be using or do we have to have made the Engagement using the new editor for it to work? 

Hi @carol.hutchinson ,

The Behaviour of Snooze button will be same irrespective of the editor you use. The engagement would get snoozed again based on the qualification. If your interval gap between two view is say 1 day then the engagement would get triggered again after a gap of 1 day. Also, if you have any throttling settings in place, then the Snoozed engagement will honor the throttling configuration. So if there’s any throttling collision, then there can be a delay in trigger of the said engagement too.

Thanks,

Abhilash

@aharkut - So, to add a snooze to a slider that is supposed to auto-open 1x, we also need to add an interval, such as 1 hour or 1 day?

Hi @mmarques ,

You need not necessarily use Interval for Snooze. It can work for any qualification scope:

1. Only Once - As long as user keeps on snoozing the engagement until then the user will be shown the engagement.
2. Interval - Engagement would be snoozed for #Times it is configured to be shown and will snooze after the frequency (#Hours, #Days etc) that is provided
3. Once per visit - It is shown every time user visits the application and qualifies for the engagement but the engagement is triggered only once per session.
4. Paywall - It is shown every time the user qualifies for engagement irrespective of session completion or not.

Few points to note for Snooze:

1. Since it does not have much impact on Once per visit and Paywall functionally we recommend not to use Snooze on these engagements
2. All engagements irrespective of snooze/ not - they follow throttling if the engagement is not ignored for throttling
3. Once Once can be snoozed multiple times whereas in Interval you can control the number of times user can snooze
4. If any engagement meets completion time then that engagement will cease to snooze
5. Only Once is recommended qualification scope for Snooze enabled engagement.

Let me know if there’s anything left unanswered.

Thanks,

Abhilash

Thanks @aharkut for clarifying!

@aharkut  - I’m now testing out for “Only once” qualification. Please see my question here: