Step 1: Update your s_code.js file with the Omniture TnT Integration Plugin – Version 1.0
/*
* TNT Integration Plugin v1.0
*/
s.trackTNT = new Function("v", "p", "b", ""
+ "var s=this,n='s_tnt',p=p?p:n,v=v?v:n,r='',pm=false,b=b?b:true;if(s."
+ "getQueryParam){pm=s.getQueryParam(p);}if(pm){r+=(pm+',');}if(s.wd[v"
+ "]!=undefined){r+=s.wd[v];}if(b){s.wd[v]='';}return r;");
Step 2: Determine if you will include the integration call in your standard SiteCatalyst page tag or if you will require to use a Custom Link call.
Is your SiteCatalyst code block located after the last mBox call on your page?
YES! Simply add the following before you call s.t():
var tntInput = s.trackTNT();
s.eVar47 = s.tnt = tntInput;
Is your SiteCatalyst code block located before the last mBox call on your page?
YES! This will take a bit more work but, if you ask me, worth it. I have our SiteCatalyst code directly following the <body> tag. This has greatly improved our data accuracy. Moving the code to accommodate an integration with Test & Target was simply out of the question.
To send the Test & Target information to SiteCatalyst using a Custom Link call add the following after all mBoxes on the page:
<script>
var tntInput = s.trackTNT();
trackTNT(s_account, tntInput);
function trackTNT(s_account, tntInput){
var s=s_gi( s_account );
s.linkTrackVars="tnt,eVarN"
s.linkTrackEvents="None"
//variable for TNT classifications
s.eVarN = s.tnt = tntInput;
s.tl( true , 'o' , 'For tracking TNT' );
}
</script>
Step 3: Classify the Test & Target Campaign and Recipe ID. Omniture has a behind the scene integration to automatically classify your TnT integration. However, I have been told it is limited to one (1) report suite. I found it easy enough to simply do this myself.
Step 3a: Create a Custom Conversion variable to capture your Test & Target integration IDs
Step 3b: Classify your conversion variable to include a text based classification called ‘Treatment’
Step 3c: This part is a little hacky but hey, it works. Log into Test & Target and view your campaign. The TnT plugin will return a value like ‘4503:0:0,’. To get the values hover your mouse over the preview icon for each treatment
Now, look down in your status bar and you will be able to see the values you need to write down. 
Now you can compile a list of Ids and treatment names
4503:0:0, Control
4503:1:0, Improved Headline
Step 3d: Download a SAINT template for your TnT classification. Map each treatment id to your friendly treatment name. Upload.
Step 4: Analyze your results. Test & Target is great for giving you a dashboard view of your treatments and how each one is converting (with statistical significance). However, you still are not able to fully understand how your tests are changing user behavior inside your site. This is where SiteCatalyst and more powerfully, Discover, comes into play. Use SiteCatalyst and Discover to slice your visitor population to better understand how your Test & Target campaigns are influencing user behavior beyond the conversion check point.
And by uploading a friendly treatment name via SAINT, this job is made much easier.
Jason Thompson is a Senior Analytics Consultant at Numeric Analytics. You can follow him on Twitter at twitter.com/usujason.
Avinash Kaushik
Crepuscular Light
Kevin Rogers
Pritesh Patel
Rudi Shumpert
2 Comments
Thanks for writing this. Do you have anymore resources with information about integrating T&T into Sitecatalyst? Anything at all?
From what I’m reading, it appears that statistical significance is not available in sitecatalyst, right?
Thanks again
P
Correct, statistical significance is not available inside SiteCatalyst.
From my experience, Test & Target reporting is good for giving an overall indicator about how a campaign in performing. The integration with SiteCatalyst/Discover allows for a much rich analysis of the campaign by segmenting visitor behavior by the recipe Id captured as part of the integration.
What in specific are you looking for?