Triggers that should be fired only once

Answered

4 Comments

  • Ramin Shokrizadeh
    Comment actions Permalink

    Hi Alex,

    Sounds like you know the answer already :) Identity is based on cookies and the triggers fire based on the activity for that specific identity. 

    Looks like your website uses Intercom already, so in theory you could use an authenticated user there and it would only fire once. If you want to use a Zendesk product to do this, you can use Outbound and authenticate the user using the Javascript API: https://developer.zendesk.com/embeddables/docs/outbound/javascript#identify-a-user

    We have no immediate plans to change how identity works in Chat for 2018.

    Thanks,

    Ramin

    0
  • Alex Hudenko
    Comment actions Permalink

    Hi Ramin,

    We are in process of moving from Intercom to Zendesk. We are going remove Intercom completely soon.

    Now we identify users for chat via:

    zE.identify(....);

    If we change it to: outbound.identify(....); will it works better?

    Regards, 

    Alex

    0
  • Ramin Shokrizadeh
    Comment actions Permalink

    Using the Outbound product and the identify call (which requires you to specify the ID), the identity is no longer tied to the browser cookie but the set identity ID in the API call.

    0
  • Lone Prairie Camp
    Comment actions Permalink

    The "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

    0

Please sign in to leave a comment.

Powered by Zendesk