Dont' send email twice | Community
Skip to main content
Silvio6
Silvio6
Level 5
February 3, 2024
Solved

Dont' send email twice

  • February 3, 2024
  • 2 replies
  • 1737 views

Hi, is there a way via condition or any other activity to avoid contact same profile in a journey twice? I know the "Allow re-entrance" option but it does not help to my use case. I'd like to add like a condition before email checking profile have not been contacted by that email. Thanks.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Mohan_Dugganab

Event data can be accessed only if the journey starts with a unitary event.

 

2 replies

SatheeskannaK
Community Advisor
SatheeskannaKCommunity Advisor
Community Advisor
February 5, 2024

@silvio6, You can use the message feedback event dataset to retrieve the sent status and the messageExecutionID to identify profiles that received the message within the condition activity and branch them accordingly.

Path: 

_experience.customerJourneyManagement.messageDeliveryfeedback.feedbackStatus
_experience.customerJourneyManagement.messageExecution.messageExecutionID

Thanks, Sathees
Silvio6
Silvio6Author
Level 5
February 5, 2024

Hi! ok, but in condition activity here's how can I add it

#{ExperiencePlatform.ProfileFieldGroup.profile.timeSeriesEvents.at(0)._experience.customerJourneyManagement.messageExecution.journeyActionID} == '1768d842-352a-467c-abc9-062af61fe6bd'

But that is nos working. I think I-m missing something in (at(0)) part...

SatheeskannaK
Community Advisor
SatheeskannaKCommunity Advisor
Community Advisor
February 5, 2024

@silvio6, You can use simple mode to define this condition like example below,

Advanced mode will translate like this,

(in(#{ExperiencePlatform.ProfileFieldGroup.profile.timeSeriesEvents._experience.customerJourneyManagement.messageDeliveryfeedback.feedbackStatus}, ["sent"])) and (equalIgnoreCase(#{ExperiencePlatform.ProfileFieldGroup.profile.timeSeriesEvents._experience.customerJourneyManagement.messageExecution.messageExecutionID}, "1234"))

Thanks, Sathees
Mohan_Dugganab
Adobe Employee
Mohan_DugganabAdobe Employee
Adobe Employee
February 6, 2024

Accessing events via yyy.profile.timeSeriesEvents.zzz will not work.

 

You can create a batch segment leveraging the attributes (feedbackstatus, eventtype, timestamp, journeyversionid) of message feedback event dataset and then exclude this segment in the condition node using inSegment() function

Silvio6
Silvio6Author
Level 5
February 6, 2024

ok you mean we can not access event data via condition even if the event dataset is enabled for profile?

Mohan_Dugganab
Adobe Employee
Mohan_DugganabAdobe EmployeeAccepted solution
Adobe Employee
February 6, 2024

Event data can be accessed only if the journey starts with a unitary event.

 

    Terms & ConditionsAccessibility statement

    Loading footer...