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, i.e., for troubleshooting or isolating/identifying issues.Please let me know your thoughts!!Thanks!- Randy
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.
Surprised Workspace scheduling does not allow for the reports to be sent to publishing lists. Being able to schedule report to be sent to publishing lists and having reporting suite overide is a huge benefit within an organisation that has 200+ websites each with multiple reports and specific recipients.Without this we cant migrate over to using Worskpace for scheduled reports.Request ..1. Allow for publishing lists to be added 2. Allow for publishing suite override to work3 Have option to Prefix report name (and email subject) dynamically using report suite specified in publishing list.
Our use case requires the creation of bulk segments (10s of thousands of identifiers) and frequent maintenance of the same. Can you build this functionality akin to an excel upload?
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?
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.
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.
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
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.
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.
Median and percentile functions are available as built-in functions for calculated metrics within Adobe Analytcs, but they are Table based,From Adobe Documentation:Table Functions versus Row Functions A table function is one where the output is the same for every row of the table. A row function is one where the output is different for every row of the table. See below example of table using the this functionality with one Median and one 90th Percentile metric.The base metric that is calculated as median and 90th percentile is a Numeric metric. With Row capability for median and percentile, instead of having the median/percentile for all line items in total it would be possible to see the median for each individual row. Ie, what was the median/percentile for Feb 4, Feb 11, Feb18.This functionality would be fantastic and help to calculate medians/percentiles directly in the Adobe interface without having to resort to large data exports and manual calculation. Useful for any Numeric metrics where you need to understand the distribution of the individual metric values (eg technical data such as load times, waiting times, or other numeric metrics such as sales numbers) across different dimension values.Below question experiences the same issue as me.Median function in calculated metrics
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.
Hi Adobe Forum, When I create one segment in Adobe Analytics, I used custom dimensions (evar variables), and the "Contains" clause appears in my operator option. However, when I drag "Countries" or "Languages" (OOB dimensions) down to the criteria, and choose my operator, there is no "Contains" like derived dimensions under my option. I am wondering if this is always the case that OOB dimensions never had "Contains" operator as the option? If so, would that be possible to have the "Contains" clause under the operator for OOB dimensions in the UI? Thanks,
While creating an alert its nice to have alert starting date that way we can define our weekly report. At this point weekly alert is not working as expected. I have weekly Alert setup for last touch channel and its trigger every week which is annoying. And the reason its happening because of wrong date comparison. I remember when i setup this alert the day was Wednesday, so my report getting compare with this week 3 days (sun to tue) vs last week's 7 days. My suggestion is 1. Either set default weekly alert as Saturday or2. Give an option to define weekly report-Amarjeet
Hi there, I have 3 suggestions which would like you to improve them to make Data Warehouse used more efficiently: 1) Add "Delete" function next to "Duplicate" function in requests in Request Manager. At the moment, there is "Cancel" function in Scheduled requests only.2) "Duplicate" function is useless when I change different reporting suite. I work with multiple insurance brand, and want to build the same data extraction request for the all brands, but can't do it at the moment. It would be very useful if I can change different reporting suite and still have all dimensions and metrics as I set up before LIKE it works in Work Space at the moment3) Granularity isnt work for 1 month reporting date which makes sense, but I do want to show the Month in my data extraction, is this possible to have this function work still even reporting date is 1 month range? or is there any other way to show Month in my data extraction? Many thanks,Nhan
This is a request to create continuity between Analytics products in terms of report delivery. For instance, DataWarehouse and DataFeed tools allow users to send data via sftp or even S3 while Analytics and ARB reports are limited in those capacities. In certain instances there may be security policies preventing delivery in some of these formats and/or other limitations. It would be helpful to have consistency between products to avoid confusion as well.
I did contact Client Care about this as I believe it's a bug / defect but they advised it's working as per design, if so the design would seem to be a bit flawed.The introduction of visibility control for an event was a great idea (though I'm still waiting on the same for dimensions). The concept of hiding except for builders so the front end isn't bombarded with unnecessary events makes a lot of sense, we can rely on calculated metrics to surface what we want, how we want and with any necessary modifications (e.g. segments or calculations). What doesn't make sense to me though is that to me the idea was about making things easy in the front end, Data Warehouse however can't use calculated metrics which means if you want to use any event in Data Warehouse you can't use the function. I would view Data Warehouse as a 'builder' given you can't use calculated metrics (in the same way you can't in builders) and it's designed for more technical users getting out large scale data.Not being able to access these metrics in Data Warehouse has meant we can't actually use the brilliant feature, which is such a disappointment, please help!
As an Adobe Analytics leader across many markets, I would like to enable account & data access governance by creating different permissions for our reporting users. In the Old Adobe product, you could provide Read Only access to the Admin - Report Suite settings section. This means user could at least go into the configuration of a report suite and see the eVar, Props, events, marketing channels rules that are created (but prevent their ability from modify the settings).Today you can not with the new portal. It has a "Read" view in Permission-Report Suite Tools, but you can still Write & modify configurations. This is not good for data & account set-up governance.I would recommend to redefine the current Read Views as they are quite inaccurate.
Currently, with the new Admin Console, there is NO INTUITIVE TOOL to send a user another e-mail when they say they have not received the first e-mail that Adobe supposedly sent. Ever since we moved to the new Admin Console on the experience cloud, it seems a lot of your e-mails are captured and sent to a user's Junk/Spam folders, which makes it a lot harder to manage new users to the system. I don't have an interface where I can say, "send this person another e-mail" like we did specifically within Adobe Analytics.Something you should have at least considered was maintaining parity when migrating to your new system. Honestly, we really don't need anything more to undermine our organization's trust in Adobe Analytics.Thanks in advance!
When utilizing freeform tables in Analysis Workspace, it's very easy to accidentally drag a dimension like "Day" into the column space when I meant to drag it in as a row. Depending on the setup, this can create many, many dynamic columns, to the point where data is no longer visible, Adobe slows while retrieving a large matrix of data, and Chrome slows to a grinding halt attempting to render everything. The only option at that point is to destroy the entire table and start over, since you can't even get your mouse in to click and select the columns to delete.Could Workspace instead prompt the user if the number of columns created is over some reasonable amount (like 30) verifying that they are sure, before rendering the dynamic columns?
Hi,I think that as a business, it's important to have flexibility on selecting reporting and reference dates so that we can get MTD vs previous MTD or YTD vs previous YTD. Example: - May 12 2019 we had 1000 visits- May 12 2018 we had 950 visits (ref period)This would require to be able to define the pretended reporting period time vs reference period time as we used to have with DaX Comscore. Is it possible to add that functionality? Thanks
Virtual Report Suites have been a fantastic new feature, but they're not compatible across the entire Adobe Analytics platform. It would be great if their compatibility could include Data Warehouse. With the enhanced permissioning recently introduced, there are some users who I may only grant access to a Virtual Report Suite, rather than the full report suite, yet I want them to be able to use and take advantage of full Adobe Analytics tool capabilities.
If you have a report in workspace using an event, something like product views as your metric and week as your dimension, and you see a drop in views in the last week and you want to see which day that started on, you would break it down by day. However, when breaking down by day, it will give you a list of all days in your time period, not just the days in the week you are breaking down, like this:I don't understand why this would be the case. I would expect to only see the days in the week I am breaking down. One thing to note, when I do that same type of report but use a standard metric (like visits, page views) then this issue doesn't happen (I only see the days of the week I am breaking down).
We have found that we can include in a Data Feed (in order to ingest that data in our Data Lake) the Last and First Touch Channel ID. Not the name of the channel, because, being processed data is imposible to have the name in the hit.But there is no way to have a matching table, because it´s not possible to automate an export of the Marketing Channels names with the ID, we can export the variables using a DWH, but there´s no variable for the ID.It will be very useful to be able to program export of the Marketing Channels definition with IDs and corresponding names.
Now that certification for Processing Rules is no longer required, it should be time to open up a Save method for processing rules in the APIPresently the only method available is 'ViewProcessingRules' in the 'ReportSuite' APIAs a company with dozens of active RSIDs with standardized Processing Rules, a change in one rule set is a pain to roll out everywhereHaving a Save method for Processing rules would make it easy to update across Report Suites, as it is done now with variables/events
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.
