Adobe Analytics

Just a reminder to everyone, a LIKE means a VOTE for this idea.It always confuses me when I see tons of views for ideas, but hardly any "likes." Description - How many times have any of you spent creating a Workspace in Adobe Analytics, only to have any number of Visualizations that you would now like to format similar to one you have recently updated?  What do you do?  Do you delete the old ones, and copy the new one so you may then tie them to the data table?  Or, do you simply proceed to each and use that new visualization as your guide to update the others?Why is this feature important to you - This would be a productivity UPLIFT.  There are plenty of times when I'm adjusting components in a workspace that I would love to simply apply changes I just made to related items. How would you like the feature to work - For this specific feature, I would simply like to go to the Visualization I like, right-click on it, select "Copy Visualization," select the V

Description - in the current Analytics extension's set variables action, one can only add known events, and those only one by one. It would be amazing if one could just have a data element that can be passed in here, that holds a comma-separated events list e.g., coming from a lookup table  Why is this feature important to you - the current UI is great if everything is static, but sometimes it would save a lot of time/rules if could just have a single data element that holds the logic, and the extension takes care of the rest i.e., add the values contained in the list in the linkTrackEvents, the same way it does for the individually set events How would you like the feature to work - add an input field for the list. The field can be populated with the standard percent placeholder for Data Elements (database symbol) Current Behaviour - one by one events to be added   

In Adobe reports you are able to run previous page and next page reports which is very handy. In Workspace you are able to see similar data using the flow analysis. An improvement on both of these, IMO, would be to have a 'Previous Page' and 'Next Page' dimensions that you could drag and drop on visualizations all within Analysis Workspace.

Description - Allow analysts to apply a "Configurable Object" to multiple panels in a workspace report (such as Quick Insights, next/previous etc) that will allow a report to become a template that other stakeholders can easily use on the fly.   This will allow users to just define their page or dimensional item of interest one time and that would then change all panels that are using this "configurable object".   Why is this feature important to you - speed and adoption of reporting templates.  Ease of use for newer users.  How would you like the feature to work - Allow analysts to apply a "Configurable Object" to multiple panels in a workspace report (such as Quick Insights, next/previous etc) that will allow a report to become a template that other stakeholders can easily use on the fly.   This will allow users to just define their page or dimensional item of interest one time and that would then change all p

It would be useful to be able to create calculated metrics in the data warehouse, or at least to be able to use in the data warehouse the calculated metrics you built in the analysis workspace. For instance this feature would, among other things, allow you to customize the attribution model by which the metrics that you use in your reports are calculated. As long as this feature isn't implemented you are stuck using the "last touch" attribution model.  

Description - Two separate asks here. One is that currently when a prop is turned on within report suites, it will permanently reside in the default view, this is not true to Events and eVars. The props being stuck permanently on is causing confusion as we only intent on looking at the enabled eVars and any missclick to "add new" will muddy the report suite. Second request is to have a description field visible on eVars from within report suites (same as it is for events). It would be helpful to be able to view a quick description of the eVars as we can for events and would save time maintaining an SDRWhy is this feature important to you - Will clean up our data and save timeHow would you like the feature to work - prop=disabled, then remove from report suite default view, Description field added for eVars page (same as events)Current Behavior - prop=disabled, prop permanently stays on default view, this is true for as many props as you enable

Currently in Workspace, we have Date Ranges like "This Month", "Last Month", "Last 7 days", etc. But these date ranges are relative to your current date.What I would like are date ranges that are relative to my project's date range.Example 1:Today is 15 August 2017.I run a report for 1-31 July 2017.The "Previous Month" date range would show the data for 1-30 June 2017, i.e. the month previous to 1-31 July 2017.Example 2:Today is 15 August 2017.I run a report for 1-31 January 2017.The "Previous Month" date range would show the data for 1-31 December 2016, i.e. the month previous to 1-31 January 2017.And similarly for "Next Month".And similarly for other time periods, e.g. day, week, month, quarter, year.

It would be useful to be able to export reports from the Analysis workspace into AWS S3 or some other storage service, since the only option, as of today, is to export via email.Although you can use the data warehouse tool to export data into an S3 bucket, the analysis workspace offers some features that are unavailable in the data warehouse, like the use of calculated metrics.  

