Build better products with our product team
Description - Seed addresses used for internal testing in campaign) are currently included in Adobe analytics reports by default. It can skew engagement metrics.Why is this feature important to you - including seed data inflates KPIs and provides misleading view of actual engagement. Accurate reporting is critical for evaluating true campaign performance, optimizing segmentation and driving meaningful decisions.How would you like the feature to work - Automatically filtering them out from AA reports or giving an option to exclude seed addresses.Current Behaviour - Currently seed addresses are treated like real customers and no out-of-the-box method to filter them out which leads to inaccurate campaign campaign evaluation.
Description - I would like to have the ability to search, sort, and filter the Fusion datastore view. Why is this feature important to you - It's very tedious to find records by visually looking at the datastore. It's also difficult to organize the Fusion datastores without the ability to sort the columns. How would you like the feature to work - I would like the ability to sort by ascending or descending order, filter each column and search the datastore for specific records. Current Behavior - The Fusion datastore is not sortable, filterable, or searchable. The only way to find a record is to manually search each page individually or to use Fusion to search.
Description - As a Fusion Developer, I would like to have the ability to search, sort, and filter the Fusion datastore view.Why is this feature important to you - It's very tedious to find records by visually looking at the datastore. It's also difficult to organize the Fusion datastores without the ability to sort the columns.How would you like the feature to work - I would like the ability to sort by ascending or descending order, filter each column and search the datastore for specific records.Current Behavior - The Fusion datastore is not sortable, filterable, or searchable. The only way to find a record is to manually search each page individually or to use Fusion to search.
Request for Feature Enhancement (RFE) Summary: Cloud Manager Deployment: Enabling Rollback from Previous Build Snapshots Use-case: The customer is trying to roll back the deployment after a successful production deployment. Currently, the only way to roll back is to re-deploy the code in Cloud Manager, which takes 2 to 3 hours. Given that they are supporting 24 websites (with more to come in the future), they need to reduce the build time for any rollback operations. The best way to achieve this is to enable re-deployment using an earlier stable built image. Current/Experienced Behavior: The production deployment is completed. After the deployment, the customer discovered blocker issues on one of the 24 websites. They decided to roll back the deployment. They reverted the change that caused the issue and pushed the revised changes to Cloud Manager. They restarted the Stage/Prod build, which took 2 to 3 hours. The customer is trying to minimize this 2 to 3-hour downtime as much as possible. Improved/Expected Behavior: The production deployment is complete. After the deployment, the customer discovered blocker issues on one of the 24 websites. They wanted to roll back the deployment. They should be able to restart the Stage/Prod deployment using an earlier stable built image. Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud (2024.4.16145.20240430T082417Z) Customer-name/Organization name: LG Electronics, Global HQ Korea 24 subsidiaries (UK,DE,PE,TR,JP,FR,SG,CO,SA,SA_EN,CA_FR,CA_EN,KZ,ID,IT,CL,TH,PT,IN,HK,HK_EN,BR ,MX ,PA) Screenshot (if applicable): Code package (if applicable):
Description - When a user's license reduces their sharing permission, this reduced access is not reflected in any of the shared objects today. This leads to issues where someone who is not supposed to make certain changes is still allowed to do so.The system should automatically check on any change being saved to see if their permission has changed. If so, their new sharing rights should override the existing sharing permission. It should also update the sharing rights on the object being saved so that it reflects the new permissions. Why is this feature important to you - To avoid users who had higher privileges, but is no longer privileged, to be able to make changes they should not be allowed to anymore. Currently, it is the responsibility of the object owners to update their sharing, but this is burdensome and error prone since owners may not know they are over-sharing now. How would you like the feature to work - The system should detect a change in permission at save time and prevent changes that are no longer allowed as well as update the sharing rights on the objects being modified. Current Behaviour - No permission checks are done on save, even though their rights have been reduced.
Description - Why is this feature important to you - We've recently discovered that delegated tasks show on Home regardless of the filtering we have set. Most of us have "Not Ready" and "Completed" unchecked -- there's generally no reason for me to see tasks that are not ready for me to work on or tasks that I've already completed. But the "Delegated" filter works separately from the other task filters How would you like the feature to work - I would like the filtering of delegated tasks to work the same as filtering on tasks assigned to me. I don't know why anyone who has "Not Ready" or "Competed" unchecked for their own work would want to see those items for someone else's work that has been delegated to them. Current Behaviour - per current functionality, the following is expected to show on the Home Work List when "Delegated" has been selected: - Delegated tasks that are both ready to start and not ready to start- Delegated tasks that are marked complete will continue to show for 2 weeks after the completion date, after which they will fall off
Because our timesheets are populated with tasks which have got Planned Start or End date within the timesheet range, even thought you mark task as complete for yourself - it still appears on the timesheets due to dates. It would be really useful if hitting 'Done With My Part' on tasks was taking the task away from your timesheets. Currently it's a pain as you don't really need a task t be on your timesheet if you are not working on it anymore. It's really annoying if you've got long list of project/tasks you work on,
Simple ideas to enhance administrative review of scenarios: Add a "Description" field that can be populated by the developer to explain the scenario, similar to reporting!Expose this description on the scenarios screen to allow a quick read of the different scenariosAdd extra systemic data such as "created by", "last modified by", "last modified date", "last run date" history etc in the list of scenarios for quick visual
Description - Today, when the Experience Platform Debugger is used by a logged-in user, the component name is pulled right into the debug output, which is great: However, this could be enhanced by a lot by pulling in more details. Some things I would love to see there: The component description Expiration/Persistence settings for eVars List settings for eVars and Props Event settings Existing Classifications This would help to make the debugging experience much easier for less-technical business users. Maybe others have some more ideas? 😊
Description - When working in a Workspace Table, rows are sometimes custom segments or specific values from another dimension. They stay in order as long as you don't edit any of the metrics. However, when you start adding/removing metrics, the order of your table is lost and you have to rebuild it. It would be better to have a feature to lock your selections in place so they remain sorted in the desired order while you actively work in the table. Without this feature I am constantly having to manually re-add the dimension values or segments and it's a waste of time. It would be ideal if the "lock order" feature was available in the right click menu with the other options to copy/download/delete/create segment from selection, etc.
Description - Expand the functionality for chart colors in reporting. Right now the only way to customize colors is to do so individually. The option to set default colors (ie: that match your companies colors) should be easier than individually changing each item. Why is this feature important to you - Easier functionality for setting up brand colors would help with system maintenance and help make reporting across an instance more cohesive and allow system admins to dictate how colors can be used. How would you like the feature to work - Put it in setup where the other branding options are. Current Behaviour - Manually change each line item in a chart report individually or use text mode.
Once someone is included on a Workfront updates thread, they are there for life. We need to be able to remove people who are no longer on projects or who were tagged in by accident.
Currently, Programs can only be associated with one Portfolio. We would like to be able to associate a Program with multiple PortfoliosWe often have campaigns with multiple workstreams and work teams that need to be integrated. A Program that can be shared across Portfolios would be a good solution for this need.
Description:Enable a native integration between Adobe Experience Platform (AEP) and Databricks to allow seamless data exchange for advanced analytics, machine learning, and large-scale data processing.Why is this feature important to you:Databricks is widely used for data science, modeling, and big data workflows. Many organizations already use both AEP and Databricks but face challenges moving data between the two. A native integration would eliminate friction, reduce reliance on custom pipelines, and unlock more value from both platforms by enabling real-time insights, model scoring, and enrichment of profiles in AEP.How would you like the feature to work:Users should be able to configure a connection to a Databricks workspace directly from the AEP UI. They could export datasets from AEP to Databricks, run transformations or machine learning models, and then write enriched results (e.g., scores, segments, predictions) back to AEP. Ideally, this would support scheduled or triggered jobs and respect identity namespaces and schema alignment.Current Behaviour:Today, connecting AEP to Databricks requires custom ETL workflows, cloud storage intermediaries (like S3 or Azure Data Lake), or APIs. This adds complexity, latency, and cost, and often involves multiple teams. There’s no streamlined, supported connector between the two platforms, limiting agility for data science and activation use cases.
Description:Allow users to upload flat files (e.g., CSV or Excel) directly into Adobe Analytics for temporary, ad hoc correlation with existing data in Analysis Workspace.Why is this feature important to you:Often, analysts receive supplemental data from external sources — like media plans, call center reports, or offline survey results — that need to be compared with web or app behavior. Currently, there’s no easy way to integrate this data quickly for exploratory analysis. This feature would enable faster insights without relying on engineering or data ingestion processes.How would you like the feature to work:Users can drag and drop or upload a flat file directly into Workspace. They can map the file’s columns to existing Adobe dimensions (e.g., campaign ID, date, region), then use those fields like any other dimension or metric in visualizations. The join would be temporary and only available within that session or project, without affecting underlying data.Current Behaviour:Today, adding external data to Adobe Analytics requires a full ingestion process through Customer Journey Analytics, Data Sources, or back-end engineering support. This takes time and isn’t practical for fast, exploratory use cases. There's no native method to correlate external flat-file data directly within Workspace.
Description - Ability to see how HCPs overlap in 3 - 4 audiencesWhy is this feature important to you - We have some of the same HCPs who would be seeing patients for diabetes, obesity and liver problemsHow would you like the feature to work - by seeing the overlap, we could determine how to communicate with the HCPs without spamming their inboxCurrent Behaviour - we have to choose days when emails are sent out or create various business logic to minimize the opportunity to send multiple emails on the same day. It is sometimes hard because we send emails daily.
Description - The widgets home page is too complex for some users who only want to see just a full list of their work. The Priorities view provides a great option for this with an enhance user interface that has just what these users need. Though a report can display most of the same info as the Priorities view, the report does not look as pleasing.Why is this feature important to you - Many users still prefer the old home interface and this is a great compromise between the old and the new.How would you like the feature to work - Go into a layout template and set Priorities as the home landing page.Current Behaviour - Priorities is not an option to to select for the home landing page
Description - Please refer adobe support ticket of Dell company "ase Number 00438765 - In proofing, where to check when a user is created and by whom ?"Why is this feature important to you - To know who and when created a account.How would you like the feature to work - Show created by and date for Guest and Member accounts in Proofing Current Behaviour - Currently Proofing showing, Created Date only for User accounts. It is not showing for Guest and Member accounts. And Proofing not showing Created By or Triggered By for any account.
DescriptionWe are requesting a feature in Workfront that enables users to filter updates on issues, tasks, and especially projects, programs, and portfolios based on specific fields that were changed. This would help users quickly locate historical changes tied to a particular field (including custom fields), rather than having to sift through a long list of general updates. Why is this feature important to youProject and portfolio managers need efficient access to field-level change history to ensure accurate tracking, decision-making, and reporting. This is particularly important when reviewing how project details have evolved over time, supporting transparency and accountability. Additionally, being able to present this data to executives is critical in portfolio-level oversight and governance. How would you like the feature to workWe envision a filterable audit log within the Updates or Journal area that allows users to select a specific field (e.g., “Planned Completion Date” or a custom text field) and view a history of only those changes, including timestamp, user, and old/new values. Ideally, this functionality would also be exportable or easily reportable to support executive summaries or audit reviews. Current BehaviourCurrently, Workfront provides a general log of updates with timestamps, but there is no way to filter changes by specific fields/dates/etc. Some limited history can be pulled through custom reports, but this does not apply to all field types (e.g., custom text fields), and the reporting itself is constrained and difficult to create/use for this purpose. As a result, reviewing historical data for key fields is almost impossible, time-consuming and often incomplete.
We (Marketing) works with some teams in IT and other vendors that use Jira. The WF Plugin for Jira is extremely valuable in letting the PM assign work to these times in a specific Jira board and have visibility over it alongside other tasks/projects we have in WF (as sometimes our projects involve both teams). We have a Jira Cloud instance and another vendor that uses Jira Data Center. We wanted to start using this for our Data Center instance and apparently this was discontinued. According to WF, "we lost the integration with Data-Center in January of 2022. This happened because Jira updated their requirements for Data-Center Plug-ins. At this time we have not made any changes to align with the new Data-Center Requirements and the integration has been moved to a 'Not-Supported' state. They have requested that the idea be submitted to the innovation lab so that they can better gauge how many of our customers are looking for this integration." Please bring back the ability to use this WF Plugin for Jira to Data Center Jira instances.
Description - PLEASE add functionality for us to connect an issue with a project that has already been set up. Why is this feature important to you - We Forecast a good portion of our work so that we have placeholders during our heavy seasons. When we receive issues for these requests from a queue, it won't allow us to connect the two while bringing over the custom form and attachments. How would you like the feature to work - When converting the issue to a Project, an option should be "convert to established project" and we should be able to add to the project we already have set up but also bring over the custom form and attachments from the Issue. Current Behaviour - this doesn't exist. As a workaround, I'm having to convert the issue to a new project, clearing out the timeline that populates, copy Forecasted timeline over to the new project then I have to delete the project I had in Forecasted. Very cumbersome workaround.
We would need different levels of permission for access in the offers tab. For example, one access to create the offers but not be able to approve them, and another access that can both create and approve.We want to prevent those who are supposed to only build the offers from activating it incorrectly without supervision/approval.currently the same employee who builds the offer is able to approve it.
Here is a list of uses cases where I would have loved a product-scoped container in the segment builder:https://analyticsdemystified.com/adobe-analytics/product-segmentation-gotchas/Here is a description of how it might work:https://analyticsdemystified.com/adobe-analytics/a-product-container-for-christmas/Here are other related ideas:https://forums.adobe.com/ideas/8709https://forums.adobe.com/ideas/10245
When building landing pages in Marketo, we often focus on elements like the form, content, and design — but one crucial aspect is often overlooked: Meta Open Graph (OG) tags.These tags play a silent yet powerful role in how your landing page is displayed when shared on platforms like LinkedIn, Facebook, or Slack. What Are Open Graph Tags? Open Graph (OG) tags are small snippets of metadata that go into the <head> section of your page's HTML. They control how your content appears when shared on social media — ensuring your link previews show the right title, description, image, and URL. Without OG Tags, Your Shared Links Might:An outdated or irrelevant imageA vague or incorrect titleMissing or unoptimized descriptionNo branding or keyword contextSince Marketo doesn’t automatically inject OG tags into landing pages, so you’ll need to manually add them to your Landing Page Template or through a Custom HTML block in the page.Here is the basic example:<head><meta property="og:title" content="Title of Page" /><meta property="og:description" content="Add Description about Page" /><meta property="og:image" content="Main Image URL of Page" /><meta property="og:url" content="Page URL" /><meta property="og:type" content="website" /></head>Adding these tags helps ensure your landing pages are visually aligned with your brand and perform better when shared on social platforms. Hope this helps you make your Marketo pages more social-friendly and on-brand!
Today, when you install Marketo Sales Insight with Salesforce, the managed package automatically creates the required fields for syncing over a variety of items, such as those around Last Interesting Moment. In particular, Last Interesting Moment Description is a textarea field--but it is limited to 255 characters. Marketo does not enforce any sort of field length limit beyond its maximum on the backend. As a result, it is exceedingly common to create Interesting Moment Descriptions that exceed 255 characters, especially if something like trigger URL is being replicated on an IM like "Clicked Important Email". My current understanding is that these fields are NOT directly referenced in the Visualforce components of MSI and thus there would be minimal impact to accepting larger items. For example, when looking at a MSI Visualforce component on a client instance, I can see a description of 285 characters is successfully displayed. As a result, I would like the ability to optionally increase the textarea field character limit within reason to accommodate these behaviors without encountering sync issues. You should be able to modify this in a straightforward way in the package schema by changing the field's manageableState to SubscriberControlled.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
