Adobe Analytics

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

Data Warehouse had a dedicated DataWarehouse API v1.3 but has been deprecated and my understanding is due to be shelved completely sometime this year. Though, it was lacking in the features I desired anyway (read on)The current standard is to use Report.Queue  to request a Data Warehouse report. 1) DOCUMENTATION UPDATE - The reportDescription listing documentation does not show how to specify ftp info for ftp delivery.  I was able to piece this together together because the example Object output by the API Explorer includes it, and it's relatively straight forward - mostly.  Specific values I was also able to piece together from the v1.3 DataWarehouse.Request listing (not the same property names but still).  Also, the v1.4 Data Warehouse Reports documentation just gives a quick comment about referencing the Report.ReportQueue method - which doesn't even exist anymore (it points to a 404 page, and the method itself was deprecated from v1.4).  So.. this should point to the Report.Queue m

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

If I create a calculated metric, I get a preview of the trend like this:  I want the same in segment builder, a line for views, visits and visitors. Perhaps a toggle, dual axis, or normalised view would be necessary. I want it because it will help me understand the data I'm including in the segment I have defined. I also want it because of the sequential features in segments. Often I will just pull out a trend in a report with the segment overlaid to see what I'm including in the report. To have this in segment builder would save so much time. It would also help us to understand the new "before/after sequence" settings.

There should be a feature that let's you add notes and events to charts and graphs, so you can remember specific events during quarterly or annual reviews.

I LOVE the calculated metric builder and I've started using some of the more advanced functions to start producing some much more useful interactive Workspaces. One wall I've hit though is that if I want to create a table of top products that match metric criteria such as "show me conversion for products with more than 1000 visits" when I rank in the opposite direction all I get is 0%. While this is technically accurate it means I can't create a table of those top products I'm just ranking the most relevant ones at the top.The reason for this is the false value of the function is 0 which is still interpreted as a value and therefore displayed in the report, what I want to be able to do is set it to NULL instead so that if I sort by that metric ONLY those products are displayed and everything with no value is hidden.

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?)

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!

My team offers support within the company for Workspace.  Because of this responsibility, we all have many many projects users have shared with us over the years.  It would be nice if we could remove these items from our project list without reaching out to each original owner individually.  We know the projects can be transferred to a central account and magic can be worked out that way.  However, we have hundreds of users and maintaining that process for one or two admins is not very practical.

We need a time segment that take current weekday and compare it to average of the same weekday the last 12 weeks. Eg. One section has xx pageviews this Friday - and to find out if its high or low level, we need the average of the last 12 weeks, on the same day. As we are a news publisher house, we cannot just compair with yesterday or same day last week, as everyday is affected of todays history. The segment is required to be rolling dates as we wan't to display the numbers in a data visualization app.

Not a new idea. This was submitted as an idea over four years ago.  It is still a problem for many users. Please expand s.purchaseID to support unique strings larger than 20 characters.  64 characters would be just peachy as it would support a SHA256 output.https://forums.adobe.com/ideas/6214#comment-241670

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.

I capture the pageName in an eVar on each page load. The expiration is on the hit. That gives me pageNames in a variety of additional reporting. However I'd like to associate the eVar pageName (and other page attributes stored in eVars such as Channel) with custom events captured on clicks that occur on the page. With the expiration occurring on the page load, the eVar completely misses them. I could use the Minute expiration, but this just isn't precise enough. If people stay on a page longer then I would miss events.  Letting it expire at the end of the visit could really confuse things in the reporting even with overwriting. It would work better if the tool had an option to expire on the Next Page Load. That would capture all potential events without worry. As an additional option, Next Hit could be helpful as well.

We have 38 actively used report suites.  Classifications require back end div IDs to be aligned across all 38 in order to create a classification on a variable. When one report suite is misaligned, there is no way to easily identify which report suite is misaligned or to update all report suites with new classification or div values at the same time. You would need to manually click through all report suites to identify the delta, delete, and realign. ALL manually.Occasionally as well, you may have a report suite with the same friendly named classifications, but the back end div IDs could be out of sync depending on how they were created in the past.  There is no way to see the div IDs in the client facing UI to know which one is misaligned. Again, the only way to correct this is to delete all classifications in all report suites and start over. I would LOVE to see new functionality in this area of the admin UI.  Something similar to processing rules where you can work in one report su

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.

The Fallout Reports in Site Catalyst show both % Continued as well as % Fall through metrics.I would like to have the same visibility to % continued on the workspace fallout reports; today I either need to hover over each step or export the data and calculate myself.Thanks!

It would be nice if there were configuration variables in the library, something like s.queryParamOverrides = firstName, first_name, fname, address ....s.queryParamOverrideValue = foo wherein a list of query parameters can be overwritten with the value contained in s.queryParamOverriveValue. Many of us face data protection issues and adding the option to strip or override these values would be a great help in helping/simplifying things. Cheers Kevin

I've noticed today that duckduckgo.com is not recognized as a search engine by the Adobe Analytics Natural Search Detection Rules. It would be nice if this could be implemented. Regards

I have an abandonment fallout path I need to create where visitors start Checkout Start>go to any page(s) BUT Thank You>start Checkout Start again>then Thank You page.  The trick is that I can't just put the Checkout start twice because there needs to be at least one page in between them (rather than a reload).Rather than create a sequential segment and drop into the checkpoint, it would be great to be able to have a condition of NOT as a stand alone in addition to Eventual Path and Next Hit.  That way we could create Checkout Start>NOT-Thank You>Checkout Start>Thank YouAlso it would be great to have a Next Visit condition as well.  It would have to be available only if the Visitor option is selected.  An example would be Checkout Start>NOT-Thank You>Next Visit-Checkout Start>Thank YouIt's certainly different than the NOT condition, but would be useful for helping to understand multi-visit situations.

Hi, If we have a list of specific IP address to upload to Bot rules we should not need to define an IP range. Current state we need to provide 3 fields: BOT NAMEIP BEGINIP END BOT NAMEIP BEGINIP ENDbot  104.236.195.72104.236.195.72104.236.195.72 Ideally, we should just need 2 fields: BOT NAMEIPBOT NAMEIPbot  104.236.195.72104.236.195.72 Thanks Incident: #170328-000293

The ability to set up alerts on the top 1000 items in a report was depracated recently (https://marketing.adobe.com/resources/help/en_US/sc/user/deprecated_alerts.html) Please reinstate!  This was a key functionality of alerts for us.  As a publishing company, its ESSENTIAL for us to be able to see how an individual content piece (on a daily basis) is performing - and to be notified in order to respond to increased (or underperforming) readership.  Without this functionality - we have much less visibility into how our news is resonating with our audience.

When using If condition in calculated metric formula, the unsatisfied values need to be set to '0'.These line items still show up in the report with zero value and there is no option to have them excluded by default. The most is to display the zero as no value. However, copying these values or extracting them still copies over the underlying zero value and the report it self show these line items.Example calculated metric:This is how the current setup shows the data with the two options available:Ask: Change the checkbox for interpreting the zero to radio buttons and provide the extra option to exclude values which are having zeroes against them in all columnsAdditional Ask: If this is idea is implemented, it would be a good idea to show only the total for the qualifying data at the top of the column and not site-wide total.

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

I had a request from a colleague to create a Workspace project that would allow them to compare two date ranges for specific metrics. The two date ranges weren't set in stone, they could be any two set of dates, so I couldn't pre-set the date ranges. I created a report that looks like this:It would be nice if I could right click on each of the date ranges and change them. This would make it quicker to alter the date ranges I want to compare.

It'd be great to able to aggregate rows of a table into "All Others." For example, say I want to display only the top 5 individual values, then group everything else together and call it "All Others." There's probably a way to do this by creating some custom segments, but that's a bit of a pain and feels like overkill. I'd like to highlight a set of rows, right click, and "merge" or "aggregate" on the fly.