Product ideas | Community
Skip to main content

10000 Ideas

brentradNew Participant

CJA: add guided analysis type to tooltipNew

DescriptionThe guided analysis feature in Workspace allows users to configure several different types, including active growth, conversion trends, and frequency. The tooltip for each of the options gives some information about what the guided analysis does, and includes a link to the Adobe documentation for that type (see screenshot). Once a guided analysis has been created,the tooltip for the saved item contains no information about what the type was. If the naming convention of the saved guided analysis doesn't reference the type, people will be less likely to know what the guided analysis will show once used. The recommendation is to update the tooltip for saved guided analyses to include the type and a link to the Adobe documentation. A separate request for guided analysis updates can be found at https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-ideas/cja-add-description-field-to-guided-analysis/idi-p/748973.  Why is this feature important to youProviding type information in the tooltip will make it easier to people to see what the guided analysis is about. How would you like the feature to workAllow a type field in saved guided analyses tooltips. At the very least it should include the type name (e.g. Active growth, Frequency), and ideally would include a hyperlink to the documentation for that type on the Adobe side.  Current BehaviourThere is no type information field available in the tooltip for saved guided analyses.

Sven-iX
Sven-iXNew Participant

Improve usability of Filter + View + Grouping in list viewsNew

Description - Store the selection of Filter/View and Grouping with the current objectID Add the ability to combine Filter, View and/or Grouping into a "Scene"   Why is this feature important to you - Often different personas use different combination of view/filter/grouping.  The chosen view/filter/grouping depending on what a "project" or "task" or "issue" represents.    Example: Take "issues" on a project. In a creative execution project the issues might be change requests. So i need to see description, status, enteredBy, and group it by parent task. I might filter to open-only In a planning project issues might be items on a ROAM board.  Here I what to see a mix of basic and custom fields grouped by status Example: Take "tasks" on a project. A project is a configuration project where a task represents a configuration entry. I have a specific set of custom fields to display On project A I am a contributor so I want to see MY open tasks, grouped by week (plannedStartDate) On project B I am the project owner so i need to see the standard task view How would you like the feature to work - Scenes can be created/named (save current scene) and edited (each of View/Filter/Grouping is a dropdown of available options). Selecting a Scene sets the Filter/View and Grouping. Allow setting a scene as default. Store the selected view/filter/grouping (not the scenes) with the specific object ID (project ID, programID) instead of being global to the object type (all projects etc)   This allows me to have a set view for the examples above my config project scene my todos scene my PM scene my change-requests scene my ROAM scene   Current Behaviour - The Filter/View/Grouping combination is stored for the objectType, meaning the filter/view/grouping I selected on project A follows me when I visit project B For power users this is a nuisance An every user has run into this issue: A brief moment of panic when we don't see the expected items, only to find that a filter (used on the project I was on previously) needed to be unset. The current behavior (storing UI choices based on object type) adds no value at best, and can at times be a hindrance.

KotiSyamala
KotiSyamalaNew Participant

Feedback form wizard using landing pagesInvestigating

Description - Currently, our platform only supports single-page forms, limiting our ability to create comprehensive, multi-step feedback or survey wizards.Marketing forms are scattered across various third-party Content Management Systems (CMS), complicating data ingestion into Adobe Experience Platform (AEP).  Why is this feature important to you - Streamlines the process of collecting detailed feedback and survey data.Eliminates the need for external CMS platforms for marketing forms, simplifying data ingestion into AEP.Enhances marketing personalization capabilities by providing a centralized data source.Improves user experience by creating a more intuitive and structured form submission process.  How would you like the feature to work -  Implement a multi-page form wizard feature. This would allow users to create forms that span multiple pages, capturing detailed feedback data step-by-step.Enable seamless data storage within AEP from these multi-page forms, facilitating marketing personalization.Centralize all marketing forms within our platform at the AJO level.  Current Behaviour -  The existing system only supports single-page forms, preventing the creation of multi-step wizards.There is no data context retained between different form submissions, limiting the ability to build comprehensive user profiles. 

Markus40235deNew Participant

2step opt-out process for email unsubscribersInvestigating

Why is this feature important to you?Loosing email subscribers is a threat to every marketing program. This is why we should assure opt-out requests are gathered where recipients actually still like to receive emails. But this happens when content filters / spam filters analyze URLs in our emails. They need to "click" every link in order to analyze where the link redirects to and if it leads to a landingpage which is potentially dangerous. As this may be done for all URLs within our emails this affects unsubscribe links as well. Unfortunately this leads to automated "bot clicks" causing unsubscribed email recipients which have to be excluded from further email campaigns. We must avoid this happens with email subscribers who actually still like to receive our content.  How would you like the feature to work?Of cause a 2step opt-out process is  a solution to solve this problem. However we need to make sure that unsubscribers which were gathered via 2step opt-out process are still counted within context of a campaign. This is needed in order to calculate unsubscribe rates on campaign-level. If unsubscribers from 2step-process are not counted / attributed for the campaign / email from where the unsubscribe link was used then the unsubscribe rates of campaigns would be incorrect. It would be way too low as it would only count unsubscribers which were gathered via list unsubscribe header. So there would be an opt-out rate - but it would be incorrect / to low. That would be worse than having reporting with no opt-out rate at all because an incorrect rate would be misleading for most users. Current Behaviour?The API where we can ingest unsubscribers from the 2step opt-out process does not reflect the campaign which was unsubscribed. Therefore unsubscribed email addresses are gathered without connection to a campaign. This results in the mentioned problem / incorrect unsubscribe rates on campaign-level.

LuGebNew Participant

Object access control inheritance through folders or automatic assignment by current user groupsInvestigating

Description: I am looking for ways to enable data segregation within a sandbox, allowing different teams to have access to different objects such as journeys, campaigns, etc. The goal is to avoid the cumbersome process of manually assigning labels after objects are created to ensure that only relevant roles can see specific labels. Alternatively, having folder level access control where objects inside such folders will inherit access control restrictions would be beneficial.  Why is this feature important to you: This feature is important because it streamlines the process of data segregation, ensuring that teams can efficiently manage and access their respective objects without the need for manual label assignments. It enhances security and organization by automatically restricting access based on roles. How would you like the feature to work: I would like the feature to automatically assign labels to all objects created by certain roles, ensuring that only users with those roles can see these objects. Alternatively, folder level control with cascading permissions for objects within the folder, with folder-level label assignments being respected for all entities within those folders. Current Behaviour: Currently, labels must be manually assigned to objects after they are created, which is cumbersome and inefficient. This manual process is required to ensure that objects are visible only to users with specific roles who can see the assigned labels.