While performing our regular application review, we observed this application allows Maker to add/delete users. Although we process the orders with attentively, but we also want to implement control check point in the application/process to confirm accuracy. Reason being that there can be instances of human error while provisioning the ID. To address this concern, we suggest implementing a Validation (Checker) step within the application, allowing an analyst to review and approve any addition or modifications performed by the maker.

Description -Why is this feature important to you - We need to implement Web SDK Analytics for over 1000 sites How would you like the feature to work - We want that we can create one global launch property with certain set of rules and then call these rules in another launch property for dedicated websites. So that if we make changes in the global launch property, it automatically gets reflected in other launch properties as wellCurrent Behaviour - Currently, we need to copy rules from one launch property to other and if there is some change in the global template property , we need to make changes for all the properties again

Description - In current scenario whenever an asset (segment/calculated) metric is updated/modified, the prior definition cannot be accessed.The version control feature in  (segment/calculatedMetric) would allow users to keep track of how this asset evolved over a period of time and also roll-back to last aligned / approved state whenever required. Why is this feature important to you - We have multiple assets that are maintained and are used for downstream reporting / use-cases (For example: Tableau dashboards / Bigquery tables etc). In case of data mismatch between AA and Tableau the primary reason always have been underlying AA asset was modified. The biggest challenge is to retrieve prior definition which was aligned for downstream system reporting. How would you like the feature to work -- Specific Tags that can be applied to (segment/calculatedMetric) assets, and these tags ensure any changes made to assets need to be approved by owner/system-admin/produc

In the new Adobe app SDK - mobile lifecycle events (such as install/crash/upgrade) are only available in Adobe Analytics - and are not exportable via Data Feeds - refer attached image for example metrics I am referring to  We expect that we can export lifecycle events in a similar manner as - so that we can import this data into our own data lake and BI platform for our own analysis In the previous (n w legacy mobile app sdk) this data was available in the Adobe Analytics Data Feed I see this as a feature regression and request that this feature be enabled/developed for the current app SDK Thanks Justin Kelly

Description - Add functionality to update VRS owner through API. When the identity of an Analytics asset owner is removed from the system (and someone new is added) the need for updating the old owner on Analytics assets is araising. Currently it is possible to change owner through the API on all other Analytics assets, but not VRS,Why is this feature important to you - In our case, when changing identity service, the old user's assets were soft deleted and we needed to transfer all assets registered on "unknown user" to the new identity of the owner.How would you like the feature to work - Owner update is reflected, in the same way as on the other Analytics assetsCurrent Behaviour - When sending in a new owner in an update request on a VRS, this is not reflected, even though the response is 200.

How difficult would it be to have the Serialized Event ID increased from 20 characters to 32 characters or more?Current 128-bit GUIDs are typically 32 characters (alphanumeric) in length, and requiring the truncation and/or trimming of characters and dashes reduces the ability to effectively ensure uniqueness as well as trust in the reliability of the process.  The use of these types of IDs is a business requirement in our organization because of other dependent systems behind our processes.I'm betting I'm not the only person who is being frustrated by this particular constraint.  Hoping this is something Adobe can quickly take action to support.Thanks in advance!

Description - When using Week of Year as a dimension, I'd like the weeks to default to sorting in chronological order (the same behavior as week) Why is this feature important to you - I can't build out a dashboard for clients and break out by week number, which they'd prefer, if the table is sorted by metric value. How would you like the feature to work - when breaking out by time/date dimensions, such as week of year, the dimension items should be sorted in chronological order (not by metric order) Current Behaviour - the table is sorted by the value of the first metric, leading to week numbers being jumbled up.

The creator/owner of a segment should be able to share edit access to others (not just read-only access).We have teams of analysts that share responsibility for reporting.  When one of them creates a segment, their teammates can't get access to subsequently edit that segment.  Example: Some time after a segment is created, an issue is identified, or a request is made to update the segment definition.  Within the team responsible for maintaining the reporting, currently *ONLY* the original author of the segment can make updates to it. If they're unavailable due to workload or they're out of the office, the request can't be transferred to another team member. The owner should be able to share edit access across their team so that a peer can pick up the work.

