Category: AB Testing

This integration is only available for Web projects

What to expect

This integration will allow you to segment and compare users based on Optimizely AB tests and variant groups they were exposed to.

What we collect

Dynamic Variables

Implementation

For Optimizely Full Stack (server side) please resume below.

You will need to be using the Full Stack Notification Listeners in Optimizely for this to work. (We are aware this feature is being sunset by Optimizely and we will be providing support for their new Feature Experimentation feature.)

These listeners will retrieve the Optimizely experiment and variation data and send them to Contentsquare. It will make use of Optimizely's Full Stack client-side SDKs (Javascript, React, React Native). Server-side Optimizely Full Stack SDKs are not supported by this integration.

Just after calling Optimizely's createInstance() method, run this code:

/*
 *Name: Optimizely Full Stack Server Side Tests CS Integration Start
 *Version: 1.0.0
 */
var optimizelyEnums = require("@optimizely/optimizely-sdk").enums;

function onDecision(decisionObject) {
    function callback(context) {
        if (!disableCallback) {
            disableCallback = true;
            if (window.CS_CONF) {
                CS_CONF.integrations = CS_CONF.integrations || [];
                CS_CONF.integrations.push("Optimizely Full Stack - v1.0.0");
            }
        }
    }

    var disableCallback = false;
    _uxa.push(["afterPageView", callback]);

    var csPrefix = "AB_OP_SS_",
        csKey,
        csValue;
    csKey = csPrefix + decisionObject.experiment.key;
    csValue = decisionObject.variation.key;

    window._uxa = window._uxa || [];
    window._uxa.push(["trackDynamicVariable", { key: csKey, value: csValue }]);
}

// Replace OptimizelyClient with the name of your Optimizely SDK Instance (where createInstance is used)
optimizelyClient.notificationCenter.addNotificationListener(optimizelyEnums.NOTIFICATION_TYPES.ACTIVATE, onDecision);
//Optimizely Full Stack Server Side Tests CS Integration End

On every experiment activation (method activate() or isFeatureEnabled is invoked), then an Optimizely's Notification Listener will execute, grabbing the experiment data from Optimizely and will forward them to Contentsquare.

For Optimizely Web (client side) please resume below.

Implementation Steps

Please go to the section How to request an integration to see the instructions to enable this integration. You can then return here once completed.

If you have already completed the step above then continue below.

Verifying it works

You can use the chrome extension to check the results are sent to CS

If you’re masking the real names then you can work out from the Optimizely UI what the numbers mean. If you select a variant inside of Optimizely, you will see both the tests ID and the variant’s ID:

You can show the real names by clicking on Settings inside of Optimizely and looking at the checkbox for Mask descriptive names in project code and third party integrations:

It will then look like this:

In Contentsquare you can find these variables by searching like this:

 

Forcing the right background

Inside of Optimizely go to the variant you want to analyse inside of Contentsquare by clicking on Experiments and then click on the campaign that contains the variant:

Click on the variant you want to analyse then click on Preview then click on Share Link

From the pop-up that opens click on copy link to copy it to your clipboard.

Inside of Contentsquare go to mappings and select the mapping with the page you ran the test against. Click on the page:

Click on the icon for more options:

Click on Url of page preview then paste the URL from Optimizely into the input box:

Now when you go to zoning and create a new zoning for the page, it will render the variant. Note – you must be logged into Optimizely when you create the new zoning.

You can now analyse the test variant in zoning – make sure to apply the segment for the visitors that saw the variant.