There are many simple plug-ins for SiteCatalyst such as time parting and previous page name that simply place values into variables.  With the advent of processing rules, it would be great if all of the functionality of these plug-ins could be transitioned into the processing rules so that coding is...

This is BADLY needed, and would make dashboards more usable. If only we could get this and MOM and YOY data in reports too, we'd be set.

At this time, the Genesis integrations will send data to the s.campaign variable and also automate the creation of classifications within the standard campaign report (or other eVar). The tracking codes generated by Genesis integrations such as DART or Email can at this time be pulled into Adobe's n...

When launching a new site to be tagged with SiteCatalyst, there can often be significant work in setting up automated Data Warehouse requests. The problem is that once a series of automated Data Warehouse requests are built and tested within a development/qa report suite, they have to be recreated a...

For many analyses in Discover I find that it is useful to copy a report to another workspace. But what if there are 10 reports that we want to copy to another workspace so that we can drop a different segment/filter over those same reports? This is why the ability to copy an entire workspace (as opp...

At this time there are list props, but nothing along that line for an eVar. So, I have seen many clients end up using the s.product variable for a lot more than just product reporting and measurement. It would be valuable if there were additional variables that functioned the same as s.products so t...

There's a plugin, getTimeToComplete, that will actually do this. You just config the plug-in to track the time between two specific custom events. If you wanted it for each visit you could just fire an event upon the initiaion of a new visit and then fire the second event on whatever your conversion...