Agreed with @mikemiller Since this is possible in Key Metrics, it should definitely be propagated to all other reports

Awesome idea - would be great to have this as a view for all reports! Eg: internal search keywords in a prop/eVar...  love it!

Should at least be an option to change back to black on white. Sure white on black looks cool ... but why else have it there?

SiteCatalyst doesn't have a view into the computer but only the browser. This is thanks to the scope of JavaScript. If a user accesses the site in two different browsers on the same computer not only will they be counted as separate visits, but separate visitors too. One way around this would be to ...

I often copy code from one Custom Code module to another and then tweak it. Would be extremely awesome to be able to duplicate custom code.

I have literally dozens of 3rd party tags placed in my tag container and it's a complete mess trying to navigate them. Especially once you have more than 16, you have to constantly scroll up and down to switch between tags - very frustrating and terrible UX. It'd be great if the code section of the ...

Quick response: I'm using Processing Rules to segment traffic, but unfortunately they can't be used to block traffic due to a major flaw in their abilities. Could we also use the new Bot Filtering to exclude sets of IP addresses? I haven't tried this yet, but it seems like a good option. - Eric

Arg, it seems that even using Counter eVars "equals" doesn't work... Definite annoyance for a client right now

It's getting to the point that one of the few remaining reasons to use a prop is for pathing or time spent. Might as well have those two features enabled for all props!

Arg - it happened again! A client is half way through their campaign and just realized they didn't enable GeoSegmentation. This is a FREE feature! It should be enabled by default!! Constant annoyance indeed