Re:Denial, anger, bargaining, depression, & acceptance: The ...
by thenomad on Thursday September 20, 2012 @04:09PM
(#4550427)
This is a great piece. I'm doing a lot of testing for advertising right now, and the emotional rollercoaster - no matter how sanely you attempt to approach it - can be pretty intense. It's good to see someone writing about that side of the process!
Re:Denial, anger, bargaining, depression, & acceptance: The ...
by bjpless on Thursday September 20, 2012 @02:58PM
(#4550098)
For our logged in user A/B testing (often relating to email), we've built an in-house solution that uses a MOD based system to track group performance (as opposed to storing each group member in our databases).
Pretty clever implementation by the data scientist on our team.
Re:Denial, anger, bargaining, depression, & acceptance: The ...
by bjpless on Thursday September 20, 2012 @02:54PM
(#4550080)
We're currently using Google Content Experiments. The Pros are that it's incredibly easy to get a test started thanks to the presence of Google Analytics scripts in the rest of the website. The major Con is the lack of true multivariate testing.
We experimented with Optimizely but had a bad experience. It seemed as though their javascript was synchronous and blocking. We may have been able to customize that but did not dig deeper.
Re:Denial, anger, bargaining, depression, & acceptance: The ...
by scoremotive on Thursday September 20, 2012 @09:01PM
(#4551649)
Another flaw in Google Content Experiments (which was mentioned in the article) is that it doesn't distribute traffic evenly. This is a big bummer with seasonal products/services where having the control start getting 80% of the traffic during a high conversion period makes the test useless. Overall, even though testing is easier in some ways, I definitely miss Google Website Optimizer.
Instead try a bunch of things, and see what sticks. Be curious, not invested.
Pretty clever implementation by the data scientist on our team.
We experimented with Optimizely but had a bad experience. It seemed as though their javascript was synchronous and blocking. We may have been able to customize that but did not dig deeper.