Adobe Analytics

Description - When creating a new report suite by copying an existing one, certain settings are not carried over. Currently, users must manually review and compare each setting between the original and copied report suite, which is a tedious and time-consuming process. Why is this feature important to you -Many clients frequently create copies of original report suites to track regional or country-specific site traffic. Manually verifying each setting is inefficient and requires significant effort, leading to delays and potential inconsistencies. How would you like the feature to work -An interface should be available to compare the settings of two report suites side by side. This would minimize manual effort, streamline the process, and provide a clear view of which settings are not copied over during duplication. Current Behaviour -There is no existing interface to facilitate report suite settings comparison.

Analysis workspace does a great job showing you the value of a bar or a line data point when you hover over them.  However when you export the project to a PDF, that information gets lost to the scale on the side of the graph.it would be great if we could display the data points on top of the bars or next to the link data points.  having the option to display all data points or just the min/max so the user's don't have to hover them and so they get printed to the PDF would be enourmously helpful as we (analyst) tend to share information via email and slack in a more informal situations.these labels should change based on the scale so if I want to display % vs numbers, I just need to change the scale of my graph and the data labels will update automatically

Hi there,An idea that would be really useful for us is metric filters/criteria in workspace.At the moment if you drop an Evar on a free form table you can filter based on values.What I would love to see is the ability to do this on metrics (greater than / less than) as currently we have to do these reports in report builder / excel.An (very crude) example of what I am after is below.ThanksDave

I would like to be able to have two items on the left axis because their scale is similar and have rate on the right axis because its scale is different. 

Hello fellow Adobe-pros,Another feature request to make all our lives a lot easier: Please, bring Full Path reports from Reports & Analytics to Analysis Workspace. That report is super helpful to understand how users move through a page in general and from a given point:What I would like to have is quite simple: A full path dimension for every dimension in Workspace! That dimension would hold the paths through that dimension for a given session with values like "Entry -> Homepage -> Product Page -> Exit". Ideally, this value would be calculated when the report runs, so that segments are also respected. For example, if I would exclude all Hits on the homepage, the dimension would then show "Entry -> Product Page -> Exit". Ideally, we would also have the option to search this dimension in a clever way, like with the old PathFinder report: With a report like this, it would be super easy to train our business users to do in-depth pathing analysis on their own. As th

As much as I love being able to hyperlink dimensions in a freeform table, this is only limited to either: Having a URL-based dimension so you can allow Adobe Analytics to create hyperlinks for all rows or Manually enter the URL for each row (There is an option to create a dynamic URL string, but that requires the dimension having direct ties to the URL.)   It would be nice to designate a URL dimension (for example, evar1 Page URL) as the destination link for the corresponding non-URL dimension currently chosen in the freeform table (for example, evar2 Page Title). This would be helpful if users are looking at Page Title or Video Names and want to know more about the page content that may influence the KPIs they are seeing.

