Build better products with our product team
Users would like for the Proofing module to behave like a browser (for interactive proofs, webpages), and display the hyperlink at the bottom of the page when hovering your mouse over that respective button. This feature is not currently available and would help them quickly check if the are any blank/not linked buttons on the page they are working on. Please see attached example on how they would like it to work:
Description - Allow for multiple conditions apply to Column Rules, Report View Why is this feature important to you - Sometimes condition on column view in a report is a combination of multiple rules and not only one. How would you like the feature to work - Allow for multiple conditions be selected in Column Rules, Report View Current Behaviour - Only one condition can be defined in the rule, rather than combination of multiple ones.
Description - Update the dimension operator in Annotations from AND to OR. Why is this feature important to you - Currently, if an annotation includes multiple dimensions, it only appears on a Workspace dashboard when all of those dimensions are present. If the dashboard contains only one of the specified dimensions, the annotation won’t be visible.For example, if I create an annotation using both eVar1 and eVar25, I must include both in the dashboard for the annotation to appear. To work around this, I have to create separate annotations for each dimension. How would you like the feature to work - Change the annotation logic so that it uses the OR operator. This way, the annotation will appear if any of the specified dimensions are present in the dashboard. Current Behaviour - Annotations use the AND operator, requiring all listed dimensions to be present for the annotation to display.
Description - Workfront Dark Mode Why is this feature important to you - Default Workfront is incredibly straining on the eyes How would you like the feature to work - Provide a black or dark background instead of white Current Behaviour - Non-existent
Description - Allow classifications based on date dimensions like 'Day'- this would make analysis of custom date periods like financial years, financial weeks, seasons, etc. much easier. Currently if you want to work with something like this you have to create individual date ranges for every value. If you could classify 'Day', you would be able to upload a single .tab file that mapped the Day to all the custom date classifications you want, then to analyse these you would only have to drag in a single dimension in workspace.Why is this feature important to you - My analytics team have asked for better implementation for datespans like financial weeks. They currently use date ranges, which is very manual when analysing long periods that split into many date ranges as they have to drag in each week individually.How would you like the feature to work - In the report suite traffic/conversion classifications tab, add 'Day' to the available dimensions to create classifications based on. Then in classification importer you will be able to upload a classifications file that maps the Day value to custom date classifications. Current Behaviour - Currently the only way I can find to do something like this is to track a custom eVar for the date the user is on the website, then create classifications based on that. The issue with this is that it isn't retroactive, so you can't use these classifications for the time before you started tracking the evar. Currently no date dimensions are available in the classifications settings to use.
Description -For any project, under Hours Tab, the total hours at the bottom shows the addition of the line items. The client's request is, it should show the addition of all the hours at the bottom of the page.
Description - More than one "Regex Replace" functions should be allowed in CJA derived fieldsWhy is this feature important to you - This will allow CJA users to build more refined rule based classificationsHow would you like the feature to work - A derived field should have options to add multiple "Regex Replace" functions in it's definition.This will help in building more refined rule based classifications (similar to Adobe Analytics' Classification Rule Builder) where a field can be created by matching multiple regex strings.A very simple requirement could be a field with two different formats of values in it having different number of delimiters. An example could be below two values,1997:Brand:Model1997:Brand:Model:ReleaseTo create a derived field that extracts all the brand values from these two formats we need to match two regex strings,^(.+)\:(.+)\:(.+)$ and return $2 as value^(.+)\:(.+)\:(.+)\:(.+)$ and return $2 as valueThis can be achieved by adding two "Regex Replace" functions in the derived field but currently we can use this function only one time per derived field.Current Behaviour - Currently CJA allows only one "Regex Replace" function per derived field.
Request for Feature Enhancement (RFE) Summary: Scheduled Copy content activities to lower environments from Prod environment Using GenAI Models in AEM Cloud Manager Use-case: We request the development of a feature in Adobe Experience Manager (AEM) Cloud Manager that leverages Generative AI (GenAI) models to enable the capability of scheduled copy content activities to lower environments from Prod environment. This feature would allow DevOps/Support teams to trigger content copy activities to lower environments on specific dates and times through GenAI-based workflows in a scheduled manner. Key Benefits: Reduction in manual effort : The biggest advantage of this feature would be - a great reduction / savings of manual hours of the AEM support team/application team in the monitoring of Copy content activity , Greater efficiency and reduction in the waiting times during monitoring ( incurred by the support team while content is being copied in Stage and Dev ). Automated Scheduling: Users can set precise times and dates for copying content to lower environments, ensuring updates occur during optimal windows, such as off-peak hours, minimising disruption. This will reduce the manual effort in solving the most common business requirement of content refresh from Prod to the lower environments, after every regular interval like once in 15 days or after every release. Enhanced Efficiency: GenAI models streamline the content copy process, reducing manual intervention and potential errors. Predictive Analytics: Utilize GenAI to analyze past content copy activities and suggest optimal times for future operations, enhancing overall system performance. Customizable Workflows: Tailor content copy workflows to meet specific organizational needs, providing flexibility and control over the process. Improved Reliability: Scheduled content copy activities ensure consistency and reliability, with GenAI models monitoring and adjusting workflows as needed. Implementation Details: Integration with AEM Cloud Manager: Seamlessly integrate GenAI models within the existing AEM Cloud Manager framework. User Interface: Develop an intuitive UI for scheduling content copy activities, allowing users to easily configure and manage the timing of these operations. GenAI Workflow Engine: Create a robust workflow engine powered by GenAI to handle the scheduling, execution, and monitoring of content copy activities. Analytics Dashboard: Provide a dashboard for users to view content copy history, performance metrics, and predictive analytics. This feature will significantly enhance the content management and content backup capabilities of AEM Cloud Manager, offering application support teams a powerful tool to manage content copy activities efficiently and effectively, with very low effort. Current/Experienced Behavior: There is no such workflow/feature available in AEMaaCS as of now for scheduled copy content activities. Improved/Expected Behavior: We request the development of a feature in Adobe Experience Manager (AEM) Cloud Manager that leverages Generative AI (GenAI) models to enable the capability of scheduled copy content activities to lower environments ( at the time as scheduled by the DevOps team ), resulting in saving of manual efforts/hours during the copy content activity and enhanced efficiency. This will be of great help in solving the most common business requirement of content refresh from Prod to the lower environments, after every regular interval like once in 15 days or after every release. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service ( AEMaaCS ) Customer-name/Organization name: UnitedHealth Group ( UHG ) Screenshot (if applicable): N/A Code package (if applicable): N/A
Description:Enable usage of Asset Request ID to allow us to group related assets and populate them as a single package to Bynder, improving our asset management process. Why is this feature important to you:As we enhance our asset management capabilities with Workfront and Bynder, we need a way to group related assets from a single task. This will improve efficiency, organization, and user experience, enabling easier tracking and management of assets. How would you like the feature to work:Introduce Asset Request ID to group assets. When assets are transferred, they should be sent as a package, utilizing Bynder's related functionality. The assets should automatically be marked as related and preferably show the actual user who uploaded them. If Asset Request ID is active in Bynder, Fusion can enable Workfront to bundle assets by leveraging subfolders etc when sending them to Bynder. Current Behavior:Currently, assets are transferred to Bynder individually without grouping or relation, complicating management and tracking.
Business Need: Stakeholders often require Year-To-Date (YTD) comparison of current year vs previous year on a daily/weekly basis to track ongoing performance trends. Challenge: Adobe Workspace does not support dynamic YTD vs YTD comparison directly. Users must manually change the date ranges or use limited preset options, leading to inefficiencies and inaccurate analysis. Adobe's Design Limitation:Workspace logic is snapshot-based, not dynamically contextual to today's date across years.Designed for fixed range comparisons (like Mar 1–Mar 31 this year vs same period last year) Current Gaps:No automatic rolling YTD comparison available.Static date ranges need to be updated frequently.Presets or Date Comparison help partially but fail when YTD is not the same number of days every year (due to leap years, weekends, etc.). Impact: Inconsistent reporting, increased manual effort, delayed insights for performance tracking and business decisions.
Request for Feature Enhancement (RFE) Summary: Reducing Stage/Prod deployment Pipeline execution Time Using GenAI Models in AEM Cloud Manager Use-case: We are requesting for the development of a feature in Adobe Experience Manager (AEM) Cloud Manager that leverages Generative AI (GenAI) models to reduce the execution time required for stage and production deployment pipelines in AEM Cloud manager. This feature would fast-track regular deployment tasks in the Adobe Cloud pipeline using GenAI models , including Unit Testing, Code Scanning, Image Building, Product Functional Testing, Custom Functional Testing, Custom UI Testing, and Experience Audits. Key Benefits: Accelerated Deployment: GenAI models optimize and expedite deployment tasks, significantly reducing the overall pipeline time. Enhanced Efficiency: Automate routine tasks such as unit testing and code scanning, allowing for faster and more reliable deployments. Predictive Analytics: Utilize GenAI to predict potential issues and optimize the sequence of deployment tasks, ensuring smoother and quicker pipelines. Customizable Workflows: Tailor deployment workflows to meet specific organizational needs, providing flexibility and control over the deployment process. Improved Reliability: GenAI models continuously monitor and adjust workflows, ensuring consistent and reliable deployments. Implementation Details: Integration with AEM Cloud Manager: Seamlessly integrate GenAI models within the existing AEM Cloud Manager framework. User Interface: Develop an intuitive UI for configuring and managing deployment tasks, allowing users to easily set up and monitor pipeline activities. GenAI Workflow Engine: Create a robust workflow engine powered by GenAI to handle the optimization, execution, and monitoring of deployment tasks. Analytics Dashboard: Provide a dashboard for users to view pipeline performance metrics, historical data, and predictive analytics. This feature will significantly enhance the deployment capabilities of AEM Cloud Manager, offering users a powerful tool to manage stage and production pipelines efficiently and effectively. Essentially the idea is to reduce the overall execution time of Stage/Prod pipeline and hence making the deployments faster during the release calls etc. This will also reduce the manual effort/time spend during the release calls. Current/Experienced Behavior: Currently it takes around 1.5 hours to deploy the code to Stage and then promote to Prod, using the Stage/Prod pipeline in AEM Cloud manager. Improved/Expected Behavior: Expected or improved behaviour is cut down this execution time to around 30 mins for the entire Stage/Prod production pipeline. This can actually help in saving a lot of man hours/support hours from the application support team during the release calls. This would also make the deployment of breakfix/hotfix items to Prod very quick and easy. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service ( AEMaaCS ) Customer-name/Organization name: UnitedHealth Group ( UHG ) Screenshot (if applicable): NA Code package (if applicable): NA
Description - The native fields of Portfolio and Program do not work the same as they should in the custom form as they do in the Overview. Why is this feature important to you - We need our PMs to select the Portfolio and Program for each project, so we added the native field to our custom form and made it required for them to fill out. Otherwise they miss doing this in the Overview of the project.How would you like the feature to work - Having the native fields of Portfolio and Program to work exactly like they do in the Overview. When you select a Portfolio, only the Programs for that Portfolio will be shown to select from. Current Behavior - Right now, when you select the Portfolio in the custom form, ALL of the Programs are listed. The PMs have to then search and scroll for the right Program. They can also select the wrong one, which they won't know that they did since it allows them to select any Program instead of the ones that are associated with the Portfolio.
Would be nice to lock folders so requesters cannot see assets until ready for them to review. Currently, requesters are viewing the "review" files that are meant for the art directors. Only solution we found was to "unshare" the requester from the project. Not ideal I must say.
Request for Feature Enhancement (RFE) Summary: Scheduled Stage and Production Deployments Using GenAI Models in AEM Cloud Manager Use-case: We request the development of a feature in Adobe Experience Manager (AEM) Cloud Manager that leverages Generative AI (GenAI) models to enable scheduled Stage and Production deployments ( at the time as scheduled by the DevOps team ). This feature would allow DevOps/Support team to trigger stage and production deployments at specific times through GenAI-based workflows. Key Benefits: Reduction in manual effort : The biggest advantage of this feature would be - a great reduction / savings of manual hours of the AEM support team/application team in the monitoring of deployments , and reduction in the waiting times ( incurred by the support team while code is being deployed in Stage and Prod ). Automated Scheduling: Application teams can set precise deployment times, ensuring updates occur during optimal windows, such as off-peak hours, minimising disruption. Enhanced Efficiency: GenAI models streamline the deployment process, reducing manual intervention and potential errors. Predictive Analytics: Utilize GenAI to analyze past deployment data and suggest optimal times for future deployments, enhancing overall system performance. Customizable Workflows: Tailor deployment workflows to meet specific organizational needs, providing flexibility and control over the deployment process. Improved Reliability: Scheduled deployments ensure consistency and reliability, with GenAI models monitoring and adjusting workflows as needed. Implementation Details: Integration with AEM Cloud Manager: Seamlessly integrate GenAI models within the existing AEM Cloud Manager framework. User Interface: Develop an intuitive UI for scheduling deployments, allowing users to easily configure and manage deployment times. This feature will significantly enhance the deployment capabilities of AEM Cloud Manager, offering users a powerful tool to manage Stage and Production deployments efficiently and effectively, saving man hours during the deployment process. Current/Experienced Behavior: There is no such workflow/feature available in AEMaaCS as of now for scheduled deployments. Improved/Expected Behavior: Develop a feature in Adobe Experience Manager (AEM) Cloud Manager that leverages Generative AI (GenAI) models to enable scheduled Stage and Production deployments ( at the time as scheduled by the DevOps team ), resulting in saving of manual efforts/hours during the deployments and enhanced efficiency. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service ( AEMaaCS ) Customer-name/Organization name: UnitedHealth Group ( UHG ) Screenshot (if applicable): N/A Code package (if applicable): N/A
Request for Feature Enhancement (RFE) Summary: The redirect from /security to /libs/cq/security/content/securityadmin.html is part of the out‑of‑the‑box configuration in AEM as a Cloud Service. This affects the functionality when there is a page with the name "security". This page is never reached and always get redirected as per OOTB configuration. Use-case: any page created with the name "security" should be reachable and not redirect to another link. Current/Experienced Behavior: /security redirects to /libs/cq/security/content/securityadmin.html Improved/Expected Behavior: /security should not redirect to any other URL. Environment Details (AEM version/service pack, any other specifics if applicable): Publisher Customer-name/Organization name: Mamta Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Removing white space from generate page source Use-case: Additional white space lines are added in generated page source from sightly code. Current/Experienced Behavior: Additional white space lines increases file size of the page and thus impacts page performance Improved/Expected Behavior: Expected behaviour is all white spaces/white lines that sightly code generates should be removed when viewing page in publish instance Environment Details (AEM version/service pack, any other specifics if applicable): Latest AEM as cloud version Customer-name/Organization name: Abhinav Kumar Sinha / Deloitte consulting UK Screenshot (if applicable): Code package (if applicable):
Description - We want to be able to copy derived fields across connections in CJA. This is important for us, because we need to repeat these steps for every new sandbox that we connect manually.The feature should allow a CJA user to copy a derived field from an existing sanbox to a new one.Current Behaviour - Currently this is only possible within the same connection when copying a dataview. Consequently requiring the adobe user to fill in the derived fields manually --> 2 - 4h additional time/effort required.
Request for Feature Enhancement (RFE) Summary: Enable dynamic dropdown in Universal Editor. Use-case: Our project has several dynamic dropdowns by using coral select. And it is supported in touch UI. Now we want to use the Universal Editor, but we found the new editor doesn't support dynamic dropdown currently. Current/Experienced Behavior: Now Universal Editor support the component type "select" and it can configure a list of predefined option. Improved/Expected Behavior: Enable the dynamic dropdown function in Universal Editor or provide a dynamic dropdown extension officially. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Cloud Customer-name/Organization name: SSGA Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: We request the ability to set a password for public links shared via AEM Assets. This feature is essential for securely sharing sensitive assets in compliance with internal security policies. Currently, AEM does not provide password protection for shared links, posing a significant security gap. Use-case: Our mobile phone assets contain critical security data, and their distribution must be tightly controlled. However, the current public link sharing feature in AEM Essentials lacks proper security management.We are seeking a password protection feature to safeguard sensitive content—particularly assets shared at the headquarters level. Since these links are often shared with external design agencies who do not have AEM accounts, existing user governance is insufficient. All users with access to the link can currently view the content, which creates compliance and confidentiality risks. Current/Experienced Behavior: AEM Assets allows public link sharing but does not support password protection. As a result, anyone with the link can access the asset, with no additional security mechanisms in place. Improved/Expected Behavior: The ability to set passwords for shared links would align AEM Essentials with standard security practices supported by other cloud platforms. This would significantly improve asset security and access control. Environment Details (AEM version/service pack, any other specifics if applicable): AEM Essentials Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Description - When adding data to a dataflow, on tha Select Data Step, when we Uploade a Json that is bigger than what the first seen screen can hold, there is no scroll bar to look/verify the rest of the json. Why is this feature important to you - Because it supposed to be there, is more like a bug than a improvement. How would you like the feature to work - It must have a scrool bar, that simple. Current Behaviour - There is no scrool bar.
Description:Introduce a Destination Activation Replay feature that tracks failed or missed activation (e.g., due to API downtime, schema mismatch, rate limits) and allows for automatic or manual reprocessing once the destination becomes healthy again - ensuring no critical activation is permanently lost. Why is this feature important?Ensures activation reliability - campaigns or journeys shouldn't silently miss users due to transient destination errors.Helps marketers and engineers troubleshoot and recover from downstream failures without rebuilding segments or pipelines.Supports auditability and compliance, with logs showing which profiles were successfully activated, which failed, and which are pending retry.Prevents data loss during outages, especially when targeting time-sensitive audiences like flash sales or churn interventions.Current Behavior:If a destination (e.g., Facebook, Google Ads, webhook, custom API) fails during profile export, the activation fails silently or logs the error without recovery options.There is no built-in retry mechanism or UI to view, filter, or reprocess failed activations from Real-Time CDP.Users must rebuild audiences or re-trigger exports manually, which may lead to missed timing or gaps in user targeting.Use Case:A Facebook Ads destination fails due to temporary API downtime. Once it's back online, the system automatically replays the failed activation for the affected profiles.A marketer views a Delivery Health Report, sees that 500 profiles failed to activate to a custom webhook, and replays them with a single click.A team uses an export log to analyze the scope of a destination outage, informing campaign analytics and customer care follow-up.
Description:Introduce a Source Health Dashboard that monitors the status, freshness, volume, and latency of incoming data sources (batch and streaming) in real time. Add alerting features for drops in ingestion, data schema mismatches, or unusual data volume patterns. Why is this feature important?Ensures data quality and trust across the platform by surfacing real-time issues with source integrations.Reduces diagnostic time for ingestion failures that silently impact audience building or segmentation.Proactively alerts technical and marketing teams to source failures, stale data, or delays, preventing downstream impacts on campaigns and decisioning.Supports data governance and operational excellence in data-driven organizations. Current Behavior:Source connection status (e.g., for streaming or scheduled batch uploads) is not actively monitored in a centralized dashboard.Failures may go unnoticed until audience segments look wrong or campaigns underperform.There is no built-in alerting for low volume, schema drift, or ingestion latency beyond basic logging. Use Case:A key CRM source stops sending updates due to API auth failure - the dashboard shows a red status, and alerts are sent to the integration team via Slack or email.A streaming source begins sending 50% less data than average over the last 24 hours - an alert flags this as a potential anomaly for investigation.A newly added source has incorrect schema (e.g., missing a key identity field) - it’s flagged before it disrupts identity stitching or segment membership.
Description:Introduce a real-time audience fatigue scoring mechanism that tracks user responsiveness (or lack thereof) across channels (email, push, ads, etc.) and automatically adjusts frequency caps or suppresses the user from further campaigns until engagement improves. Why is this feature important?Prevents over-messaging and burnout, which leads to unsubscribes, opt-outs, and negative brand perception.Allows more intelligent campaign pacing - showing restraint can often improve long-term engagement.Reduces manual guesswork around send frequency by making decisions based on real-time engagement signals (opens, clicks, site visits, etc.).Optimizes deliverability and compliance, especially in regulated regions with communication limits.Current Behavior:Frequency capping is usually static and channel-specific (e.g., max 3 emails/week).No native cross-channel fatigue detection or unified scoring that evaluates all touchpoints.CDP does not dynamically adjust campaign eligibility based on individual user saturation.Use Case:A customer opens 0 out of 5 emails and ignores 3 push notifications in one week. Their fatigue score increases, and they’re temporarily suppressed from outbound campaigns until they re-engage.Another user is highly responsive on SMS but shows fatigue in email; the system shifts more messaging to SMS while reducing email frequency.A global brand ensures regulatory compliance by using fatigue scoring as a proactive suppression layer - minimizing opt-out rates and respecting user tolerance.
Description:In Adobe Target, once changes are made to an experience (e.g., offer content, audience rules, design tweaks in VEC), there is no built-in versioning or rollback functionality for that specific experience. If a mistake is introduced or someone wants to revert to a previously working version, it often requires manually redoing the changes or referencing screenshots or documentation - if available. Why is this feature important to you:Teams working on multiple activities across A/B tests and personalization campaigns need the ability to iterate quickly and safely. Mistakes can happen, especially in large organizations or distributed teams. Having a version history would reduce risk, support better collaboration, and speed up debugging and approval workflows. It’s especially useful for regulated industries or agencies where approval trails matter. How would you like the feature to work:Each experience within an activity should automatically store a version history whenever a change is made. This should include:A timestampThe name of the user who made the changeA summary of what was changed (e.g., audience modified, HTML updated, design edited)Users should be able to:View previous versionsCompare them visually or via a diff viewRestore a previous version with a single clickOptional: Allow notes/tags for major changes ("v1 approved", "client review", etc.). Current Behaviour:Currently, Adobe Target does not offer any version history or rollback capability. Once a change is saved and/or published, the previous version is lost unless manually backed up or documented outside the system.
Description –Managing Adobe Target activities often involves multiple roles across teams - marketers, developers, QA, and analysts. However, the current access control model does not allow fine-grained permission settings, making it difficult to delegate responsibilities securely and efficiently. For example, a QA specialist might need access to generate QA links but should not be able to modify offers or audiences. Similarly, a content editor might need to update offer text but not change targeting rules. The inability to configure such detailed roles leads to over-permissioned users and inefficient workflows. Why is this feature important to you –In large organizations or agencies managing multiple clients and campaigns, there is often a need to allow multiple team members to collaborate on activities. However, the current role-based access control lacks the flexibility to allow fine-tuned permissions (e.g., editing audiences but not offers, or managing QA links without publishing changes). This lack of granularity creates risk, slows workflows, and often forces teams to use shared credentials or workarounds.How would you like the feature to work –Adobe Target should provide customizable, granular access controls that allow admins to assign specific permissions to users or groups. For example:User A can create and edit audiences but cannot modify offers or publish activities.User B can update offer content but cannot change targeting or QA settings.A new "QA Reviewer" role can only view activities and generate QA links without edit rights.These permissions should be assignable at both the workspace and activity levels, and should support inheritance with overrides where needed.Current Behaviour –Adobe Target only offers broad user roles (e.g., Editor, Approver) that apply to entire workspaces. This often results in users having more access than they need, increasing the risk of unintentional changes or publishing errors. There's no way to restrict specific types of actions within an activity.
Already have an account? Login
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.
Sorry, our virus scanner detected that this file isn't safe to download.
