How to Integrate A/B Testing with Voluum, Redtrack, and ClickFlare

November 17, 2024

Bruno Agalliu

Bruno Agalliu

LanderLab Team

Introduction

In the world of digital marketing, AB Testing is essential to successful campaigns. LanderLab is now offering a great tool to set up AB testing on server-side, using the same URL to rotate different variations. With this update, users can A/B test their landing page and cross-check results within their preferred tracker.

Why Using A/B Testing with LanderLab

Most marketers use their own tracking softwares such as ClickFlare, Voluum or Redtrack to split test landing pages and in most of the cases that’s more than enough. However, there might be cases where split testing is not possible using a tracker. Premium traffic sources do not allow redirects, final destination URL needs to be the same as the landing page URL.

Here’s where LanderLab comes in handy with its server-side A/B testing, eliminating a redirect in the flow. You can read the more details on how A/B Testing works in LanderLab by checking this article. And the best part is that LanderLab can be integrated with most modern trackers.

A/B Test

The concept is easy, combinating LanderLab’s A/B testing with direct tracking method offered in every tracker. Trying to cover the basics, this article is going to provide information on how to implement this setup with ClickFlare, Voluum and Redtrack.

Setting up AB Testing with ClickFlare

Using ClickFlare’s direct tracking method can provide the perfect combination for this setup. Afterall, both platforms are created and developed by the same company, so it makes sense to have a better integration using both. Here’s an article to read more about direct tracking offered in ClickFlare.

There are 2 base steps to follow when implementing this setup and the same steps can be applied to Voluum and Redtrack. The first step is going to be how to define a new tracking parameter for reporting variantID in ClickFlare. 

VariantID in ClickFlare

In order to track variantID in our tracker, we will need to make some changes to the direct tracking script. The following script contains 2 variables that need to be replaced: “REPLACE_ME_CAMPAIGN_ID” and “REPLACE_ME_CUSTOM_DOMAIN”. Once ready, the whole code needs to be placed into LanderLab Settings > Custom Code > Header Section.

Setting up AB Testing with Voluum

Voluum is among the oldest trackers in affiliate marketing and it still has a large part of the market. We will still rely on direct tracking to report variantID into this tracker, using the same method as previously.

VariantID in Voluum

VariantID is added into the traffic source template at the bottom, but it does not really matter in which order it is being inserted. To be aligned with the same terminology, the same 2 variables need to be replaced: “REPLACE_ME_CAMPAIGN_ID” and “REPLACE_ME_CUSTOM_DOMAIN”. Copy Paste the following code into LanderLab’s custom code section, so the setup can be completed.

Setting up AB Testing with Redtrack

Last but not least, we’re going to implement the same setup for Redtrack. This tracker takes a good % of the market and it offers the same features as ClickFlare and Voluum.

But compared to the other 2 trackers, variantID needs to be allocated into a specific token since some of them are dedicated to system tokens. In this example, variantID has been allocated into sub18 and it will be reflected into the direct tracking script as well. 

VariantID in Redtrack

 

REPLACE_ME_CAMPAIGN_ID” and “REPLACE_ME_CUSTOM_DOMAIN” need to be replaced and the code is ready to be used in LanderLab.

Conclusion

With data now reported in your tracker, it can be actually measured how many events is a specific variant bringing in. Once you know the winning variant, just end the A/B testing and set it as main variant. Start split testing today with LanderLab while eliminating the risk of getting banned.

Want to Optimize A/B Testing with your Tracker?
Start your free trial now to use advanced A/B Testing with LanderLab using ClickFlare, Voluum or Redtrack!