I would love to be able to use the new CIRD format to add IP address ranges to BOT rules and to Exclude by IP settings At the moment I can not exclude 40 CIRD values of internal traffic using Exclude by IP as:- 40 CIRD include roughly 400 IP addresses and I can only add 50 - I can not define ranges I have to use BOT rules which cater for IP rangers, however it would be a good time to update the tool to cater for new CIRD formatting.It will bring the solution up to speed with the new standards and will save me a lot of time for playing with more exciting Adobe stuff Thanks!
It would be great to have a replace all "of this metric" or append metric "to all tables" feature within a workspace panel or project. I know there may be some limitations as it relates to existing visualizations but it would help speed up dashboard creation and quick analysis. I find I spend a lot of time formatting workspace tables and visualizations to handle multiple metrics. If I could create a dash based on a single metric that allows users to swap or append metrics quickly it would help overcome a barrier to entry.
We have 38 actively used report suites. Classifications require back end div IDs to be aligned across all 38 in order to create a classification on a variable. When one report suite is misaligned, there is no way to easily identify which report suite is misaligned or to update all report suites with new classification or div values at the same time. You would need to manually click through all report suites to identify the delta, delete, and realign. ALL manually.Occasionally as well, you may have a report suite with the same friendly named classifications, but the back end div IDs could be out of sync depending on how they were created in the past. There is no way to see the div IDs in the client facing UI to know which one is misaligned. Again, the only way to correct this is to delete all classifications in all report suites and start over. I would LOVE to see new functionality in this area of the admin UI. Something similar to processing rules where you can work in one report suite and copy to multiple report suites would be ideal, or at the very least exposing the div IDs and a difference view across report suites (similar to the variable portion of the UI where you can click on "multiple" to see the differences by report suite).For all our report suites, length of time our account has been around, and amount of classifications we use, this would be a HUGE time saver for us and client care.Thanks,Erin
It seems that once I share a project with anyone in the Workspace I can no longer have 0 persons under the sharing list. The update button is grayed out when I leave no name under the sharing option.
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 of prop38/ evar 38 unique variable to 1M from 550k.Adobe Incident 2: 181105-000067Extending the variables limits from 550K to 1MAdobe Incident 3: 181220-000198==============Issue: Non-personalized pages still in v38 report after fixing the hash collision issueCo-ordinated with support team to understand why non-personalized pages are appearing in v38 report after increasing the unique limit for evar38 and prop38 to overcome hash collision issue.Adobe Response: Non-Personalized pages for evar38 / Prop 38 are returning in the reports even though it does not qualify the segment condition is because of hash collision. Recommendation provided by adobe support team doesn’t help us to meet the reporting requirements.souhardahn,
I've been doing a series of Workspace workshops with groups of people who are not familiar with Analytics at all. In my workshops, I cover basic concepts, implementation and, of course, how to create projects in WS. However, the biggest difficulty I see from these folks is to be able to tell what are the page names they need to use to create flows, fallouts and page reports. Although they have internal documentation with these details, they are not available to everyone and not so easily accessible.My suggestion would be to allow the customer to upload screenshots for their pages to Analytics and these screenshots show up when you hover over the dimension details in WS. So when a business user is not sure if that's the page they're looking for, then can do a quick check looking at the image and they don't have to go through a bunch of excel or powerpoint files to make sure they're picking the right one.The images could be pulled from AEM Assets as well.
My idea is regarding the Marketing Channel Overview Report:There are default metrics for the conversion reports, but I can't find any option for Marketing Channels. Especially for content sites without tracked revenue it's laborious to always change the metrics and further this always needs to be explained to less experienced users. It would be great to set a company wide default for the selected metrics. Best Regards,Sebastian
The Data Feed interface is great. However the the ability to apply segment filters or use Virtual Report suites will greatly reduce the size of requeststed data feeds allowing us to be more efficient with the data received.
I have been working with support to determine whether or not the inability to set s.linkName in the custom code section of a rule is by design or is a bug. Engineering came back and said that the functionality is by design but everyone I have discussed this with on Adobe's side has agreed that they would expect that if s.linkName is dynamically set in the custom code section, then the value from the input for link name should be overwritten. Currently that is not the case, but I am hoping we can get that functionality added for use cases where this is necessary.
Managing segments across requests had been a huge time saver fo us. Can we get something similar for managing metrics? I see the potential issues as adding metrics will increment either rows or columns to the request.. I assume there could be a check if the action to add metrics will cause overlapping requests.
I've seen a similar question in the past (Aobe Admin UI is hopeless and many years' past its best. Will it ever be updated? ), but it appears it was not submitted as an idea afterward. I would like to know if there are any plans to update/change the user interface for the Admin portions of Adobe Analytics anytime soon (and sooner would be VERY much preferred).From the amount of time we have to wait to view a report suite to the drop-down menus for concatenating values in the Processing rules, the experience leaves much to be desired.The linked question above points out plenty of issues as well. This appears to be a change that is well overdue. With everything else you're doing, let's please not forget the people who are using and administering your tool behind the scenes. Thanks in advance!
calculated metrics and analysis workspace projects do not have event category in Admin Logs of User Activity. would be nice to have these categorized.
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
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.
