Adobe Journey Optimizer

There is a Seed List feature in AJO when it comes to use of Seed Lists, but that needs to be further developed. Today the Seed List is configured on the email surface. That means that you cant decide if you want to use it or not, when the surface is used. F ex if you have a marketing surface and you use that surface for "all" your emails, like onboarding, sales and Newsletters. Whatever you are sending with that surface is using the Seed List even it is wanted or not. A use case is it Customer service wants to know what has been sent out in a mass sending, like a Newsletter. Then the Seed List works great. But it you then use the same surface for your onboarding activities, customer service gets a copy of each and every single email that runs through the onboarding prosses.  Our ideas is if you can decide from the email node configuration if you want to use a Seed List or not. And if you also could select from a list over different Seed Lists, who you wanted to use, this

Description -We need the Abiltiy  to determine the engagement of customer based on the the Journey or Campaign Name in an audience.  In particular, to state, if the Journey Name starts with/contains "xyzFY25..." Why is this feature important to you -Currently, we can only use the Journey ID, which means that we need to manually update the audience each time a different journey would be applied. When a Journey is updated and republished this creates a different ID, more additional work.  How would you like the feature to work -Journey Name would be a variable when creating Audiences and searching for an event.   Current Behaviour -Only the Journey Version is available.

DescriptionWe would like an API in Adobe Journey Optimizer (AJO) that allows us to preview an email template for a given profile. The API should return the rendered HTML of the email as it would appear when sent to that specific profile. Why is this feature important to us?We have existing tools that measure email quality, score campaigns, and validate templates before sending. How would you like the feature to work?An API endpoint where we can pass:Profile ID / Attributes to generate a personalized preview.Email Template ID or campaign details to specify which template to render. The API should return:Fully rendered HTML of the email as it would appear for the given profile.Any errors or warnings if there are missing personalization fields or rendering issues. Current BehaviorCurrently, AJO does not provide an API to fetch a personalized email preview for a profile.

Description -Why is this feature important to you - - We need to share an annual receipt with our customers for tax purposes.   The file needs to be in a format that is not easily editable. - Not all customers have an account, so the requirement to create and account to access the PDF is not an option.   How would you like the feature to work - - We need to be able to pick up the appropriate version of the PDF from a server based on customer ID and attach the version to the email and deliver to the customer.   This is possible in other Email Solutions (Acoustic, SendGrid, MailGun) - A url to the PDF is not acceptable....unless the URL could locked down to only that email address, with no ability to guess/hack/scrap and determine the location of the other files for the customer.  Current Behaviour -Need to engaged Third-party tools

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. 

Description:Introduce a "Pause" functionality for journeys, allowing temporary halts without permanently stopping them. This would help address short-term issues while preserving the integrity of the journey data. Why is this feature important to you:A "Pause" feature provides flexibility in managing journeys by enabling quick fixes without disrupting the entire process. It ensures that IDs remain consistent and avoids mixing or fragmenting reports, which is essential for accurate performance analysis. How would you like the feature to work:The system should include a "Pause" button alongside the existing "Run," "Stop," and "Close" options. When paused, the journey should retain its current state and resume seamlessly once issues are resolved, with all IDs and reporting data remaining intact. Current Behaviour:Currently, the only available options are to run, close, or stop a journey. Stopping a journey disrupts continuity, alters IDs, and complicates reporting, making i

Description - Why is this feature important to you -Business wants to understand the profile count for reporting in advance without actually triggering communications (Email/DM/SMS) but custom action can work as intended. This is mostly because of condition checks added in the journey and, to gauge the journey's behavior given the high volume.  How would you like the feature to work -1. Do not want this journey step events data going into the steps events schema as this is just a dry run. OR even if it writes it, expire the data after couple of hours. Given the high volume it is not ideal to write it (so toggle option to write or not would be good).2. Mock the Email/DM/SMS activity - Real communications must not be triggered except for test profiles.3. Produce a report to share with the business. Current Behavior -1. There is no dry run capability.2. Test Profiles option does not help much.

