Build better products with our product team
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 - When kicking off a Universal Approval (document approval) we need the ability to add a message prior to sending to the reviewers. Proofing workflow has this ability. Why is this feature important to you - It's consistent for both Workfront owners and reviewers/approvers as they experience in Proofing workflow.How would you like the feature to work - After choosing my reviewers/approvers, I'd like to type in a message that will appear in the notification they receive.Current Behaviour - I have to add a message in the "Updates" feature which then disconnects from the review/approval notification. Leads to confusion and multiple notifications on the same document.
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.
Descripción - Me and my colleagues are using the set auto_to_json function a ton while querying, partially it is because it only works for a single session. Therefor, one day, I thought that it would be a low effort hight reward implementation inside the query service UI. This function might be implemented at an account level or just by adding a little toggle inside next to the "copy" or "undo text" functionalities. Something like this: I am really sorry for my drawing skills, as you might have already figured out, I am not an artist haha.
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.
User field "reason" should be editable.Since Marketo migrated to Admin Console, this field is no longer available. It used to be available on creating a New user in Marketo, but it isn't available when creating a user in Admin Console.It was always annoying that it couldn't be edited after creation.With a large instance, and almost 100 users, this field is important for managing who is who in the zoo.
Often time there are small steps/items that need to be remembered for a particular task. It's too granular to be it's own task, but it would be helpful for the user/resource to be able to add a checklist/to-do list to their own task and for a checklist to be added to templates. For example, an article creation task may have the following to-dos: Update editorial calendar - Takes less than 5 minutesCreate writing assignment - Takes 15 minutesSend writing assignment - Takes less than 5 minutes Writing assignment accepted - Just a reminder to check in Hopefully you get the idea.
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.
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.
Description - Allow the versioning of or the replacement of documents that are in a folder in a Workfront project that is linked to AEM Assets. Why is this feature important to you -Our marketing teams use Workfront to route their materials for review and approval. There are situations where minor changes are needed to be made to documents after that are approved and moved into a folder in their Workfront project that is linked to AEM Assets. These changes are typically made by external agency partners and loaded into Workfront for review and approval routing by those agencies. Once the changes are approved, the marketers must move those changed files into the linked folder, either replacing or creating a version of what’s there. Today this functionality does not exist. The Marketer must use the following workaround:Download the document(s) from Workfront.Upload or drag/drop the document(s) into AEM Assets - they either replace what’s there or create version(s).To avoid duplicate documents, delete the document(s) from the Download location.This creates extra unnecessary steps and also creates the potential for duplicate documents if the user forgets to delete the document(s) from the download location, impacting our single source of truth. How would you like the feature to work -The users would like to drag one or more documents (that have the same names as what’s already present in the linked folder), from one folder in their Workfront project into the project's linked folder. They should get a message, like in AEM Assets, to either replace the document(s) in the folder or create version(s). Current Behavior - Once documents have been moved into the linked folders in a Workfront project, users are no longer able to edit, delete, replace, version, or move those documents.
We'd like to have a default "Cancelled" task status (as opposed to using the Complete status with a "Cancelled" label). We don't want cancelled tasks to affect the Actual Completion Date or other project calculations.
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.
Description - Since the search functionality updates in May 2025, we find the "basic search" feature in Workfront confusing and not useful. It has some serious limitations basically causing it to not display accurate results which leads to confusion. Why is this feature important to you - at this point I've directed my users to pin the "advanced" search page and use that instead, which feels clunky and confusing compared to just being able to use the search bar as one would expect. How would you like the feature to work -When I type in the search bar, recent items are suggested to me (working today well)If I don't immediately see what I'm looking for, I'll click "search" and then I would expect it to flow into the "advanced search" page from there where I could drill down as needed.Basically, go back to before May 😉 feel free to enhance search with AI so it makes smarter suggestions, but having both basic and advanced search feels unneeded from my chair.Current Behaviour -Basic search doesn't display the results I'm looking for..When I enter a keywordWhen I enter the exact name of somethingEven if it is something I've interacted with
When I go to Workfront "Recents", the clock icon in the toolbar at the top right, I want the dropdown list in the "DOCUMENTS" section to open the actual proof instead of going to the "DOCUMENT > Overview" page. I see no benefit to opening the "Overview" page.I use "Recents" to reopen my current WIP proofs. The proof should be one click away not 2 clicks away. It is not a good user experience to first open to the "Overview" page. It would be better to open the actual WF proof.
Please add Google Gemini to the collection of Gsuite Fusion connectors! My organization uses Gemini and we cannot use ChatGPT.
Description - For Adobe Analytics Data Warehouse exporting, I would like to suggest for an export option to a Microsoft Fabric Lakehouse as this is Microsoft's newest data platform. Our business use case involves analyzing the Adobe Analytics data alongside our existing 1st party data in Microsoft Fabric, and then using some outputs in our reporting.Why is this feature important to you - Microsoft Fabric gives us the most processing power for analyzing 1st party data. By being able to export Adobe Analytics data to a Fabric lakehouse, we can utilize that processing power to combine web behavior data with 1st part data for reporting and ad hoc analysis.How would you like the feature to work - Export option to Microsoft Fabric LakehouseCurrent Behaviour - Right now we can export to an Azure source then setup a data process that can take it from Azure and upload to Microsoft Fabric. Those are extra steps that slow down our ability to further ETL and analyze this data in a timely manner.
Description - right now, WebSDK only supports sending data to Experience Event schemas/datasets. This is reflected in the WebSDK data elements, where only Experience Event schemas are shown. Usecase: build up a Profile when the user fills out e.g., a newsletter form. It's a CDP and this should be a standard feature and it cannot be that one must set up some server-side API connection to make this work somehow. This approach is way(!) too complicated and should be possible to be done in the Tag Manager like sending page view or other events. I found threads from years ago where Adobe said it would come and is on the roadmap. So, ...? Why is this feature important to you - I cannot be that you must be or ask a programmer to send any kind of Profile-related information to the CDP, whereas you can easily send interactions through the WebSDK. How would you like the feature to work - allow the user to create Profile-schema XDM data elements and also give the user the choice to send this information to the Profile dataset e.g., through a dedicated "Update Profile" event type or similar. Current Behaviour - All WebSDK sendEvent calls end up in the Experience Event dataset. If a custom code sendEvent is used and Profile attributes added to the XDM, they are dropped since they are not in the Experience Event schema. Side note: to achieve the Profile update through Launch and not needing to ask a CMS dev, I had to come up with a solution that puts any Profile-related data into the "data" section and use Launch SSF to pick up this data and send it to the AEP HTTP API. Obviously it is less than ideal that you must to either have the SSF SKU or implement it on your own webserver through customiz APIs implementations.
Description - I'm currently migrating a team from Asana to Workfront. And an important stakeholder asked if there was a Dark Mode. I thought it was such a good idea, I wanted to drop it here!Why is this feature important to you - For folks who work on computers day and night, they like to take some of that blue light strain off with the dark mode.How would you like the feature to work - Similar to Teams, or Asana, Maybe it's a user setting, or an Admin setting in a Layout Template where you can choose which desktop interface you want, light or dark mode.Current Behaviour - Light all day every day! (My EYES!)
Description -Why is this feature important to you -i want to hide the shared components to some users which work in different bunsiness unitsHow would you like the feature to work -Current Behaviour -can share to all - but everyone will see all of the segments/calculated metrics that admin shares. putting in user group will give users the ability to share to all users.
Description:We are requesting an enhancement to Workfront form field validation to better handle ligature-based special characters (such as ff, æ, fl and others). Currently, these characters can be entered into form fields without restriction, which creates downstream processing issues when the data is consumed by integrated systems or exported for further use. Current Behavior:Workfront does not validate or restrict entry of ligature-based special characters in form fields.These characters remain undetected until they cause issues in downstream processes (e.g., PDF conversions, integrations, or reporting).Requested Behavior:Workfront should include real-time validation logic that can automatically detect ligature-based special characters at the point of entry.Users should be prevented from proceeding to the next step until such characters are removed or replaced.Ideally, the system should display a clear error message indicating which field contains invalid characters.Business Impact:Prevents data corruption and failures in downstream workflows such as PDF conversion, reporting, or integration with other Adobe and third-party tools.Reduces manual intervention required to troubleshoot and clean invalid data.Improves data quality and reliability within Workfront forms, ensuring smoother automation and scalability.
Description - Enable a module that can call another scenario directlyWhy is this feature important to you - This would enable a more modular design of our workflow by having common functionality in one scenario that can be called by other scenarios without having to duplicate the functionality across all of the scenarios.How would you like the feature to work - A simple module that provides the input of the scenario name to call and the inputs to pass.Current Behaviour - Have to code custom webhooks to call scenarios
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.
