Generic A/B Testing

In order to differentiate data for URLs with the same URL but different layouts/views, you can use our A/B testing functionality and configure the different layouts as variations. This can be used for various split testing tools that are not included in our standard integrations.

Enabling Generic A/B Testing

To enable this option, simply navigate to Settings > Integrations > Split Testing > Generic A/B Testing and tick the Generic A/B Testing Integration Enabled checkbox, before clicking Save. You will now have a number of options for implementation.

Implementing Generic A/B Testing

The first option for implementing Decibel Insight's Generic A/B Testing Integration is to add the Decibel Insight API call individually to each variation that you want to track, such as the below, and this code will need to be implemented after the initial Decibel Insight tracking script.

You will need to replace the ID and name above with relevant information, and each different variation will require a unique ID and name to enable Decibel Insight to recognise these as different variations. This includes different variations of the same split test, so if you were running a split test called "New Homepage" and wanted to track the original and variation of this, you would need the following code on the original:

This will then allow Decibel Insight to collect these variations independently and recognise these as different variations.

The second option is to add JavaScript Code to the text box that can be seen in the image above, which can be found in the Generic A/B Testing Settings. This will add the JavaScript code to the Decibel Insight script and will need to be customised to only fire on pages that have variations, while it will also need to collect the ID and name of the variation from the respective tool using an on page variable. An example can be seen below:

The if statement would of course need to be replaced to only fire on pages with a variation, while ID and name will need to collect the information from a variable, otherwise Decibel Insight will collect every variation as the same ID and name.

Please note: Generic A/B Testing does not work retroactively as it requires us to collect and aggregate the variations each time the script is fired.

Trigger Variation Javascript

The Trigger Variation Javascript text box allows you to input JavaScript that will trigger the particular variation in Heatmaps, if this is available with your selected A/B Testing provider. Simply input the required JavaScript here that allows for variations to be triggered when visiting the particular page, and this will then "force" the particular variation that you are Segmenting by in Heatmaps. Similarly to the Opentext Optimist and Optimizely integrations, if you have this JavaScript added, you can simply create a Segment with the selected variation as a filter, then in Heatmaps browse to the page that contains the variation. You can then filter this page by the Segment that contains the respective variation, and this will trigger the variation to display on that page.

Using Generic A/B Testing Variations

Upon collecting Generic A/B Testing Variations, you can begin to use these by creating Segments based on them.

When creating a segment, in Segment Filters, click on the Integrations tab and navigate to Generic A/B Testing Variation and use the text box to search for a variation, such as in the image below.

Upon creating the segment, you can begin to filter Sessions, Heatmaps, Forms and other features in Decibel Insight based on those users who have viewed that particular variation.