Adobe Target

The Adobe Target data connector allows you to connect Adobe Target with Decibel to analyze split-testing variations and personalization with Experience Issues.

Note: The Adobe Target data connector does not work retrospectively. DXA collects and aggregates Adobe Target variations each time the script is executed. Adobe Target data is available in DXA once the data is processed.

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 analyze split-testing variations using DXS and experience signals by creating segments for Adobe Target experiences
Move from iterative testing to innovative testing

Prerequisites

Adobe Target must be deployed on a page alongside DXA.

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

Note: This method is only available if you are using at.js.

Configuring the Adobe Target data connector in DXA

On the navigation bar, go to Connect > Data Connectors > Configure Data Connectors > Split Testing > Adobe Target.
Select Adobe Target Integration Enabled.

The API Version dropdown menu appears.
In the API Version dropdown menu, select one of the following versions of the at.js you're using:
- 1.0 — At.js version 1.x
- 2.0 — At.js version 2.x
Click Save.

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:

Note: Response tokens are only available for at.js versions 1.1 and above.

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

Deploying Adobe Target with a tag manager

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

In Adobe Target, in the Setup tab, go to Implementation.
In the Implementation Method section, select at.js.
Click Edit at.js Settings.
In Library Footer, paste the relevant DXA/Adobe Target library footer code depending on the version of at.js you're using.
Go back to Implementation and click Download at.js.
Redoploy the at.js file with a tag manager.

Deploying with Adobe Launch

In Adobe Launch, create a new rule or modify an existing rule that executes on page load.
After the action that loads Adobe Target, add a custom code action called "Send Response Tokens to DXA". To do this:
1. Under ACTIONS, click +.
2. In Extension, select Core.
3. In Action Type, select Custom Code.
4. In Name, rename the custom code action "Send Response Tokens to DXA".
5. Depending on the version of at.js you're using, paste the relevant DXA/Adobe Target library footer in a text editor.
6. In Adobe Launch, click Save.

In the image below, the "Send Response Tokens to DXA" action uses both a core extension and custom code action: Added custom code action called "Send Response Tokens to DXA"

Using Adobe Target segment filters in DXA

When adding segment filters, click the Integrations tab.
On the list on the left, click Adobe Target variation.
Click Please select ....

A list of Adobe Target segment filters appears.

DXA/Adobe 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 version 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);
    }
})();