Build better products with our product team
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.
Project, Task, and Issue priorities are currently managed globally.We would like this functionality to be pushed down to Groups so that each groups can manage their own conditions lists.
Project, Task, and Issue conditions are currently managed globally.We would like this functionality to be pushed down to Groups so that each groups can manage their own conditions lists.
It would be great if Marketo had an API endpoint for managing fields, such as hiding them.For example, we have dozens of fields that we need to hide that are unused, and it is time-consuming and tedious to hide them one at a time.
Description of change you want to see:I would like the ability to expand or collapse the various top and side interface elements on the Adobe Workfront home page—specifically, the Adobe unified experience bar at the very top, the Workfront top navigation bar, and the "Home and Priorities" left-side panel. Currently, these elements take up significant vertical and horizontal screen space and cannot be hidden or minimized.Why is this feature important to you:This feature would greatly improve usability and workspace efficiency. The persistent interface elements reduce the available area for viewing and working on tasks, especially on smaller screens or laptops. Having the option to hide or minimize these sections would allow for a cleaner, more focused working environment and improve the user experience—especially for users who spend most of their time within the task list or dashboard views.How would you like the feature to work:I would like to see collapsible or toggle-able interface sections—similar to how the object navigation panel on the left side of object pages (like projects, tasks, etc.) can be expanded or collapsed. Ideally, there would be a small arrow, icon, or hover-triggered control to expand or hide each major UI section. The user's preferences (collapsed or expanded) could also be remembered across sessions for convenience.Current Behaviour:Currently, the Adobe bar, the Workfront top navigation, and the Home and Priorities side panel are fixed and cannot be minimized or hidden. This results in a cluttered interface and reduced usable screen space, which can make navigating and managing work more cumbersome.
Description - I have a field that I would like to duplicate and rename without having to create another field manually. Example - I need to manually create fields with drop down options on the open/close time for one of our specific locations (this can get extensive when building it out for each day of the week). Why is this feature important to you - It would save me a ton of time when building out custom forms. How would you like the feature to work - Have an option within the custom form area to copy existing fields (and rename them) similar to how you are able to do this with templates, projects, tasks, etc. Current Behaviour - Inability to copy custom fields (need to manually create each).
Description:Introduce the ability for multiple users to collaboratively build and refine audience definitions in Adobe Real-Time CDP with support for version history, change tracking, and inline comments.This feature would help cross-functional teams (marketers, analysts, data scientists) work together more efficiently while ensuring traceability and reducing errors in audience logic. Why is this feature important to you:Audience building often involves multiple team members, and right now, it’s hard to track who made what changes or why.Sometimes, edits overwrite each other or lead to confusion without proper documentation or context. How would you like the feature to work:Each saved audience should include a version history, showing what was changed, when, and by whom.Users should be able to leave inline comments on specific filters or conditions (like commenting in Google Docs).Rollback functionality should allow users to restore a previous version if needed.Notifications when changes are made would help keep teams in sync.Current Behavior:Audience building is a single-user experience with no built-in collaboration tools or history tracking.Teams must rely on external documentation or naming conventions to manage edits - which is prone to human error. Use Case:A global brand's marketing and data teams are collaborating on a holiday campaign audience.The analyst creates the initial logic, the marketer adds refinements, and both leave comments explaining choices.When the campaign under performs, they review the version history to identify what changed and when - leading to quicker iteration.
Request for Feature Enhancement (RFE) Summary: .aex & .aep (Adobe After Effects ) files are not supported in DAM today. Requesting to extend the support to these file formats Use-case: Current/Experienced Behavior: .aex & .aep (Adobe After Effects ) files are not supported in DAM Improved/Expected Behavior: .aex & .aep (Adobe After Effects ) files should be supported in DAM similar to .ai files. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.21 & Cloud Customer-name/Organization name: Mondelez Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Ability to bookmark things in AEM Author Use-case: All types of Touch UI activities Current/Experienced Behavior: Not often you can find yourself working on mid or long term implementations of features if you are a developer, or often working on a specific set of pages and assets if you are a content author, or continuously doing regression testing on specific points of the solution as a tester, or purely having to do only with a small portion of "everything" and not usually go in the entire content or solution all the time.In these often situations I found that the person working on that specific area tends to have lots of browser tabs opened, trying to go back and forth between them to do their work, to do investigations, trying or find things out, oftenly doing mistakes or forgetting where things were, and spending lots of time to untangle stuff and to make sure he is looking in the right place each time before actually addressing the actual underlying need he has. Improved/Expected Behavior: I propose that AEM would provide the possibility to create shortcuts/bookmarks lists within AEM. Different points in AEM should contain a Bookmark button (which points ?, that is something to be analyzed further). Clicking on this button should open a simple Dialog containing two fields for the user to fill in: name, which will be the visible label of the bookmark and group which will be the bucket list where the bookmark will be added to. Environment Details (AEM version/service pack, any other specifics if applicable): I believe this will beneficial as it will increase and boost productivity once the user can create his own lists of places to rapidly go to, not waste time to find same things each time and also avoid doing mistakes as it may happen that he might not go or look at the right place at some point. Example:Assuming I am working on some Dynamic Media implementation, and I often need to go to Tools, to the Dynamic Media cache invalidation page. In the same time I have a huge content of tons of sites but I only need to work on few 5 to 10 pages within the entire content hierarchy. Same for Assets, I only need to work with some specific assets, lets say some Content Fragments that I need to edit, save and publish. Plus, I have some config files stored in JCR and managed through some custom Coral UI tool built in-house. All of these places require for me to navigate to them each time and also take an action on them. Would be good to have a Bookmark button on each of these places so that I can save a bookmark of it. And then visualize all the bookmarks from a single place in AEM. And from there I can always quickly navigate to where I need.Below I added some example screenshots. But I imagine the Bookmark button to be available in way more places within AEM. Customer-name/Organization name: tethich.com Screenshot (if applicable): Code package (if applicable):
It Would be nice if I could rename a variable in Analysis Workspace for a specific project.For example, I just created a simple report for a colleague of mine looking at tracking codes and the number of clicks. For number of clicks I used 'Tracking Code Instances'. As a regular AA user, I understand what Tracking Code Instances means but someone who isn't a bug AA user might not know what it means. So, it would be good if I could right click on the metric and have an option to rename it. This renaming would only exist in the specific project.Thanks.
Description - It would be nice to have at profile-level the amount of emails each profile have received and opened in the last 30 days.Why is this feature important to you - It would be possible to address journeys based on communication-engagement withouth having to do it at audience-level. How would you like the feature to work - a computted attribute that returns the count of emails a profile have received/ opened in the last 30 days, something link:xEvent[_experience.customerJourneyManagement.messageInteraction.interactionType in ["open"]].count() Current Behaviour - Computed Attributes currently do not support System generated datasets
We would like the capability to configure the visual view of reports in our Dashboards.Currenlty each report has horizontal space for;- Tabs Menu (Details / Summary / Matrix etc.)- Options (export, lookup, Gantt etc.)It would be great if these lines could be configured, as they take up a lot of space and are not always required by the users.See the attached image for an example of the space that these unused rows are taking up in one of our Dashboards.For this particular Dashboard / Team, 'Details' is not required on the majority of reports, as there are no other tabs and 'export / search / Gantt' would also not be required on the majority of the reports for this team. It would be great if there was an option to configure these lines to create a better visual and make better use of the Dashboard space.Thanks
In the Omniture Legacy UI, there is an option to expire a user after a set amount of days (I have a screenshot I can provide). It would be helpful to be able to utilize the same functionality within the Admin Console, specifically Adobe Analytics, to ensure that external users are expired after a certain number of days (ideally 6 months), but ONLY if they haven't had any activity in the last 6 months.By having to expire every external user after 6 months, we are facing many users being locked out every 6 months, requiring our User Admins to unlock them, as well as not allowing them within the tools in the interim. If we changed the solution to only expire the inactive users, we would prevent time lost and would properly expire only those who required it. ----------------------------------------------------------------------------------------------------------------------------The customer, General Motors, requested a product enhancement for Adobe Analytics to automatically expire users after 6 months of inactivity. This feature is available in the Omniture Legacy UI but not in the Admin Console for Adobe Analytics. The current process causes unnecessary user lockouts and administrative overhead.**Customer Impact:**- Users are being unnecessarily locked out every 6 months, requiring administrative intervention to unlock them.- Only inactive users should be expired to prevent time loss and ensure proper user management. JIRA: [AN-369787] User Expiry after 6 months of no login - JiraSupport Ticket: E-001545785
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.
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.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK