- Best Practices for Implementing Adobe Target using Dynamic Tag Management
- Dynamic Tag Management Implementation
- Adobe Target
- Adobe Target Tool
- Add Target
- Add the Adobe Target Tool
- Option 1: Implement Target Automatically via the Marketing Cloud (Easiest and Recommended)
- Option 2: Implement Target Automatically with Manual Entry of Your Target Client Code
- Option 3: Implement Target Manually with the Target JavaScript Library Hosted by DTM
- Option 4: Implement Target Manually with the Target JavaScript Library Hosted Outside of DTM
- Configure Target
- Update the Adobe Target Tool
- Deploying
- Additional Resources
Performing QA Steps
Steps to help you perform QA steps before approving and deploying your Target implementation.
The following sections contain more information:
- Previewing DTM Changes on Your Production Website
- Ensuring that the Target Tool is Loading Properly
- Ensuring that Target Mboxes are Firing Properly
Previewing DTM Changes on Your Production Website
Changes saved within DTM are immediately available in DTM’s staging library and should be QA’d before they are published. At most, they will take a minute or two to roll out across the Akamai network. To QA DTM changes on your production website:
- Load your production website in your browser.
- Use the DTM Switch tool or console commands to force DTM to load your staging library.
- Reload the page to preview the changes made in DTM.
When you use the DTM Switch or console statements to load the staging library, you should see “-staging” appended to the end of the file via your developer tool’s Network tab:
If you are ever concerned that you are not seeing the latest changes, you can run the Console statement “_satellite.buildDate” to confirm the timestamp of the build you are loading.
Ensuring that the Target Tool is Loading Properly
- Open your web browser’s developer console.
- Turn on “Debug” mode with the DTM Switch plugin.
When the Target Tool loads the following statements display in the console:
Also, using the Network tab, you can verify that the mbox.js file has loaded. It will look something like this:
Ensuring that Target Mboxes are Firing Properly
In the Network tab, you can verify that your mboxes are firing (they typically begin with “standard?” or “ajax?”):
The Adobe Marketing Cloud Debugger is also tremendously helpful to verify the calls and parameters:
