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:
|Implement mbox.js or at.js, with no
|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 Experience 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+
Choose the option below that applies to you:
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.
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.
To set the Auto Create option, click Setup > Implementation > Edit mbox.js Settings, then enable Auto create global mbox.
For information about implementing mbox.js, see mbox.js Implementation.
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.