| Attribute | Average |
|---|---|
| Features | 5 / 5 |
| Reliability | 5 / 5 |
| Ease Of Use | 5 / 5 |
| Documentation | 1 / 5 |
| Vote Count | 1 |
Google Website Optimizer is a free multivariate testing service that allows you to rotate different segments of content on your key sales pages to work out which sections and combinations convert the best. This module provides an easy way to insert the appropriate javascript code on your testing and... [More...]
| Maintainer: | Schoonzie |
| Links: |
|
| Categories: | Administration, Statistics, Third-party integration |
| Version | Date | Files | Release notes |
|---|---|---|---|
| 7.x-1.4 | 2011-Oct-18 | Download | Recommended |
| 6.x-1.3 | 2009-Jun-23 | Download | Recommended |
| 5.x-1.2 | 2009-Apr-25 | Download | Recommended |
| 7.x-1.x-dev | 2011-Oct-18 | Download | Development |
| 6.x-1.x-dev | 2011-Feb-25 | Download | Development |
Options: Add a review
Overall, this module helped immensely getting my test up and running quickly.
Google's Website Optimizer is a handy tool to compare how user's react to different page formats by randomly switching out page variations and measuring how many times a page variant makes its way to the target "Call to Action" page. GWO requires JavaScript in the head portion of the page, which is difficult to do dynamically in Drupal for specific pages and not others. After trying unsuccessfully myself, I found this module and installed it. It allows the user to easily take the Google generated code and insert it via the module into the appropriate pages.
The only problem I had was that I was running two different tests (two different pages, each with its own variant - four pages total) that targeted the same goal page (which requires its own tracking code). What I found out is that this module only drops the tracking code for one test or the other on the target page - not both. So I had to make two different target pages, one for each test. This restriction may be a Google issue, or it may be me. I'm not sure.
In any event, after trying for many hours on my own, this module allowed me to get Google to verify the site and my test was up and running shortly thereafter.
There was no documentation for this module that I could find, so it scores low there. However, Google provides decent (not great) documentation and there aren't a lot of options to worry about once you define your test.
The only problem I have found so far is that it doesn't place the code immediately after the opening head tag as recommended by Google, but I am still able to capture data from my test. This issue also shows up on the bug tracking list for this module, so they are aware of it.
By the way, you should define your test through Google first. After installing the module, activate it and configure permissions for who can use it. You will find it located under "Configuration->Content Authoring".
