...by the way, time between different places on our website is something people always ask about so it would be great if Adobe came up with something!

I'd actually like to be able to get at time between any two hits.I'd rather not be limited to just where we have implemented events as use cases will come up where we don't have events set. e.g. How long did it take to get from step 1 to step 2 of the application process?It would also be good it the...

One of the problems we've ran into in the past is where a particular data set has some outliers (e.g. one really high value).  The auto formatting then seems to use this to set the limits for the formatting.  It then doesn't show the nuances for the majority of values which are in a much narrower ra...

That's really useful - I couldn't figure out how to do this with segments but this works really well!I also found a work around for isolating the first page view:Use processing rules to set an event every time the page URL existedserialize the event to record once per visitThis means the event only ...

The centralized management/linking of segments and calculated metrics is great for speedy maintenance, but there are some key scenarios where I really wish I could break the connection to the master segment/calculated metric (e.g. so changing a segment no longer updated previously linked versions of...

For most normal dimensions you can only generate dynamic columns for the top 5 items.  5 is a very small number (I needed 8 the other day and was stuck!) - is there any chance of increasing this? If there are performance worries, even a small increase to 10 or 20 would be very useful! The feature ca...

Being able to hold ctrl and 'drag' to copy an element is a really useful time saving feature that works almost everywhere except the calculated metrics builder.This is particularly bizarre given ctrl + drag does work in the very similar segment builder It would be very useful if the calculated metri...

Literally had this issue today.   Accidentally deleted a container which contained loads of logic - no undo, no way to get it back

I haven't checked but I think list vars suffer in a similar way.  If they do they should be considered along aside this.

Hi there, just started looking at migration.  Are you able to explain why Lifecycle metrics now have to be manually implemented where they were automatically collected under v4.x?