I just updated by SiteCatalyst tracking so that the image request is under a first-party cookie. Fortunately my hosting provider made it very simple to apply the CNAME. If you look at the image request you will see that the domain is k.willeitner.org rather than the kwilleitner namespace I had on the 2o7.net cookie. The request is still being sent to 2o7.net but under the friendly alias of k.willeitner.org.

Why switch to a first-party cookie?
First-party cookies are more accepted than a third-party cookie. This is because it is under the same domain as the site that you requested rather than a possibly unfamiliar domain. Also, the 2o7.net cookie is a known tracking cookie which makes it more suseptable to being nuked by security software that you might have on your computer. Additionaly, if you start getting too many cookies on the 2o7.net domain then cookie bumbing or cookie size could become an issue.

In the end, first-party cookies are the way to go. For me it was free because I don’t have any tracking on secure pages but if you did need tracking on secure pages you can buy an SSL Certificate that Omniture can upload to it’s servers. This is done so that the request is secure and there aren’t any security popups in the browser. These usually cost a couple hundred to a thousand bucks and can be bought from a certificate authority like VeriSign, NetworkSolutions, Thawte or others.