Adobe Target

This page explains how to connect Adobe Target with DXA to analyse split testing variations and personalization with DXA experience insights.

Key use cases

The following list highlights some key use cases for connecting Adobe Target with DXA:

• Identify hypotheses for split testing variations and experimentation.
• Identify causes of split testing failures and successes by visually comparing performance using the Smart Selection Heatmap background and Session replays.
• Benchmark and analyse split testing variations using DXS and experience signals by creating Segments for Adobe Target experiences.
• Move from iterative testing to innovative testing.

Requirements

Adobe Target must be deployed on a page alongside DXA.

Experiences and multi-variant split tests are tracked automatically with response tokens.

Configuring the Adobe Target data connector

In the DXA portal:

1. From the navigation bar, click the Connect drop-down menu.
2. Under Data Connectors, click the Configure Data Connectors button.
   Data Connectors Settings appears.
3. From Data Connectors Settings, click the Split Testing tab.
   The Adobe Target data connector appears.
   
4. Select Adobe Target Integration Enabled.
   The API Version drop-down menu appears.
   
5. In the API Version drop-down menu, select the version of At.js you are using. The following versions are available:
   • 1.0: At.js version 1.x
   • 2.0: At.js version 2.x
6. Click the Save button.
   The Adobe Target data connector is enabled.

Implementation

Enable response tokens

To allow Adobe Target to share metadata with DXA, you must enable the following response tokens in Adobe Target:

• activity.id
• activity.name
• experience.name
• experience.id

Deploying Adobe Target via tag manager

To enable DXA to use the Adobe Target response tokens, you must add the DXA/Target Library footer code to the Target library. To do this:

1. In Adobe Target, in the Setup tab, go to Implementation.
2. In the Implementation Method section, select at.js.
3. Click Edit at.js Settings.
   
4. In Library Footer, paste the relevant DXA/Target Library footer code depending on the version of At.js you're using.
   
5. Go back to Implementation and click the Download at.js button.
   
6. Redeploy the At.js file through your tag manager.

Deploying via Adobe Launch

1. In Adobe Launch, create a new rule or modify an existing rule that executes on page load.
2. After the action that loads Adobe Target, add a custom code action called "Send Response Tokens to Decibel". To do this:
   • Under ACTIONS, click the + button.
   • In the Extension dropdown, select Core.
   • In the Action Type dropdown, select Custom Code.
   • Rename the custom code action Send Response Tokens to Decibel.
     
   • Depending on the version of At.js you're using, paste the relevant DXA/Target Library footer code in a text editor.
     
   • In Adobe Launch, click Save.
     In the image below, the Send Response Tokens to Decibel action uses both a core extension and custom code action:
     

Decibel/Target Library footer codes

For At.js version 1.x:

(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);
  }
})();

For At.js 2.x:

(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);
    }
})();

Using the Adobe Target data connector

After enabling the Adobe Target data connector, you can use Adobe Target Segment filters in DXA.

To view Adobe Target Segment filters:

1. On the navigation bar, go to Define > Segments > Create.
2. Under Segment filters, click Add filters.
3. Click the Integrations tab.
4. On the left-side menu, click Adobe Target variation.
   
5. Click the Please select ... text box.
   A list of Adobe Target Segment filters appears.