If Pages and Site Section are not part of at least one correlation then the drill-down icon does not show up, so I cannot drill down to eVars/Custom Conversions. Once I added a 2-item correlation between Pages and Site Section, the icon appeared on both reports and I can now drill to them. Hopefully...

Hm, I strangely was unable to get this to work. I switched to Arial Unicode MS and the Russian characters that are showing up in SiteCatalyst are still not appearing correctly in Discover. I tried several other fonts (Arial, Sans Serif, Lucia Console, Times New Roman, Courier New, etc) and was unsuc...

Already miss the Pathfinder report and I've been on v15 for only a couple of weeks. One of the most powerful Omniture reports, a true separator from Adobe's competitors. Please reinstate!

The current features (starts with, contains, ends with, etc) are nice, but having actual Regular Expressions would be even better! If this isn't possible, one great improvement would be to allow for IP Address ranges to be used. For example: Instead of creating a Processing Rule defined as:Starts wi...

This way we can set up Processing Rules but wait until just before the site goes live to enable them. It'd also be nice while QAing Processing Rule issues, we can simply disable one to see if the data comes in as expected.

It's nice to have the function to Copy All Processing Rules from one report suite to another. It'd be even nicer if we could pick and choose which Processing Rules to copy over.

Seriously! Super-disappointed to find this was not included in SiteCatalyst version 15 segments. Hopefully it's made available there and Data Warehouse soon!

Thanks Simon - Not every day that my ideas are considered "sensational!" =) I like the idea of a default dashboard with every report in it too. Unfortunately, we'd have to create it once for every company account. Would love to create an iMacros script that does this for me!

The only other timeframe that I might be interested in seeing is the ability to switch to a 24-hour timeframe. This would be good for times when new Omniture solutions are deployed. I still think 30 days would be good enough if giving us the ability to change the timeframe is difficult.

haha - of course the answer is 'let us choose!' But to me, that honestly seems unnecessary. IMHO 30 days is a good timeframe. If a specific variable hasn't been populated in the last 30 days, then it's a variable worth digging into. Is the reason that the variable isn't getting populated because it ...