@rterakedis - I thought that a guide was completed if someone saw every tooltip and dialog in the guide. Otherwise, I think that it is viewed.
Hey Everyone! Here are the answers from our Product Team but I have also requested us to create some better documentation around this
If an engagement is snoozed is it counted as a view but not a completion?
- Yes, it is counted as Viewed with a Snoozed action taken.
- The Snoozed engagement is not counted under Completed
- Only for a single step Guide - even if user snoozes the engagement it is marked as complete because the user has seen the engagement.
We will look at fixing this that a Snoozed engagement at that is not to be considered as Complete in that interaction.
Do we have reporting on the number of users who have snoozed?
- In the analytics, there will be a column for Snoozed which if non-zero then denotes that the user has snoozed the Engagement
- There is no direct filter for now - but from Analytics you will be able to check the users who have Snoozed the engagement
How does it work with throttling and priority if using the only once qualification scope?
- If the engagement is not marked for Ignore Throttling then a snoozed engagement will adhere to the Throttling norms because a Snoozed engagement is also counted as a View
- Hence Throttling will be adhered to.
What is the difference between the skip tour button and the snooze button when on an interval scope?
- Functionally Skip and Snooze will not have any difference for Interval Qualification scope
- The difference will only arise in analytics - where Snooze interaction can be tracked but not the Skip.
If a user will not meet the qualification scope again after they have snoozed it, will the engagement just not reappear? ie, if an engagement is set for 'all users who have used x feature less than 1 time', will the users not see this engagement again since they're no longer qualifying for it?
- Yes, for a user to be able to see the snoozed engagement, the user needs to qualify for the engagement at that point of time. Our real time evaluation mechanism triggers only those engagements to the user for which they qualify.
If an engagement is paused before a user is able to see the engagement after snoozing it, will the user still see this engagement?
- A completed or paused engagement is never triggered to any user and we follow the same irrespective of an engagement was snoozed or not.
Also just FYI this is currently Planned in our Roadmap (no firm date)
@kathleenkenny23 - This is excellent! Thank you for tracking this all down and for laying it out so well! This definitely helped fill in the blanks!
Hi @kathleenkenny23.
@jmobley has been looking into this as well, but I thought I would add to this thread.
The only thing that is still outstanding in my mind is if snooze and close (the upper-right “X”) are functionally the same (except for the tracking of snooze that you mentioned)? If we have the engagement set for the user to view 3 times with at least 7 days between views, they’ll only qualify to see it 3 times total, regardless of whether they click snooze, correct?
@jmobley has confirmed my previous point… Snooze and the X are functionally the same with the only caveat being that the snooze-click is recognized and in the report.