I'm seeing situations in which many of my users without DW access are creating multiple segments (you don't need DW to create them), but then have no ability to delete them. Even as an admin, I don't have a way of deleting their segments, as they are creating "local" segments in SC15 rather than "gl...

Just got off the horn with ClientCare - they confirmed that, in SC15, if I want to edit or kill a segment I've created, I need to do it via Data Warehouse. Pretty clumsy... flash forward six months to a segment list crammed full of ad hoc segments that no one has used since. Would love to see a way ...

fully agree... it has actually been covered here:http://bit.ly/qjK0E5you might want to pile on over there.

It would be helpful to use processing rules to copy all incoming data to a second "master" report suite for roll-up reporting. This would remove the need for multi-suite tagging at the page level, and thus eliminate required secondary server calls. I understand this might affect revenue from Adobe's...

Big big agree. I constantly have to send follow up emails explaining the reports I just sent, specifically because of those often meaningless percentages...

(I know I've read other ideas about some of these issues, but I'm not aware of them all being housed in one location) The current implementation of the emailed HTML reports is too inflexible to be useful in many situations. For illustration, see the custom conversion report intended to measure conve...

Really disappointed not to see this listed as one of the "completed" items for SC15. This is a big need for our company - would love to get the right eyes on this.

I've been enabling (via customer care) some visit based serialized events, so that these events will only be recorded once per visit.Problem is, I can't find any evidence of these events being serialized in the admin console. There needs to be some visual acknowledgement in the admin interface that ...

Currently, you can restrict group access to specific s.props and events in the SiteCatalyst admin console, but you cannot restrict access to individual eVars. This is an extremely important need for us, and (I'm hoping) many others...

I think it's really integral to provide the single access metric for keyword reports. I'd also like to see single access for the referring domains report.