Adobe Analytics

Change the value "Others" to "Desktop" for the "Mobile Device Type" dimension.

We are currently weighing whether to enable the IAB bot filtering functionality in Analytics (this is a communication challenge internally - as a B2B media company, we often quote traffic numbers in sales materials, and these numbers will obviously be impacted). Some of the primary downsides of enabling IAB filtering functionality include: no solid estimate of how enabling filter will impact traffic numbersloss of the ability to accurately measure year-over-year growthIf a segment were available in Analytics that allowed us to either exclude or isolate bots, we'd be able to address both of the above concerns. The segment would obviously need to be regularly updated to keep up to date with the IAB list.

In Adobe Analysis Workspace we found a little nuisance with the description of one of the default Date Ranges (Last Week) - it says "By default, this refers to the time period that starts on Sunday and ends on Saturday prior to the current week.", but our users don't know that our defaults are set differently in Europe (week starts on Monday). Can Adobe please update this description to something like "This is set accordingly to the respective Report Suite configuration" (in Report Suite Manager > General > Calendar Settings)?

We need a better way to auto sort 'bucketed' values in CJA.Current Method: Value bucketing is a great feature, but the current sort method uses either alphabetical sorting or population based sorting. Neither of them are useful. Current Workaround: To get values in the right order I either need to make manual segments and drop them in a particular order OR use table builder to pre-determine the order. This is a tedious process, and there is a risk of everything resetting should I choose to change the bucket values. Feature Request: We need a more intelligent way to sort dimension values - for example, ordering in descending order should put values in following order...less than 2525 to 5050 to 75so on...  Supporting images: 

Dear Adobe Team,I hope this message finds you well. I would like to propose an enhancement for Adobe Acrobat Reader that I believe would significantly improve user experience and efficiency.Currently, when users open a PDF document, they need to reselect their frequently used tools each time. This can be time-consuming and disrupts the workflow, especially for users who rely on specific tools for their tasks.I suggest implementing a feature that retains the recently used tools when a user reopens a PDF. This would allow users to quickly access their&nbsp

Description - Working on monthly scorecards, I need a date range that can always update itself to the report date range, but in the prior year. Would be even better if there was a day-of-week adjusted version, but I would take a "this month last year". This seems very basic for what Workspace should offer. Just a "this date range minus 365" would get me there. Why is this feature important to you - Creating comparison date ranges that can't update themselves and/or have labels that don't make sense to my internal customers means that we are going to have to create the reporting in PowerBI or Excel. How would you like the feature to work - If my panel date is for the month of February 2025, "this month last year" would show February 2024. Current Behaviour - I can create a static date range for this comparison, but it will not update when it's time to update this monthly scorecard for the next month.

The naming and format of the CJA ootb metrics time spent (seconds), time spent per session, time spent per person is very confusing for the user. Time spent (seconds) -> the name of the metrics highlights that the format is in seconds -> actual format HH:MM:SS -> confusingtime spent per session, time spent per person -> name doesn´t say anything about the format -> actual format is seconds -> not very user friendly, if it´s more than 60 seconds -> user needs to calculate in HH:MM:SS My expectations: easy to understand names of the metrics, user-friendly format 

Description - I have been manually monitoring the amount of rows ingested into CJA and using rolling windows to keep the consumption within licensed range. Why is this feature important to you - to prevent the company from being overcharged for overusage. In addition, this forces us to keep only the most relevant data in CJA. How would you like the feature to work - in the current License Usage section, just update the number on a daily basis. Current Behaviour - CJA license usage is updated on a monthly basis.

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