mbox.js implementation

To use Adobe Target Standard or Target Premium, add one line of code to call mbox.js.

You can use either of two library references: the Adobe Experience Platform Web SDK or at.js. Benefits of at.js explains the differences between the mbox.js and at.js libraries.

IMPORTANT

mbox.js end-of-life: On March 31, 2021, Adobe Target will no longer support the mbox.js library. Post March 31, 2021, all calls made from mbox.js will gracefully fail and impact your pages that have Target activities running by serving default content.

We recommend that all customers migrate to the most recent version of the new Adobe Experience Platform Web SDK or the at.js JavaScript library before this date to avoid any potential issues with your sites. For more information, see Overview: implement Target for client-side web.

The single reference to mbox.js on each page provides the libraries needed for all of your activities. mbox.js calls Target from every page that references the mbox.js file. This enables Target to do the following:

  • Deliver Target activities
  • Track clicks
  • Track most success metrics
TIP

To simplify implementation, you could reference mbox.js in your global header.

You do not need to maintain different activity-specific versions of the file.

  1. Reference mbox.js in the <head> section of each page on your site.

    <script src="/%20*%60directory%60*/%20*%60scripts%60*/mbox.js?lang=en"></script>

    Where *directory*/ *scripts* is the directory where you saved your mbox.js file after downloading it.
    If you already have mboxes on your page from a legacy implementation, these mboxes can still be used in the new interface. The updated mbox.js file is still required, but these mboxes can be selected for activities and edited using the Visual Experience Composer.

On this page