Essentially, you load a different domain in IFRAME which sets the cookie. IE requires you to set a P3P header for it to work properly. And Safari required the visitor to have visited the website before. To get across this, you first load a different domain in IFRAME and then have form submit to that domain (with target being IFRAME). (IE7 opens a new window in this case since it doesn't recognize target attribute). Crazy cross-browser issues. I wish there were a simpler way of doing cross-domain tracking.
This is a new feature that we have released today! I'm excited about this because it solves pain-point of a lot of our users.
No, VWO doesn't dynamically optimize because statistics become s really complicated once you try to model such optimization. As far as I know Genetify (or any other tool out there) doesn't have a statistically valid method of optimizing the test (while it is running).
The math required to do such optimization while maintaining statistical validity is beyond me, at the moment. (Though I am actively researching on this front. Any pointers/links will be appreciated)
Essentially, you load a different domain in IFRAME which sets the cookie. IE requires you to set a P3P header for it to work properly. And Safari required the visitor to have visited the website before. To get across this, you first load a different domain in IFRAME and then have form submit to that domain (with target being IFRAME). (IE7 opens a new window in this case since it doesn't recognize target attribute). Crazy cross-browser issues. I wish there were a simpler way of doing cross-domain tracking.