Adobe Analytics

Description - Where a subclassification is already created as part of copying a report suite, it is currently not possible to identify which report suite the subclassification is attached to. Tags on subclassifications do not appear in the left rail of the classification sets UI, and filtering by report suite does not return subclassifications.Why is this feature important to you - Where there are multiple report suites that have similar classification requirements, it is difficult to identify which one has been most recently updated with the latest classification file.How would you like the feature to work - I would like to be able to use the report suite filters or tag filters available in the classification sets UI to filter subclassificationsCurrent Behaviour - subclassifications cannot be easily identified or filtered by report suite or Tags

Description -It is so easy when expanding a panel to accidentally click on the x and delate it!How would you like the feature to work -Please add a warning popup when the x is hit.Current Behaviour -It deletes the entire panel and you have to press Ctrl-Z to undo.

Description -Currently, when using "flows" in Adobe Analytics or CJA, you are limited to using only individual dimensional items one at a time.  It would be super helpful to be able to use a hit-based segment so that you can see flows into a "group" of items (ex: a group of URLs).   Why is this feature important to you - Scalability, it will allow the user to see more macro flow visuals. How would you like the feature to work -Allow hit-based segments to be dropped into "flow" displays.    Current Behavior -You can only include individual dimensional items.    

Description -One of the biggest pain points in Analysis Worskpace for my users is that they don't understand which dimensions and metrics should (and should not) be used together in freeform tables or other visualizations. Having a means to connect related dimensions and metrics so that when a user selects one component, the other related components become immediately visible in the left rail would make this easier for less advanced users.  Why is this feature important to you -It would greatly help less experienced users become more familiar with how dimensions and metrics relate to each other and empower them to confidently select the right components for their needs with fewer mistakes and less need for support. It will also cut down on the amount of incorrect data shared company-wide due to misinterperetation of the data or use of the wrong components for their reporting needs.  How would you like the feature to work -A UI tab where admins can create curated com

DescriptionOne of the CJA guardrails limits the number of derived fields that can be added to a Freeform Table to five. When a user tries to add more than this, they will see a popup like the one shown below: While the limit itself isn't an issue, it's highly likely that an everyday user will have no idea what a derived field is and how to avoid using an additional one. There are really only three ways to tell whether a component is based on a derived field: The user can look at the component tool tip, which will include a "Field settings" tab if the component is a derived fieldAdmins can indicate that a component is based on a derived field in the component nameAdmins can indicate that a component is based on a derived field in the component descriptionUsers aren't super likely to look at #1 or #3, and organizations probably don't want to clutter up component names. This means that they may see the notification and immediately contact an admin for help. One option to ma

Description of the Business Challenge:Currently, if you are using a virtual reporting suite to provide a controlled clean environment for your analysts, you need to first go to the admin console to assign dimensions, metrics, and segments to the reporting suite.  It would be easier to have the ability (as an admin) to assign components to a reporting suite while directly working inside Workspace.   Why is this feature important to you - Having this feature will accelerate organizing virtual reporting suites and will also allow assignment of components on the fly.  I cannot count the times I have thought "this should be in the VRS" but then didn't have the time and forgot to make the change.   How would you like the feature to work - When in the components list view or inside a component configuration, allow a dropdown to be present so you can select what reporting suits the component is applicable to.     Curren

Description -1. AWS Web Analytics product team uploads AWS blog meta data via classification importer feature in Adobe Analytics (AA). Also we use Classification rule builder feature to automatically classify AWS product pages meta data in AA reporting. Unfortunately these classification data can't be sent to downstream AWS s3 location via Adobe Analytics data feed feature. We have a downstream bigger data lake system where we send hourly data feed from Adobe Analytics. Every time my team works on the classification addition or modification needs to be manually worked by AWS downstream data engineering team to add the same details in their database to bring parity to AA and other system reporting. This is time consuming and repetitive task. 2. There are limited eVars (250) available for Adobe Analytics. Classification is a great feature to separate out concatenated data being passed to an eVar and store individual values in different coulmns associated with that eVar. This feature

