Metric selection panels should have info link (if available) which provides a summary of the metric in a modal window. To support this, the calculated metric creation, and events definition should offer summary field (which is the text shown in the modal) This would help* non-regular users easily vi...

Allow for fallout report(s) to be generated using segments instead ie.. segement a (pagename = x or y) > segment b (sprop/evar = x ANY y) > segment c (success event x)

We achieve this by using the get TimeParting plugin which captures in 30 min buckets, which is then re-classified into hourly buckets (and any other definition such as your definition of morning, afternoon etc) You can then use to create the segment .. ideally this should be out-of-the-box without n...

Publishing widgets only displays the first metric rather than all the metrics that are in the report.  This means having to un-necessarily create individual reports/widgets for each metric (and not great from a user/reporting pov either).  eg .. a report with Page Views and Uniques will only show Pa...

The Issue ..We have 140+ sites with single suite solution.  Majority of the RB requests in the workbook have the 'site' segment applied along with other segments. For Scheduled Workbooks : We have to edit every request where site segment applied x140+For Dynamic (with control) Workbook : We could ma...

AdHoc, Report and Anlytics both support  VISIT : Single Page Visit = EnabledVISIT : Page Views is less than 2 Neither of these segments are supported for Datawarehouse.  Whilst it's possible (based on our implementation) to create a segment which is very close (in terms of numbers) it would be bette...

This would be useful for bot rule filtering as one of the options is to filter on UAUse case.googlebot.com identified as one of the domains in R&Acreate segment domain=googlebot.com and export IPs using DWCheck/verify IPsRather than just filter on long list of IPs, it would be better if filter could...

With introduction of stacking segments in Analytics we're able to reduce the no. of segments we create as we're able to stack various combination.  Unfortunately this feature is not available in DW and therefore we have to create nested segments specifically for DW. User Case.We export our data for ...

A large proportion of bot activity occurs by faking useragent and across multiple IPs/ranges, however this usually occurs on IPs belonging to certain hosts and therefore it'd be extremely useful and time saving if we could set up the bot rules using Domain = condition.User Case 1.Every so often Amaz...

Before making a Bot Rule Set(s) live it would be extremely useful if it could be applied to historical data.  Even better if it could be applied as a segment.User Case : Identified what I suspect to be non-human traffic (no referrer and 100s of 1PV/Visitor) for  IPs belonging to a certain domain. Ex...