You can hire my services

I am Ben Lang an independent web conversion specialist with over 20 years of experience in IT and Digital and 12 years Conversion Rate Optimization (CRO) know-how. I provide a full analysis of your website conversion performance and the execution of tried and tested CRO optimization exercises through AB testing, split testing or MVT (Multivariate testing ) deployed to fix your online conversion issues. Contact me at https://www.benlang.co.uk/ for a day rate or catch up with me on LinkedIn

Maxymisers Visual Campaign Builder (VCB) test tool

Updated: 19th August 2014.

If you've been using Maxymiser for your MVT testing in the past you may already appreciate this very competent testing tool. Recently the Maxymiser team have developed a new feature that I've been very keen to get my hands on, their Visual Campaign Builder, aka, VCB.

What is it?

Well essentially it's a way to build and launch your own tests very quickly using the MaxTest solution (and leverage the MaxSegment solution too if you have that) using a WYSIWYG on page wizard. You navigate to the test page, create a new test campaign, create new variants, drag and drop assets, change copy and content, assign an existing Action for action tracking and then publish it.

I've trailed two tests to date, one where I'm introducing a new banner to a page and another where I've embedded a YouTube video. Reporting is exactly the same as conventional testing whereby you log into the Maxymiser report console.

Where is it?
Log into the Maxymiser console and navigate to the Campaigns page, you will see a button for the VCB in top right side...

Once it's enabled for your site, when you click the VCB link it should the option to create or edit an existing campaign...


And how do I use it?

Well you should of course get the Maxymiser team to talk you through the first couple of set ups for VCB testing but here's the easy process in summary...



1. Create Campaign.
2. Give it a name.
3. Choose Audience. Here you can target visitors by device, browser, geography, behavior or just choose to test with all visitors.
4. Select the Page(s) you wish to test on by page URL. Cut & Paste the URL into the the URL box provided and add to campaign. At this point you may want to 'Include any query string parameters' or 'Include both HTTP and HTTPS protocols'
5. The next step is the Content creation step for your test. Here you can either add or remove content or create alternative experiences for your test variants. Tip: This is the tricky part of the whole endeavor and I strongly recommend you test how your variants are looking in all browsers and devices you wish to test against.
6. Next step is to select the Actions. Give it a primary action from your drop-down. If you don't have an appropriate action to track on your test you will need to speak to Maxymiser. This can be a stumbling block for getting a test straight out there but if you've got a suite of test actions you've used before there's potential to re-purpose those for a VCB test as long as it doesn't conflict with any other tests you may be running at the same time.
7. Review & Publish. From here you're more or less going through the normal test publishing process, for example, adding change comments and going via the publishing console to send your test live. Tip: You may get a warning about new pages being mapped and might take an empty publish first before you can publish your VCB test.

That is it in it's simplest form.

Good luck and happy testing : )







Click To Call testing

Consious I havn't posted for a bit. Apologies for my tardiness, just busy with the day job : )

Dead quick summary of our first dedicated smartphone app MVT test using Maxymiser. We were introducing a 0330 phone number on the app for the first time. In the UK this meant that it was actually not too expensive to use your mobile phone to contact our call centre. We wanted to get the best possible call to action for the click to call button from the outset. So we engaged the testing team and we tested several competing button designs and discovered that a nice green button  that closely mimicked the native call button of a smartphone produced the highest click/call volumes. This acheived a 16%+ uplift in fact over competing designs. The take away from this I guess is that familiarity drives positie behaviour.

Unequal visits in Google Experiments

Having run my new Google Experiment for a couple of weeks I have noticed that the distribution of traffic between the default and test page has become hugely unequal.
After a bit of trawling around the web I discovered that this was most likely caused by Google applying a Multi-armed bandit test approach (here)

Google states "a multi-armed bandit is a type of experiment where:
the goal is to find the best, or most profitable action, and
you learn about payoff probabilities as the experiment progresses."

"Once per day, we take a fresh look at your experiment to see how each of the variations has performed, and we adjust the fraction of traffic that each variation will receive going forward. A variation that appears to be doing well gets more traffic, and a variation that is clearly under performing get less."

So essentially Google are no longer retaining an equal traffic share for each variation in the test. If a variation is perceived to be doing worse than another or the default it gets less number of visitors. Equally if a test variant is doing better than another variant or the default it gets a greater share of the traffic. This is fine and will be rewarding for people who want a quick win during experiementation time but it's harder to swallow for those that have been doing conventional A/B or MVT testing up until now. In the past Google have let you adjust test weighting manually and it would be good to offer an overide option whereby the Multi Arm Bandit approach can be disabled by those who want clarity of their tests.

Google Content Experiments

Google has announced its moving away from Google Website Optimizer to 'Content Experiments'. This effectively means Optimizer has been fully integrated into the new version of Google Analytics. There are as ever positives & negatives involved. First off it means less coding to be uploaded to your test pages. Great. On the downside tests are now wholley driven around Google Goals. In the past I've found setting up goals to be hard work and they dont always work so coupling testing to goals fills me with concern. Finally I think Google have missed a trick. I think they had an opportunity to make their testing tool a 'tagless solution' under this approach. If they worked in a bit of dynamic javascript into their normal analytics tags you would never have to upload test code for each new experiment. This would greatly increase peoples abilities to conduct testing without further IT input, essentially the holy grail of professional testers. I'm just lining up my 1st test under this regime, I'll you know how it goes.

1st iPhone MVT test. So proud...

Had to share this because, well frankly it was a ball ache & also there is little if not naff all documented on the internet about this (at time of writing). Basically today I managed to get Google Optimizer (now branded as Google Experiments)  to work for MVT testing on an iPhone landing page and also circumvent all the issues that go with coding GWO tests on a HTML & jQuery page. The test page in question is here: 
Essentially it's very hard to do conventional MVT testing on mobile pages as the use of jQuery etc can really complicate straightforward test building & coding. My tip is to knock out all jQuery references such as 'data-role' and make inline requests to restore your CSS. I may add further detail in a later post but this mobile testing is in its infancy as far as my experience is concerned.