This is just a small idea to work more aligned with who other applications use folders, and how we as users are used to work with folders. It would help the way of working if AJO could adopt what is established way of working with folder structures. I am sure it is created in AJO for a reason, but for us as and users it creates a lot of irritation and frustration. Why do we need to unpublish a published landingpage just for moving it into another folder - that dont make any sense. And if we then connect access right issue with it, it becomes even worse. You can unpublish, move - but not publish it again. It could be local sett rules, but this seams a little over complicated. If you have access rights to the landingpages, you sould be able to create a folder, and move a page to that folder without unpublishing the page, move it and publishing a gain. I guess the page had the same ID where ever in the structure the page is. This process creates frustration on several levels - f

The folder possibilities for storing Audiences in a folder structure has become a nice function. It save a lot of time to find your right Audiences when you dont know exactly the name. I would like to expand this functionality to also be able to use for Offers and Journeys. It will makes it easier to find what you are looking for. To be able to work even faster it would be nice with  f ex a button in/on every folder that with one click could open the folder tree from where you are standing/clicking. It is nice with the tree but we still need to go inn and out from the folders to fint what we are looking for it we operate with a deep folder tree. 

It would be a great feature in journey design, if read audience based journeys can be scheduled at different dates. Basically schedule follows a irregular pattern. Journey could be triggered on 11th of Jan, 17th of Feb, 25th of Mar, 15th of Apr and so on. We understand one can use business events to trigger the journeys at different dates OR use a time condition journey. But it will be a cool feature to configure different dates in the journey.

Currently a decision needs to be defined per Placement, even if for many Placements you want to apply the same decision. It should be possible to define a decision (Offer collection, eligibility, ranking method) as a re-usable object that can be linked to multiple Placements. If you change the decision, automatically the changes will apply for all the locations it is linked to. 

Description:Currently we have a business team that send our customers email from a unique email address (1:1) so that it's more personal to have the sender email address with their contact name instead of a generic email address.   That said on a team of 16, this requires 16 channel surface and therefore 16 emails.   The signature in the email can be made dynamic, but the inability to change the sending email address makes for a lot of extra work.   This is possible in other ESP. Why is this feature important to you: - Reduce workload on team How would you like the feature to work:Allow the sending email address to be dynamic based on a variable in the customers profile.  For instance we have a SalesRep ID associated on the customer profile, this should dictate what email address is used. Current Behaviour -- Not possible.  Require 16 separate email nodes in every email send when all the versions are the same.

When starting to use Fragments to build and create emails the amount of fragments is increasing rapidly, and it is getting hard to have the overview. Especially when several business units is using the same Sandbox and different Fragments is been used in different situations and in different units.To keep a clean and a good organized way of working, a folder structure would have been nice to have - for the email fragments. Be able to have a folder hihierarchy with f ex country or business unit as top level and content categories as level 2 and so on. It would then be easier to have control over what is what what of all the fragments that is been created. 

Description - One-off Journey status behavior Why is this feature important to you - This way we will maintain the total amount of journeys live reduced cause usually users forget to stop it or close it and that causes to reach the limit of the total live journeys. Also, when working on the same platform with multiple agencies, we cant control other journeys created by other agencies. Thats why its important How would you like the feature to work - When activating one-off journeys, there could be an automated way to change the status to close to new entrances or completed as there is in campaignsCurrent Behaviour - One-off journeys stay live and you need to manually stop or close them

In most cases when working with batched data we also need to be more close to real time. Both the bach and streaming audiences has a threshold when it comes to number of active and live audiences. Rules can in many cases replace the way we use audiences, and with not the some threshold rules. But today we are not able to use event data in this rules. If we f ex in a computed attribute could use event data and not just Attributes we could create rules instead of using streaming segments - that has limitations in the systems.