Product Communities

In cases where you need to have a custom bounce rate metric, it would be nice to hide the out of box metric (bounce rate) from Reports and Analytics and Workspace.

It would be great to have two types of Admins, on for the Product  and one for the whole system.Admin list for the entire Adobe Experience Cloud (not just Adobe Analytics).  We have a customer in a large organization that would like to have Product Admins and System Admins listed as roles.

Hi There,Two that I would to have in the server call usage report:1)Quicker processing - Adobe Analytics is (on the whole) very quick. Why does it take 7 days for the server calls to process? Coremetrics used to offer daily server call usage 11 years ago.2)When I download a usage report it would be great if I had the option of "Daily" / "Weekly" / "Monthly".Thanks

Within the attachment you can see that we can apply a filtering possibility on the blank panel element. This is very useful for our complex deepdives on page or section level. However this isn’t possible yet for freeform tables. We could really use this functionality so that we can make a breakdown per specific freeform analysis on a page level that we want to drag in. I would assume that this innovation could easily be built for the freeform tables as well?This would make it possible to make complex analyses and easily filter between pages/sections. This will prevent making very long workspaces where you have to do a lot of manual work.

Analysis Workspace allows users to create down down menus using dimensions and segments, but the amount of space allotted to the drop down is fairly narrow. As a result dimensions or segments that have long names are truncated, and the full name can only be seen by hovering over menu item. Two solutions that would allow drop down menu options to be more visible:Allow friendly names to be used that do not rename the underlying segment or dimension item. This is similar to label editing in an Analysis Workspace visualization.Allow the drop down menu widths to be adjustable.

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!

In Adobe Analytics the Character limit of PageName is 100 bytesReference:https://marketing.adobe.com/resources/help/en_US/sc/implement/pageName.html If PageName exceeds the limit, it gets to strip off so increase the limit upto 255(characters)

Users are currently limited to only opening one template at a time from the "templates/standard templates/custom templates" window. We cannot right-click and open custom template in a new tab or window, making it difficult for users to easily open multiple templates at a time.We DO have the ability to right-click and open projects in new window from the "manage projects" view. I'd like this option to right-click & open templates in a new window to be extended to the templates view. .FEATURE REQUEST:1) Go to Workspace2) Create new project -> "custom templates"3) Add feature that allows users to "right click" on template, and open template in a new window.BENEFIT:This will improve UI functionality so that users can easily access and open multiple templatesPlease see attached word doc for more details on this feature request.

It would be great to have a link to the report automatically included in scheduled workspace report. Although it possible to generate a link to the report and include it in the report, the link is sometimes broken and require to be updated (eg. when they are changes in the workspace report)

When running analyses on server call usage against reporting totals (e.g. occurrences for a given date range), data can be difficult to validate as a result of hits that were processed but excluded from reporting for whatever reason (exclude by IP, bots, etc).  It would be helpful to itemize these counts in Server Call Usage reports to simplify these analyses.

Disclaimer - Please discredit this if I am incorrect, but I do not think I am. The out of the box 'bounce rate' metric, which is calculated as 'bounces / entries' does not work when used with the product string.  the reason is that 'entries' does not work with the product string, but bounces do.   after some discussion with client care I was told the following as it relates to the entries metric.  From Help SectionEntries represents the number of times a given value is captured as the first value in a visit. Entries can occur only once per visit. However, it is not necessarily the first hit if the variable is not defined. From discussions with client carethe product string can contain multiple products.  if the entry server call contains multiple products, only the first product in the string will get credit for the entry.  all other products in the string will not have an entry associated with it. We often drive people to landing pages that contain multiple products on the page, thus

Segments are useful for data pull of specific requirements, esp. customized pathing. However, sometimes segments are created for one-time use and don't need to be saved in the segments manager. I'm hoping we can bring back the function to create a segment without saving. (I believe Ad Hoc has this function in segment builder). Another idea is to create folder or tags for segments so it's easier to group things together and search. Raising this idea because a lot of us are facing the struggle of a long list of segments on the left panel, which is hard to navigate or find the commonly used segments.

