Troubleshoot content delivery

If your page does not display the expected content, there are a few steps you can take to debug content delivery.

  • Check your activity or campaign code carefully. A typo or other error could cause the expected content not to display.

  • Use mboxTrace or mboxDebug to troubleshoot the mbox.

  • Use the Adobe Experience Cloud Debugger, an easy-to-use tool that provides much of the same information as mboxDebug, to troubleshoot the mbox.

mboxDebug is especially useful when you are setting up Target on your page to make sure the mbox is firing and the cookie is being set. However, it does not go into the kind of detail that is useful when debugging content delivery. If your activity does not appear on your page or undesired content appears, use mboxTrace to examine and debug the page in detail.

Troubleshooting Video

The following video demonstrates tools to troubleshoot Target. (14:14)

  • Use native browser tools for inspecting mbox requests
  • Use the Experience Cloud Debugger, mboxTrace, and ttMETA
  • Understand the Target timeout

Retrieve the Authorization Token to Use With Debugging Tools

Because mboxTrace and mboxDebug can expose campaign data and profile data to external parties, an authorization token is required. The authorization token can be retrieved in the Target UI. The token is valid for six hours.

To retrieve the authorization token:

  1. Click Setup > Implementation.

  2. Select mbox.js or at.js.

  3. Click Generate Authentication Token.

  4. Add the generated token as a parameter to your URL to enable one of the advanced debugging tools.

mboxTrace

mboxTrace enables you to receive trace information attached to mbox replies. Trace information reflects the outcome of an mbox call (for example, a conversion or an impression) and any additional data that may help in determining why this particular outcome happened, such as a set of available branches among which the selection was made in a campaign. Use this information to debug content delivery.

The following parameters are available:

mboxTrace Options Outcome
?mboxTrace=console

Prints into console log as objects

For at.js, instead of popping a new browser window or outputting to the console as in mbox.js, you will need to inspect the Network request and look under Preview (Chrome) or Response (Firefox).

?mboxTrace=json

Prints into console log as a literal JSON string

?mboxTrace=window

Prints into a popup window as a JSON string

?mboxTrace=disable

Turns off tracing session mode

Example mboxTrace Call

http://www.mysite.com/page.html?mboxTrace=window&authorization=f543abf-0111-4061-9619-d41d665c59a6

The output displays very detailed information about your content. mboxTrace shows details about your campaign or activity and profile It also provides a snapshot of the profile before execution, and a snapshot of what changed after execution. It also shows which campaigns or activities were evaluated for each location.

Some of the information includes matched and unmatched segment and target IDs:

  • SegmentId: The IDs of segments, either from the reusable segments library or anonymous ones created for the particular campaign.

  • TargetId: The IDs of targets, either from the target expression library or anonymous targets for any segments from campaign.

  • Unmatched: The request did not qualify in this call for those segments or targets.

  • Matched: The request qualified for the specified segments or targets.

Using mboxTrace on Recommendations pages: Adding mboxTrace as a query parameter on pages with recommendations replaces the Recommendations design on the page with an mboxTrace details window, which displays in-depth information about your recommendations, including:

  • Recommendations returned vs. recommendations requested

  • The key used, and if it is generating recommendations

  • Criteria-generated recommendations vs. backup recommendations

  • Criteria configuration

  • Exclusions and inclusions applied

  • Collection rules

You do not need to include =console, =json, or =window in the query parameter. When you are done with the mboxTrace details, add =disable and press Enter to return to the normal display mode.

The normal functioning and appearance of your site is not affected by mboxTrace. Visitors will see your regular Recommendations design.

mboxDebug

To use mboxDebug, append an mboxDebug parameter to the end of your URL. The following table contains information about mbox-related URL parameters.

Note: Some mboxDebug parameters are available with or without authentication.
URL Parameters Purpose

mboxDebug=1

Debugger

Adding this parameter to any URL with mboxes defined opens a pop-up window with valuable debugging details. Cookie information, PCid and Session ID values are written out, and all of the mbox URLs are visible. Click on a mbox URL to show the response for that mbox. More details are available in mbox_debug.pdf.

mboxDebug=x-cookie

Modify the cookie

mboxDisable=1

Disable mboxes on the page

mboxDebug=x-profile

View profiles set.

mboxDebug=x-time

Show response time for each mbox request

mboxOverride.browserIp=Insert IP address

Test geotargeting

Test geotargeting with this URL parameter. Type an IP address as the value for this attribute, and Test&Target's geotargeting evaluates that IP address to match against any geotargeting or segmentation set in a campaign.

Adobe Experience Cloud Debugger

The Adobe Experience Cloud Debugger makes it fast and easy to understand your Target implementation. You can quickly view your library configuration, examine requests to make sure your custom parameters are being passed correctly, turn on console logging, and disable all Target requests. Authenticate into the Experience Cloud and you can use the powerful Mbox Trace tool to inspect your activity and audience qualifications as well as your visitor profile.

For more information, watch the following videos:

Add the Extension

Basic Target Debugging

Mbox Trace

For more detailed information, see the Adobe Experience Cloud Debugger Extension documentation.

If target.js Fails to Load During Delivery

Mbox.js sends a cookie called "em-disabled" to the visitor if target.js fails to load during delivery. This cookie prevents offers created using the Visual Experience Composer from rendering on the site. Visitors with this cookie neither see the test content nor get counted in those activity reports. All other offer content (from campaigns in Target Classic for example) continues to load. The cookie has a lifetime of 30 min from the time of load failure.

Top sellers are not appearing in Recommendations

The SIteCatalyst: purchase mbox can't be used for Purchase algorithm traffic data. Use the orderConfirmPage mbox instead.

Check Activity Priority

Form-based activities created with Target Standard/Premium might collide with activities created in the Target Classic UI that have the same priority and use the same mbox.

Custom code does not produce the expected results in Internet Explorer 8.

Target no longer supports IE 8.

JavaScript content delivered by the global mbox doesn't load when using mbox.js.

Upgrade to mbox.js version 58 or later.

Mbox.js version 58 and later executes non-JavaScript content for the global mbox immediately after the HTML BODY tag is present. JavaScript content inside <script> tags for the global mbox executes after the DOMContentLoaded event is fired. This order of content delivery ensures that JavaScript content for the global mbox is delivered and rendered properly.

Target Cookie Does Not Get Set

If your site has a sub domain, such as us.domain.com, but you need the Target cookie set on domain.com (instead of us.domain.com), you must override the cookieDomain setting. For more information, see targetGlobalSettings()

Target content flickers or is not shown if an element is also part of AEM personalization.

If a DOM element is part of Adobe Experience Manager (AEM) personalization targeting and a Target activity, Target content might flicker or not be shown.

To remedy this, you can disable AEM personalization on pages on which Target is running.

Redirect and remote offers fail to deliver due to an invalid URL.

If the redirect or remote offer uses an invalid URL, it might fail to be delivered.

For redirect offers, the mbox response can contain /* invalid redirect offer URL */

Or

For remote offers, the mbox response can contain /* invalid remote offer URL */

You can check the mbox response in the browser or using mboxTrace. See https://tools.ietf.org/html/std66 for more information on valid URLs.