Site­Cat­a­lyst cus­tomers have been using the Dig­i­talPulse Debug­ger and its ear­lier incar­na­tions to trou­bleshoot imple­men­ta­tions for years. Test&Target cus­tomers, on the other hand, have relied on an assort­ment of var­i­ous book­marklets and hard-to-remember URL para­me­ters. I’m glad to say that over the last year numer­ous improve­ments have been made to help you see the clock­work behind Test&Target. All you need is the Dig­i­talPulse Debugger!

If you have the Debug­ger installed, you already have all of the lat­est enhance­ments. If you don’t, go to the fol­low­ing URL and drag the “Dig­i­talPulse Debug­ger” link to your browser’s Tool­bar or Book­marks folder:

http://​dwright​.host​.adobe​.com/​b​o​o​k​m​a​r​k​l​e​t​s​.​h​tml

Now that you have the book­marklet, go to any page on your site with an mbox and click on the book­marklet to open the Debugger.

The most basic and pow­er­ful change was sim­ply to roll up all of the obscure query string para­me­ters and other tools into one place. In the upper-right hand cor­ner you will see a drop­down menu called “T&T Tool­box” with many of your old favorites like mboxDis­able, mboxDe­bug, mbox­Cookie, and mboxProfile:

Adobe DigitalPulse Debugger's Test&Target Toolbox

The very first option, “*What are these?” explains all of the other options. I highly sug­gest read­ing through this. Here are the tools that I use the most fre­quently when debug­ging issues for my clients:

      1. mbox­High­light—I use this all the time to see where mboxes are on the page. There is also some advanced func­tion­al­ity that will show you the cam­paign name, expe­ri­ence name, and offer name asso­ci­ated with the mbox response. I will show you how to enable this advanced fea­ture in my next arti­cle. For most cus­tomers, it will show the mbox name and offer id like this:mboxHighlight feature in the Adobe DigitalPulse Debugger
      2. mbox­Pro­file—this launches a popup to expose all of the rich pro­file data that has been col­lected against you as a vis­i­tor. All of your pro­file para­me­ters and script pro­files. If you are not able to enter a cam­paign or seg­ment that is based off a pro­file, your first step should be to con­firm that you have the cor­rect value set in mbox­Pro­file. Hint #1: The out­put is just raw XML and can be very long. We hope to improve this in the future, but until then use Ctrl-F to jump to the pro­file name you are inter­ested in:mboxProfile XML from the Adobe DigitalPulse Debugger
      3. Hint #2: If you use setLocal()/getLocal() when writ­ing pro­file scripts, these val­ues will also appear in the mbox­Pro­file popup. You can iden­tify these local vari­ables by the num­ber that appears between “user.” and the vari­able name. Here is an example:Local Variable XML example in the Adobe DigitalPulse Debugger
      4. delete­Cook­ies—there are a mil­lion dif­fer­ent ways to delete cook­ies, but since I often have the Debug­ger open, I just do it here. Not only will it delete all of the first-party cook­ies on the domain, it also reloads the page, allow­ing you to enter another expe­ri­ence. (Note: if you use a 3rd-party or 1st– and 3rd-party cookie imple­men­ta­tion, the delete­Cook­ies option will not delete the cook­ies needed to reset you as a visitor.

Those are the three main Tools that I use, but there are many more use­ful fea­tures. Please explore!

Many cus­tomers are unaware, but ear­lier ver­sions of IE limit URLs to a length of 2083 char­ac­ters. When server calls from vis­i­tors on these browsers crosses that thresh­old some of the data you are intend­ing to pass to the Adobe servers gets clipped. This doesn’t hap­pen often but tends to be more preva­lent when cus­tomers use incred­i­bly long URLs or pass up too many para­me­ters. To call atten­tion to these lengthy URLs in the Debug­ger, we now auto­mat­i­cally high­light them red and add a lit­tle bit of explana­tory text:

Too many char­ac­ters warn­ing in the Adobe Dig­i­talPulse Debugger

I hope you enjoy the recent improve­ments to the Dig­i­talPulse Debugger!

(Note: After a recent update of Chrome, the Debug­ger ceased work­ing on secure pages in Chrome.  We are aware of the issue and will update this post when it has been resolved).

0 comments