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)

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 Page Views when published using publishing widget. from engineering .."Currently publishing widgets only support a single metric (regardless of the report) as they were originally designed to work on mobi...

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 make the site segment(s) the select control but that would only apply that segment, alternatively users would need to know or to be told which multiple segments to use for which requests. Possible Soluti...

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 better to use out of the box dimensions/definitions that work across the three products. Even better if 'Single Page Visits' metric was available out of box (as on AdHoc) USER CASE :Newspaper Publishers in U...

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 auditing purposes for around 15 sites. 'One' of the metrics is Single Page Visits thus we have to create 15 segments instead of using the segments 'site x' and 'single page visits'

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 Amazon AWS adds new additional IPs which are used for bot activity and therefore we have to consistently monitor and quite often miss until significantly hit. Being able to block by domain should alleviat...

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. Exported list of IPs from DW (for domain segment) which lists a mixture of IPs (can't attach as only image files accepted) which could either be part of class B/C network. Therefore at present we either t...

I've quite often applied a segment and then wanted to compare Key metrics or events between two date ranges at a top level. Currently Workaround is to look at a report where only one value recorded or use ReportBuilder.