Decibel Insight
Knowledgebase

Adobe Target

In order to differentiate data for URLs with the same URL but different layouts/views that have been created using Adobe Target, you can use our Adobe Target Integration to configure the different layouts as variations. This guide will explain how to enable this integration. 

Contents

Enabling the integration in Decibel

To enable this option, simply navigate to Settings > Integrations > Split Testing > Adobe Target and tick the Adobe Target Integration Enabled checkbox, before clicking Save. You will also need to select the version of at.js you currently use. 

Enable Response Tokens in Adobe Target

In order to take advantage of the integration, you will need to enable some Response Tokens in Adobe Target. This allows Adobe Target to share metadata with Decibel.

Please Note: Response tokens are only available with at.js version 1.1 and above. If you are using at.js < 1.0 or mbox, please see Manual Tracking 

To enable Response Tokens, login into your Adobe Target instance and:

Deployment

Deploy via Launch 

In order for Decibel to take advantage of the Response Tokens enabled, you will need to fire a Custom Code action after you load the Target Library, as shown below:

This action should use the Core Extensions and the Custom Code Action, please use the Decibel/Target Library Footer Code

Deploy via tag manager

In order for Decibel to take advantage of the Response Tokens, you will need to modify the Target Library Footer to add the Decibel/Target Library Footer Code:

  1. Navigate to Implementation within the Setup tab in Adobe Target 
  2. Ensure at.js is enabled as the Implementation Method 
  3. Select Edit at.js Settings
  4.  Paste in the Decibel/Target Library Footer Code
  5. Finally, go back to the Implementation section and click the Download at.js button
     
  6. Finally, redeploy the at.js file through your tag manager. 

Decibel/Target Library Footer Code

If using any AT JS version 2.x, use the following code:

(function () {
    var mbox, tokens;
    // Add the adobe target response token event listener
    document.addEventListener(adobe.target.event.REQUEST_SUCCEEDED, getEventData);
    function getEventData(e) {
        // Check to verify all necessary information is present for the integration
        if (e.detail && e.detail.responseTokens) {
            // Store the token and mbox data
            tokens = e.detail.responseTokens;
            // Send the response data when Decibel is fully initialized
            if (window.hasOwnProperty('decibelInsight')) {
                decibelInsight('ready', sendAdobeEvent);
            } else {
                window['_da_ready'] = sendAdobeEvent;
            }
        }
        // Remove the Adobe listener
        document.removeEventListener(adobe.target.event.REQUEST_SUCCEEDED, getEventData);
    }
    // Send the ATDecibelTokens custom event when decibelInsight is ready
    function sendAdobeEvent() {
        var adobe_event = new CustomEvent("ATDecibelTokens", {
            detail: {
                tokens: tokens
            }
        });
        document.dispatchEvent(adobe_event);
    }
})();

If using AT JS version 1.x, please use the following code:

(function () {
  var mbox, tokens;
  document.addEventListener(adobe.target.event.REQUEST_SUCCEEDED, getEventData);
  function getEventData(e) {
    if ('detail' in e && 'responseTokens' in e.detail && 'mbox' in e.detail) {
      tokens = e.detail.responseTokens;
      mbox = e.detail.mbox;
      if (window.hasOwnProperty('decibelInsight')) {
        decibelInsight('ready', sendAdobeEvent);
      } else {
        window['_da_ready'] = sendAdobeEvent;
      }
    }
    document.removeEventListener(adobe.target.event.REQUEST_SUCCEEDED, getEventData);
  }
  function sendAdobeEvent() {
    var adobe_event = new CustomEvent("ATDecibelTokens", {
      detail: {
        tokens: tokens,
        mbox: mbox
      }
    });
    document.dispatchEvent(adobe_event);
  }
})();

Manual Tracking

Alternatively, manual tracking can be configured to capture individual experiences when Response Tokens are not an option. This is mainly for any customers still using mbox and not at.js.

The following Decibel method can be called on each variation that you want to track, such as below.

<script type="text/javascript">
if (window.decibelInsight) {
    decibelInsight('ready', function () {
        decibelInsight('sendIntegrationData', 'AdobeTarget',{id: 12345, name: '12345 control'});
    });
}
</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 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:

<script type="text/javascript">
if (window.decibelInsight) {
    decibelInsight('ready', function () {
        decibelInsight('sendIntegrationData', 'AdobeTarget',{id: 12345, name: 'New Homepage Original'});
    });
}
</script>

While the following code would need to be added to the variation:

<script type="text/javascript">
if (window.decibelInsight) {
    decibelInsight('ready', function () {
        decibelInsight('sendIntegrationData', 'AdobeTarget',{id: 12346, name: 'New Homepage Variation'});
    });
}
</script>

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

Within Adobe Target, the following needs to be done for each variation:

  1. Select a split test experience.
  2. Choose Code.
  3. Select Custom Code and enter code such as the above.
  4. Ensure that the Add code to the HEAD section is unchecked

Please note: Our Adobe Target Integration does not work retrospectively as it requires us to collect and aggregate the variations each time the script is fired.

Using Adobe Target Variations in Decibel

Upon collecting Adobe Target 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 Adobe Target 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 based on those users who have viewed that particular variation.