Depending on your implementation of Target you can create a JavaScript function to send data to be processed in profile scripts.function targetPageParams() {     That function returns URL style parameters that will be automatically added to the parameters that are already sent (Eg. screenWidth, scre...

And also this more useful one bookmarked. It's good for checking on Analytics variables too.AAjavascript:void(window.open("","dp_debugger","width=600,height=600,location=0,menubar=0,status=1,toolbar=0,resizable=1,scrollbars=1").document.write("<script language=\"JavaScript\" id=dbg src=\"https://www...

I also have this as a bookmark in Google Chrome.atdebugjavascript:void(0);!function(){function e(e,t){function n(){return t.isObject(e.XMLHttpRequest)}function o(){return n()&&"onload"in new e.XMLHttpRequest}function r(){return o()&&"withCredentials"in new e.XMLHttpRequest}function a(){return t.isOb...

I'm not exactly sure what you want, but you could use the ttMETA test plugin, or use some combination of the mboxTrace, mboxDebug and authorization URL parameters to get information in your browser inspector console, or even in the JSON returned from the at.js call to the cloud.

I need a definitive answer on whether an XT (Experience Targeting) Activity will run our Profile Scripts every time, checking the parameters that are passed back from at.js running on page load.We are checking parameter values in our Profile Scripts to decide and output a string which then an Audien...

Also Adobe have changed the preview parameter. Make sure your website isn't striping this new one. So besides *at_preview* there is now *at_experience*