Adobe Analytics

This used to be available in the previous "Billing" tool but the new Server Call Usage report doesn't seem to let you trend over time.  I don't don't see where to change the date range unless I go back to Reports.

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

Right now, Reloads metric is available only for the Pages Dimension in Adobe Report Builder. If we need to see the Reloads for overall site, we need to use Page Dimension to sub-total it based on the ganurlarity which is tough to build the auto dashboards. Have created a calculated metric PageViews without Reloads (Page Views - Reloads) and automate it using Report Builder, but the option is not available in Site Metrics(Available in Adhoc Analysis). It will be great if we can add Reloads to the Site Metrics.

Hello,It would be nice to be able to include data labels on Workspace visualizations and tables that will display either the absolute value, the percentage of total, or even an abbreviated value. This would best function as a toggled feature. The lack of this feature today prohibits our organization from utilizing Adobe Analytics Workspace at an enterprise level because the visualizations don't provide a clear delineation between similar values. If I schedule a Workspace as a PDF to my organization, we may get questions from the visualization as per the values each bar, or pie section represents.

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:

Let's face it - bots are getting smarter. Bot Filtering needs to get smarter too. Bots are getting better at changing user-agents, IP addresses, domains and more in between visits. Bots are now even adding delays between page views to look more like a normal visitor. And don't forget, they're running JavaScript too. Adobe needs to expand Bot Filtering to use look-alike modelling to discover visits with abnormally high page views.Similar to this Idea: http://ideas.omniture.com/t5/Idea-Exchange-for-Adobe/IAB-Bot-List-Segment-in-Analytics/idi -p/11708    we need a way to be able to apply 'Bot Segments' to reports so we can better understand what traffic changes will result prior to committing them as rules. Right now the industry is losing too much accuracy in our data to rely solely on a black box of IP and user-agent based filtering.

Hello,When I compare time periods I can not always compare to same periods last year so I have to do it with the customized way. Moreover, when I change the initial period, the comparison doest not change reciprocally and I have to do it manually.It would be great and useful, if these updates could be done.Thanks for the support.

While Report Builder has a fallout report, it doesn't have the same capabilities as the one in Workspace.  Specifically it would be really helpful to be able to add events and the like to the Report Builder report.  Right now I can't recreate the same ones in both tools and it is adding multiple extra steps to our monthly reporting.

It would be great to add a customer further analyze url to an alert notification.  We have much more comprehensive workspace dashboards for analysis into alerts.  it would be great if we could link directly to them rather than the standard further analyze dashboards which are pretty thin.

Hi Adobe Team,It would be great if you could add Last Analytics Access details in experience cloud. Currently, we are reporting on Last Analytics info. of the Adobe users from Omniture portal but it will be disabled after 15th Jan'19 as we are migrating to experience cloud. We have found multiple users who didn't enable their adobe account. Hence, this info. is very useful for us to identify these users and delete their accounts or give limited accesses.Regards,Keshav

I love the difference between breaking down a fallout visualization touchpoint by either Fallthrough or Fallout:I'd love to see the same functionality for Segmentation: Fallthrough (current functionality) or Fallout.

Feature request for a product syntax segment. Basically when you fire multiple products in a single hit and those products have product syntax variables, you can't use them in segments. Any hit level segment captures the entire hit, not just the specific product syntax value you're looking for. For example, if you have one order with three products (two new, one used) and each new item is $11 and the used is $6, let's assume you're setting the condition as a product syntax variable. For the first two the value is "new" and the third is "used". If you build a hit level segment where this variable equals "used", you'll see $28 instead of $6 since all three products were set in the same hit.

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

We have a few websites that generally used the same classification rules and tracking code template but there we a few differences. After a few years, it was decided to bring these together to use the same tracking code template. This meant aligning classifications and classification rules.The issue was that you can not align classification for two or more report suites by name, because they have a hidden ID in the background. this meant that when if I was on report suite 1 looking at the Channels report and then changed to report suite 2, it would no show me the same Channel report (due to the classification IDs being different).It would be good if it was possible to update these IDs to make sure they match, thus making reporting across report suites easier. Considering you can create classification rules based on the classification name not ID, why is it not possible to align them?Thanks.

Now that Analysis Workspace includes "copy to clipboard" and "show only selected rows" functionality as options in the right click menu, I think it would make sense to add another option to create and/or add to already existing filters from resulting dimensions/row items in a Freeform Table.For example,  if I created a Pages report with a number of filters already applied, but I was still seeing a few pages that needed to be excluded, it would be great to be able to just right click on the resulting row(s) and select exclude selection (or filter by selection to zoom in on that item) without having to open the filter dialogue.Selecting the "Create filter from selection menu" item from the menu could open to a sub-menu with several more options, but below are two as an example (exclude and focus):Choosing one of the sub-menu options would then reload the newly filtered report.This would be super helpful if you needed to whittle down to specific item/s from a larger list ON THE FLY,

