Good call. I think one way to do this would be to have a parameter
setting panel above the report. You set all the parameters you like,
which get 'remembered' so to speak, then run the report - rather than
adding a metric, waiting, changing the date range, waiting, and so on.
And it'd be nice to select which report suites the IP-exclusion should
apply to. We have report suites for our release candidate site versions,
and development versions; we want to include our internal traffic for
those, but exclude it from Live/production reports.
We're looking at using a relatively new search engine for some paid
search work, and they are not listed in the drop-down box under "Search
Engines" for paid search detection in the admin console. At the moment
that means they'd be treated as a regular referrer and not included in
the search engine reports, so we'd like the ability to add these guys to
the list, just for our own reports.
"None" is metric-dependant. If you're looking at a custom conversion
report and revenue is on there as a metric alongside instances, you'll
get "None". First thing I'd suggest is checking if the report you're
looking at really requires whichever metric is showing the "None"
values, and if it does, try simply filtering by -None. Failing that, I
do agree that it'd be nice to have the option to explicitly turn off
None, on a per-report basis.
Does the browser really make a difference or am I imagining it?
SiteCatalyst seems to work considerably faster in Webkit-based browsers
like Chrome and Apple's Safari than it ever did in IE. Eric, have you
added any new custom or calc metrics that might be slowing things down?
Here in London I'm not seeing the same problem, but we do get a slight
performance slow-down in the afternoons.