Adobe Target

First off, let me start by saying I am a T&T noob - and am 'learning as I go'.     I've been using T&T for about a month now, developing for some campaigns for my organization. One basic issue that I have revolves around the difference between mBoxCreate() and mbodDefine()/mboxUpdate() - especially when it comes down to performance.Right now, we create mboxs with mboxCreate within our global provisioning campaign to run our tests/experiences.   So each campaign we create typically creates is own mbox (or mutiple mboxs) for that campaign. This is working fine, but our site optimization team is on us to see if the mboxs can be created after the DOM is ready (right now, its happening before).By switching to a more dynamic model, we might be able to facilitate the site speed team and make them "happy"  - I'm just curious on the downsides of this plan, if if using mboxDefine/mboxUpdate is more or less efficient than just doing it the way we always have been via mboxCreate.One issue

Hello experts!According to the Adobe Target Classroom book, PCID profile data is cleared/reset in a maximum of 84 days.Does this mean that I cannot connect two sessions of web activity that happen 4 months apart to the same person? ie is the PCID cleared, or just the profile data for that ID?If the latter, this will be a nightmare for Master Data Management, and maintaining a Single Customer View, unless I'm missing something? Thanks, Chris.Marketing consultant, UK.

Hello - My company and I are just getting started on some Global Homepage Testing for our site.Our first area of testing is our current content of a flashing, rotating panels versus a static image panel with that same content. However, rather than solely testing the mbox content of flash vs. static, we also want to know how the total homepage is affected by the test based on what experience a customer was served. For example, if they saw flashing, did a submessage outside the mbox perform worse or better...and vice versa for the static experience. Essentially, everything outside the targeted mbox experiences A or B, should also be targeted with A or B appropriately.Is this possible through a Global mbox and targeting them within the same experience?Thanks for your help!

I have an mboxDefine()and after a certain condition check call the mboxUpdate and also send some parameters. The resulting network call shows these parameters in the console. These are also shown in the parameters list of the associated location.But When I do an mboxCurrent.getParameters() in the accociated offer, only the default ones (browser height, screen width etc) are available. I tried a bunch of things but so far have not been able to access these custom parameters in offer itself. Any pointers will be helpful. Thanks.

Adobe target is great for AB testing static HTML pages, but can it be used to AB test dynamic contents? e.g. UI for search results screen etc.