Adobe Journey Optimizer

Balrajm · 1/8/26

Hi,

Is anyone came across chained journey in AJO, as long running programs more than 91 days, making them divide and run.

I was exploring solution like updating profile attribute as 1st journey completed and using it to enter 2nd journey, however the challenge is if the same customer eligible for multiple journey at the same time the attribute can be overwrite as last write wins.

SatheeskannaK · 1/8/26

@Balrajm

Here are the two main approaches for addressing this scenario, with their respective limitations:

Using a "Jump" Activity: You can utilize a jump activity if suitable. However, be aware of a key restriction:

"You cannot jump to a journey that starts with an Audience Qualification event or Read Audience."
Reference: Jump Activity Limitations

Updating a Profile Attribute: The other method is to maintain and setup a specific profile attribute for each campaign, as you mentioned. While this approach is not ideal, it currently appears to be the only other available option.

Thanks, Sathees

Balrajm · 1/8/26

Yes, my journey starts with read audience, so can not use jump activity.

The other option is to be only solution, however just I am worried about maintaining more attributes as if customer is eligible for multiple chained journey at the same time then the overwrite chances are there if we use only single attribute. Then end up creating many attributes for each journey.

SatheeskannaK · 1/8/26

Yes, that's correct. Maintaining a specific attribute for every journey is indeed a challenging and cumbersome process.

Thanks, Sathees

Balrajm · 1/8/26

right, also exploring solution around using a journey feedback event dataset(

ajo_message_feedback_event_dataset

to filter out profiles which receive a specific email from last joinery where it braked? Any thoughts on this?

with using journeyversionid and messageExecutionID

SatheeskannaK · 1/9/26

Yes, you can setup a batch audience using the message feedback event dataset. Remember, there's a TTL associated with the dataset on how long you can look back.

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

You can start with journeyversionid and actionID for this.