Adobe - please allow for public Workspace projects to be embedded in third party platforms/websites.Currently, your page includes a Content Security Policy (CSP) directive which prevents the pages from being framed by non-Adobe domains. I can think of a great number of use cases for such functionality, including AA reporting in Tableau dashboard without having to design an entire ETL process for moving the data from AA into Tableau.

Description - Multiple Breakdowns Applying as Time Expands.Why is this feature important to you - It alleviates lots of manual work.How would you like the feature to work - To automatically apply breakdowns with certain dimensions to others as time increases.Current Behaviour - You have to manually add 1 or more breakdown dimensions to each month dimension value that gets added as time goes on.

Description -I set my panel dates and checked the advanced setting "make date range components relative to panel calendar".On my table, i right clicked on my custom metric, did "compare time periods" and "custom date range to this date range". The new custom date range + percent change metrics are correct at first. But when i change the dates on my panel, while i see custom date range metric updating accurately, percent change column always goes to 0%. So the custom date range metric will update dynamically but the % change metric will not.  Why is this feature important to you - This to me seems like a defect and can be confusing for other Adobe users who expect that to change. i had to remove % change column from my dashboard altogether to avoid confusion because changing dates in the dashboard is a common use case for this dashboard.  

Description - The current limit of 250 eVars and 75 props restricts how many custom dimensions can be tracked and analyzed, making it difficult for organizations with complex customer journeys to capture all the necessary data. This limitation hinders the ability to fully customize data collection and tracking for large-scale implementations. I propose removing these caps on custom dimensions and enabling unlimited eVars and props, similar to what is currently offered in Customer Journey Analytics. CJA provides unlimited custom dimensions by leveraging the Adobe Experience Platform’s Experience Data Model (XDM), which allows for flexible, scalable, and cross-channel data tracking without any variable limitations. Why is this feature important to you -  This feature is crucial for us because the current limits on eVars and props in Adobe Analytics restrict our ability to capture the full complexity of our customer journeys across multiple channels. As a business

We would like to show the clicks data by region in Adobe Activity Map extension but it is not supported.I believe this feature would provide visual layout for users who may not be data person. This would be a user friendly for them. This would benefit many users who have similar needs. For me, I am a data person. I can pull it from workspace.  

Description - I have simply reached critical mass on this one, and I really can't believe no one else has cried uncle yet.  So, I will do it.  Here is an #AdobePainPoint.Entering a Visualization Title when the component is small: I mean seriously ADOBE!!  Why should I have to resize the entire visualization just to enter a title??  Would it not be easier for you make it easier for the dialogue to resize for us so it is readable while we enter text? Why is this feature important to you - As opposed to typing my titles elsewhere, then copying and pasting them in, OR, resizing my visualization just to view the title so I can type in my title.  The first requires forethought to either set up titles in a different document.  The second often causes the Workspace to recalculate when I change the size and shape of visualizations and move things around. How would you like the feature to work - When I place my cursor in the Title Bar of a visualization,

DescriptionThe ability to use tags assigned to segments to bring all related segments in a workspace visualizationWhy is this feature important to youWe frequently have to create segments that are just OR groups of other segments, especially for cross-market (eg EMEA region or APAC region) or cross-product (eg Category A or Section X) analysis. This is time-consuming and imperfect since we have to update the grouped segments.How would you like the feature to workWe already have the option to add tags to segments. Ideally, these tags should translate to an OR segment grouping in Workspace so we can quickly pick all relevant segments for a report. For example, I could tag all relevant regional segments as EMEA and then be able to report on individual regions as well as the cumulative view by simply dragging the "EMEA" tag in the report. I could also group segments that are used frequently as panel filters by tag, for example by tagging all segments for excluding internal visitors or pote