This article describes how to add and configure the asynchronous or synchronous version of the Adobe Target tag, formerly called the Adobe Test & Target tag.

In this article:

Table of Contents Placeholder

Tag Specifications and Requirements

Specifications

  • Name: Target
  • Vendor: Adobe
  • Type: Personalization

Requirements

  • Adobe Marketing Cloud Account Service
  • utag, version 4.26 or above
  • If you will be using the Adobe Experience Cloud ID Service, add the Adobe Experience Cloud ID service before the Adobe Target tag.
  • If using Internet Explorer (IE), only version 9.x and above is supported.

Asynchronous Version Only

Synchronous Version Only

  • If you plan to load this tag synchronously, then you must also load the utag.js file synchronously. For information about acquiring the synchronous utag.js code, see Code Center.
  • Mapping is not supported for the synchronous version of the Adobe Target tag.

How it Works

Tealium supports both asynchronous and synchronous versions of the Adobe Target tag. The asynchronous version is recommended. If you have concerns about flicker, see the the Tealium Flicker-Free Test & Target solution, which allows you load the Adobe Target tag asynchronously and avoid the appearance of flicker.

Tag Configuration

Add the Tag

Click here to learn how to add a tag to your profile.  If you are using the asynchronous version of the tag, add and configure the Adobe Target Content Modification extension with the asynchronous tag.

Configure the Tag

Asynchronous

As a best practice we recommend using the asynchronous version of the Adobe Target tag. The differences in the configurations are dependent on which version you use.

Adobe Target Tag Settings_v17_v20.jpg

For the asynchronous version, set the following configurations:

  • Title
    • Required.
    • Enter a descriptive title to identify the tag instance.
    • Assign a unique name when using multiple tags by the same vendor.
  • Client Code
    • Required.
    • Enter the client name, such as mycompany in  mycompany.tt.omtrdc.net.
  • Timeout 
    • Required.
    • This setting is a fail safe in the event that the Target server is not responding.
    • Enter the amount of time, in milliseconds (ms), that you want the tag to wait for a response from Adobe before assuming the Target server is not responding.
    • Set to 5,000 milliseconds or greater to wait for a response from Target before assuming the Target server is not responding.
    • For optimal performance, do not set to a value less than 5,000 ms.
    • If there is no response from the server, the tag call is halted.
  • Adobe Org ID
    • Optional.
    • Used with the visitor tracking across Adobe Target and Site Catalyst.
    • This field allows you to track visitors across Adobe Target and Site Catalyst.
    • This configuration is found is the mbox.js file as follows:
       var imsOrgId = 'XXXXXXXXXXXXXXXXXXXXXXXX@AdobeOrg'
  • Auto Create Global mbox
    • Required.
    • Values are True or False.
  • Global mbox Name
    • Required.
    • Example: target-global-inbox
    • Adobe typically uses target-global-mbox for the name of the globally hidden mbox.
    • This tag automatically calls mboxCreate to create this mbox.

Additional configuration of the test content can be configured using the Adobe Target user interface.

When complete, configure the remaining settings as needed, and then click Next.

Synchronous

The synchronous version of the Adobe Target tag has a minor difference in configuration and requires a change to the Advanced Settings for the tag.

Adobe Target Tag Advanced Settings Synchronous.jpg

If you plan to load this tag synchronously, then you must also load the utag.js file synchronously. For information about acquiring the synchronous utag.js code, see Code Center.

For the synchronous version, configure the tag basics using the same information described above for the asynchronous version, with the following difference:

  1. Scroll down to Advanced Settings.
  2. Under Scope, use the drop-down list to select No Wait Tags.
  3. Under Synchronous Load Type, click Yes to load the library synchronously.
    A warning message displays.
  4. Click Continue to continue the configuration of the synchronous version of the tag.

Apply Load Rules

Load Rules determine when and where to load an instance of this tag. The 'Load on All Pages' rule is the default Load Rule. To load this tag on a specific page, create a new load rule with the relevant conditions.

As a best practice, Tealium recommends that you load this tag on all pages by leaving the default 'Load on All Pages' selected. For the asynchronous version, you can control the conditions under which your tests load using the Adobe Target Content Modification extension.

Set up Mappings

Mapping is the simple process of sending data from a data source in your data layer to the matching destination variable of the vendor tag.

For the asynchronous version of the Adobe Target tag, mappings are managed in the Static Params field of the Adobe Target Content Modification extension.

Mapping is not supported for the synchronous version of the Adobe Target tag.

Save and Publish

When configuration is complete, click Finish and then Save and Publish your changes.

Vendor Documentation