“We changed to an orange button because it felt right …” or “our boss thought …” might have worked before. Today? No. Competition is getting tougher and data-driven decisions are becoming the norm. Haven’t you started A/B testing yet?
We give you 3 simple things to test to get you started:
1. Test retroactively
2. Test different existing landing pages
3. Test copy/value offer
1. Do retroactive tests – prove past changes
Remove or hide one or more previously added elements or features – to know for sure that the change is / was better. One of the easiest ways to get started with A/B testing is to test backwards/retroactively.
For example: You added images to the home page speaker presentation and in the A/B test tool you removed the images and thus created a test candidate retroactively.
That you do a retroactive test can also be based on the fact that it is actually easier to directly implement your test idea on the site and much smoother in a test tool to remove elements/functions than the other way around.
Retroactive testing is also a great way to get testing into your organization if you, like many others, have difficulty getting time/budget over for a thorough A/B testing work based on data analysis, formulating test hypothesis, designing test candidate, code and set up the test.
Here’s how we did a retroactive test
Namnband wanted to sell more online. We tested whether a function to rate products could increase confidence and thus increase motivation for purchases. We added the feature live on the site to remove it in our test candidate in the test tool. The test was run on all product pages at the same time.
The only bad test is where you learn nothing
The result: No change in sales in this case – which gave new insights and led to new test candidates.
2. Test different landing pages and see which one converts
How well does your landing page really work? It may not always be an easy question to answer as it requires that you have something to compare with.
Testing different landing pages gives you valuable insights into what your visitors are triggered by. As a good first step to A/B testing, we can test existing pages rather than create new ones.
To make it more tangible:
- You drive traffic to a product page.
- You create a test.
- You divide the traffic between the product page and category page instead.
- Which landing page converts better?
Use your existing data to draw conclusions about whether your existing landing pages are converting. Based on this, you can formulate your hypotheses about which sites you want to test against each other.
With a few keystrokes, you have a test set up. See links below on how to set up a so-called Split URL test.
3. Test copy/value offer
This is simple and can take you far. Did you know that your visitors give you a few seconds to be convinced to stay on the site? This makes copy and typography important. Very important.
Your visitors will in a few seconds ask themselves the questions:
- Do you have what I’m looking for?
- Why should I shop with you?
- Can I trust you?
Read more about the model we use to analyse a landing page.
Testing your copy is a given input to start with A/B testing. We have all seen examples where words have had a big impact and increased the conversion by several hundred percent. This is perhaps wishful thinking, but examples show the potential of testing copy. Test everything from copy in headings, to buttons. Test the elevator pitch that describes who you are and what you do!
In most A/B testing tools, you can easily change both appearances and copy in their WYSIWYG editor which does not generate the finest code but does the job of getting started with testing.
Time to test – what tool?
There are hundreds of different testing tools, they have different functionalities, pros and cons.
To mention some of the closer 70:
- Optimizely (free for limited traffic, 50’000 visitors per month)
- VWO (free for limited traffic)
- Google Content Experiments (free but not compatible with GTM)
- A/B test via GTM (free with unlimited traffic – like this)
What is your biggest challenge in getting started with testing?