Build better products with our product team
This might sound unusual, but I request custom form for HOUR object. On hour records, such as on January 1, we would like the option to enter more information along with the comments.There is where the custom form should be available:
DescriptionThe proposal is to integrate quantum computing capabilities into Adobe Target’s personalization and optimization workflows. Quantum computing enables processing of exponentially complex datasets and can solve optimization problems faster and more accurately than classical AI. By embedding quantum-inspired or quantum-hardware-accelerated models into Adobe Target, businesses can achieve ultra-precise personalization and superior optimization outcomes. Why is this feature important to youNext-level personalization: Today’s AI-driven personalization is powerful but constrained by classical computing limits. Quantum computing can unlock new levels of accuracy and context-awareness.Faster experimentation: Reduce time-to-confidence in A/B and multivariate testing, helping businesses act on insights faster.Competitive edge for Adobe: Adobe would become the first mover in merging marketing technology with quantum innovation, increasing adoption of Adobe Target.Revenue impact: Superior personalization drives higher conversions, customer engagement, and long-term loyalty, directly benefiting Adobe’s clients and Adobe itself. How would you like the feature to workIntegration Layer: Introduce a “Quantum Optimization” mode within Adobe Target, where certain algorithms (e.g., multi-arm bandits, constrained offer orchestration, journey optimization) can run using quantum-inspired solvers.Opt-in Pilot: Allow businesses to enable quantum acceleration as an experimental strategy for specific activities or recommendations.KPIs for Measurement:Accuracy lift in personalizationReduction in regret/time-to-confidence for testsConversion rate improvementsArchitecture Suggestion:Start with quantum-inspired algorithms on classical hardware (D-Wave, IBM Qiskit simulators, etc.)Provide extensibility to connect with actual quantum hardware backends in the future. Current BehaviourCurrently, Adobe Target relies on AI and machine learning models running on classical infrastructure for personalization, testing, and optimization. These models are effective but face computational limitations when handling:Very large audience segmentationHigh-dimensional testing with multiple offers and constraintsReal-time, privacy-safe personalization across billions of signalsQuantum acceleration does not exist in the current system, leaving unexplored potential for ultra-precise personalization.
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
Description:The current capabilities of Adobe Workfront and Fusion do not fully support the need to restrict users from changing proof decisions after a stage has been locked. This poses a risk to the integrity of the proofing workflow, as it allows proof creators to unlock stages and alter decisions, potentially affecting the outcome of the proofing process.Why is this feature important to you:This feature is essential for ensuring the security and reliability of our proofing workflows. By preventing unauthorized changes to proof decisions and stage locks, we can maintain the integrity of our decision-making process and ensure that all stakeholders have confidence in the final outcomes. This is particularly important for teams that rely on accurate and consistent proofing processes to make informed decisions and maintain accountability.How would you like the feature to work:Restrict Stage Unlocking: Implement a feature that allows administrators to set permissions that prevent any user, including the proof creator, from unlocking a proof stage once it has been locked. Only users with explicit system administrator rights should have the ability to unlock a stage after it has been locked.Enhanced Decision Change Tracking: Develop a feature that allows for tracking and reporting on changes to proof decisions. This could include:A new "Decision changed flag" field that is automatically filled out when a decision is changed, allowing for easy reporting on changed decisions.A notification system that alerts relevant stakeholders when a decision is changed after a stage has been locked.Current Behavior:Proof creators can unlock proof stages and change decisions after a stage has been locked (regardless of their proof permissions level), which poses a risk to workflow integrity.Fusion does not reliably track changes in proof decisions, especially when the overall proof status does not change.Workfront lacks specific reporting capabilities to filter and identify changed decisions, making it difficult to track and report on decision changes.
Description - Some users (either on accident or on purpose) list the tasks of a project by percent complete, start date, due date, etc. instead of by the task number. This leads to them requesting help or questioning if Workfront has had an update that then blocks them from seeing "+ Add More Tasks" below the list and the inability to nest task only discover that those features aren't allowed because the tasks aren't listed by their number. They were unaware that not listing the tasks by their numbers would disable those features. Why is this feature important to you - It would be helpful for people to know that the way the tasks are currently ordered in will block certain actions to the tasks or projects. While the text and icons for those actions are missing for them, it has caused them to question if there's a bug, did something change with their access level to the project, did something change with their account, or if clearing their cache and cookies is the fix. If they had a visual indication that features are blocked due to the current sorting, that would cut down on the amount of confusion and calls system admins field when listing the tasks by the number ends up being the solution. How would you like the feature to work - Enabling some sort of visual indication or warning on either the project or tasks that features like nesting aren't allowed with the current ordering of tasks would help users understand what is going on when they try to perform those actions. Something similar to when you try to assign a user to a task when their access level won't let them complete it. Current Behaviour - There's currently no visual indication that some features are blocked when the task list is not listed by the task number.
Description - Right now, users with "Team Monitoring" access cannot view WF module configurations or datastoresWhy is this feature important to you - With our governance model, only a few individuals can develop in PROD while other devs work in lower lanes. But when it comes time to troubleshoot their PROD scenarios, Team Monitoring doesn't allow them to see WF Module configurations or datastores. Making it near impossible for accurate troubleshooting so they can fix in Sandbox and promote to ProductionHow would you like the feature to work - Team Monitoring access should allow users to VIEW EVERYTHING without the ability to make changesCurrent Behaviour - Team Monitoring restricts users to only seeing Fusion scenarios at a high level without going into the details
We can set tokens a first level folder level, but it is impossible to set token on the root folder.And yet this would be awesome as we could set company defaults.When using workspaces, these would become workspace level tokens.
Make the Field Manager more useable! I hate that I have to download my entire list every time I just want to look up the API value of a field. Would love to see the field manager tab show the API names. Don't really care as much about where it's used, especially since the "And More" button does nothing. Show us useful info: what kind of field is it, what are the API names.
Per this thread - Interesting moments for custom activities - I would love to have the ability to include custom activity as additional insight within our Interesting Moments. The IM by itself, e.g., "watched a video", would be so much more valuable if we were able to include specific detail, like the video name.
We are currently cleaning up our projects in MKTO by manually turning off all of our old smart campaigns that are not needed anymore so we can archive them. It would be great if there was functionality when archiving a campaign or folder that turns off any smart campaigns automatically. Or at least add an option if a new smart campaign is created to turn off at a certain time.
Description - Would love to have the option to attach a file to a request in Planning.Why is this feature important to you - We thought we had a solution to our public facing request problem through Workfront Planning's ability to create public request links. However, the inability to attach files makes it a non-viable option for us.How would you like the feature to work - Just like in Workfront Core, we would like to have the option to attach files to requests.Current Behaviour - Currently there is no file attach option in Workfront Planning.
Description -In Workfront, in Settings->System->Customer Info and in Settings->System->Preferences:Save and Cancel buttons coming without editing anything. Just by clicking into them getting these Save and Cancel. In other sections of settings this is not the Problem, only if we edit anything in that page then we are getting Save and Cancel buttons dynamically. Only in these 2 pages we have this problem. Those buttons not going away even I click Cancel. Only option is to move away from that Page. With this problem it is difficult to say whether I changed anything on that Page or not. (Screen shots attached).Why is this feature important to you - For consistency and user friendlynessHow would you like the feature to work - Should keep the Save and Cancel buttons visible at all times across all setup pages that require saving before leaving to ensure consistency. The buttons should remain inactive until the user makes changes. The experience is different in other pages of Settings. Example below in Settings->Proof Settings When you go to that Page, by default Save button is disabled. Once you edit anything then Save button is enabled. Screen shots below. I am expecting this behavior in Settings->System->Customer Info and Preferences pages also but it is not.Current Behaviour - Detailed above
This request is for Adobe Target. Please add to the Target Admin API "List Activities" endpoint a param/value pair with "modifiedBy" that would correspond with the already-existing "modifiedAt" param/value pair. Doing this work manually takes 1 FTE an average of 7 hours/month. This costs us $21k/year and hundreds of thousands in Business Decisions made from this.
Currently, we can only retrieve deleted Projects, Tasks, Issues, Documents, and Templates from the recycle bin. Sometimes, Template Tasks are deleted by mistake and also need to be restored. Because this is not an option in the recycle bin, however, we have to rebuild these from scratch if they are deleted accidentally.
Description - Allow DWG file types to be ProofedWhy is this feature important to you - We have many different Teams who use AutoCAD for initial designs and wish to collaborate via Proof. Current State these Users have to convert this file type into a pdf, which greatly increases their workflow. How would you like the feature to work -Like any other approved file type in ProofCurrent Behaviour - It is not a supported file type
Hi, I have a suggestion for Approval Processes. Right now, when an Approval Process is attached to a Project, Task, or Issue, any time that object is put into the status it triggers the Approval Path. What I would like to see is a configuration setting that would only allow each Approval Path to trigger once per Approval Process use. For instance, I have a Project that triggers an Approval with three Paths‚ÄîCurrent, Go-Live, and Complete. Once the Project goes Current, and then moves on to another status, I don’t want that Project to be sent out for approval again for the Current Status, even if it is put back into it. Then the same would apply to the other Statuses on that Approval Process as well. I think the current setup is fine, as there is definitely a use-case to re-trigger Approval Paths multiple times. Could we get a setting when configuring the Approval Process to toggle whether each Path could only trigger once, or multiple times?
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 settings every time the fragment is been used.
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. How would you like the feature to workIdeally, Adobe would expose a public API endpoint (via Adobe I/O or Journey API) that returns the same JSON currently available in "Copy Technical Details".This endpoint should return a complete JSON structure with all configuration fields exposed in the UI technical details. Current BehaviourCurrently, the only way to access the technical details JSON is through the "Copy Technical Details" button in the AJO interface or check via UI. This action must be done manually, and there is no documented or supported API to retrieve this configuration programmatically. As a result, automation of journey validation is not possible with the current setup. Thanks!Lucas Sanches AndradeDigital Analyst @3238541 Bmg
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-without being forced to duplicate it. This would allow for quick updates and version control within a single journey, similar to how other platforms handle workflow and content editsCurrent Behaviour -Once a journey is published, you cannot edit and re-publish it directly. You must stop the journey, duplicate it, make your changes (including any updates to content templates) in the new copy, and then publish the duplicate. This leads to unnecessary duplication and complicates journey management.ThanksAJODev
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
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