Description - Currently you can apply. date range to all panels.  However, you cannot apply your drop-downs and segment filters to all panels.  Additionally, if you want to rearrange your filters (ex: move one to the front to keel things in order, you have to delete items in from of them and reapply them again.   Why is this feature important to you -Ease of use How would you like the feature to work -Allow a "apply to all" button to apply all filters and drop-downs on a specific panel to ALL panels in a Workspace project.  Allow a user to reorganize the positioning of filters and drop-downs within a panel without first having to remove filters/drop-downs.  Current Behavior - You have to remove filters/drop-downs to move filters from the end to the beginning.  

Description -Currently you can place annotations on line displays to provide an understanding when events have happened in time.  However, for other trend views like Area and combo, you cannot apply annotations.  It would be great to be able to do so.   Why is this feature important to you -It makes annotating events easier to adopt across multiple views.  It doesn't force the analyst to use only one display method.   How would you like the feature to work - Allow annotation for area, bar, and combo displays.   Current Behavior  - only line charts allow for annotations.  

Description -Currently, you can only use dimension items in the flow display.  This limits visibility into pathing in and out of a "group" (example: if you had a URL dimension, you may want to see pathing into all URL's that contain /products/ instead of just /products/widget-a/ ) Allowing users to use segments in addition to dimension items would allow the user to have visibility into an overarching pattern of behavior into like items.   Why is this feature important to you -There have been many frequent cases where this would be useful in my personal analysis.  As a web analyst, I want to see flow displays in and out of a hit-based segment to see the bigger picture for journeys in and out of all similar pages all at once.   How would you like the feature to work -Using the segment as the start, the middle or end of the flow display would work.  But not with multiple segments.  Pathing in and out of the segment would be

Customer Journey Analytics recently got a new visualization called "Journey Canvas", which lets us define user journey through dragging and dropping elements onto a canvas. It nicely fits between the exploratory Flow viz and the more rigid Fallout viz and is great to visualize, well, journeys: However, if we right-click any node and choose the "Create Segment Filter from node" option, we see that there is no magic smoke inside of this new visualization. This impressive viz falls in the category which I like to call "Segment Builders", as all that it's doing is creating complex sequential Segments Filters on the fly, then display the result in a nice way. It's practically just a couple Freeform tables in a trench coat: This doesn't make the Journey Canvas viz any less impressive but clearly highlights one important detail: There is no technical reason why this shouldn't be in Adobe Analytics. We have built Segments like the one on the screenshot above for years in AA, especially with

Description - For users on organic search (i.e. Google) and land on a result such as 'Morgan Stanley PDF' this link takes them directly to the PDF instead of going to the Morgan Stanley website first. This means we are losing millions of visitor analytics data.Why is this feature important to you - The current workaround of embed API is a timely workaround we are exploring. It is important to have this feature as a toggle option within Adobe Data Collection similar to 'download links'. It is important because we have many users going through this flow for many PDFs and it's over 1 million hits we are missing attribution. Given they are both Adobe products, we expected a seamless integration with analytics.How would you like the feature to work - By default Adobe Analytics captures analytics from users that click on MS PDF that links directly to PDF from google search. This can be toggled on in similar way to  'download links' check box in Adobe Launch.Current Behaviour - Currently

If you go the Filters or Calculated metrics managerhttps://experience.adobe.com/#/@intelcorp/platform/analytics/#/components/filters/managerhttps://experience.adobe.com/#/@intelcorp/platform/analytics/#/components/calculatedMetrics/managerThe "used in" function was release in 2024 but is only available for Adminshttps://experienceleague.adobe.com/en/docs/analytics-platform/using/releases/2024#sep24  It works great and I used it to clean up my unused assets but I can't do that for users. Please  make this function available to all users.

Description - Making A4T compatible with the Cross Device Report Suite (not currently using CJA)Why is this feature important to you? Understanding how cross-device behavior influences the results of our digital experiments.  We have a very integrated customer journey across Mobile Apps, Desktop Web, and Mobile Web.  It would be beneficial to understand conversions across devices to tie back to whichever Recipe of the test they are allocated to.How would you like the feature to work - Simlar to the way Analysis Workspace + A4T works todayCurrent Behaviour - Known limitation -- "CDA is not currently compatible with A4T"https://experienceleague.adobe.com/en/docs/analytics/components/cda/overview 

It's often very important when undertaking analysis to be able to understand when a value is set rather than propagated forward.With eVars this is possible using the corresponding "instance" metric for the eVar.With List Vars I cannot see any way of differentiating between values carried forward and those values actually set within the hit.Please can you consider introducing a way to differentiate between List Var values that have been 'set' rather than just carried forward?[note: I think this is similar to the issue often faced with products variable where segmenting a specific product at a the hit level returns all products captured in the hit  i.e. it is currently impossible to isolate something at a 'sub-hit' level]

Description: I would love to have a dashboard where you can both select the date range (as it is currently) and have a second date range picker for a "compare date range". this way, user can easely compare any date ranges they want just by select one of the date ranges.   Why is this feature important to you: almost in every dashboard the people would love to have more than just 1 date comparison, sometimes there are 4-6 different comparisons. currently we need to pre-build every different comparison in advance, wich is both a lot of work and makes the dashboard more complex   How would you like the feature to work: I would love to have an additional date range picker at the top of the panel. the second date range picker would be for the "compare date range". each "date range" can be relative either to the main date range (default) or to the "compare date range" (as a flag). or there are completely new date ranges just for comparison. however, the workspace would lo

Currently, setting up connections to third party data sources is the most time consuming, difficult, and costly aspect of a CJA implementation. Having a native connector that allows for easy setup of connections to Salesforce and other common third party applications would bring down costs, reduce the time needed, and generally make the transition to CJA more attractive.

Description:Enhance the Adobe Analytics API 2.0 to include the start date and end date fields as part of the API response payload. Currently, these fields are only present in the request body.Why is this feature important to you?Data Context and Completeness:Including the date range directly in the API response provides essential context for the data being retrieved.It ensures that the data is self-contained and complete, eliminating the need to cross-reference with the original request.Simplified Data Processing:Currently, users must extract the date range from the request body and manually add it to the processed data.This enhancement would automate this process, simplifying data processing and reducing the risk of errors.Improved Data Integration:When integrating Adobe Analytics data with other systems, having the date range readily available in the response facilitates seamless data integration.It eliminates the need for external data mapping and lookups.Increased Efficiency:By inc

Description:Enhance the Adobe Analytics API 2.0 to include the itemId value from the parent request in subsequent multi-level breakdown responses. This will facilitate seamless data joining across API responses.Why is this feature important to you?Simplified Data Integration:Currently, multi-level breakdowns require external data management to link parent and child response data due to the absence of the parent itemId in child responses.This feature would enable direct and efficient data joining, reducing complexity and potential errors.Improved Data Analysis Efficiency:Many analytical use cases rely on combining data from multiple API responses.The proposed enhancement would streamline this process, enabling faster and more accurate data analysis.Enhanced API Usability:The lack of itemId persistence makes multi-level breakdowns cumbersome.This feature would make the API more intuitive and user-friendly.How would you like the feature to work?itemId Inclusion in Child Responses:When a b

Description:Enhance the Adobe Analytics API 2.0 response structure to include actual metric names as column headers or labels instead of, or in addition to, numerical indices (0, 1, 2, 3, etc.) when requesting single or multi-level breakdowns. This will improve readability, usability, and automation capabilities.Why is this feature important to you?Readability and Usability: Currently, the numerical column names make it difficult to quickly understand the data without referencing the original request or external documentation. This adds unnecessary complexity and slows down analysis.Automation and Efficiency: Automating data processing and analysis is hindered by the need to map numerical indices to metric names. This requires additional logic and increases development time.Debugging and Maintainability: Debugging becomes more challenging as it's not immediately clear which metric corresponds to which column index. Code relying on these numerical indices is less maintainable and prone

A tool that can go into reports, calculated metrics and segments/filters that can programmatically find and replace old or deprecated assets with new ones. Why is this feature important to you - This would make asset management much easier for admins to update assets as new ways of reporting and data collection comes out.  How would you like the feature to work - A page in the tools dropdown where an admin can look for a dimension or metric, locate and replace  some or all instances of it with another dimension or metric. Very similar to how a find and replace works in Microsoft office. Current Behavior - No tool exists, a user would need to replace these manually after finding all instances of it.

Description - Long values, particularly when paired with multiple metric columns, get truncated visually with an ellipses. While this is okay in a live Workspace report where the user can hover over the row to see the full value, when in a rendered PDF the values are completely lost, leaving stakeholders with missing information.   It would be of great value to allow long values to wrap (similar to how there is an option to wrap headers).     Why is this feature important to you -   Data will be easier to see, with less information being lost when presented to Stakeholders. Having the wrapping be optional allows for people to control when and if they want their data to wrap or to truncate.       How would you like the feature to work -   Add an option to the settings on the dimension to allow the values to wrap, or not to wrap.    Current Behaviour -   No option to wrap, and PDF generation doesn't allow for hover states to see the

Description - One of the great things about Adobe Analytics is the rich set of components that come out-of-the-box, like Bounce Rate, First Time Visits, Mobile Traffic, etc. Today, Customer Journey Analytics doesn't have that but, IMHO, can and should. Why is this feature important to you - So customers don't have a "huh, feels empty around here" experience when starting with CJA and novice users have something to start with. How would you like the feature to work - Based on the Adobe-provided XDM Schema Field Groups used in a Dataset for CJA, creating a Data View should have the option to add Adobe-provided Components, like Calculated Metrics or Segments, that fit the underlying Field Groups. For example, using the Web SDK Field Group should come with a Bounce Rate Metric, Mobile Traffic Segment, etc. Current Behaviour - 👁️👃👁️      👄

Description -In the Omniture Legacy UI, there is an option to expire a user after a set amount of days (see screenshot). It would be helpful to be able to utilize the same functionality within the Admin Console, specifically Adobe Analytics, to ensure that external users are expired after a certain number of days (ideally 6 months), but ONLY if they haven't had any activity in the last 6 months. Why is this feature important to you -By having to expire every external user after 6 months, we are facing many users being locked out every 6 months, requiring our User Admins to unlock them, as well as not allowing them within the tools in the interim. If we changed the solution to only expire the inactive users, we would prevent time lost and would properly expire only those who required it. How would you like the feature to work - Have an editable expiry date for users within Admin Console who haven't had activity in the tool in x number if days Current Behaviour - no way to

Description - This is something I continue to be frustrated by when I have to break out data in Workspace.  I created Classifications so I could break out my data, but it's a highly time-consuming challenge to constantly break out the data to make it consumable on a larger scale.  Instead of a limited set of results, I am requesting for Adobe to simply blow out the full breakdown for a specific table that we build in a Workspace.For instance, if I have THREE fields from a Campaign Tracking code I would want to break down, it would be a lot easier to drag them into the Table Builder and hit BUILD than to individually drag my fields into the Freeform table, even if I have multiples highlighted to enable a certain level of mass updates. Why is this feature important to you - This is about saving a LOT of time and tedium. How would you like the feature to work - Drag the necessary fields into the Freeform Table, and instead of being limited to 5 items in my breakdown, it wou

Description - We have a business use case where users need to export CJA Reports to DLZ. Currently, the exported file names appear as follows: cja-export-CDE-9a9DDD-e6bd-456b-a1e6-f99b9fb1d622-173111111537-0.csv.gz. With this naming convention, it's challenging to identify which user exported a specific CJA report when multiple users are exporting files to DLZ.Why is this feature important to you - If multiple users are exporting the files its hard to understand who exported the file and what type of export it is.How would you like the feature to work - What we need:1. Is there a way to prefix the report with the  (user ID) and a timestamp during export2. As soon as a scheduled (or manually) report is exported, an alert email should be sent to the end user, indicating that the report CNID_DATESTAMP_REPORTNAME... has been exported to DLZ. Current Behaviour -  file export to DLZ just shows this:  cja-export-CDE-9a9DDD-e6bd-456b-a1e6-f99b9fb1d622-1731111