alan.stephens
Comments
-
What you could do is force the user to snooze the guide rather than dismissing it. i.e. remove the "X" and have a button on the guide which has a snooze action. Snooze can be as little as 1 minut...
-
Hi Hannah - you can make everyone in the segment eligible for it again by bringing it back to Staged status, and clearing the guide metrics. Just bear in mind you will lose all previous analytics i...
-
Hi Susan - We pass across a visitor attribute indicating the date of the visitor's last login (i.e. the one before the current one) to get around that limitation.
-
+1 for more proactive alerting. For example, I would like to be able to set thresholds on guide views i.e. if the guide analytics change from week to week by more or less than X% trigger an alert t...
-
Yes, you can. We do exactly that. We have several surveys running and we use sample group attribute in segment definition to ensure there is no overlap in the audience. Every user is randomly assi...
-
The only way I can think of doing that would be to have 3 separate guides, and in the segmentation include specific rules that state the guide for Spanish users can be viewed by users with a langua...
-
Totally agree with the summary of the challenge around snoozing guides and potential solutions. One workaround to consider would be to have a button action on the guide (e.g. "Minimize") which move...
-
Hi David, I also see this frequently when there isn't actually any obvious error. Would be good to understand what is driving it's appearance like you say.
-
Hi Meredith, if you open the guide designer and click on Activation, you can disable the guide from all activation methods there (Auto, Badge, etc.) That way, it can only be launched by API or Perm...
-
Hi Emma, I think that's just a poor description tbh (i.e. where it says it can only be activated by API) If your permalink guide is live, and the user you are using falls in the segment, I would s...