I'm getting increasingly frustrated that when I go to edit an existing segment, calculated metric, Workspace, or other element it will often times change the Report Suite to one I was operating in recently. It does not alert you it's happening. It does not take into account the Report Suite in which the element was originally created or saved. This is infuriating because I work with clients with multiple report suites and several times a day, inadvertently one of my elements will get saved to the wrong suite. While I understand in many cases, you can still use them across Report Suites, it means losing track of them when searching and in the case of Workspaces, data is changing without my noticing, resulting in client questions about accuracy of a report.
I suggest that IBM Cloud Object Storage be added as a destination for Analytics Data Feeds. The Cloud Object Storage API is very similar to that of Amazon S3. They share common features like Buckets, Access Keys, and Secret Access Keys, so I think Adobe could leverage their prior work as they do this integration.
I suggest having a button in the Processing Rules manager, that when clicked generates documentation for all existing Processing Rules.Rationale: Processing Rules are managed separately from tags, and they sometimes receive somewhat less attention. They do have the ability to significantly change tracked data, so documentation is crucial.Adding some "auto-doc" for Processing Rules would alleviate that need.
I would like a feature that would allow us to schedule or control what time the Adobe Alerts run.Currently Alerts run around midnight or 12:30am.For our particular business, we upload the Revenue and Orders (from our partners) the next morning around 8:00am. However, all of the Adobe alerts run around midnight, so I get alerts that revenue is $0 (and anomalous) and conversion rate is 0% (and anomalous) because they are running several hours before our systems populate Adobe. If I were allowed to schedule my alerts in the morning, after Revenue & Orders were uploaded in Adobe, then the alerts would be so much more useful.For now I have had to delete all references to revenue and orders in all of my Alerts, which really limits their usefulness. My Alerts would be so much more robust and helpful if I could keep Revenue, Revenue/Visit, eCPM, Orders, Conversion Rate, etc. due to scheduling them in the morning, instead of midnight.
HiWe are currently preparing the migration of Analytics users to the Adobe Experience Cloud. As we have quite a few users, we practiced the migration with five users first, which was worth it.Here the feedback they came up with and some interesting findings after 3 client support sessions.I think some of them might be interesting for your own migration :In Analytics the login happened with usernames (in our case NOT the E-Mail adress), while in the Adobe Experience cloud, the user logs in with his/her E-Mail Adress. This fact is not reflected in the login dialogs.When users use their old bookmark (e.g. sc3.omniture.com) and login to with their Adobe ID oder Federated ID, the first login attempt fails and you have to try login a second time. Current Workaround: User shall use the new url "experiencecloud.adobe.com".The example mail given in Analytics Migration Help references "marketing.adobe.com", which leads to a redirect. Seems that depending on the security settings, this leads to an SSO problem. The Login Dialog is irritating for users which are using a enterprise or federated ids. It works, but usability is sub-optimal.First Login Dialog prompts for "Adobe ID":The second Login Dialog prompts for the Adobe ID (where user can put in their Enterprise/Federated ID). Alternatively the Enterprise ID not very prominently found at the bottom of the dialog.The Welcome Mail contains a typo, which might irritate a bit. The button is above and not below (BTW: Also the german version is wrong)We will compile those feedbacks in a separate Welcome Mail, which we send upfront to our user community.It would be helpfull to be able to configure a company specific welcome Mail, which is sent out in the same moment as the Welcome Message of the Adobe product is sent. Maybe anybody knows, how to do that?When adding users by mean of the bulk import into the Admin Console, we encountered a region specific problem. Our CSV's were not comma delimited, but Tab delimited. The resulting error code is not specific enough to spot the problem quickly. So if import fails, verify that your CSV is comma delimited Hope some of those findings is helpfull for you.FrankPS: I post this findings in the community (hoping, that they find their way into the FAQ and help pages).
The Fallout Reports in Site Catalyst show both % Continued as well as % Fall through metrics.I would like to have the same visibility to % continued on the workspace fallout reports; today I either need to hover over each step or export the data and calculate myself.Thanks!
Hello,Right now, to schecule a report on Month Last Date, we only have options to select the days i.e. 1st Day, 2nd Day etc.The logic wont even for all the months since the number changes : 28, 30 and 31.As in Worspace, if we can include 'Month Last Date' option in Reports and Analytics, Dashboards, Report Builders, Data Warehouse etc, it will help everyone in the longer run.Thank You!Arun
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.
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.
Currently if you drag a segment A into another segment B in the builder it will just copy it in i.e. it rebuilds A in B. This means if you change the original segment A it won't update in B.What would be great is if you could drag a segment into another segment in a similar way to how a calculated metric works. This means you only need to maintain the original A segment as it will feed through into any other segments that reference it.
I would like a option to see the maintenance time information based on my own timezone. Or as a minimum it should show what timezone it is based on.
Because this sounds obvious, and would allow us to sequence user behaviour across different channels.Sounds like it's what appeared in the "Experience Analytics" sneak at the Summit this year.
Currently, page event ids are only documented in the clickstream reference documents. New ids have been added in the past, and there's no way to know when this occurs. I would suggest adding page event to the list of lookup files that are delivered with the clickstream feeds. ThanksKeric
The search textbox is too broad. For example, we have segments names per country and per site, so Site ABC AU, Site ABC US, Site XYZ AU, Site XYZ US, etc. If I want to search for Site AU, I expect to see only Site ABC AU, Site XYZ AU, but instead I also see Site ABC US and Site XYZ US.
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.
I have about 400 scheduled reports that I need to audit. It would be nice if I can export the scheduled report list to excel for further analysis.
It would be great to have the ability to archive old segments so that they’re not gone forever, but perhaps only show up when using a new "Archived" filter in Segment Manager. It becomes extremely distracting and cluttered to have old segments show up in Segment Builder, Analysis Workspace, etc.
It seems like "instances" is only available in the regular Reports & Analytics interface. When using a listvar, I want to be able to see instances, not occurrences, associated with the dimension. Thanks!
It will be great in the FLOW chart, specific pathes could be keeping highlighted between 2 checkpoints.Sorry I have no idea how to well describ this in words.
We need to be able to identify if we reach the 250 values limit or not.List Variable Adobe Client Care answer:The limit of 250 values is saved at a visitor by visitor level in the back end of the data base. This information is not available for which visitor has the value reached 250 and for whom it has not. The report for list variable shows aggregate values. Further, impressions may not be exactly same in case user had got some values expired because of reaching the limit of 250 values already saved for that visitor and only the latest value could be sent to reporting.
I would be very useful to have an overview of which projects have been sent via the 'Send File on Schedule' option. Whilst the “Scheduled Projects” tab shows you which schedules exist and allows you to check the associated rules/recipients there’s no log of projects that have already been sent. If a queue and a log are too complicated, then even just having a “Date Last Sent” column would be better than nothing.
The bar charts in a fallout take up 2/3 of the size of the panel. This is ok when it is the full width of the screen. However when condensing the size it ends up leaving very little room for the dimension title but lots of wasted space in the bar chart. Either make the bar chart size adjustable or prioritise the dimension name when shrinking.
I would like a option to choose a Report Suite or Virtual Report Suite directly from the Workspace "start page".The report suites should be placed in the left side menu, where project links are located now (My Favorite Project + Frequently Viewed Project)When i then select a report suite from the list the project listed should reflect those made/assigned* for that specific report suite.(* assigned: This is a part of the idea Assign a Workspace Project to multiple Report Suites ) As it is now, i need to first choose a project, and then i can shift report suite after. And in many cases you start working on the wrong report suite.A user/analyst would normally know WHERE (specific Website or App), he want to see data for, and then chose WHAT after that.And you would normally have multiple WHAT (project) question to one WHERE (Report Suite):But in Workspace the logic is turned around, where a user first need to chose WHAT, and then have to chose WHERE after that.I'm new to Adobe and Workspace, and it came as a big surprise that Workspace did not worked this way already.I predict so many cases where a user, make wrong conclusions, (or waste time) because they look into data for a wrong report suite.
In Analysis Workspace, provide a new table type called “Details Table”. I would think this would be on the level of Freeform Table. From there dimensions and metrics can only be applied across the top It would treat everything at the Hit level. Dimensions that are Visitor/People level would align automatically to the left, Visit level would be to the right of Visitor/People and Hit level dimensions and metrics would always be right most.Hits would be sorted and grouped by Visitor, Visit and Hit in chronological order. There should be some type of shading to show the groupings.Any Visitor or Visit level values would repeat itself for each Hit in their respective Visitor or Visit grouping (note that Data Workbench does not repeat the value for each Hit but I think it should to make it easier to create Pivot Tables after exporting to Excel).Allow up to ten dimensions/metric combinations. Any dimension or metric could be applied. It would be great if the Marketing Cloud ID were available since that would be an easy way to show a unique Visitor and might be used to drill down to one Visitor (such as a potential fraud use case).It may make sense to default a timestamp dimension. Ideally it would show down to the minute but Data Workbench typically only goes to the hour.The table would only show a sampling of the data but users could narrow their applied segment to potentially show non-sampled data.The table could be exported to show more data.Use Cases To troubleshoot suspected tagging issuesTo explain unusual data. It is typically always explained when looking at the lowest (Hit) level.To research suspected cybersecurity or fraud Visits and Visitors. The Cybersecurity team may provide a customer ID, IP address or other identifiable attribute to drill down to a single Visitor. They want to understand the online traffic pattern of that user to confirm or clear suspected fraud.
can we see custom link instances or occurrences in the data warehouse tool ?
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
