Build better products with our product team
Analysis in Flow looks like:Often, I find that I want to see all 140+ values in the left column, or 76+ values in the right column. To do this takes click after click, where each click shows 5 items at a time. Would love to be able to right-click to expand the full dimension and see all values.
Would like to see the following features in Adobe Workspace: 1. Calendar events - Can see this only in standard reports 2. Channel overview - Only seen in standard reports 3. Next page flow reports - similar to standard reports 4. Adding TargetsAlso would be really good to be able to add future dates in Data Sources.ThanksSapna
Have a template option in Workspace analysis that allows you to pick any metric/s to be used in freeform tables with all your dimensions broken out into a single panel. This would be used as a starting point in Workspace to validate dimensions to either audit or maintain over time. Basically you pick the template and get presented with the option to pick which metrics you want and then a wizard will create a Workspace project where every dimension is in its own freeform table with the corresponding metrics. The name of each freeform table would be the friendly name of the dimension illustrated in the table.
There are two use cases for VRS component customization:1: Specifying a smaller set of core components to be available in a VRS (auto-exclude anything new)2: Removing specific components that might not be applicable to a VRS (but wanting everything else included)By default, any new component created in the parent report suite is placed in the Exclude bucket, this works great for use case #1, but for use case is #2, we constantly have to be going into the VRS settings to move new components from "Exclude" to "Include".It would be awesome if there were a toggle in the VRS settings to auto include, or auto exclude newly created components.
When using a Full Processing data source type, you have to manually click "Complete Processing" for each file upload. It would be very useful to optionally automate this process, so we could for instance complete processing of the given data on a daily or hourly basis. The challenge from Adobe's point of view regards processing data for 'open visit', i.e. populating variables in the middle of a user's visit; but just as the "Complete Processing" functionality deals with this problem, so should a scheduled processing completion occur.
Hi All,After working with non -Analytics people and showing them Adobe reports I realized that they need to really dig in to understand report metrics. They are overwhelmed by stacked segments and metrics.What I was thinking, why dont we create labels by combining segments and Metrics. This idea came to me after seeing that we can rename Legends in WS graphs to simpler ones.Imagine this as the modular switches we use at homes. When a switch is fixed we see screws gaps and boxes. These bare screws are like the segments and metric that we stack on each other. Then we put a cover on them to give a clean look. This cover would be the new label that I am suggesting. In the background everything remains same.Example:Current structure : Multiple segments and metrics that make it confusing.(cant show any data due to privacy)Suggested Labels:I am suggesting that is it possible that we just select a metric and a segment or segments and then right click. There can be an option Create Label > Edit Label > Give custom name.You may say that we can create Custom Metrics. But there are 3 issues with it.1) Creating a Custom Metric is a bit time consuming. For one it may be fine but when we need to do for 5 to 6 it takes time and impedes the flow of work.2) Not always we need a custom metric.3) Too many custom metrics will confuse the user while searching in metric list.Hence, can this ability be created ?
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.
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.
Hi, If we have a list of specific IP address to upload to Bot rules we should not need to define an IP range. Current state we need to provide 3 fields: BOT NAMEIP BEGINIP END BOT NAMEIP BEGINIP ENDbot 104.236.195.72104.236.195.72104.236.195.72 Ideally, we should just need 2 fields: BOT NAMEIPBOT NAMEIPbot 104.236.195.72104.236.195.72 Thanks Incident: #170328-000293
On the new Experience Cloud Debugger, please add the following fields that existed on the old Digital Pulse Debugger::1. Version of Code - this shows which version of AppMeasurement the page is using (note: this is different than the Javascript version)2. Third Party Cookies - this shows the tracking server in use.Having these two added in would make it much easier to properly debug new pages to make sure the comply with the rest of the site.Thanks.
When a user opens a shared project in Analysis Workspace and would like to leverage somebody’s segment with a few amendments, they have to build a segment from scratch as there is no option to open it in the Segment Builder to apply desired changes and save it with a new name.Please add an option Save As (open in Segment Builder) for the segments that are in shared projects.
When scheduling a workspace to be sent via CSV, it would be great if we had the option to 'include hidden tables'. We have some large projects that we use for dashboarding and analysis but would also like to leverage the CSVs. It annoying to have to either 1) unhide all tables or 2) manage two projects (one with unhidden tables)thanks,Mike
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.
Current Issue:Right now, users may add custom descriptions to eVar & prop dimensions, however users cannot add custom descriptions to Adobe standard "out of the box" variables or classification dimensions. This inhibits user enablement as it may cause confusion to users who do not understand what certain dimensions are intended for. See screenshots for what I mean: Proposed Idea/Solution: The proposed idea would be to enable Admins the ability to add custom descriptions to out-of-the-box standard Adobe variables (such as Product variable) and also to attributes that are built from classification columns.Benefit/reason for request:This will help enable users to understand what the definition/description for every dimension, and will promote user adoption, especially for customized Adobe implementations. Our Adobe implementation does not leverage the "Adobe tag". Rather, we use a proprietary tagging solution, and so a lot of the standard Adobe variables are not applicable to our account, and we want to be able to flag these with a description that says "DO NOT USE". Also, some of the standard Adobe attributes have been re-purposed for other uses, and so their default use-case does not apply, and we would like the ability to update the description of them so that it reflects the actual definition according to our implementation (as the Adobe help documentation only applies for standard Adobe implementations). For example, the "server" dimension has been re-purposed in our implementation to be populated with values that represent the page domain of a page URL in our implementation. We would like to educate/enable users of this logic adding a description to the "server" attribute, however we are unable to do this. Thank you!
Currently the only way to rank dimensions by metric is to sort them (example: page URL's by Visits). But what about when you want rankings for a certain metric to persist, even after you've sorted by a different metric? (Similar to the Rank function in Excel). This is particularly important in web analysis from a page performance and path optimization perspective as it's possible to create participation/contribution metrics but extremely difficult to track changes in rank leaders over time. The fix for this would be to add a simple rank function in the metric container.
Hi,if I got the exact same linkIDs in my (sub)navigation, Activity Map shows the same values and rank, but it would be better if there was a warning sign for those duplicates.RegardsStefanie
Could we please introduce additional preset date range selectors in Data Warehouse? Currently, we don't have any options between 7 and 30 days (14 & 21 days would be great). And the custom date range doesn't include a rolling data range feature. This causes problems for regularly scheduled reports.
There is a need to have a view only of all the variables and processing/channel rules in analytics. Currently, unless you are an admin, you cannot see which variables are activated for your report suites, when they expire or any of the processing rules that assign values to variables. This can be limiting if you are trying to decipher some of the reporting (especially if things are not quite adding up).Don't want admin rights to change things – but would like the right to view things.
Currently Admin Console gives the perception that granting permissions by product profile is a scalable way to grant permissions, with AND logic, and reinforced here: Enterprise Help | Manage product permissions in the Admin Console. After talking with Adobe client care, this is false. Not only can product profile permissions conflict with each other, in an OR logic fashion, but there is no way to know how product profiles will interact with each other except through trial and error (per Adobe Client Care Incident: 190204-000614). For example, in trying to combine a product profile with a single report suite in it with a product profile granting access to an array of data feeds utilities, the user does not get access to the single report suite such that it can be used in combination with the data feeds permissions. This was confirmed by ACC.Solution proposed:- Create product wide AND or OR logic for product permissions and document it, ideally AND logic
We are heavy Alert Users.The challenge: We want *relevant alerts*. Adobe's Anomaly detection system is ok, but 95% of the *Hourly Alerts* it spits out are completely irrelevant as traffic simply oscillates too much from one hour to the next, AND because Adobe seems to take only the last 24 hours into account when looking for Anomalies. So we had to deactivate all our Hourly Alerts.1. However, Daily Alerts are too late for something really critical, so Adobe needs to either improve the Hourly Alert logic, or offer something in between, like _3-hour-periods or 6-hour-periods_ which don't jump up and down all the time like hourly data.2. Alerts should be configurable to fire only "only if a value is _HIGHER/LOWER_ than expected" (and a certain Significance Level. We don't care so much if the Conversion Rate of Google Shopping is greater than expected, we want to be ALERTED when it goes DOWN because then we have to take immediate action.
Hello, When using A4T integration in Target for my activities, I can see in Target reports AND in Analytics reports which experience is the control experience for any given activity. But after speaking with Analytics support, it is not possible to retreive that information from Report Builder. So, make possible to get information about which experience for any given Target activity (with A4T integration) is the Control experience. That would greatly help on subsequential calculations based on that output.
The Analytics Data Feed is only available over SFTP to port 22. It would be more convenient if the user could specify other ports.
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.
The link generated from "Get Project Link" in Workspace directs you to the legacy analytics login. This should direct you through Marketing Cloud login instead.
Data Warehouse had a dedicated DataWarehouse API v1.3 but has been deprecated and my understanding is due to be shelved completely sometime this year. Though, it was lacking in the features I desired anyway (read on)The current standard is to use Report.Queue to request a Data Warehouse report. 1) DOCUMENTATION UPDATE - The reportDescription listing documentation does not show how to specify ftp info for ftp delivery. I was able to piece this together together because the example Object output by the API Explorer includes it, and it's relatively straight forward - mostly. Specific values I was also able to piece together from the v1.3 DataWarehouse.Request listing (not the same property names but still). Also, the v1.4 Data Warehouse Reports documentation just gives a quick comment about referencing the Report.ReportQueue method - which doesn't even exist anymore (it points to a 404 page, and the method itself was deprecated from v1.4). So.. this should point to the Report.Queue method, but now we've come full circle with no info detailing Data Warehouse API usage for v1.4 Report API. Can someone please update the v1.4 documentation to include Data Warehouse report pull usage?2) FEATURE REQUEST - Report.Queue only lets you make a one time report request to Data Warehouse. It does not let you include/configure anything for scheduling a repeated/ongoing report export like you can in the interface. Well, it's not documented, anyways. Not even in the v1.3 version. This is a very big pain point for several of my clients and it would be super nice if it could be added.3) FEATURE REQUEST - Also, there is no way to retrieve information about Data Warehouse reports currently in the Data Warehouse queue. I would like to be able to make an API request to get a listing of all Data Warehouse reports in the Data Warehouse queue, whether it be one time jobs still in the queue, history of completed jobs, and - most importantly (to me, anyways) - list of Reports on an ongoing / repeating schedule. Maybe a method to pull a list of all id/names and then another method to pull config data based on id? That would be super nice and helpful.4) FEATURE REQUEST - And following that train of thought, it would also be nice to have API methods that allow me to update configuration or cancel/delete report jobs.5) BUG FIX (?) - In the Data Warehouse interface, I am able to choose Marketing Channel Last Touch Instances as a metric. It is there. I can select it, and it shows up in the exported FTP. I can provide screenshot evidence. But it is not available via an API pull. I have tried generic "instances" - says this metric is not available for data warehouse pulls (what??). One trick I have found over time to get around lack of documentation is to inspect html elements on pages within the Adobe Analytics interface. I can do this in the Data Warehouse interface screen and in the html code "@marketingchannellasttouchinstances" - does not work (with and without the leading @ sign). I've tried many variations of that. I've tried a Report.GetMetrics API call and nothing relevant is listed, though I saw a lot of other "instance" type metrics for other elements listed with their "instance" prefix, followed by their element id, so I tried "instanceslasttouchchanneldetail" - no joy. I tried all kinds of combinations of these words. Reordered, added. Removed. No joy all around. But clearly this is available as a metric within the DW interface, so it MUST be a metric available on the back-end, and the API just isn't aware of it. Or more accurately, the Report.Queue API's data validator isn't aware of it so maybe any one those things does in fact work but is getting blocked by the API's validator because the whitelist is not comprehensive. Whatever the case may be, can someone please add this, and while you're at it, do an audit to sync up what is available within the DW interface vs. the API!6) BUG FIX (?) - I created a segment in segment manager. In the Data Warehouse interface the segment is available. I can schedule a DW report within the interface using the segment. I receive the exported report and the data accurately reflects what I expect. I have verified this thoroughly. I attempt to throw the same segment into the Report.Queue API call for Data Warehouse, and I am sent a blank file with nothing but the column header row. The DW API request sends me all the data in the world without the segment thrown into the mix, but returns me nothing when I add it. Scheduling the same exact thing within the DW interface sends me data. Yes, I have triple checked that the segment id is correct. I even used that inspect html element trick I mentioned earlier to verify it both within the segment manager AND within the DW interface. All shiny. So this seems to me that there is some kind of bug with applying segments to Report.Queue API calls for data warehouse. Sidenote : segments applied to regular Adobe Analytics reports work just fine for me; I do those all day long for other projects. So whatever is wrong with segments via API call, I think it is Data Warehouse specific ("source":"warehouse"). Can someone please look into and fix this?
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
