If the confirmation page uses the same domain as your test entry the mbox cookie is available on the confirmation page. If you can add a script to the page that pulls the session ID and PC ID out of the mbox cookie you can manually fire a confirmation mbox request from the page without the library file. Here is a sample JS tag that will do this:
if (document.cookie.indexOf('mbox=') != -1) { var mbxSes = document.cookie.match(/session#[0-9]+?-[0-9]+?#/).toString().split('#'); var mbxPC = document.cookie.match(/PC#[0-9]+?-[0-9]+?\.[0-9][0-9]_[0-9][0-9]#/).toString().split('#'); var img = new Image(); img.src = "//CLIENTCODE.tt.omtrdc.net/m2/CLIENTCODE/ubox/image?mboxSession="+mbxSes[1]+"&mboxPC="+mbxPC[1]+"&mbox=orderConfirmation&mboxURL="+encodeURI(document.location.href)+"&mboxReferrer="+encodeURI(document.referrer)+"&mboxDefault=ENCODEDGIFURL&mboxXDomain=disabled"; }You'll have to update your CLIENTCODE value and add an encode gif url (ideally a 1x1 gif on your site) for the value of mboxDefault. This will fire an mbox called: orderConfirmation. You can then configure your success metric in your test to look for this mbox.
NOTE: if you are using at.js the match regex for the session and PC variables will need to be different as at.js stores those sessions with alphanumberic values not just numeric values. These should work:
var mbxSes = document.cookie.match(/session#[a-z0-9]+?#/).toString().split('#'); var mbxPC = document.cookie.match(/PC#[a-z0-9]+?\.[0-9][0-9]_[0-9][0-9]#/).toString().split('#');