I think that's fine, and that can be a caveat to using this.  This feature is awesome in what it does with unique visitor counting and persisting variables that have an expiration greater than a visit across devices, but splitting the visit (and thus visit-based reports) when s.visitorID gets set is...

Ben, you are awesome.  I was just talking you up with some of my colleages, letting them know how great this site is and that you are the person to thank for it.  Awesome!

One other HUGE point on this is the Traffic Sources reports.  If I come into the site without ever having logged in, and then I login, the visit gets split, and anything that happens after login will not give credit to the Traffic Sources reports.  The visitor is still considered as the same, so any...

Yeah I like this one, but maybe have it be a setting that the user can turn on (not something that has to be done by Client Care).

That's where I'm not sure what would happen with visitor stitching.  I'll have to do some testing to see if setting s.visitorID to multiple values treats them as separate visitors.  I still think that the pros outweigh the cons with visitor stitching, but it will result in some inflated visit counts...

This one is huge.  The main reason I'd say is that the current settings for the search keywords are rather lacking.  Putting this in an eVar will open up many more options.  It'd be nice to not have to do a hack to get this by using a processing rule (make the variable that captures this just like a...

Eric hit it on the head.

In addition to scheduling them, it'd be nice to be able to cancel them at any time, especially through a link in the daily email.

In addition, it can even show back end settings such as pathing, merchandising, delimiters for list props, hierarchies, and list vars (not ability to edit though), etc. Another nice feature would be a change log, so you can click on a variable and see when changes were made to the settings, and when...

A newer feature of events (although not documented in the help section or KB) is that you can give a counter event a value greater than one really easy without having to use the products variable.  For example, s.events="event1=5".  The only problem is that it cannot have a decimal value, and settin...