Last week I discovered Google Website Optimiser. It’s a great free service that allows you to perform some simple A/B and multivariate tests on a website. And it helped me to understand more about what these types of tests are, and how to set them up.
First, A/B Testing.
Put simply, A/B testing is where you test two complete pages in order to see which one has the greater conversion rate to your desired target page.
To try this out, I created a copy of my original London for Free homepage and simply removed some text and links, saving it as index2. Then, using google’s wizard, I added some javascript code to each version of the home page as well as to the target conversion page (which I chose to be my bus tour page).
The idea was to see which page was the best version when it came to encouraging people to click the link through to the bus tour page.
All well and good, except that the quality of the google code was awful. Even though it validated for google’s purposes (allowing my test to run), the W3C validator hated it. I managed to fix two elements of the code but everytime I edited the third part, the optimiser rejected it.
So I persevered with buggy code just to see how this test would work. After running it for a few days, it became clear that the page with less options encouraged greater conversion to the bus tour page. Probably fairly obvious, but it was an excellent way to get my head around how to set up and run A/B tests.
Multivariate Testing
This is where, instead of having two complete pages to test, you select only one page and indicate the sections or elements of that page that you want to vary and test. You still need a conversion target but you can test say several different images and see which one encourages greater clickthroughs to the conversion page.
I removed the A/B test code from the home page and decided to run a multivariate test on it, varying the text in one particular style element, the subfeatures section. I created two versions of the text, both aiming to encourage users to click through to the bus tour page.
Then, using the google wizard, I dropped some javascript code into both the home page and the target page, and copied my “variant code” directly into the google dashboard. The variant code is effectively a second version of the “subfeatures” ID code snippet.
(Yet another reason for using div IDs in page designs).
I’ve now been running this test for over a week and though the results are interesting, what has been of most value to me is to be able to understand how easy it is to use the google tool and how multivariant testing works.
I need to try and validate this google code and will probably also extend the tests to include multiple variants and see how it goes.
That’s tomorrow taken care of, then