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:
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.
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.
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.
For the asynchronous version, set the following configurations:
var imsOrgId = 'XXXXXXXXXXXXXXXXXXXXXXXX@AdobeOrg'
mboxCreateto 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.
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.
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:
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.
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.
When configuration is complete, click Finish and then Save and Publish your changes.