Use this troubleshooting information if you have difficulties with your mboxes.
Follow the process for validating mboxes.
If the Debug window does not appear:
If the Debug window appears but enabled = false:
This means the mbox cookie was not set properly to deliver content and track success.
Some common errors include:
If the mboxes are not listed in the mboxDebug popup window, or if mboxes appear blank on the page, review your page code for the following:
Mboxes insert new nodes into the DOM tree as the browser creates it. Since each brand of browser has its own implementation of the W3C DOM specification, mboxes can affect page rendering differently based on the browser type. Specify absolute sizes of table cells and images to help the browser more accurately display a page's HTML layout.
If you see mbox content delivery lag:
The content inside any mbox is hidden on the page until the mbox response returns from Target. This happens because the css class mboxDefault is applied to the div tag that surrounds content in an mbox. Even when default content is selected as the experience in a test, the content does not display until Target responds. Because of this, the only difference between the loading of default content and test content is the time it takes to actually execute the code in the offer delivered by Target. This is almost always so marginal that there is no benefit to recreating the default content experience as an offer.
You may want to deliver both the test and default experiences in mboxes if you are delivering very complex code via the HTML offer or a dynamic offer. A redirect offer should not have an effect on performance, other than the actual refresh of the new page. If the pages on your site load slowly, then that could affect the test. In that case, you might choose to redirect the user regardless of the destination, to rule out any effect.