Product Price Point Testing Using Google Website Optimizer

I've just launch my first price point test using G OPtimizer and a new clickbank product. Here is how I did it:

First, I setup 2 addional CB products which are actually the same product just different prices. I use DLGuard download manager so I had to do the same thing there, point to the new CB product numbers for each price point.

The three price points are 22.00, 12.99, and 9.00.

The object is to determine which combination of volume x price creates the best revenue stream (expenses are the same for all three price points).

In Optimizer, I sectioned off (for those new to this blog see my terms post here) the portion of the sales page that had buy links and the price stated.

I use a link > redirect to help organize my buy link so I created 2 more of them (/buy.htm, buy9.htm, buy12.htm) so each one refreshed to the appropriate CB download link I created in DLGuard. For those not using DLGuard, you would simply put your different product link associated with each price point on the different pages. This can also be done directly in the variants if you use a direct buy link.

The variants each sectioned off three links to purchase: the buy now button, the image of the ebook cover, and the "buy right now" text. You can see it here:Buying a Mattress.

Thats it. All incoming traffic (see here for post explaining what traffic Google Optimizer measures)will be divided up among the three prices...and eventually we'll see a clear winner.


meegwell

G Optimizer Split Test Setup & DLGuard

The first problem I ran into when setting up my first G optimizer test had to do with the way I have DLGuard setup. At the advice from Sam at DLGuard, I set the download security software up so that the "thank you" pages are all on the same domain as the DLGuard software itself - this is necessary - and not an issue if you are dealing with one website. My multiple sites that sell products all direct the transactions through a single centralized domain w/ DLguard on it. This works fine.

G optimizer requires, at this point, that the "test" page (the page you are running a/b tests on) & the Conversion page (the page that measures the success of your a/b test) be on the same domain.

In my case, and many others I'm sure, the conversion page was my 'thank you' page for product downloads - on the centralized domain.

How I resolved this: this issue came up just last night as I setup my first Gooogle Optimizer test, so maybe I'll eventually figure out a better way to resolve it. For now, what I did was add some text to the download page (the page itself and the customize area of the DLGuard "box") telling the customer that they NEED TO CLICK HERE after downloading in order to get the password for the eBooks they just downloaded. I normally just gave them the password right there.

That clicks bring them to a "thanks - the password is blah blah" page back on the domain I'm running G Optimizer tests on. So now Im able to use that new page as my Conversion Page in Optimizer. It will be a day or so before the Gooogle optimizer data kicks in so I'll see how that goes.

Why Are We Here?

About a week ago I was actually shopping around for A/B testers when I first heard about Google Website Optimizer. It was definately time for me to stop jumping from one new marketing project to the next, and begin fine tuning what I already had out there. I'm a big fan of stats, analytics, and such so I knew what I needed to do, I just didn't have the right tool.

Over at the Warrior Forum I made a post asking what A/B test tools folks used and someone said Google Optimizer. I searched and soon discovered it was an invite-only beta so I signed up to be a tester. I read some info. on it and knew that G Optimizer was the tool I needed. I just needed to be patient and wait for the invite.

The more I thought about it the more excited I got about split testing every little aspect of my landing and sales pages...I checked my spam filter twice as much as usual in case the invite got sucked up there. Sure enough, it did. I found it last night and spent the next couple hours setting up my first test. Note: this would have taken much less time if I was not using DLGuard on a separate domain from the site I was testing...and since that was my first of a few stumbling blocks, I'll focus on that issue for my next post.

I'll make separate posts for each major issue I run into, resolved or not, as I jump into the world of G Optimizer...