Build better products with our product team
Hi,when I currently segment for hits with certain values, unfortunately, the segment does not apply to entries/exits/bounces (rate) because those metrics are not "hits" by Adobe definition and hence glued to the visit but not to a particular hit :-( . Problem: I cannot use segmentation for many kinds of analysis, i.e. Exit Rate calculation. It's not logical to me and I might make mistakes.I would expect: entry = 1st hit of visit / exit = last hit of visit / bounce = hit is both 1st and last (the only hit of the visit) I have raised it with Clientcare and they say this is a feature.If you have any further questions, just let me know. RegardsStefanie
The ability to add Target Activity & Target Experience dimensions into Data Warehouse reports.
It would be great to be able to classify standard reports. We end up having to use custom variables to copy the reports and the data never ties exactly.
Hi,Currently in the workspace we can use the option "Display only selected rows".Can we add the opposite : "Hide selected rows" or "Delete selected rows" and recalculate the total ?Best regards,Mathilde
Currently when month segment is used in calculated metrics it doesnt roll up or aggregate tot he changed time period. For example: Lets say for some reason there was no data for a page during April 01 to April 15, and calculated metric is built with If function to populated static number (say 1000) for those days, data display appropriately with day breakdown however when date range is changed to week/month/quarter it doesnt aggregate instead display 1000.
Adobe,The Admin Console is still HIGHLY labor intensive when you want to control permissions for Adobe Analytics. Not only that, it's a BAD user experience.First of all, I should not have to go to the Help documentation just to understand the sub-groupings of permissions you previously had in the group and user access management in the Adobe Analytics tool.Even worse: On any of the Permissions edit screens - EVERY time you add or remove an item from either the Available Permission Items or Included Permission Items, the list jumps back to the top and also wipes out your search criteria. You also can't select more than one permissions option at a time (REALLY?!?). The Metrics and Dimensions permissions contain ~2,000 options alone, and you want me to either add/remove everything, or tediously scroll (or search) for every single change I need to make?I was honestly hoping when we went through the user migration that this would be fixed shortly afterward, but I'm thinking Continuous Improvement has really missed the boat on this interface. PLEASE, PLEASE, PLEASE, make this easier for us to administer. I should NOT have to lose half a day of productivity just trying to create an Adobe Analytics Product Profile.
Running into an issue with visitor vs. hit level segments, that's also causing issues with virtual report suites and the new distinct count segment operator.Basically, it seems like regardless of where segments are applied, visitor segment is always applied first, then hit-based segmentation second.Example:Visitor level segment where it only includes visitors that have 1 distinct value for something like "shopping category"Apply a hit-level segment to exclude some category values (possibly due to accidentally bad data, or if you want to analyze a subset).The result is you still have visitors in the 1 distinct value segment, but they have no hits. These visitors should be moved into the 0 distinct value segment since their hits were deleted.The problem that exists currently is that if you end up with data pollution, you have no way to delete bad data and the dimension now becomes error-prone when doing the intended reporting.
Hi Adobe,since ages I wait for you to do some proper stuff for your customers. This is the first time I follow the invitation to place the idea here, but I still find it blaming for you that I have to do so!Here's why:- I need YTD- I need it through sFTP- For sure there will be more than 50.000 rows of dataUnfortunately, there is no tool that can fulfill all the 3 requirements!YTD can only be fetched through Report builder but it wouldn't support rows more than 50,000 and it delivers to FTP only!Data warehouse will give you unlimited rows with SFTP support but doesn't support YTD feature!Don't talk about delivering by mail and forget reports & Analytics or Workspace!This is like the distinct count, which is also not available and a ton of other really normal things when working with data, but you're the Leader in analytics, well....
Currently the printer-friendly options for Workspace are horrendous - the PDF always displays as a single page, regardless of project length. And I get this is partially because the full breadth of features are in visiting the page, but not all of our clients have the user capacity to create a new login for every person to whom they want to distribute this information.Idea is two-fold:- Create a "Page Break" option/feature so reports can be more easily designed for printing of the reportAND- Create Workspaces that can be viewed by anyone with a link (not required to use a login or allow logins that don't count against total users)It severely limits the usability of Workspace in the current format, as our clients have to budget when they can actually use it and many end-users of the data still prefer physical documents in front of them.
Can we have the ability to alter rule builder vai the admin / classfication api? When you have hundered of sites imapcted by serveral rules it would be nice to utalize an api to do bulk edits. ThanksSteven
It would be infinetely beneficial to enable processing rules to build/handle the product variable. This is something other 3rd party tools like Segment & mParticle are able to do. As our implementation becomes more complex and spans multiple platforms we are reliant on mutliple developers (web, ios, android, windows, etc) for implementation support. Asking our developers to update the product string for all new measurement requirements requires time & money. However, asking them to prgoramatically solve adding new variables to a product context variable (or any context variable) reduces developement resources and increases implementation speed & flexibility. It would be great if we could pass an array of product data as a context variable that we could then use to build the product string with processng rules. See below for an example array. Also, it would be an added bonus if we no longer had to set s.events for events existing wthin the product variable. But if this idea ever comes to fruition, I would hope the processing rule would automatically do the work for us. : ) {category: xxxxx,prooduct: xxxxx,units: xxxxx,revenue: xxxxx,variable1: xxxxx,variable2: xxxxx,variable3: xxxxx,etc},category: xxxxxprooduct: xxxxx,units: xxxxx,revenue: xxxxx,variable1: xxxxx,variable2: xxxxx,variable3: xxxxx,etc
I would have to say the transition from the admin console to manage group permissions in Adobe Analytics has taken a significant step DOWN. The UI on Adobe Analytics, while clunky in its performance, at least gave us the ability to quickly interact with and understand the context for what choices were related to certain functionalities. There is nothing intuitive in the choices provided in the newer interface, and worse, any new user to administrating user access will have no clue what certain choices relate to in the product.Which is easier to understand, Screen A or Screen B?Screen A:Screen B:PLEASE update the interface in Screen B, which is the current configuration of the Admin Console to help us manage our associates' access more efficiently.Please provide groupings for better understandingPlease provide mouse over descriptions to aid understandingDo not reset the user to the top of the list every time they add an itemDo not reset the user to the top of the list every time they search and add an itemThanks!
Allow for configuration of colors like you can do for conditional formatting. Right now this visualization displays data best against a positive goal, meaning more is good = green. What if you want to visualize costs and you don't want to go over a certain budget threshold? Allow not only changing of the scale but also defining whether high or low is good vs. bad.
Problem:I see many Workspace (or standard Reports) users drilling down from things like Marketing Channel Last Touch reports down to other reports like "Referrers." The problem here is that the user is drilling down from one report/var that might be Last Touch, 30 Days to another variable that is Last Touch, Visit. This causes breakdowns that do not make sense to the average user.As a consultant, I have answered question as to why things like this do not make sense for more than 10 years (i.e. the basic idea that not all things should be broken down by one another just because they can be), and this comes up on a regular basis to this very day.Solution:When hovering over a dimension or clicking the "i" icon, integrate admin console data as to the attribution and expiration of that dimension (to at least make people aware of a possible difference if they lookWhen one dimension is dragged under another (for drill-down) notify the user with a message as to the fact that they are using dimensions with different attributions and/or expirations.#2 may be difficult to execute since dimensions can be used in segments and other complex ways. But at a minimum #1would speed things up so that a user (who has admin access) doesn't have to go to the admin console to look up this information.
Today it is not possible to assign admin rights that only covers an individual report suite, which introduces a couple of challenges for companies that do not have a central administration team.Here are the options that I am aware of:1) Give everyone with 'admin needs' full admin rights. This introduces way too much risk in my opinion.2) Central admin team to retain all tasks that require full admin rights and implement internal intake process for sub-admins. Lots of overhead for little value... Also not practical in many situations where you need full admin rights to even understand what needs to be done (perfect example would that admin access is required to see what mobile parameters are available to map to props/evars in the Mobile Services admin screens.3) Implement new log-in company for each admin user group. Not ideal because it makes it difficult for end users who need to report on multiple report suites to know which 'company' to find their data in.Suggestion:1) At a minimum: It should be possible to assign full admin rights to individual report suites.2) Potentially also useful: ability to assign full admin rights to individual components of one report suites (for example, being able to configure specific props/eVars)
With everything changing over to Admin Console for user management within Adobe Analytics, it would be extremely helpful for us to have the ability to include some additional information against our users:A notes section, which would provide a centralized location and an easy documentation process for recording any important notes about a user's role as well as the justification for the role any specific user is given.A way to designate 1 or more individuals as overall lead Administrators for any certain tool, especially Adobe Analytics, because we have a number of different groups who use the tool. As a result, it make it a lot easier for us to identify a very small subset of individuals who can make decisions about the entire tool.Last, if we could also have the ability to give a user the ability to Administrate a single report suite instead of gaining Admin access to the entire tool, that would be EXTREMELY helpful and provide for a better security model.Thanks in advance!
Hello Team,Right now getPercentPageViewed Plugin is not working for Single Page Applications. Kindly help to update the plugin so that we can use it for Single Page Applications.Thank You!Arun
Adobe CampaignUse Case: Our business has departments and business functions using ACS with their own "Brand Instance" within ACS. Example: Sub brands of our company who send visitors via email to one or more websites we own. We have separated report suites within Adobe Analytics for our sub brands and our various websites/apps. We would like to send our ACS data into their corresponding report suite relevant to their website and/or sub brand.Issue: Currently the new Adobe Campaign Standard integration with Adobe Analytics brings all campaign data into the selected Adobe Analytics report suite, not just specific "Brand instances" or "Programs".Feature/Idea Request: Allow for more ability when setting up the ACS and Adobe Analytics integration to filter for specific data based on all or most of the variables available in ACS (brand, delivery, program, etc). This would allow us to provide email metrics and data in Adobe Analytics per report suite that is relevant to the website or sub brand owning those report suites and not see a bunch of ACS data not relevant to their business function.
Some versions of Regex include a "\L" syntax that allows a string to be forced to lowercase. This would be really useful as at the moment the classification that is created reflects the case of the original input - which can lead to messy looking values in reports. For example... Input value:website.com/PROMotion RegEx:^(.+)(\/.+)$ Mapping rule:$2 Results in:"/PROMotion" appearing in the report, where as I would prefer "/promotion" to appear in the report Note: this is about the output, not the matching criteria - aware we can already do case insensitive matching
Trying to enforce a naming convention taxonomy in Adobe Audience Manager and utilize that for reporting in Analytics is burdensome and prone to error. It also requires the creation of segments in order to roll those segments up into broad criteria for reporting. It would be massively helpful if Audiences ID could be described using a user-defined classification table to support reporting in Adobe Analytics.
I understand that there was once a time when the cost to supply and maintain Adobe Analytics was based directly on the number (and size) of server calls being processed and stored. I would guess that this is no longer one of the main operating costs in providing and supporting Adobe Analytics client companies. I'm not saying that bigger companies with higher volume shouldn't pay more than smaller ones with lower volume. But, the strict 1:1 relationship between server calls and dollars presents a perverse economic incentive that twists implementation design and methodology in ways that don't best serve the goal of providing good information for analytics. The primary example of this can be seen in the implementation of a product detail page on an e-commerce website. We have a few things that we might want to track on this page: The load of the page itself (for AA traffic reporting, Pathing, etc). The product view for the primary product (or products on the page). Impressions of cross-selling products served from a 3rd party service (e.g. Rich Relevance, Certona, Adobe Target). Product Rating and review information served from a 3rd party server (e.g. Bazaarvoice, or PowerReviews)Any other latent 3rd party tag info relative to the product or customer which may be loaded asynchronously. If cost were no object, I would argue that it is a better design to send an s.t() (page view) tag to AA for #1 above and send s.tl() (custom events) for #2-#5 above. Since cost is a factor (driven directly by server call volume), as an implementer I am forced to suppress the page load (#1 above) and write code to wait for events #2-#5 hoping to consolidate all the information into a single server call. This leads to less accurate reporting since the delayed page view tag is recorded less often. It also leads to more complicated implementations which are harder to maintain. It is a mindset based in the past, based on synchronous, monolithic, server-managed websites. It does not translate well to Single Page Apps, or microservice/component-based design patterns.
Right now it is not possible to create product profiles via the API, but only manually within the Admin Console. Since this is very time consuming and annoying, it would be great if it will be changed.
when I try to transfer an asset from one user to the other, I have 3 things that makes the process slow. I kindly request the following changes to the "asset transfer process"1) by default all categories/assets are checked. that means if I only want to transfer some of all the items, I first need to disable/uncheck all categories before starting to select. since the most common case is to transfer single items:=> set "unchecked" all items by default2) transferring single assets from a user with a huge library can be a mess. I would love to search for names/tags as it is possible in any other asset manager screen (eg. project manager, segment manager,...)=> implement an option to search for names/tags3) when transferring assets from an admin to a non admin user, the receiver gets admin rights. that means I need to hot to admin console and undo the change.=> add option to disable "admin" propagation
See in the Admin Console > under Products > Permissions. How do I get a lising of the Metrics, Dimensions, etc… So what I need is a csv of the 1,400+ Metric, the 580+ Dimensions, the 50+ Report Suite Tools and the 35+ Analytics Tools.Also a short definition of each item in the Report Suite Tools and the Analytics Tools would be very useful.
We have many report suites, and many users, each of which can see only 1 or 2 report suites. I have access to all the report suites. I need to make a dashboard that I can share with all the users. When each user views the dashboard, it needs to show the data for the report suite that the user has access to. So the dashboard will be a template that is filled in with different data, depending on who is using it. This could be done by each user having a default report suite that will be used automatically in the dashboard, or by letting me assign a report suite for each user that will be used in the dashboard.The current situation requires me to re-create the dashboard, along with all reportlets, for every single user, using a different report suite each time. Since we could have over 100 report suites and users, this is time consuming and impractical. Thanks,Christopher Stanwood
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.
