Adobe Analytics

Currently Conditional Formatting in Analysis Workspace evaluates the values within a single column. Please add a feature that would allow to switch the logic to the entire freeform table so that the cell colour would reflect the value against all other cells in the viewable area of the table (within the page).

I build segments a lot and would like the feature to filter the comparison operator by typing. It's a small change that would speed up building segments that small amount! For example, if I wanted to apply the "equals" comparison operator, it would be great if I were to begin to type "equals" and only have options containing equals appear. This would save time by not having to scroll and look for it!

When scheduling weekly reports in Data Warehouse it asks "Day of Week" which since Monday to Sunday is all day of week, and doesn't tell you anything, could this be changed to "Week Begins" so it makes sense.

Giving an option to add user comments during add/edit > new/current > eVar/prop/events will help a lot to manage variable change log in Adobe at the report suite level. This can be used to annotate "change reason" in reports.Thanks,Asheesh

Would love to see an improved variable change log incorporated within the Report Suites area of Admin Console (Conversion Variables, Success Events, Processing Rule, Traffic Variables, etc).   I could see this as an additional expanded menu that shows changes for that specific variable and the date.  This would help with quickly debugging issues and keeping a record of changing that can have a large impact on your data.  The Admin Tools Log is not exactly what I want to be sifting through when I am double checking a change seen in a particlar variable and need to get a better understanding of potential changes on this variable's settings. 

Telecom Customer would like to update a number of Adobe Reports and Analytics segments at one time. Example: Identify segments that use a specific prop like prop 22 and replace it with prop 25. But the segments would not have the same definition.Currently searching for segments and editing one by one is not ideal and very time consuming.

I think it would be super-cool if users could use SHIFT or CTRL to select rows in Analysis Workspace and temporarily see them grouped together and with metrics for the grouped rows summed. Today, you have to leave what you are doing and either build a segment or create a SAINT Classification. This stops the flow of doing analysis.For example, let's say that I am looking at a Freeform Table with Day of Year as the dimension. What if I wanted to group the first 7 rows and see the data aggregated. It would be great if I could select the rows and then right-click to open a new table that has those rows summed.As another example, what if I were looking at a set of blog posts (or pages) and I randomly wanted to search for the ones that include the word "campaign" (shown below) and see all of that aggregated into one row:In the future, it would be cool if these ad-hoc (no pun intended!) selections could be saved, shared and turned into segments...Better yet would be a way to create these aggr

Once a custom event is enabled/created in the report suite, it'd be nice to have a corresponding custom event processing rule automatically created within the processing rules.

REQUIREMENT:Report the personalized pages where the Target activities are running.SITECATALYST REPORT:To pull the list of Personalized pages, we used the following conditionsDimension - “Page URL CC - v38”Segment 1 – “Target Activities exists” to exclude non-personalized pagesSegment 2 -   Excluded the activities “PROD_0701_NAPR_US_TCMS_ARSW_MUL_XT_HOME” and “PROD  || POC -  LPV profile script - OMNI-825” in the segment by using “exclude container”. Those 2 activities are not related to PZN campaigns.Report Link : https://sc5.omniture.com/x/5_7pnd6Issue Noted: Non-Personalized pages are listed in the reporting line items. E.g.https://blogs.vmware.com/euc/2018/10/infographic-android-enterprise.html & https://www.vmware.com/site_maintenance.htmlREQUESTED ADOBE CLIENT CARE SUPPORTAdobe Incident 1: 181015-000031As per Incident: 181015-000031, due to hash collision the non-personalized pages are appearing in v38 report. Solution proposed by client care is increasing the unique values o

When setting targets on a bullet graph in workspace, it would be really helpful to have a callout pop up like on line graphs to show the values. Although the data is there in the tables, it can be a bit arduous to have to open up the tables to see the actuals vs the target. Since there's no way to see the target value vs the actual, we can't build a chart summary difference from them or anything.

After enabling Activity Map configuration for a report suites, uses should be able to disable it as well. Or at least a warning message should be added to show up when enabling it stating "You would not be able to disable it once enabled".Use case for this which we saw recently was that when users identify that there are PII present in the links which are automatically being tracked by Activity Map, they want to get it disabled, but aren't able to.Obviously there is a solution by removing the Activity Map code from the pages, but that is not an immediate solution for many and can be delayed due to deployment cycles.

Issue: An analytics user needs to be an Adobe Analytics Product Admin in Adobe Admin console in order to map variables in Adobe Mobile Services. We have multiple analysts and developers who want to do the mapping but I don't want to make every an Adobe Analytics Admin giving them full range over our entire analytics platform. The permission group "Mobile App Admin" should be enough except it doesn't include being able to edit mappings. Makes no sense.What I've tested:I've concluded that even though I give someone access to every available permission in our Adobe Analytics profile, that user still cannot map eVars, Props, or events in Adobe Mobile services without being an Adobe Analytics product admin. There is a default Adobe product profile called "Mobile App Admin" which still only gives a user read only access. I need developers and analysts able to map variables that they have setup in Adobe Analytics report suites without having to give them admin access to the entire product sku

