Expand my Community achievements bar.

Adobe Journey Optimizer Community Lens 7th edition is out.
SOLVED

Wait Activity - User Journeys that Exceed the 30 Day Maximum

Avatar

Level 1

Is there a way to fulfill a user journey that has multiple actions (email, SMS, etc.) and wait periods that exceed the 30 day wait activity limit? For instance, if a user submits an application, they are sent a thank you email 24 hours after the submission. A journey of sequential emails is then sent to the user 30, 60, 90 days after the application submission. My initial thought is to break them out as separate journeys, but unsure as to how you could accommodate the 60 and 90 day actions as those would exceed the 30 day wait activity limit.

 

I see that a user can add start and end dates for journeys, but not sure if you put the end date past 30 days, if it automatically overrides the 30 day occupancy limit a user can remain in a journey. Any recommendations that can be shared would be greatly appreciated. Thanks!

 

njanky15_0-1694106582979.png

njanky15_1-1694106606067.png

 

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@njanky15, You can have a segment qualification activity where you will have a segment to qualify profiles for those who submitted an application in the past 90days. Separately create four segments(24hr, 30days, 60days & 90days). Each one identifies profiles based on the application submission date. For example, the 24hr segment identifies users with an application submission date =previous day, the 30days segment identifies users with an application submission date =30days, the 60days segment identifies users with an application submission date =60days, and so on. Then within the journey use the condition activity to create a separate branch for 30 days, 60days, etc,.

In this way everyday, you're sending messages that are qualified based on the application submission date instead of relying on the wait activity and journey timeout.

Thanks, Sathees

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

@njanky15, You can have a segment qualification activity where you will have a segment to qualify profiles for those who submitted an application in the past 90days. Separately create four segments(24hr, 30days, 60days & 90days). Each one identifies profiles based on the application submission date. For example, the 24hr segment identifies users with an application submission date =previous day, the 30days segment identifies users with an application submission date =30days, the 60days segment identifies users with an application submission date =60days, and so on. Then within the journey use the condition activity to create a separate branch for 30 days, 60days, etc,.

In this way everyday, you're sending messages that are qualified based on the application submission date instead of relying on the wait activity and journey timeout.

Thanks, Sathees