Adobe Analytics

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

We currently use the metric "Adobe Advertising - CPC" and "Adobe Advertising - Costs" in our reports with a key metric summary visualisation. The problem is, the color highlighting Costs/CPC decreases = red or Costs/CPC increases = green is not correct in this case and make visual analysis more difficult. If Costs/CPC decreases, the colour in the visualisation should be green and if it increases, it should be red. Would be very nice if this could be configured in some way or at least corrected for these metrics.

Description - In CJA, persistence setting should always be shown, even when not set ("none" or something similar) Why is this feature important to you - We teach users to use the information available for components.  It's confusing to them when there's nothing shown for persistence . How would you like the feature to work - When set, show value (as it currently does).  When not set, show "none" or something similar. Current Behaviour - Nothing is displayed for persistence as shown here  

Description - I want to filter out all the rules and Data elements which I have worked on, so that it is easy to publish those changes(only my changes) or may be add " add all changes done by me" section while building library. Why is this feature important to you - Lot of developers and different teams work simultaneously and building library is tideous as I need to pick rule by rule before adding it to libraryHow would you like the feature to work - Should be able to add filter option on top ( filter by developer, build stage( dev,stage,prod), etc)Current Behaviour - No such filter. There is only way to sort it.

On our website and in our apps, we have a lot more traffic on Weekdays than on Weekend days.For some flows/pages we have data alerts.  But defining the level on which we want to be alerted is very difficult.If the level is too low, we won't be alerted if there is an issue on weekdays; if the level is too high, we'll get (unwanted) alerts on Weekend days. In the As Is situation you can (theoretically) add "Weekdays" in the definition on the alert.Eg. I had created an alert for specific pages: if the # of pageViews was 0 on Weekdays (only on Weekdays), I wanted to receive an alert.On Weekdays the alert works fine.  But for each Saturday and Sunday I received an alert saying that the # of pageViews was 0, although this was NOT the case.  It was very confusing. We had plans to create a lot more alerts, a very nice feature of AA, but because of the impossibility to  differentiate the levels to test on between Weekdays and Weekend days, this feature looses a lot

Description - Our Firm has not been able to use Activity Maps since it was re-engineered to v3 due to our security policy that forces us to modify the extensions guid as software is not permitted to update outside of the Firm. Why is this feature important to you - Adobe Extension is a great tool that makes analytics more accessible to users.  The work around limits its use for some users. How would you like the feature to work - We would like Adobe to allow custom guid so that our users can authenticate using the extension. Current Behaviour -  Authentication is blocked by Adobe as it does not recognize our GUID. 

We would like to understand what combination of events equal to what user actions via CJA Audit logs.The CJA Audit logs help doc https://experienceleague.adobe.com/en/docs/analytics-platform/using/cja-privacy/audit-log gives insights on very general things but we want to be able to get more specific information.For example: Project Created: Name = #### will that only show up once per project creation? Project Viewed will show up multiple times for a single view of a project(tested) or on a future date after the actual view. This makes it a bit challenging to extract precise usage insights.What are API_REQUEST? Why is there no User Name against some Action Name in the Audit logs? Description would show: Project Viewed: Project Objects - What are Project Objects?

Description - I found community threads from 10 years back(?!) where people asking about lowercasing prop/evar values in processing rules. Till date, this still does not seem to be possible, correct? Why is this feature important to you - Why would I use processing rules if even this simple functionality does not exist? How would you like the feature to work - have an option to lowercase as string value as one of the given dropdown items Current Behaviour - still no can do in 2024