We have a few websites that generally used the same classification rules and tracking code template but there we a few differences. After a few years, it was decided to bring these together to use the same tracking code template. This meant aligning classifications and classification rules.The issue was that you can not align classification for two or more report suites by name, because they have a hidden ID in the background. this meant that when if I was on report suite 1 looking at the Channels report and then changed to report suite 2, it would no show me the same Channel report (due to the classification IDs being different).It would be good if it was possible to update these IDs to make sure they match, thus making reporting across report suites easier. Considering you can create classification rules based on the classification name not ID, why is it not possible to align them?Thanks.

I recommend you to improve the current Real Time report.There are many bugs we need to overtake because currently realt time is not reliable most of the time.Basically we are talking about a few small changes, but they can make the difference.Example:"Today" column does not include the data tracked in the current time-frame. That means we usually have Now=1 and Today=0% with the comp YOY and WOW sometime is not accuratethe trend we have in the main chart refers to the first dimension only! while users expect to have the trend of the metric that sovereigns the reportplease add the possibility to switch between "count every instance / count only unique instances"Jarno Rossi

Enable voice commands to access Adobe Analytics data. This could be used with Siri, Alexa, or other voice activated devices. Removes emails, texts, etc sent to analysts to get very simple questions. Empower leadership and executuve or any non-analyst to get simple answers. Vocie can reply for which report suite or web property. 

We run an ETL process with a scheduled Data Warehouse report as input.  When the format of this report changes between CSV and ZIP from one month to the next, it breaks our ETL process.  I would like to see an option to choose the format of the Data Warehouse report so that it is consistent every time it runs.

It would be incredibly helpful to add a few columns to the Request Manager display.  I would most like to see Report Suite ID or Name.  And Date Range would also be very helpful.

Column heading in Workspace should be freezed once user clicks on it so that it becomes easier to click on 'I' and 'settings' icon. Right now, sometimes its so difficult to click on these icons if there are multiple columns and due to which full column items are not visible.For example, in below case its very difficult to click on 'settings' and 'I' icon, however slow I hover on the column.

Current analytics intelligent alerts are much better than legacy alerts. These are some thoughts to enhanced Intelligent Alerts in 2019.1. Ability to exclude/filter alerts on weekends vs weekdays. (Much awaited request since a long time) @ursboller has great workaround ideas here https://forums.adobe.com/thread/2598789. 2. Ability to add custom text alerts on certain future dates. Campaign start/end Dates. 3. Ability to add an alert on evar/prop value anomaly.  eg. "standard" login evar value anomaly vs login event anomaly.4. Ability to add an alert when a report is ready to pull in another system.Please add more thought in comments.

The additions of maps to Analysis Workspace has been a nice evolution, but most US businesses will find that the volume of activity is highly correlated to population size.  It would be really valuable to have population context available by default within Adobe analytics so that users may quickly analyze which regions over or under index on performance in relation to population.  This would make the map tool and geographic dimensions significantly more valuable.

We would like to see the actual click-through rates for page links when using Activity Map, not a value rounded to the nearest whole number.  Please allow users to turn off the rounding and get the actual value. If not, you must eliminate the 2 digits after the decimal! Those digits imply a precision in the number that is not there. And it is very distracting having all those zeroes cluttering up the screen when they add no value whatsoever.

I would like the Workspace to include the line breaks we have made in our descriptions on the variables (evar, prop and events)In Admin i can make a description like this:I make the line break for a reason. It makes it easier to read.But in Workspace it look like this.

is there any way to cleanup the template list for data feeds ? i dont need any of them. would be nice to modify and be able to manage data feed templates.

It's a shame Adobe is deprecating adhoc, as an analyst, this is my favorite tool. It's clear Adobe did not survey any analysts when making this decision, and simply looked at the number of end users who had access to analytics (a majority of the employees had access, while all reports were generated by ~3 people, so of course it looks like barely anyone is using the tool). Workspace does not have the same abilities, speed, reporting capabilites, or visualizations that adhoc has. One of the reports with the biggest difference from adhoc to workspace is the flow reports. In Adhoc, end users can click on the different line items if they wish to break down the next user flow, while the flow grows, the visualization is made smaller and can be easily moved around. Workspace is missing those capabilities, it takes over the entire screen, long titles are cut off with ellipsis so it's impossible to see what they are, users can not click through or move the image around, and exporting it is not

I'd like to have a button from the filter modal that would let me easily create a segment from the filter I have setup.