In the old admin system, you could easily en masse transfer all segments, calculated metrics dashboards etc from one your to another. This was particularly helpful when deleting a user from the system (for example if a person left the company and they were a heavy AA user, i'd transfer their segments, calculated metrics dashboards etc to my account so they wouldn't be deleted).I raised this with customer support and they said it is no longer possible, so my idea is to bring this feature back.Thanks.

The Analytics & Target Integration Best Practices for Analysis page is great.  Analytics & Target Wondering if you could create one for Analytics & AAM?

Please bring back the ability to enable and disable and alert without having to delete and recreate an alert. 

DB Vista is one of the most under-utilized features of Adobe Analytics because it requires working through Adobe's Engineering Services. I would like to see a version of DB Vista that is available to administrators as a self-service instead. Just as Data Feeds used to require Engineering Services, but now is self-service, so too could DB Vista. I have found that Data Feeds is used much more now that it is more accessible.  I think the same would be true for DB Vista.I also think that this would help enable this tangentially related idea: relational data for processing rules

HiThe recent release has seen a change to the components in workspace.You now no longer see icons next to all dimensions, metrics and time segments (calculated metrics still have the calculator).We have some users that are colour blind, and now this makes things difficult for them, are there are dimensions and time segments with the same name (out of the box adobe ones) such as Day.People who are colour blind can now not easily see which is the dimension and which is the time segment

When i share a workspace project with someone and select the Automatically Shared Embedded Components with Recipients option, the other user can view any Calculated Metric. However, if there is a segment nested in the shared Calculated Metric, the user is unable click to view the segment logic.

In the data warehouse if you setup a schedule it is not possible to see what date range the extract was setup to cover or the dimensions added. This can make it impossible to manage on older schedule unless you put all the details in the schedule name.It would be good if reporting date could be added to the request manager and there was a way to see what dimensions are being extracted.

Adobe is a global company, offering its products around the world. The expectation is that the tools work also in non-English environments. There are several issues where functions do not work as designed due to lack of language support (or foreign language testing), especially in ReportBuilder.I am not talking about translation issues or missing languages (all our reporting and also Adobe UI settings are in English), but there are issues if the Windows client and/or UI is not English. For example, the "segment segment from cell" script does not work if the OS is German (even if Excel UI and ReportBuilder UI are English). My suggestion: Adobe, please test your tools in non-English UI environments before rolling it out to the customer.

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

It would be good to have 2 different types of graphs on a duel axis. For example you may have volumes of logins as a bar chart with the login rate as a line chart of the top.

In most of the Analysis and deep-dives, Pathing reports contributes well. With all of us moving to Workspace for our Data Analysis needs, would it not be a good idea to have these PATHING reports in WorkSpace as well?I am not referring to the visualization type "FLOW" in the Workspace as it does cover some of the pathing needs but doesn't really serves the purpose fully.The real power of Path Analysis lies in the reports like "Path Finder" which is NOT supported in this visualization type "FLOW". In addition to that other OOB Pathing reports like Page Summary and Path Length are also not available in workspace.List of Pathing Reports requested in Workspace:Path Finder.Page Summary.Page Length. I seriously miss these reports in Workspace    Do you miss them as well ???

Any chance to move tracking calls to use HTTP2 protocol in order to take advantage of performance? In our particular Adobe Analytics use case we have many resources requesting from the same exact domain and instead of sharding the domains it would be great if HTTP2 was used in order to allow multiplexing and other benefits to kick in. Fastly has had HTTP/2 available for all of its customers since last Fall. You can see their write-up on the benefits of it here: https://www.fastly.com/blog/http2-now-general-availability Additionally, you can see Information on the benefits and features of how HTTP/2 solves the "head-of-line blocking" problem here: https://http2.github.io/faq/#why-is-http2-multiplexed

Hi I have previously raised this point but it didn't get much attention.We are very keen to share workspace wider with our users however we want to do this in a controlled way using curated projects. We don't want all users to have complete un-curated access. We wouldn't give everyone access to ad-hoc and workspace is now more powerful.However we have found that users have found a way to bypass their access levels and create un-curated projects when they shouldn't be able to. They can do this just by clicking the 'Try in workspace' button in R&A. This gives them a completely unrestricted access to workspace when they shouldn't be able to. When we have external agencies able to do this then it is potentially breaking all sorts of data security processes.Joe