Configuring abandon basket event in AJO | Community
Skip to main content
Michael_Soprano
Michael_Soprano
Level 10
July 16, 2026
Question

Configuring abandon basket event in AJO

  • July 16, 2026
  • 1 reply
  • 28 views

Would you build this event based on ECID identity of Email identity? 

Execution field is taken from profile attributes and the email attribute might not be present in the event payload ….

Any advise??

1 reply

SatheeskannaK
Community Advisor
SatheeskannaKCommunity Advisor
Community Advisor
July 16, 2026

​@Michael_Soprano 

  • I believe your abandon basket captured via Web/Mobile SDK behavioral events

  • ECID is automatically populated on every single hit.

  • Email is only included in the event's identityMap if explicitly set, such as after a login.
  • Keying the trigger event match on Email will result in missing sessions where the user has not authenticated, which represents a large portion of the cart abandonment audience.
  • Why the execution step can still find Email even though the event didn't have it:
    • The send-email action reads the identity off the stitched Profile rather than the triggering event.
    • The profile lookup at send-time will successfully resolve the Email as long as:
      • The ECID from the browsing session is or becomes linked in the Identity Graph to a namespace carrying an Email attribute (e.g., via login, any other data ingestion).
      • Your merge policy has Identity Graph enabled with Email namespace included in the stitching.
      • This stitching has already occurred by the time the journey action is evaluated.
Thanks, Sathees
John_Man
Community Advisor
John_ManCommunity Advisor
Community Advisor
July 18, 2026

​@Michael_Soprano 

  • I believe your abandon basket captured via Web/Mobile SDK behavioral events

  • ECID is automatically populated on every single hit.

  • Email is only included in the event's identityMap if explicitly set, such as after a login.
  • Keying the trigger event match on Email will result in missing sessions where the user has not authenticated, which represents a large portion of the cart abandonment audience.
  • Why the execution step can still find Email even though the event didn't have it:
    • The send-email action reads the identity off the stitched Profile rather than the triggering event.
    • The profile lookup at send-time will successfully resolve the Email as long as:
      • The ECID from the browsing session is or becomes linked in the Identity Graph to a namespace carrying an Email attribute (e.g., via login, any other data ingestion).
      • Your merge policy has Identity Graph enabled with Email namespace included in the stitching.
      • This stitching has already occurred by the time the journey action is evaluated.

 

Also working on similar scenario, while Web/Mobile SDK can populate the Email to the profile identity after login/authenticated, it cannot populate to the profile attribute, so in order to send the cart abandon email, the email address has to be populated to the profile attribute with custom profile update script or from other data source. Or is it possible to configure the Email Execution field to use the email in the profile identity field instead of attribute?

 

 

Terms & ConditionsAccessibility statement

Loading footer...