HiThis is expanding on the idea submitted by @Andrey in his idea Improve how Activity name is displayed in Adobe Target UI . I think the improvement can go beyond how the activity name is displayed. In the edit experiences screen, the way the interface displays audience and experience names is also less than optimal, with the amount of unusable space in the UI it is frustrating that I have to hover over my experiences, audiences, etc.. to reveal the full name. If we could drag the right hand rai...

HiAdding the mboxTrace query string parameter to the Target QA string seems to unnecessarily long winded. The current process is to...1) Copy QA string from 'Activity QA' screen (then put somewhere)2) Click 'Done'3) Click 'Setup' from top menu4) Click 'Implementation'5) Click 'Generate Authentication Token'6) Select and copy the parameter.7) Add parameter to end of QA string I had copied in step 1This process could be made way more efficient by putting this option in the screen where the QA stri...

HiIt would be so much more efficient if within the edit activity screen we had the options to generate the activity QA codes. As it is, if I'm working on code and want to see the effect this has on an experience, I have to do the following...1) Save and close edit activity screen2) Click 'Activity QA' link in 'Overview'3) Copy link4) Exit page 'Activity QA screen' clicking 'Done'Then if I want to continue editing the code5) Click 'Edit Activity'6) Find experience I was working on, and work out w...

HiI work on a wide screen monitor so find it bizarre that the code editor will only take up a third of the width by default.In order to see more of my code I therefore widen and lengthen this window, fine. However, as soon I save, look at another experience, etc, it'll revert back to the original size. Is there anyway to make this a bit more smart, e.g. make the window a reasonable size for my display, or retain the size I adjust the window to?ThanksDan

HiAn idea that would make creating profile scripts slightly less frustrating would be if Target told me within the script editor window whether the script had any syntax errors, or errors that would prevent it going live. Only after saving it, going back out to the 'Profile Scripts' page, waiting for a few seconds, then looking at the status, do I find out if it will run or not. I'd like to be able to check within the editor that the code will run, before saving it.ThanksDan

HiI'm attempting to retrieve specific values from an array I have stored within a profile. The usual method I would use to retrieve these via Javascript doesn't appear to be working, so not sure if I've missed something obvious or not?!I have created an array with 2 dimensions, which, from looking at the mbox trace, seems to look as I would expect it to look, see below:The above array contains 4 2 dimensional values. If I copy this local profile to a variable, e.g.var testArray = [];var testArra...

Having started to re-use Analysis Workspace, after being away from it for a little while, it's been great to see the progress that has been made with the visualisations and the neat functionality that has been added. However, with the news that Ad Hoc is to be deprecated, I'm concerned at the number of inefficiencies that continue to make using Analysis Workspace a frustrating experience, and will keep me using Ad Hoc until it is eventually switched off. In particular I've found great frustratio...