Deprecated: Assigning the return value of new by reference is deprecated in /home/ophir/prusak.com/wp-settings.php on line 512

Deprecated: Assigning the return value of new by reference is deprecated in /home/ophir/prusak.com/wp-settings.php on line 527

Deprecated: Assigning the return value of new by reference is deprecated in /home/ophir/prusak.com/wp-settings.php on line 534

Deprecated: Assigning the return value of new by reference is deprecated in /home/ophir/prusak.com/wp-settings.php on line 570

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home/ophir/prusak.com/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home/ophir/prusak.com/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /home/ophir/prusak.com/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /home/ophir/prusak.com/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /home/ophir/prusak.com/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home/ophir/prusak.com/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home/ophir/prusak.com/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /home/ophir/prusak.com/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /home/ophir/prusak.com/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /home/ophir/prusak.com/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /home/ophir/prusak.com/wp-includes/wp-db.php on line 308

Deprecated: Assigning the return value of new by reference is deprecated in /home/ophir/prusak.com/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /home/ophir/prusak.com/wp-includes/cache.php on line 431

Deprecated: Assigning the return value of new by reference is deprecated in /home/ophir/prusak.com/wp-includes/query.php on line 61

Deprecated: Assigning the return value of new by reference is deprecated in /home/ophir/prusak.com/wp-includes/theme.php on line 1109

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /home/ophir/prusak.com/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /home/ophir/prusak.com/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /home/ophir/prusak.com/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /home/ophir/prusak.com/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /home/ophir/prusak.com/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /home/ophir/prusak.com/wp-includes/http.php on line 61

Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /home/ophir/prusak.com/wp-settings.php:512) in /home/ophir/prusak.com/wp-content/plugins/wordpress-automatic-upgrade/wordpress-automatic-upgrade.php on line 92

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/ophir/prusak.com/wp-settings.php:512) in /home/ophir/prusak.com/wp-content/plugins/wordpress-automatic-upgrade/wordpress-automatic-upgrade.php on line 92

Strict Standards: Redefining already defined constructor for class ftp_base in /home/ophir/prusak.com/wp-content/plugins/wordpress-automatic-upgrade/lib/ftp_class.php on line 56

Strict Standards: Redefining already defined constructor for class ftp in /home/ophir/prusak.com/wp-content/plugins/wordpress-automatic-upgrade/lib/ftp_class_sockets.php on line 8
Revenue Tracking with Google Website Optimizer

Prusak.com

Online Since 1996

Revenue Tracking with Google Website Optimizer

Posted by ophir on February 28th, 2008

I came across this question on the Google Website Optimizer group:

Hi, I run a website where I sell 7 different products each at a different price level.
I am wondering whether there’s a way so that I can track the changes I make in terms of their effect on my overall revenue?

From a marketing perspective, this raises an interesting question.
Will the test version with the best conversion rate always bring the most revenue?

If what you are testing has no relationship to what you are selling, then probably yes.

On the other hand, lets say you want to test what product you should be highlighting.
In such a case, measuring overall revenue makes sense.

So here is how I would do it…

The first thing you want to do (which you should be doing in any case, even if you’re not tracking revenue) is apply the Google Website Optimizer + Google Analytics hack.
This provides you with all of the Google Analytics data for each one of your combinations.

Next, you need to use Google Analytics E-commerce Tracking.
Here are the instructions from Google:
Tracking e-commerce transactions in Google Analytics

If you’re just testing a single page, this alone should be enough as you can get the revenue data on a per page basis (Pageviews * $ Index).

But what if you’re testing a site wide change, like the “add to cart” button or “product of the month”?

You can easily get revenue data for each combination using the Google Analytics e-commerce tracking by simply over-riding one of the item fields in the addItem call.

Here’s the original example:

pageTracker._addItem(
   "1234",                           // Order ID
   "DD44",                           // SKU
   "T-Shirt",                        // Product Name
   "Green Medium",                   // Category
   "11.99",                          // Price
   "1"                               // Quantity
 );
 

I’m going to put the GWO combination number in the SKU field.

Here’s the modified example code:

var combo = ‘combo - ‘ + getcombo(); // getcombo function from the GWO + GA hack.

pageTracker._addItem(
   "1234",                     // Order ID
   combo,                      // SKU
   "T-Shirt",                  // Product Name
   "Green Medium",             // Category
   "11.99",                    // Price
   "1"                         // Quantity
 );
 

Then simply use the GA e-commerce report for product SKU performance.

That’s it!

2 Responses to “Revenue Tracking with Google Website Optimizer”

  1. Gavin Doolan Says:

    Interesting technique, I wonder though if this is the best method? This is probably due to the fact that the article is old now, but on Eric Vasilik’s blog he shows a method of inserting the utmx combination value in the _utmv cookie so you could just go to Visitors -> User-Defined and E-commerce tab to see revenue associated with a combo and p/visit value etc.

  2. ophir Says:

    @Gavin

    Putting the GWO combination number in the user defined variable is also a valid solution.
    This of course is assuming you’re not using it for something else.

    Each method has it’s pros and cons.

    I myself have used the setvar method in a couple of instances where we couldn’t make changes to the actual GA eCommerce code.

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>