Technical Implementation

How you implement Target depends on whether you use mbox.js or at.js, and whether you use Adobe DTM.

The technical implementation phase is complete when you have completed the following steps:

Step Task
Implement mbox.js or at.js, with no incompatible plugins.
Important: If you are moving from Target Classic to Target Standard/Premium and want to continue using mbox.js, you must download a new mbox.js file from the Target Standard/Premium UI and update your web pages accordingly, even if you already have mbox.js deployed. This is especially important if you are planning to edit page content in the Visual Experience Composer (VEC) in Target Standard/Premium (see Visual Experience Composer Best Practices and Limitations). However, there are advantages when using the newer Target JavaScript at.js library that you should consider during the transition. For more information, see Understanding the Target JavaScript Libraries.
A global mbox firing successfully either across your site globally or on pages where testing or tracking will occur.

Optional: My organization uses Adobe DTM to deploy the Marketing Cloud

Follow the deployment steps for DTM.

My digital properties are deployed on the latest library files for Target, either at.js or mbox.js V53+

Either update your mbox.js file or update to at.js.

Note: mbox.js V58 is the minimum version if using Marketing Cloud Core Services.

mbox.js

Choose the option below that applies to you:

  • I want to use my JavaScript library to auto-deploy my target-global-mbox for a Single Line of Code implementation

    Make sure the Auto Create option in the mbox.js download settings is enabled. To set the Auto Create option, click Setup > Implementation > Edit mbox.js Settings, then enable Auto create global mbox.

    Note: If you are on a Target Classic SKU, you might exceed your allotted number of server calls.
  • I already have a global mbox deployed (hard coded) and want to keep it

    Ensure that the Auto Create option in the mbox.js download settings is enabled. To set the Auto Create option, click Setup > Implementation > Edit mbox.js Settings, then enable Auto create global mbox.

  • I have already deployed (hard coded) a global mbox, but I want to get rid of it in favor of auto deployment
    1. Make sure the Auto Create option in the mbox.js download settings is enabled.

      To set the Auto Create option, click Setup > Implementation > Edit mbox.js Settings, then enable Auto create global mbox.

    2. Remove your hard coded global mbox from your site code.
    3. Deploy the mbox.js file with these settings enabled.
    Note: If you are on a Target Classic SKU, you might exceed your allotted number of server calls.
  • I want to migrate to only a global mbox to reduce server calls
    1. Make sure no Target Classic campaigns are running against your classic regional mboxes.
    2. Deactivate other mboxes in the Target UI first to verify site experience.
    3. Remove Target Classic regional mboxes from your site code.

    For information about implementing mbox.js, see mbox.js Implementation.

at.js

My digital property uses a Single Page Application Design and I want to use at.js instead of mbox.js

Review the at.js documentation to make sure your Target implementation is compatible with the at.js library file.

Our deployment of Target uses Response Plugins

Audit Response Plugins for illegal methods deprecated in the file. See at.js Plug-ins.

Our mbox.js features custom code modifications or other edits

Audit Custom Code for illegal methods deprecated in the file, for example AAM>Target. See at.js Limitations.

We make sure of custom site code using documented mbox.js methods

Audit site code for illegal methods deprecated in the file, such as mboxFactory. See at.js Limitations.

We fire a global mbox on a hash change, route change, or state change

Work with Adobe Target Consulting to build an SPA Framework Plan for implementation.