To use Target Standard or Target Premium, add one line of code to call mbox.js.
You can use either of two library references: mbox.js or at.js. Benefits of at.js explains the differences between the two libraries.
mbox.js end-of-life: On January 18, 2021, Adobe Target will no longer support the mbox.js library. Post January 18, 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 at.js library before this date to avoid any potential issues with your sites. For more information, see How At.js Works.
Although, mbox.js is currently supported, we have not provided feature updates to this library since July 2017. The newer at.js provides many advantages over mbox.js. Among other benefits, at.js improves page load times for web implementations, improves security, and provides better implementation options for single page applications.
By moving all customers to at.js, our engineers and support staff will be able to provide you with new functionality and offer the support you have come to expect from Adobe.
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:
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.
Reference mbox.js in the
<head> section of each page on your site.
<script src="/ *directory
* 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.