NormCloutier, The issue is that SC is calculating it as (old-new)/new instead of (new-old)/old For example, if the current period is set to August and the comparison period is July (i.e. a month over month report) and you're fortunate enough to have tripled from 1MM UVs to 3MM UVs, you'd expect the ...

I submitted an idea today to allow users to define calculated/derived metrics using segments. If that feature was implemented, you could define this custom report by creating calculated/derived metrics:1. New Visits: Visits where visit #=12. Repeat Visits: Visits where visit #>13. % Visits News: [Vi...

Allow users to define calculated metrics that use segments. For example, if you wanted to create a report that showed the top product categories including total revenue, total orders, % of orders that were $50 and % of orders that were from VIP members you'd define two calculated metrics:% Orders VI...

I submitted a similar request a while back for improved time comparison reports: http://ideas.omniture.com/t5/Adobe-Idea-Exchange-for-Omniture/Improve-time-comparison-repo rts/idi-p/3791 While I agree that this would be tremendously useful in the retail space, the functionality would also be benefic...

Provide the ability to have a report suite use the same classification settings and data as another report suite. When classifying a variable, give the user three options: Link to an existing report suite (share the settings and data)Copy the settings and data from another report suite. [This should...

Currently, when creating a report suite from a template, only some of the settings are copied over. Other settings such as SAINT classifications and pathing have to either be manually configured or manually copied over by Client Care. It would be tremendously helpful if all settings were copied over...

The login screen currently defaults to SC14. For companies on SC15, this is kind of annoying. You have to remember to switch to SC15 and if you don't, you have to log out and then log back in.Simple solution:- Set a cookie each time someone logs indicating which version they selected- Default to tha...

We used a slightly different approach for this: - A VISTA rule populates a single prop with a timestamp of the most recent 15 minute time period (e.g. June 1 11:00 PM -- but as GMT timestamp) - SAINT classification categorizes the timestamp by day, hour, weekday/weekend, section of day (e.g. early m...

Possible solution: If viewing multiple, report suites, include a pull-down (ideally a combo box with AJAX auto-complete functionality) for choosing which report suite to use for the variable names. If the calculated metric is not defined for that report suite, show warning message.

Make it easier to compare time periods. For example, setting up automated (or on demand) week/week, month/month or YTD compared to same period prior year.Problems with current functionality:- You can select "Last Week" or "Last Month" but no way to indicate prior week/month. i.e. You have to use the...