Adobe Target tool

Information about creating the Adobe Target tool for deploying Adobe Target in Dynamic Tag Management. You can configure the library automatically (recommended) or manually.

<Web Property Name> > Overview > Add a Tool > Adobe Target

Field descriptions - Add a tool (Adobe Target)

The following table describes the fields and options on the Add a Tool page (and the tool edit page) for Adobe Target.

  • Tool Type

    The type of tool, such as Adobe Target.

  • Tool Name

    The name for this tool. This name displays on the Overview tab under Installed Tools.

  • Library retrieval method

    Specifies whether Adobe should manage your Adobe Target code automatically, or whether you would like to provide your own custom code manually.

Manual configuration method

You can manually manage the Adobe Target code. You can download the at.js or mbox.js file from the Target solution interface as follows:

  • Target Standard: Setup > Implementation > Download at.js
  • Target Standard: Setup > Implementation > Download mbox.js
  • Target Classic: Configuration- > mbox.js > Download

After you download the code locally, copy and paste the code into the editor field in the Library Management section of the tool settings. You have the option of hosting the code at a specific URL as an alternative to manually pasting in the code.

Automatic Configuration Method


This works for mbox.js only.

Dynamic Tag Management automatically retrieves the latest mbox.js code from your Adobe Target account configuration. If you select Automatic, you must either be logged in via the Experience Cloud, or you must provide a Client Code value described below.

Client code retrieval method

(Automatic method) A code unique to your Adobe Target account. It is required for your code to be provided and managed automatically by Adobe. If you chose the Automatic method, you must either be logged in via the Experience Cloud, or provide your Client Code value after selecting Manual as the retrieval method.

  • Client Code

    (Automatic method) The Client Code value can be retrieved from the Adobe Target solution interface as follows:

    • Target Classic: Configuration > mbox.js > Edit > copy value for Client.

    • Target Standard: Setup > Implementation > Download mbox.js > copy value for Client from within mbox.js file.

Library management - Adobe Target

Descriptions of the fields and options in the Adobe Target Library Management settings in Dynamic Tag Management.

Property > Edit Tool > Library Management

  • Load Adobe Target Library synchronously
    This option ensures the at.js or mbox.js code is loaded synchronously in the <head> section. It is generally recommended that you leave this option enabled. It is an Adobe Target best practice to load the code in this way.

  • Code Configuration
    Managed by Adobe: (mbox.js only) This option is equivalent to the Automatic configuration method available when creating the tool. This option loads the mbox.js code directly from Adobe.
    This feature optimizes the configuration process when using a manual method, because no more copying or pasting from the Adobe Target admin console is required.

    • You must be logged in via Experience Cloud or have provided the appropriate Client Code for this option to be available.
    • Clicking Check for Updates automatically checks for new versions of the mbox.js code within your associated Adobe Target account. If a new version is identified, you have the option to use it or retain the current version.

    Custom: You can manually configure the at.js or mbox.js code. Two methods are available to manually host the code in Dynamic Tag Management:

    • In DTM: Click Edit Code and paste the code in the editor. If you were using Managed by Adobe and switch to custom, the editor automatically populates with your mbox.js code. You can replace this with the content of the at.js library.
    • At URL: If your at.js or mbox.js is configured as desired, you can provide the URL to the file. Dynamic Tag Management consumes it for use in the Adobe Target tool.

Global parameters - Adobe Target

Descriptions of the fields and options in the Global Parameters settings in Dynamic Tag Management for an Adobe Target Tool.

Global parameters let you pass additional data to the global Adobe Target mbox, and also on a per-page basis via page load rules.

The parameters configured in Dynamic Tag Management do not override parameters already defined on the page, but instead appends and sequences to create maximum flexibility and customization on a per page basis.

Property > Edit Tool > Library Management

Element Description
Name Indicate the name of the additional parameter(s) you wish to pass to the global mbox.
Value Indicate the value of the additional parameter(s) you want to pass to the global mbox. The value is typically a data element.

Mbox rule example for Dynamic Tag Management

An example of how to place wrapping mboxes with built-in flicker handling via Dynamic Tag Management when an Adobe Target tool is installed.

This functionality currently uses the mboxUpdate method.

  1. Click Property > Rules > Page Load Rules > Create New Rule.

  2. Name and configure the rule.

    Step Info

    Configure the rule so that it fires only on the pages where you want to deploy the mbox.


    Adobe recommends load rules triggering mboxes at Top of Page to ensure the default content is hidden until the mbox response has been received.

    See Rule Conditions and Functions for information about available rule criteria.

  3. Expand Adobe Target.

    Specify the element to wrap with the mbox using a CSS selector, name the mbox, then configure the timeout if needed. (It is generally recommended to leave this at the default 1500 ms).

  4. Configure the parameters you want to add to the Target mbox or to the global Target mbox.

    Step Result

    In this example, this rule deploys an mbox named Hero that wraps a div element with an id of hero and includes an mbox parameter named Page Name with a value of homepage. It also includes a parameter named Path with a value of home that it passes to the global mbox.


    You can also use data elements in the parameter UI fields to dynamically populate the value. See Data Elements for more information on data elements.

On this page