With the launch of SiteCatalyst 15, we now have the abiltiy to trend up
to 5 key metrics at one time. I think that it is awesome that we can
trend up to 5 key metrics at one time, which is more than we have in SC
14. But I like the ability to trend more than 5 (somewhere around 7-10).
While the graph may seem a little messy, the problem that I am running
into is that our customers cross-shop between different segments a lot
and I have specific metrics for the different segments that I would like...
I like this idea and would like to take it one step further by having an
alert when Uniques Exceeded is reached and then another report for what
information in that variable was in the Uniques Exceeded bucket.
I agree with a lot of people that the new publishing widget is a great
new feature and is a great way to give information to people without
having them log into SiteCatalyst. Something that I would like to see to
be added to the widget is a configuration setting that allows the person
creating the widget to be able to hide the graph or the data of the
widget, which is similar to what can be done in a dashboard. This idea
is similar to allowing the user to change the size of the widget, but I
wou...
I think an alert would be a great start, I would like to have the
latency for each report suite exposed somewhere in the interface or on
customers.omniture.com, no matter how latent the report suite is.
I would like to see better documentation for APIs. All of the
documentation that I have seen so far for APIs are the technical
requirements, which is great. But I am looking for API business
documentation. For example, how are the API tokens charged and which API
calls are charged a token (ex. Report.QueueOvertime) and which ones are
not charged a token (ex. Report.GetStatus). This will make explaining
how APIs are charged to our development team.
