I have shared this with the appropriate people in Product Management. Thanks for submitting, Jeff, and others should please continue to vote for this idea if it is important to you.

We also noticed the announcement about the search results change, and will do our best to stay on top of this and other subsequent changes to the way that referrers are passed. For now I am marking this "Under Review" while we assess the best way to handle this change in SiteCatalyst.

+1 for the idea of List Vars and ReportBuilder out on a date. Well done.

For what it's worth, this was one of the features demonstrated at Summit in Discover 3. That isn't quite the same as having it in SiteCatalyst, but it's a start.

Victoria, Can you share where you learned that this is the result of a recent change in SiteCatalyst 15? We might need to fix some documentation. The reason I ask is that this is how the Pages report has always worked, at least since 2006 when I started at Omniture; the full page URL would only disp...

Item #3 was implemented a few months ago. There is now a Device Type report which breaks down data by mobile/tablet/etc.

Possible solution: Couldn't the ability to block IP addresses be added to the Processing Rules interface somehow?

+1 for mobile browser reporting. I'm assuming that data by PC/mobile/tablet should be available in SC 15 soon (if it is not there already), as I know in Data Warehouse you can now segment by Device Type (in both v14 and v15).

Does it help that SiteCatalyst 15 allows admin users to "boot" people from Discover in order to free up a license? I guess my question is, what is the incremental value from what you're proposing over what was added to SiteCatalyst 15?

Could there be unique value issues with this? Seems like user-agent string can have a TON of variations. But even if those values were optimized like the Traffic Sources reports (top 20,000 user agent strings per day are retained in SiteCatalyst/Discover), it would be helpful to us.