Another vote for this one. We are a publisher and have dates that would help us understand age of content. It's insane the kinds of work that needs to be done in order to select a range of date values. 

Does "bump"ing do anything here? This is 4 years old but seems quite simple and an elegant solution to a problem i imagine many Data Warehouse users have. I never use email as I never know if I'll be above the size limit, and often wait hours to find out.

A few more, since I've already started: X-axis labeling of the timeline is inconsistent, especially for a long training period. So, "Fri 20, Feb 4, Mon 9"... it makes it hard to see which month an anomaly happened in. This might be better fixed by doing major markers/gridlines for the start of each ...

Woohoo, looking forward to it. Thanks again to the entire team that worked on this. My favorite thing from the Summit (besides the cookies.)

I am loving Anomaly Detection and Contribution Analysis. As a feature this is such a helpful thing to have, and I know we'll engage with it often. However, I've noticed there are a few hiccups / usability issues that could improve use of the tool:  Sometimes I can't click an anomaly in the timeline ...

At least once a week, I'll get a request from a client or colleague asking for metrics on a specific set of product IDs/page IDs/object keys. Or, we'll release a feature on our platform that impacts a subset of products (by ID) and I'll want to make a segment. Currently, my two options are:Drag a co...

@benjamingaines We haven't adopted Office 365. It's a possibility in the future, especially if that means we can use RB. 

In theory, the "matches"  operator in a segment builder should work for this purpose, so long as the values are against the same variables. However, matches only supports a wildcard operator (*) and not an "OR" operator (|). I've always been a little confused by this limitation. It seems like it wou...

It looks like the current language report is simply a 1-1 translation of system language codes sent by the user agent [en-us = "English (United States)"].  When we require a level of granularity such as understanding language codes, such as for engineering decisions, this obfuscates the data, meanin...

+1. It's a pretty ridiculous assumption that any enterprise product is going to have a maximum of 3 one-to-many values of interest.