Build better products with our product team
Request for Feature Enhancement (RFE) Summary: Automatic Redirects for URL Changes If a page’s URL changes while it is live (due to a title change, page move, or unpublication), could AEM automatically generate a redirect to the new location? Ideally, authors should also have the ability to specify which URL to redirect to (e.g., another page or a 404 page). Use-case: If a page’s URL changes while it is live (due to a title change, page move, or unpublication), could AEM automatically generate a redirect to the new location Current/Experienced Behavior: A page url is changed, we will have to manually use ACS Common Tools to add in a redirect url. Improved/Expected Behavior: Have a list of all redirects If a page’s URL changes while it is live (due to a title change, page move, or unpublication), could AEM automatically generate a redirect to the new location. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: OneTrust Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Bulk Page Movement Right now, AEM only supports moving one page at a time. This makes taxonomy updates and bulk redirects very time-consuming. Could AEM allow authors to select and move multiple pages simultaneously to streamline these workflows and move it to another location? Use-case: Currently, Adobe Experience Manager (AEM) only allows authors to move one page at a time. This limitation makes it inefficient to perform large-scale site restructuring tasks—such as taxonomy updates, reorganization of content folders, or implementing bulk redirects—especially for enterprise-level websites with hundreds of pages. By introducing a Bulk Page Movement capability, authors could select and move multiple pages simultaneously within the AEM interface. This enhancement would streamline content management workflows, reduce manual effort, and minimize human error during site reorganizations. It would also improve overall authoring efficiency and help ensure faster delivery of structural updates across the website. Current/Experienced Behavior: Right now, AEM only supports moving one page at a time. This makes taxonomy updates and bulk redirects very time-consuming. Improved/Expected Behavior: AEM allow authors to select and move multiple pages simultaneously to streamline these workflows and move it to another location? Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: OneTrust Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Enable the ability to add custom fields to the Content Fragment GraphQL schema via code, SlingDataFetcher, or programmatic means, without requiring changes to the Content Fragment Model definition in AEM. Use-case: Developers and integrators need to expose computed, derived, or integration-specific fields in the Content Fragment GraphQL API for headless delivery, without modifying the underlying Content Fragment Model. Current/Experienced Behavior: The Content Fragment GraphQL schema is auto-generated from the Content Fragment Model and system fields. It is not possible to add custom fields via code, SlingDataFetcher, or other programmatic approaches. Business Impact Limits flexibility for headless integrations, increases maintenance overhead, and requires model changes for every new field, which may not be feasible or desirable in large organizations or for computed/integration fields. Improved/Expected Behavior: Ability to programmatically extend the Content Fragment GraphQL schema with custom fields (e.g., via SlingDataFetcher or similar mechanism), allowing dynamic, computed, or integration fields to be exposed without model changes. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5 LTS; Content Fragment Models and GraphQL API; persisted queries; endpoints as described above. Customer-name/Organization name: JPMorgan Chase Code package (if applicable): https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-expose-a-custom-resolver-field-in-content-fragments-for/m-p/776485 . I have added the code here
1) Dimension Value Highlight Visualization DescriptionIt would be great to have a new visualization in Adobe Analytics / Customer Journey Analytics that highlights dimension values. For example, showing which product has the highest conversion rate or which page is the most viewed. The visualization would be similar to a Summary Number or Summary Change, but focused on what rather than how much. Why is this feature important?Currently, summary visualizations are excellent for showcasing key metrics, but they don’t emphasize the specific dimension value driving those results. Having a way to visually highlight the top-performing dimension item would make dashboards more insightful and storytelling more effective. How would you like the feature to work?Users could select a metric and a dimension, and the visualization would automatically display the top (or bottom) dimension value according to the chosen metric. Ideally, it would also support conditional formatting (e.g., color-coding by performance) and allow display of secondary metrics for context. Current BehaviourFreeform tables are useful, but not quite visual. Additionally, there are limitations to create something a bit custom.2) Sentiment Analysis–Style VisualizationDescriptionAnother interesting visualization could be one inspired by Sentiment Analysis — designed to highlight dimension values in relation to a specific metric. It would resemble a scatter plot but use text labels instead of points, making it easier to identify and interpret key drivers at a glance. Why is this feature important?This would provide an intuitive way to analyze performance or perception differences among dimension values (e.g., campaigns, products, or pages) in a single, visually engaging chart. It’s especially useful for understanding “how each dimension feels” relative to a metric. How would you like the feature to workThe visualization could plot dimension values (as text) along two axes — for example, performance vs. volume — and apply color or font size to indicate sentiment, change, or relative importance (or even font size). Hovering over text could show detailed metrics or trends.
Our team depends on knowing the priority of a task to know which task to complete first. We use the task priority field to indicate if a task has a hard, soft or urgent deadline. That priority needs to be visible as a column in the My Tasks widget.
If you have a Conversational Flow with a Meeting Booking, and set info capture to "Skip if value is already in database", the meeting confirmation email does skip these fields as well. That's not a great experience. If the value is skipped, because it already exists in the database, the confirmation email should grab that value from the database. Otherwise the sales person that takes the meeting doesn't get that information. Here's the confirmation email for a new person that doesn't skip values: And here's the same confirmation for a person that is already known in Marketo:Sales Person wouldn't know First, Last, Country and Company Name.
Description:It would be highly beneficial to display the size of an individual profile directly within the Profile Viewer in Adobe Experience Platform (AEP). Why is this feature important?Currently, while we can view various attributes and audience memberships in the UI, there is no visibility into the actual size of a profile. Having this information readily available would help us better understand data volume, optimize storage, and troubleshoot performance issues more effectively. How would you like the feature to work?Within the Profile Viewer, alongside existing profile attributes, display the total size (in KB/MB) of the profile. This could be shown as a summary metric or as part of the metadata section. Current Behavior:There is currently no way to determine the size of an individual profile through the UI, which limits visibility into data usage at the profile level.
I've had this request from our sales team. They would like to be able to view leads who have visited specific pages and/or content on our website. While I can set this up as an Interesting Moment its still only showing at the person or account level. They want a view where they can filter by using a URL on from our website and see a list of their leads have viewed that content.
Description - Particularly Billing Record fields should be reportable Why is this feature important to you - currently when a billing record contains billable hours, expenses, and tasks, there is no way to report on the breakdown totals. These fields show on the billing record itself adding up all the hours, expenses, or tasks, but you have to open each billing record to find them and cannot report on all billing records and their respective totals. How would you like the feature to work - allow the below fields to pull into a report of Billing Records Current Behavior - These fields from a Billing Record are not reportable: Billable Hours Billable Expenses Billable Revenues We are currently relying on Fusion to fill in custom fields with these totals so they can be reported on.
When editing any email in the new email designer, Edit Email Content>AI assistant (option on the right bar)>Text settings>Language. The only language option in which the text can be generated is English. There should be support for multiple languages like, German, Polish, French, Italian, Spanish, Dutch, Portuguese, etc.
We have received confirmation from Adobe Support that when importing customer attribute data from non-Adobe CDP sources using the Adobe Target Bulk Profile Update API (v2), although the data is transferred in array format, Adobe Target can only process it as ‘single-value strings’.If array format can be received, should it not then be possible to handle it as an array within Target?This would be significantly more convenient when creating audiences, so we would very much appreciate your consideration of this matter. test
It would be great to be able to have multiple dimension columns rather than having the information stacked. Currently whenever you breakdown dimensions it stacks this on a line by line basis which makes it harder to analyse and also looks messy for the end user.Example below
DescriptionCurrently, Adobe Analytics 1.4 API provides several powerful endpoints that allow administrators to manage report suite configurations programmatically. These include the ability to:Fetch and update eVars, props, events, and classifications.Retrieve configured processing rules for a given report suite.Adobe has announced that the 1.4 API will be deprecated in favor of the 2.0 API next year. However, these configuration-level features are not yet available in the 2.0 API. Once 1.4 is removed, these critical capabilities will be lost.For many enterprise-scale implementations, this functionality is not just convenient — it is essential. Proposed ideaExtend Adobe Analytics 2.0 API to include endpoints for:Variable Management: Create, update, and fetch eVars, props, events, and classifications at the report suite level.Processing Rules: Fetch and (if possible) update processing rules for a given report suite.Cross-Suite Comparison: Provide efficient ways to compare variable configurations between report suites via API.This would ensure continuity for projects currently relying on 1.4, while aligning with the modernized API framework. Benefits / Use CasesScalability: Easily update or configure variables across multiple report suites in bulk instead of relying solely on the UI.Transparency: Retrieve all processing rules in one call, making it much easier to audit mapping when there are 100+ rules.Consistency: Compare variable configurations across report suites to ensure alignment in enterprise environments.Efficiency: Save time and reduce manual effort by automating repetitive admin tasks.Call to ActionPlease consider adding these configuration endpoints to the 2.0 API roadmap to avoid losing critical functionality when 1.4 is deprecated. This would greatly benefit customers managing multiple report suites and complex implementations.
Description - I just made an error in my custom form that has layers and layers of display logic. I am trying to create a report to pull the fields I need to fix, but my report is massive since there are so many IF THIS THEN THAT scenarios. Can you create an option to disable display logic for reporting? Why is this feature important to you - This feature would save me/others a tremendous amount of time and help us rectify issues quickly. How would you like the feature to work - Could you include this in the report settings as a check box? Current Behaviour - This feature does not exist. Mistakes happen and the display logic makes it very hard to correct errors.
Experiencing an issue while creating new event channels in Marketo—specifically, the dropdown under System Mappings isn’t allowing us to input additional values.Need to link the defined Statuses under the Channel with the appropriate System Mappings.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.