Classifying this data is essential - please implement!

This is a constant annoyance - wouldlove to see this implemented!

Good one Joris! In addition, I'd like to see version numbers in even more detail - ie. iPhone 5.0 vs. iPhone 4.3. Given that this information is based on the User Agent, I'd prefer to be able to see this (or extract it via Data Warehouse).

Love this idea!

Good one Andreas, I love this idea. As a supported user with several years experience, I do sometimes find it frustrating that contact with newer client care agents involves the whole "it must be user error' attitude, and subsequent back-and-forth until the client care person realises you aren't a) a complete newbie, or b) generally of below-average intelligence. I must point out here that this never applied in my dealings with you, Jorgen! In terms of your questions, Jorgen - I can see your poi...

Nice one Toby - a bit more flexibility in colour setting would be a great enhancement.

Definitely! Latency's a big issue, and report speed here in Oz is lamentable. Embarrassing even.

Hear, hear - both have their merits, but for my needs, option 2 would be my preference.

Yet again I have had to waste my time explaining to senior management that we can't set up YOY monthly comparisons in dashboards, Excel client, or Discover. We have asked Omniture for this at every CAB I've been to over the past few years. Seriously guys, how hard can this be? We're suffering here, and it's only a date range - simple bit of programming, really. Yours in desperation...

As suggested at the AU/NZ CAB, this is an absolute no-brainer.

Hi Ben, I'd love to see this - I've been waiting for it for ages. A search filter-based option would suit my needs, but you're right - both are valuable. Cheers,Christopher

Echoing Jenni's comment, this one's a must-have for us as well. We waste SO much time resetting year-on-year time frames. Dashboards just don't cut it when they have to be manually updated. This also applies to Excel Client.

I'd agree, but in addition, some idea of what has changed in a new code version would also be good, especially if it impacts on fundamental measurement issues.