Avoiding Duplicate Attentive Events with Elevar

You have just set up your Attentive server-side tracking with Elevar, now you might be asking whether or not you need to disable my old client-side Attentive tracking. The answer is that you do not need to and we actually recommend keeping it!

Running both your client-side and server-side (Elevar) tracking together helps maximize coverage for key journeys like cart and browse abandonment. But naturally, that brings up the next question...

Will This Send Duplicate Texts to My Shoppers?

It's a valid concern. Both client-side and Elevar’s server-side tracking may capture the same action (like an Add to Cart), which means two events could be sent to Attentive. Whether that results in duplicate messages depends on how your Elevar destination is configured:

If Your Elevar Destination is in Test Mode:

• Your events are sent as Custom Events to Attentive.
• To avoid duplicate texts:
  • Create a new Journey in Attentive that triggers on the Elevar Custom Event.
  • Add logic to exclude users who triggered the client-side version of the event in the past 2 days.
  • (Example: Exclude users who triggered the standard “Add to Cart” event recently.)

If Your Elevar Destination is in Live Mode:

• Your events are sent as standard eCommerce events to Attentive.
• Both client-side and server-side events will go into the same Journeys (like cart or browse abandonment).
• If both events are received, Attentive will use the first event it receives, and the second will be discarded.

This is thanks to Attentive’s Entry Frequency rule, which limits how often a subscriber can enter a Journey: