How to Setup Two GWO MVTs on the Same Page

This is a follow up post to the one I did yesterday, where I explained how to go about running a Google Website Optimizer a/b test and multivariate Test on the same page. I mention this because I intend to skip a lot of the steps I explained in that post already to avoid repeating myself.

The Problem

Consider the following hypothetical scenarios:

• You have two areas of one page that you want to test different variations of, each of which have separate goals, so you would like to run two separate Multivariate Tests on the same page to track the results separately.
• You have a site wide element that you would like to test, and a page specific element that you would like to test.

In both of the above cases you will need to setup two multivariate tests on the same page.

The Solution

In the above image, I point out that you have to mentally split the page into parts, where the number of parts is equal to the number of tests you want to run on the page. In the image I have Page A, which is split into two pieces for the two tests that will run on it, which are Part A for Test A and Part B for Test B. In order to setup two tests on the same page you must encapsulate the test in to it's corresponding part of the page. The tracking scripts however can all go at the bottom of the page in no particular order.

For help on setting up the tests in the GWO console, read the steps laid out on how to setup a Google Website Optimizer a/b test and multivariate test on the same page, they are pretty much the same.

The Example

This is my example page.

The Conclusion

In the above image I have a screen shot of my example page of two tests on the same page with an interesting twist to make a point. The two tests have two sections, and the twist is that the two tests share a section name "Header 1".

Also on the test page, you will notice that I call utmx_section("Header 1") and utmx_section("Header 2") on the page twice, once at the top of the page after the first control script, and once towards the bottom of the page, after the second control script. The reason for this is to show you that the utmx_section function only works of the test of the most recent control script to be loaded.