Debugging at.js

Information about the status of traditional Target debugging techniques when used with at.js.

Debugging options are slightly different for mbox calls using at.js.

The following video demonstrates tools for troubleshooting at.js:

Tools for Troubleshooting Adobe Target 14:14
  • Use native browser tools for inspecting mbox requests
  • Use the Marketing Cloud Debugger, mboxTrace, and ttMETA
  • Understand the Target timeout
Debugging Technique Details

Adobe Marketing Cloud Debugger

Not supported.

All mbox calls with at.js use XHR requests, which are not exposed by MC debugger. Instead, use your browser's Developer Tools to inspect the Network requests, filtering to "mbox" to isolate mbox calls.

atList

Supported. http://dwright.businesscatalyst.com/bookmarklets.html

atList shows Mbox Names, Activity Names, Experience Names, Offer Names dev console as an alert or both (true/false configs are at the beginning of the bookmarklet). Requires ttMETA response plugin.

mboxHighlight

New version.

mboxHighlightJSON outlines wrapping mboxes created with at.js. Use atList to expose activity details.

mboxTrace=console

Supported, but in a different location.

Instead of popping a new browser window or outputting to the console, you will need to inspect the Network request and look under Preview (Chrome) or Response (Firefox).

mboxDisable=1

mboxDisable=

Disable or enable Target.

If you are using at.js 0.9.6 or later you can disable Target by setting an mboxDisable cookie via the console.

Use the following console statements to turn on/off Target (same behavior as ?mboxDisable=1), but you don't have to keep adding this to the URL. Disabling persists until you remove the cookie or set the value to an empty string.

document.cookie = "mboxDisable=1";

document.cookie = "mboxDisable=";

mboxDebug=1

mboxDebug=

Disable or enable logging.

If you are using at.js 0.9.6 or later you can disable logging by setting an mboxDebug cookie via the console.

Use the following console statements to turn on/off Target console logging (same behavior as ?mboxDebug=1), but you don't have to keep adding this to the URL. Console logging persists until you remove the cookie or set the value to an empty string.

document.cookie = "mboxDebug=1";

document.cookie = "mboxDebug=";

mboxDebug=x-profile

Not Supported.

Use mboxTrace to expose profile information.

mboxDebug=x-cookie

Not Supported.

VEC Offer Debugging (_AT_Debug=console

Not supported.

mboxDebug=1 will show the details of Visual Experience Composer offer delivery.