Adobe Journey Optimizer

It is important to us that, when you import a package with changes to existing email Fragments the existing Fragment can be updated not just imported. When you use Fragments in many templates it become a problem when the Newley imported fragment comes in as a new "file with a new id" the templates using the old existing fragment is not been updated with the new version. This most be done manually template by template where the fragments is used - and change the old one to the new one. We hope that this can be automated when importing a fragment you can choose is this new one should update a old one - and witch. Even better is you also can do multiple selection where it is the same process for many segments.  

We would like to have the possibility to put conditions on a whole e-mail fragment, on the fragment it self. Meaning when creating a Fragment it would be nice to be able to create conditions on how the fragment should behave when been used. It could be conditions like, who should be able to see this Fragment and not bases on attributes. This can be done today but with coding it directly in the Fragment code. A interface to do this would be very helpful and create a new dimension to the use of Fragments. Yes this can be done inside the template when dragging the fragment in, and setting the condition on the container - but it we do this in the fragment itself this is then pre defined for all user that used this fragment - and is working directly out of the box when dropping the fragment into a template. This is really helpful if you are creating a library with pre defined Fragments with pre defined logic on the fragment. Then the end user can just use them without setting the right

Description - Would love to see Adobe Journey Optimizer enhanced with an AI-based feature that detects and alerts on journey anomalies—such as sharp engagement drops, routing errors, or unexpected delays in customer progress.Why is this feature important to you - Improves real-time decision-making by flagging issues before they hurt the customer experience.Helps marketers optimize journeys proactively rather than reactively.Reduces manual effort in monitoring complex journeys across channels. How would you like the feature to work -This could be powered by Adobe Sensei and visualized through a heatmap or alerts dashboard, with potential tie-ins to Adobe Analytics and Workfront. Curious if others see value in this? Would this help your teams optimize journeys more efficiently?

DescriptionAdobe Journey Optimizer (AJO) currently provides a "Copy Technical Details" option in the UI that exposes key configuration parameters of a journey in JSON format. This includes important fields such as throttlingRatePerSec, entryConditions, and activity configuration. However, this JSON is only accessible manually via the user interface, and not available through any public API. Why is this feature important to youWe are building governance and automation processes to validate AJO journeys before and after publishing. One of our goals is to enforce configuration standards, such as ensuring that the throttlingRatePerSec is always set to a specific value (e.g., 500).Having API access to this technical JSON would allow us to implement:Automated pre-publication approval workflowsRegular audits of existing journeysCI/CD-like governance for journey configurationWithout programmatic access, we are forced to rely on manual inspection, which is time-consuming and error-prone.&n

Description -Currently, when we need to make changes to a published journey in AJO-such as updating content templates or making workflow adjustments-the only option is to stop the journey, duplicate it, edit the duplicate, and then publish it as a new version. This results in multiple versions of essentially the same journey and adds unnecessary steps to the update process.Why is this feature important to you -This feature would greatly improve workflow efficiency and organization. Having to duplicate journeys for every update, especially for routine changes like updating content templates, leads to a cluttered workspace, makes journey management more confusing, and increases the risk of errors. A simpler process would save time for teams and ensure a cleaner, more manageable environment.How would you like the feature to work -After stopping a published journey, I would like the ability to directly edit and re-publish the same journey-including making changes to content templates-witho

Current Behaviour - Currently there is strict rule when it comes to capping. If we set up capping ex. 5 mails i one month then 6 mails in that month would not be send. Why is this feature important to you - service companies (telco, banks) have churn campaigns. Often they would like to ignore message capping rule in order to retain customer How would you like the feature to work - simple checkbox with text - ignore capping rules in journey properties 

Description -Why is this feature important to you - to quickly and easily see what has been sent to our customers and to continuously check and monitor it How would you like the feature to work -similar to the email channel, I can store a seedlist in the channel configuration Current Behaviour - it is not possible to do this in a simple way, we make do with including individual profiles in the segment which we then exclude from the contact rules, all very cumbersome

Description - Increase the maximum number of nodes allowed per journey Why is this feature important to you - for companies with multiple brands (including different sending domains) and complex journeys, this will allow journeys to be condensed into one true journey, allowing customers to flex brand in line with real-time behaviour whilst continuing the journey. We are also limited by the number of journeys allowed, this will reduce the number of journeys that we require whilst streamlining journey management. How would you like the feature to work - For the cap on number of nodes within journeys to be increased, to allow more sophisticated journeys and the encompassing of more channels. Current Behaviour - We are capped by the number of nodes and have to split out programmes across multiple journeys

We have in several occasions experienced that created content in a email templates disappears - and needs to be redone. This is extremely annoying and time consuming for the content producers. There are several theories what this happens, some from you at Adobe also. Like: there is several tabs open with the same template open, or there are several users working on the same Journey and/or email at the same time. To avoid this kind of situations where content actually disappears, we would like to have a features that lock the content to the user that has it open - and changes can not be done to the content by other than one user at the time. When open and try to change content when it is open already a warning message should appear and inform that this template/journey is blocked be user xxxxx. You can take over the editing role by overtaking the role. What we would like is basically a build in control feature that makes it possible for just one user to make changes at th

When you have many master e-mail templates in use, and you need to do a change f ex to styling that is placed in the Head section of the templates, it takes a lot of time to update all templates with the change. If the email templates could have a centralized place where the head section was stored it could be maintained from one place - the whole style config used in the head section for all templates. This makes it easier and faster to maintain the system especially when you have many different templates to maintain.  

It is important to us to be able to select multiple email templates at the same time and do a batch delete instead of deleting one by one. This is time consuming and unnecessary. The same goes for archiving Fragments. It would be nice if we could have multiple selections of Fragments and then do a batch archiving. A similar process is also wanted when you are creating a package of templates and/or fragments to be moved from one sandbox to another. It would be nice if we could do a multiple selection instead of selecting one by one fragment and one by one template into one package, This is time consuming for a administrator to do. We hope for a better and smoother solution here.