During user migration process , we had an option to select multiple analytics users then update all their expiry date in a single action , However set expiry header action has been turned off after ‘Set Migration Complete’’ action .Use case of updating expiry date for multiple users is a common one and extending that functionality for Analytics user management would be valuable
It would be very useful if there was a way to "expand all" processing rules for a report suite
It would be nice to have the metric gauge selection where we can have the red, orange, and green set based on a rolling 12 week period and have the meter based on the 12 week average, plus and minus 10%. Right now this is done manually so would like to automate as much as possible.
Wouldn't it be great if we had something similar to the "log" inside the Adobe Analytics Admin console, just with an overview of where the different evars, events and props where used, for any custom report that is built inside report builder, data warehouse requests, Workspace and which calculated metrics etc. It could be either a search functionality or a request that could be downloaded with a specific timeframe, just like in data warehouse. This would make it easier for people to see if the data is used or if it's just sitting there for no obvious reason (especially when going through implementation).
We need the ability to create an alert at the dimension level, which we were able to do with the old "top 1000 items" functionality in the legacy alerts. The alert should fire if any single item in a dimension reached a certain threshold.
As we move toward the ability to automate the build-out of an implementation via the launch API, it would be great to be able to automate the classification rules that support that implementation.
There are some OOTO variables which are not shown in the segment manager, such as timestamp, visitor ID, etc...I would like to create a new segment using those parameters, too. For example, I would like to create a new filter that includes all hits that are occurred during every 7pm - 9pm.Cloud you allow all users to use such internal variables (dimensions?)
It's a shame Adobe is deprecating adhoc, as an analyst, this is my favorite tool. It's clear Adobe did not survey any analysts when making this decision, and simply looked at the number of end users who had access to analytics (a majority of the employees had access, while all reports were generated by ~3 people, so of course it looks like barely anyone is using the tool). Workspace does not have the same abilities, speed, reporting capabilites, or visualizations that adhoc has. One of the reports with the biggest difference from adhoc to workspace is the flow reports. In Adhoc, end users can click on the different line items if they wish to break down the next user flow, while the flow grows, the visualization is made smaller and can be easily moved around. Workspace is missing those capabilities, it takes over the entire screen, long titles are cut off with ellipsis so it's impossible to see what they are, users can not click through or move the image around, and exporting it is not helpful whatsoever.I am really hoping Adobe makes vast changes to workspace before deprecating adhoc!!
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.
So the idea of Attribution IQ is market leading, ingenious, great, fantastic, we love it BUT it's really annoying not being able to use calculated metrics directly in Workspace. I know you can create a new calculated metric with a model applied but you can't use a calculated metric in the Attribution IQ panel or apply a model on the fly to a calculated metric in your workspace.JenteDR - not sure if this helps with the question you'd asked in the forum.
In the Admin area, where you can create product profile for your users, it would be nice to have an option to give users Read Only access to the classification rule builder.I've come across this situation a few times where a user wants to see our classification rules but has no need to edit/add to them, they just need to view them. As the AA admin in our company, it would make me feel more at ease if I could just give them Read Only access to it instead of needing to give them full access (where they, theoretically, could make changes).Thanks.
The new improvements for the virtual report suites VRSare really great. what i love the most is the ability to create VRS with component curation - this way the user just sees those dimension/metrics that i want, and i can even rename the components in a way the business understands.but: setting up the VRS for different users/user groups can end in a big effort by creating a bunch of VRS just to meet all the business requirements.Idea: add API function to create and change VRS.possivle solution: having a normal VRS im already able to get the settings (GetSettings | Adobe Developer Connection ). it would be great if i have an option to change the metrics/dimension of the VRS by a single API call the same way as i can do with the normal report suites
Once a custom event is enabled/created in the report suite, it'd be nice to have a corresponding custom event processing rule automatically created within the processing rules.
I would love to be able to add a classification, especially on a product level, with product images.And then, to be able to use these images in reports, so we can easily add images of the products reported on.
Hi,This idea is related to a question I posted : Incorrect attribution of conversions to Target activities in Analytics(?)It would be great to be able to choose the attribution period. Currently there is no expiration, which means that conversions are attributed to a past activity even long after this activity was live. So, doing your Target activity evaluation one week after your test or one month after your test or 2 months after your test might result in ending up with a wrong conclusion related to that test (because of being impacted by many other external factors, campaigns & tests).Some people might now think "but you can do this in the Segment builder by creating a segment on visit level and selecting Activity (Analytics for Target) exists THEN conversion exists" (cfr next screenshot). But no.. the result will still be that conversions are attributed to activities that were active even long ago. Reason: the IF condition 'Activity (Analytics for Target) exists' does not expire. It does not refer to the actual (one and only) impression.Ideally we would be able to select the actual impressions only and then select/define the evaluation period that is required for a certain test. This can be next hit, same visit, within a week,... since the type of conversion (a click or a sale) probably defines the length of this evaluation period.Kind regards,Sarah
Hi,for a customer registration process we have a funnel report setup in reports (classic).This funnel uses events which are serialized via an event id (kind of transaction number set by tracked application itself).We use event serialization for this funnel because from business perspective it is the best match. In workspace we set up a funnel (fallout visualization) with the same events. The fallout displays different values. This is probably because in workspace you have to choose as fallout configuration based on visits or visitors. The problem is that our events use event ids and we need to configure the fallout in the same way in workspace - but this seems impossible. So how can we currently set up in workspace a fallout displaying the same values like the funnel in reports? From my understanding we need something like a third fallout configuration type "based on event id" besides existing visits or visitor configuration.We miss such fallout configuration in workspace. In (classic) reports this options exists, so currently we can not switch to workspace.
Allow revenue to be viewed in workspace to be viewed in the user defined currency rather than the report suite default currency.
With Workspace in place people in our company use it more than the traditional tool. What is a pain for many end-users is that they miss the folder structure from the Adobe Analytics GUI. It was quite intuitive to use with folders, you could direct the users to the reports they needed, even without knowing the variables name or evar index number. And the average user doesn't use props, so people get confused between the two.
I'm new to AA, currently migrating from Webtrends.As i have stated in other idea, most features are better in AA than in Webtrends.But one thing i will miss is a spark-line per row in the (freeform) table.This was standard in Webtrends Analytics 10, and looked like this.It represented the trend for for the time-period selected on a daily basic.It made it easy to identify a sudden shift in data for a row.In AA Workspace i would imagine it would look like this.
Hi,Glad to see the new enhanced options for workspace.It would be great if below are fixed in next release.1) When new segment is created it is not retroactively available on other opened work space tabs to use (it requires refresh-not a good option when you are in midst of deep diving). It will be great time saver as it will enable users to use the segment without disturbing the current thought flow in data analysis.2) Enable count of months/days/weeks/quarter to create/use in advanced calculated metrics based on report date range.For ex: visit/day should automatically be adjusted to set date range.Thanks!
Dear Team,Currently we do not have any date ranges that are dynamic in nature and can operate on the basis of date selected in Date Filter. I had tried to custom date range which is a rolling monthly date range for last month [say 1 Mar - 31 Mar], the custom date works as current month - 1 month. Now if I set up a date filter on my report for any particular month [say 1 Oct 2018 - 31 Oct 2018], the custom date range range still reflects data for 1 Mar - 31 Mar but I expect the data to be displayed for 1 Sep - 30th Sep (Date selected-1 month). My assumption is any custom date range works on CURRENT DATE and NOT selected date in date filter of report.Could you create a functionality to change custom date filter to show data based on Date Range selected on Report and NOT CURRENT DATE.Thanks,
Example: In AA, I am only able to see the variable name, but not if it is a prop or evar.AA: Adhoc, which clearly states if thi is an evar or a prop.Asking since AA will be sunset eventually.
I have a rolling date range starting January 2019 until last month and every new month it gets automatically another month included.I have created a freeform where visits are the rows and colums I drag the dimension month in it and it woul show me January until June. But when another new month gets into this custom date range this Freefrom is not automatically including this date range and I think this would make it much easier to work with Adobe. Because it is actually just the same when I would include month as rows and this always automatically changes so why not when only switching row to columns?
HiI've noticed that summary change visualisations in AA Workspace shows 0% change as a positive result.Is there already a workaround for this?In an ideal world, they would show as neutral (e.g. orange/yellow with a dash).Edward
My global business reports traffic based on the following regions: Europe, Middle East, AfricaLatin AmericaAsia and AustraliaUS and Canada The geosegmentation report currently lists metrics by country or region (which is similar to country). I cannot easily view data by continent, which would be close to how I currently report on geographic region. The only way to report by continent is to create a segment that lists each country in a continent. This is cumbersome. Can we add a continent report?
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.
