Adobe Journey Optimizer

Hi @PuneetLa 

We don't have visibility on the roadmap. We can it to the product team. As a work around, I will say to use the datasets lookup personalization as fragments have guardrails and limitations

Thanks,

David

@PuneetLamba_ 

Adobe is improving and updating the Sandbox Tooling frequently. Please check the lists of Adobe Journey Optimizer objects that are currently supported for sandbox tooling and limitations

In the August 2025 release, a main improvement is below

Sandbox tooling will now always reuse existing objects if objects with the same name are detected, to avoid object proliferation. This change applies to the following objects:

• Schema
• Field group
• Audience
• decisioning_ranking
• decisioning_rules

Support and/or Product team are working on this issue. Please open a ticket with Support to get a fix or a viable workaround.

Agree. We've abandoned incremental read because it essentially prevents journey versioning (causes incremental read to reset)

For anyone that's facing a similar limitation on the Incremental Read option in relation to journey versions, you should be able to accomplish something similar, leveraging an audience exclusion.

1. Configure the journey audience to be read as the starting point of your journey as you normally would.
2. Configure an audience for all profiles that have already been contacted as part of the journey. For this audience, define the criteria in relation to your re-entrance period. If you'd like to allow someone to be contacted again after 14 days, this audience should be defined, for example, as customers who have been contacted in the last 14 days.
3. Enable the use case described by reading the audience described in step 1 then excluding the audience described in step 2.

This set-up should allow for re-entry after the customer has moved through the journey but prevent them from being contacted more frequently than you'd like.

Thanks, @Sukrity_Wadhwa. I'm happy to be here and looking forward to hearing from the community!

Hi @PuneetLamba_, refreshing the page will update the thread with any new responses. You’ll also receive a notification via the bell icon on your community profile whenever there’s a new comment or reply. 

I'm not aware of this specific issue but I'd start by focusing troubleshooting on your Mobile SDK implementation. 

Use Assurance to validate that the events you've configured as triggers within Journey Optimizer are, in fact, being fired when expected. It may be that there's a reason within your implementation that the events that trigger the message are not being fired.

In the event that you've validated that, I would also double-check the frequency settings within the in-app message configuration.

If you've already validated that the events are being fired as expected and the frequency settings are not going to block the expected message display, then I'd open a ticket. In the event there's actually a bug, leveraging the details from the debugging done in Assurance (mentioned above) will help narrow in on the specific issue with engineering.

Thank you Adam for your inputs.

There's no out-of-the-box alerting option for this specific scenario but there's a few ways to approach this.

• If your marketing teams are already using planning tools (such as Workfront) that allow for custom notifications or reminders to be configured, you can build these reminders into your planning templates there.
• A simpler, alternative, option would be to incorporate the inclusion of "Journey check-in" reminders in your journey/campaign set-up process. Whenever a team member is developing and publishing a journey, they would create a reminder in their calendar to check-in either at a set point within the journey duration or a few days before it's intended to expire. This would ensure any journeys which may require action will not be missed.
• A complementary option would be to develop a tagging structure within Journey Optimizer that identifies journeys or campaigns expiring on a set day, week, or month. Your team could then build an activity into their day-to-day activities where they filter on those tags and review any campaigns which will be expiring soon.

Adobe Experience Platform provides several predefined alert rules that you can enable.

Here is a tutorial to subscribe to data ingestion alert using Adobe I/O Events notifications

You can leverage this approach with Observability Insights to build your own monitoring/alerts

There are a few out-of-the-box alert options for specific journeys.

If you're leveraging custom actions, you can be alerted when any of those actions leveraged within your journeys fails. A threshold can also be set in case you're only interested in being alerted if the action fails on more than <xx>% of profiles moving through the journey.

If your journey is leveraging Read Audience actions, you can also configure an alert to ensure you are notified if there is a failure in reading profiles on recurring journeys.

Details on these journey-specific alerts can be found within the product documentation here.

A side-note on alerts; if you'd like to be notified outside of the platform UI, double-check within your account settings to ensure you have email notifications enabled!

As of today, AJO offers several tools for conflict management and prioritization. These tools are available for campaigns and unitary, Audience Qualification, and Read audience journeys.

• Conflict detection tool
• Priority scores
• Rule sets

Find mor details here

It's not recommended to use the same trigger at the different stages of your journeys. You can try to leverage Rule-based events to identify the relevant events that will trigger your IAMs at the stages. This rule can be based on any field available in the event payload but as best practices do not over engineering.

Thanks

Great question!

While customer actions are the most common use case, you occasionally want to trigger a journey based on an event that's not tied to an individual profile. This is where Business Events are useful.

There are a few things you will want to consider when setting these up.

• What use cases do you want to enable? Do you simply want marketers to be able to trigger journeys ad-hoc or do you want journeys to be triggered on a more general class of events (for example, the start of a sale/promo period).
• Usage of this feature requires an Experience Event schema so you will need to create a schema based on the scenarios you want to enable.
• How will marketers send data to the platform? With your data modelled in a schema, event records prepared for this schema will need to be ingested into the platform.

With these things considered, you can leverage these business events within a journey where the occurrence of one of these events will trigger a journey that subsequently reads an audience of customers for inclusion within the journey you define.

Thank you, @Sukrity_Wadhwa, and to the community for the great questions!