How to use exit criteria to remove an already contacted email address

[DanSpigs1]

Hi,

I am working in a system where the same email address can be associated with multiple profiles.  The profiles need to be distinct, however for the purposes of this email send I do not want the same email address to be contacted multiple times, even if each profile would qualify independently.  Previously in Adobe Campaign I would just dedupe my audience on email address. I am trying replicate this kind of behavior in a journey in AJO.  One thought was to use exit criteria for the journey and exit any profiles where the email address had received the contact, but that still means in the initial touch in the journey there could be duplicate email addresses. Has anyone dealt with a similar situation and if so how did you manage it?

[Silvio6]

Using a streaming audience and add it in a Condition?

[DanSpigs1]

Thank you for your response, unfortunately I need to do this for a batch audience.  I was continuing to dig into the documentation and saw that was an option for streaming audiences.  Is there any way to do the same for batch?

[Silvio6]

not sure if I'm understanding well but I mean creating a streaming audience with profiles who received that email, so then in journey, add that audience in a condition just like "not in (AA audience)" just before the email so that profile won't receive the email.

[DanSpigs1]

Gotcha, that might work!  Let me play around with that. Thank you!

[SatheeskannaK]

@DanSpigs1 Take a look at the recent update on the streaming segmentation will no longer support the use of send and open events from Journey Optimizer tracking and feedback datasets.

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/data-management/datasets/datasets...

You will have to use the batch audience to exclude the records from the initial touch in the journey.

[DanSpigs1]

Thank you for your reply.  Based on this comment how would you recommend I solve for the following use case.

Profile A and Profile B share an email address. Both qualify int he audience for Journey 1 which is being sent in incremental waves.  I want to ensure that the email address is only contacted on one occasion during the entire journey.

I don't have any easy identifiers to only include one and not the other for a separate batch as their information is largely identical, but they need to be maintained in the system as 2 distinct profiles.

Appreciate any guidance here.

[DiegoPa6]

Hi SatheeskannaK,

Could you provide more details on how the TTL reduction would affect the ability to use sent and open events in streaming audiences? The documentation you shared doesn’t fully explain this. Would it be because profile data is only retained for 3 months and the data lake for 13 months?

Thanks in advance for your clarification!

Best regards,
Diego P.