Product Communities

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 pa

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

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 - Until very recently the Auto-Align button was on the main screen.  Now it is hidden under the More (...) button.Why is this feature important to you - When I'm building I use this button dozens of times per day...possibly even hundreds of times. Now with it hidden underneath the More (...) button it is doubling my mouse-clicks....very frustrating.How would you like the feature to work - Please put it back on the main screen.

Currently we have an inhouse design team utilizing Proof to get approvals on animated web advertising. However, these ads have to be built at several unique sizes and all of them need signed off on. Since the only way for the approvers to see the animations is through a video proof, the designers are forced to upload all these sizes one at a time. This is making the tool more time consuming for them and also more frustrating for the approvers who have to open all these separate proofs for these very small, very similar pieces of art. Any way to address this would be appreciated.

Description - Customize the Task Summary in Workload BalancerWhy is this feature important to you - We would need to customize fields that are getting displayed here so that it is each for the resourcing manager to choose the required fields that is neededHow would you like the feature to work - Provide an option to user to choose the fields that are displayed in Open summary section. This should be either controlled by assigning appropriate Template changes Current Behaviour - No option to edit the fields that are displayed in Task Summary field

Hi everyone, One common issue I see often in Adobe Campaign is how risky it is to make schema changes—especially on core tables like nms:recipient.Changing things like primary keys or data types can break references, cause data loss, or even crash the system.It’d be super helpful if ACC had a Smart Schema Change Guard feature that could:1. Warn you before making risky changes Show the full impact on related tables, logs, and workflows2. Suggest safe migration steps or fixes3. Allow easy rollback if something goes wrongThis would save a lot of headaches, prevent downtime, and help teams evolve their data models safely.Has anyone else run into this? Would love to hear your thoughts or if you’ve found good workarounds! Thanks!