Feature Request Description: The current report suite data from Adobe Analytics is presented in a two-column tabular format, which includes the data type and its associated details. For instance, one row might display "Conversion Variable" alongside details such as "Conversion Variable 6. Status: Disabled". This format lacks complexity, making it challenging to parse individual attributes into separate columns without advanced Excel or Python skills.Importance of the Feature: Digital Marketing professionals, who are the primary users of Adobe Analytics, typically do not possess advanced technical skills in Excel or Python. Therefore, the current data format can be a significant barrier to effectively utilizing the analytics data.Suggested Improvement: To enhance usability, I recommend that the data in the second column be separated by a delimiter, allowing for easier parsing and manipulation of the data into distinct columns. This change would greatly facilitate the anal

Description - Create a new user group setting to restrict users to create( read only ) segments and calculated metrics but able to change report suiteWhy is this feature important to you - Currently if an organisation has multi brands and we have multi report suites. We want certain users to have read only access to segments but at the same time able to change report suites. As of today there is no combination setting like thisHow would you like the feature to work - I would like to have a user group setting that would enable me to customize the settings as I need as aboveCurrent Behaviour - There is only restrictive setting which does not let users change report suites too

Description - To get some order into dashboards, I sometimes use a Text visualization. Unfortunately its title must have at least one character text in itWhy is this feature important to you - Make dashboards more cleaned up without the need to add a character like "."How would you like the feature to work - Allow no text (see screenshots)Current Behaviour - When the "Text" is removed and confirmed, it snaps back to "Text" Select TextDelete text Meh!  

Description - In a displays settings, have the ability to display individual data-point totals. For example, this will allow an analyst to display the totals for each bar in a chart (see image).  In the display settings you could set the display to be in top, or inside the bar top.  when the width of the chart is decreased, the totals will begin to show only every other bar, and eventually only the max/min as the display grows skinnier.  can apply to vertical bars, horizontal bars, lines, and areas Why is this feature important to you - easier digestion of the data for leadership.  I have seen in many cases they will hover over individual bars, but this would be easier if they were already displayed.  How would you like the feature to work -See explanation above.Current Behaviour -you have to hover your cursor or just select max/min for lines.  

Would love to see Report Builder available for the Mac. Out of my last 3 jobs, I've only been able to use it once for this reason. Not willing to get a PC just for Report Builder, but it would be huge to begin using this tool once again.

Description - Currently, the steps in which visualizations in the Analysis Workspace can be resized, are way too big. Sometimes, it would be amazing if e.g., a summary number can be resized a tad bit to make the title readable withou increasing the size to 25% or whatever it is. Vice versa, sometimes it would also be super to make these summary numbers smaller.Why is this feature important to you - For more dashboard flexibility and efficiency of used dashboard spaceHow would you like the feature to work - Just reduce the distance between the snap points to e.g. 5% stepsCurrent Behaviour - The component resizing typically ends up ina) crazy bigb) way too small

Description - Allow moving around tables and visualizations inside of panels Why is this feature important to you - The current auto-snap/-arranging of components is sometimes too limitingHow would you like the feature to work - Have a "snap to grid" or "auto arrange" default setting that can be disabledCurrent Behaviour - moving elements around will try to snap into place which hinders some layouts

There seems to be an irony to the fact that Adobe Analytics doesn't provide analytics on how Adobe Analytics is being used As an organisation we have massively bought in to using Workspace to drive the self-service of data/insight throughout our business.As a result we are centrally managing a large quantity of workspace projects, segments, dimensions, calculated metrics for a significant number of Analytics users.In order to manage these effectively with Workspace, we desperately need to be able to understand things such as:how many times are components actively used (e.g. Segment X has been used 200 time in the last 30 days to retrieve data)which workspace projects a given component is associated with (e.g. Segment X is used in project A, project B and project C)what projects a given analytics user is accessing (user X has access Project A ten times in the last 30 days)Please can you consider giving us a decent level on Analytics on the Analytics?

Description:We need be able to identify irregularities/defects in our ecommerce business (declines in web traffic/sales/conversion).Using Alerts (both daily and hourly) with segments applied helps our teams triage in root cause analysis and investigations.Some of our hourly alerts trigger frequently if the criteria are met, most often during hours of the day where a large portion of our website/app visitors and purchasers are not browsing or purchasing. Why is this feature important to youWe are receiving specific hourly alerts for certain use cases more often then we would like.We have leadership and other stakeholders that have requested to receive these alerts, but we do not want to add them to the distribution until we can control the frequency to exclude these known instances from firing. We want to prevent the integrity of the Alerts tool from being deemed inaccurate and irrelevant as a result of this. How we would like the feature to workWe would like to have