"Fire only once per visitor" Doesn't Work
RéponduThe "Fire only once per visitor" should be renamed to "Fire only once per visit" or (even better) fixed. This isn't just a cookie issue. A user can have a high previous "visits" count but the trigger will still fire because it is a new visit even though it is NOT a new visitor.
Tags don't persist from one visit to the next, so tags can't be used to limit a trigger to once per visitor.
Triggers can append something to the notes, but notes can't be used as conditions, so notes can't be used to limit a trigger to once per visitor.
Using Visitor previous visits doesn't work because my trigger only fires when we are online (ie. they may have visited while we were offline, didn't see the trigger then but should see if for the first time now).
I have spoken to multiple agents and no one can offer a solution that genuinely limits a trigger to once per visitor.
The "Proactive Greeting" is VERY annoying without this fix.
-
Hi there Lone Prairie Camp,
You posted the same feedback in multiple posts, so will be just be answering here.
Based on your request of wanting to show the message only once per visitor, you should look into using the Zendesk Outbound product instead of the trigger functionality inside of Chat.
You can learn more about the Outbound product here: https://www.outbound.io/
We have no plans to change the Chat trigger functionality in 2018 so that it would only fire once per visitor beyond the id in the Chat cookie on their browser/device.
-Ramin
-
Can I somehow use the ID in the Chat cookie on their browser/device to limit the trigger to once per visitor?
-
Not possible at the moment. We are working on authenticated visitor support in the widget that would carry over visitor stats across devices/browsers, but it wont be available for a couple months.
-
Just to make sure: The "Fire only once per visitor" fires only once per visit? Am I rigth?
-
Hi Clemens,
It means once per visitor and the visitor is defined by the id in the cookie required for the widget to load. If they use a different browser, device, or remove the cookie that will cause the cookie id to be different then the trigger will re-fire.
-Ramin
-
Hi Ramin, I don't think your reply is accurate. The system knows the user is a repeat visitor (ie. a user can have a high previous "visits" count) but the trigger will still fire because it is a new visit even though it is NOT a new visitor. If this is caused because they use a different browser, device or remove the cookie, how is their previous "visits" count over 0?
-
@Lone Prairie Camp, please email chat@zendesk.com to get help with your triggers setup. The advocacy team can look into why it is firing multiple times. Thanks.
-
Hi Ramin,
The problem I was having (and was confirmed by support several times) is that a user can have a high previous "visits" count (ie. have the cookie) but the trigger will still fire because it is a new visit even though it is NOT a new visitor.
I did some testing today and it looks like the issue may have been resolved since I reported it 8 months ago. I will circle back if the issue resurfaces, but I think it may have been fixed.
-
Ok, thanks for the follow up. Let me know if you notice the problem resurfaces.
Vous devez vous connecter pour laisser un commentaire.
9 Commentaires