Explore product-specific spaces to ask questions, share insights, and learn best practices.
Recently active
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 helpful if we have an option to add a common segment across all reports in workspace report. Currently, we are adding segments to each panel / freeform in workspace report. This option is available in adobe analytics dashboard.
The Data Feed interface is great. However the the ability to apply segment filters or use Virtual Report suites will greatly reduce the size of requeststed data feeds allowing us to be more efficient with the data received.
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 thi
I was referring this page browserWidth , as per this document browserWidth will be setup before "doPlugin" but this is not correct for AppMeasurement. It was working fine for s_code.
There is a tool called Crazy Egg that provides the ability to do heat mapping and video recording on one's sessions based on Google Analytics. We would like to have heat maps and additional real-time activity pathing in Adobe Analytics so we do not have to use other tools to do these functions.
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?
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.
Working with complex segments and calculated metrics that contain many nested containers and may take a few screens, it's quite often when I move or add something into a wrong place. Sometimes the recovery may take longer than making everything from scratch.The Undo feature (Cmd+Z, Ctrl+Z) would be extremely helpful if supported in the Metric Builder and Segment Builder UI.
Legacy Admin User Management Console currently filters on either user ID or name, but special characters such as @, _, ., etc break the search. This is typically problematic for users with a UserID following email syntax. Furthermore, localized names (such as those using Japanese characters) require admin users to search on the localized name. This request is to improve search functionality and experience to be inclusive of special characters and considerate of things like localization, etc.
It will be ideal to have “Enforce FTP IP/Domain Restrictions” menu under “Company Settings > Security” of R&A for Analytics scheduled/unscheduled reports.
About 35% of our traffic is not real and we working towards implementing ways to filter out this traffic. One of those is the blog post below:Advance Your Bot Filtering Powers | Adobe I am a big fan of the idea. However, as I began implementing I realized that the Customer Attribute Segments that are created are only compatible with the reporting interface and not Datawarehouse. We run a ton of reporting through data warehouse.Can we please add Customer Attributes / Customer Attribute Segmentation to Datawarehouse?Thanks,Michael
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 Im
I am begging to have these features be added for report builder, more specifically for fallout: - Be able to output fallout as daily/monthly instead of just aggregate (PLEASE!)- Be able to add more than 8 fallout checkpoints- Ability to add more than 1 option for a checkpoint (e.g. homepage or subpage together on a single checkpoint) Thank you!
Hi,I have created a report builder template using a report suite where I have enabled every variable (prop, eVar, list var...) which I wanted to use to audit across our main report suites, verifying that each variables are capturing the data that I expected. Unfortunately, I have now learned that Report Builder will throw an error when a variable was not enabled for that report suite, making the main use of the template unusable.I would like to see Report Builder just skip or return back "variable not enabled" instead of throwing an error. As it is already catching this and showing a pop-up when a variable is not enabled, it shouldn't be any harder to let the request run and return a value indicating the variable is not enabled.ThanksAndrew
I created a VRS and hand picked the different elements to put inside. I was quite surprised that the Activity Map doesn't work for those type of VRS. It would be nice that it works as it can be very useful to use VRS as main report suite for basic users. Also when creating a new metrics, it is quite misleading to use the segment as they are marked as "not contained in the ...VRS name."As I know that I hand picked them, they are contained but basic users are misleaded. I would be nice to have this kind of selection fixed so the users can
I'd appreciate the ability to use calculated metrics with histograms.
With the release of Processing Rules where all Admins have the ability to leverage processing rules to increase their data accuracy and completeness, it would extremely helpful if we added Events to the line item conditions.Use Case - We currently have a DTM Javascript heavy based implementation of Adobe Analytics and have been working with our IT department to reduce the size of both the JS files (DTM's satelliteLib and AA's s_code) as well as reduce the size of the client side beacon calls / hits to the Adobe servers.we are looking for ways to achieve these size reduces without sacrificing our tracking / metrics capabilities. so we thought processing Rules would be a great place to start, as we can set our metrics and define our props/evars based on the end user's URL and the Defined Page Name.Since this is a migration strategy and not a new install, we have to use conditions like set prop14 = name when prop14 is not set. which means processing rules are simply filling in the gaps
While it is handy to be able to search for pages containing certain text, it would be good to also be able to filter based on a metric. I imagine this can be accomplished with some complicated segments but this would be much simpler and more dynamic.For example, filter to show only pages which have more than 100 page views, or pages which have a bounce rate of >50%, or pages which have contributed a certain amount of users to a certain conversion event. In some situations, this column could then potentially not be included in the table, freeing up space.On top of this, it would be great if the column totals updated when filters are applied, almost as if a segment had been used on the table.
I think it would be super-cool if users could use SHIFT or CTRL to select rows in Analysis Workspace and temporarily see them grouped together and with metrics for the grouped rows summed. Today, you have to leave what you are doing and either build a segment or create a SAINT Classification. This stops the flow of doing analysis.For example, let's say that I am looking at a Freeform Table with Day of Year as the dimension. What if I wanted to group the first 7 rows and see the data aggregated. It would be great if I could select the rows and then right-click to open a new table that has those rows summed.As another example, what if I were looking at a set of blog posts (or pages) and I randomly wanted to search for the ones that include the word "campaign" (shown below) and see all of that aggregated into one row:In the future, it would be cool if these ad-hoc (no pun intended!) selections could be saved, shared and turned into segments...Better yet would be a way to create these aggr
Lets say I have two metrics I like (Visits and Conversion Rate), and I frequently look at them by 'Visit Number', 'Marketing Channel', 'Products'. Yes, I should just make a dashboard and be done with it. However, I would love the ability to have the following workflow.1. Add metrics to a table. (in my example, I am thinking about adding them as columns/on top)2. Grab multiple dimensions and drop it on the the table.3. After the above action is taken, workspace would automatically create multiple freeform tables based on the number of dimensions dropped on the table.Here are some use cases for this:1. Faster dashboard creation.2. Faster analysis.3. Admins, Analysts, New Users want to quickly see what values are showing up in each report/dimension.4. Analysts can quickly grab important (favorited/tagged) dimensions and create a view very quickly.I think admins and analysts would find this feature particularly helpful and i believe it would make working in analysis workspace that much b
Hi,if I got the exact same linkIDs in my (sub)navigation, Activity Map shows the same values and rank, but it would be better if there was a warning sign for those duplicates.RegardsStefanie
To be able to create more than 3 real-time reports per report suite.Currently 3 is the max.https://marketing.adobe.com/resources/help/en_US/arb/real_time.html
allow us to creative custom weeks in virtual report suites (i.e., week ending friday as opposed to saturday)
With the push to remove complexity out of tagging, reporting and analysis I would like to see eVar support inside of the real time reports and API.For those of us that want to use the realtime reports we are forced to leverage props. But we do not want to use both props and evars for the same data (too confusing for end users!).I propose that the support for evars works exactly how the prop support works. Whatever data is on the hit should be available in real-time and we leave persistence of data to reporting and analysis workspace.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.