In most cases, folks create new Bot Rules specifically because they've uncovered a bot that has been messing with their data... unfortunately, by the time you've identified the problem and created the rule, it's too late: the bot has already done damage.The workarounds are pretty drastic- applying a segment to every report, or moving entirely into a Virtual Report Suite that doesn't include the bot traffic retroactively.Bot rules working on historical data would be a huge help.

Working on React Native and getting Adobe Analytics to work in a pain, we need to create bridge and make methods avaliable from the Native path in ReactNative, so can we please have a npm package that works in React and ReactNative?

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.

The feature inside Analytics called Views Mobile Scorecard is a nice way to create mobile dashboard and it instructs curators of Adobe Analytics data on how to configure and present mobile scorecards for executive users.  Video Tutorial: https://experienceleague.adobe.com/docs/analytics-learn/tutorials/additional-tools/analytics-dashboards/adobe-analytics-dashboards-in-app-experience.html?lang=en Doc: https://experienceleague.adobe.com/docs/analytics/analyze/mobapp/create-scorecard.html?lang=en Could you please implement this feature using Single Sign-On? At the moment this feature is not working with SSO. Benefits: Analytics users can use this feature with SSO

Sharing PDF's is great since it gives a right away picture of the insight. Problem is that the PDF seems to be always only one long, very long page. Would be great to be able to personalize the format of the PDF, such as the ability to add page breaks.

Hi guys, not sure if this is an idea or more a question: But are realtime dashboard available somewhere within AA? I'm not talking about the old "reports" where it was somehow possible but which will be discontinued anyway by end of 2023 but about workspaces. In simple: something that Google Analytics offers where I can see which users are currently on my website/page, from where they are etc.   Why is this feature important to you: to get an realtime overview what happens now, e.g. interesting for big events like Black Friday, etc. How would you like the feature to work: simple and quick 🙂 Current Behaviour: not possible

Description - Many visualizations in Analysis Workspace are based on Freeform tables. Some of those visualizations, like the Histogram viz, can therefore be used to create complex Segments or Freeform tables from a simple interface. That's awesome! However, not all visualizations are based on Freeform tables and don't offer a quick way to take the generated data a step further. Luckily, those visualizations usually offer some form of right-click magic to create single tables or Segments, which is a concept I would like to extend on. For example, consider this Flow viz: We can right-click individual nodes to break it down but not show a full column (only when we hack it to show a full table) or even the full viz as a table. This could be added quite easily with some new buttons to show the full Flow or just a single column as a table: Clicking those would create a new Freeform table with the respective Segment(s), dimension, and metric applied, potentially like this:   This

Description - Currently custom time ranges are limited to an 800 day lookback.  I would love this to go back a little farther, enough to accommodate a Last 90 Days two years ago rolling range.Why is this feature important to you - With pandemic, YoY comparisons are not all that telling so I've been using Prior Prior Year to establish a better baseline for how much business we've recovered this year.  Last 90 days is a standard comparison window for us but I can't create that period two years ago because I hit the 800 day limit.How would you like the feature to work -  Specifically, I'd just need the lookback window for days extended to 825 days.  Though since we have a rolling 37 months window of data, ideally the custom time range limit would go would go back to that (~1125 days).  Current Behaviour - Days in time ranges stops at 800.  You could theoretically maybe do it in weeks or months, but for us "last 90 days" is the optimal time comparison ran

Description - Today, components in CJA are presented as a flat list, like we know it from Core Analytics: While this makes sense in Core Analytics, where components have no inherent relation to each other, components in Customer Journey Analytics come from the XDM Schema, where fields are always contextual to the Schema. For example, the standard Web SDK Field Group positions the ID and Click number of Link Clicks at "Web > Web interaction > Link Clicks > ID/Value": This context for individual components provides CJA with the potential to solve a few long-standing challenges in Analysis Workspace: For similarly named components, provide an intuitive way to explain the context (and thereby use case) of individual components As a novice user, help them to combine the right dimensions and metrics by showing that they come from the same context (in the example above: "combine the value metric with the id dimension") As an advanced user, give hints and inspiration to explore the

We have found out that there is a difference between Time spent on page - bucketed and Time spent on page - granular.The bucketed takes into account only the pages, the granular also takes into account the link events.In our interpretation the "time spent on page" should take into account the link events.  That means that we can only use the "granular" definition, but the data we receive is almost useless, because almost every page has a different time spent on page, and it becomes impossible to make conclusions of those data.So we would like to have a dimension "Time spent on page - Bucketed" taking into account the link event (as it is or the granular definition now).