SessionCam can easily enable you to capture Experience information from Qubit when you are running an MVT or A/B Test. 

In order to get this working simply drop us a message on support@sessioncam.com, click here to raise a ticket, or use the link for "Need more help?" in our navigation menu.

Product Admin Users and the SessionCam Customer Success Team can easily activate this integration directly from the SessionCam console.

In order to set this up please the following instructions:

1. Log into SessionCam
2. Expand the "Manage" section in the navigation menu
3. Click "Account Settings"
4. Click the tab titled "Integrations"
5. When enabling the integration with Qubit for your A/B Testing you will need to go through the following steps below, this will give you the option to customise the data that is sent to SessionCam, you can chose to not send any customisation to see the most basic level of the integration.

Experience tracking

There are three different ways to track your experiences, depending on how much detail you want to pass to SessionCam. You can decide this for each experience individually. You will add these code snippets to the Advanced Mode in your Qubit triggers.

1. No additional data

If you decide to not add any additional information, then no code snippet needs to be added to the experience trigger.

In the SessionCam console you will see the data in the format below:

2. Experience name

You can choose to provide an experience name to help identify it in the SessionCam console. To do this you need to add the snippet below to your Qubit triggers. All you need to change is the string at the end of the second line.

window.__qubit.sessionCamData = window.__qubit.sessionCamData || {}
window.__qubit.sessionCamData[options.meta.experimentId] = 'Abandonment Modal'

In the SessionCam console you will see the data in the format below:

3. Experience name + variation name

You can also provide experience and variation names. This is the recommended option if you create an experience with multiple variations. It allows you to provide a name for each variation, so you can distinguish between them in the SessionCam Console. An example for an experience with two variations is shown below.

window.__qubit.sessionCamData = window.__qubit.sessionCamData || {}
window.__qubit.sessionCamData[options.meta.experimentId] = {
 expName: 'Sale Banner',
 variations: {
  335464: 'control',
  335465: 'variation 1 - banner',
  335466: 'variation 2 - overlay'
 }
}

 “variations” is an object, containing the names for each variation. You have to make sure the numbers match the variation IDs. Also remember to update them if you duplicate the Experiment. The variation ID is the last number in the URL when editing an Experience. Your control ID is always one number less than your first variation.

4. Find the sessions in the SessionCam Console

You can find a tutorial below that can guide you through filtering your sessions by the Qubit Variation details that are sent to SessionCam.

To start filtering for your Qubit A/B Tests you first need to add a new filter

Simply click on the dropdown menu to select the filter.

From the dropdown list select <b><i>Qubit</i></b>

On the next list you will see a list of the Qubit test names that you have set up. Click&nbsp;<span>on the name you want to filter for</span>

From the next dropdown you will want to select the "is" operator. This will allow you to then filter between the different variations.

The next dropdown menu will give you the option to filter for either the control of variation. Unless you have setup the advanced options of the integration which will allow you to custom name

Click <span class="component"><i><b>Apply</b></i></span>