Another option is this:parametersFunction: function() {    function readCookie(name) {        var nameEQ = name + "\x3d";        var ca = document.cookie.split(";");        for (var i = 0; i < ca.length; i++) {            var c = ca[i];            while (c.charAt(0) == " ") c = c.substring(1, c.leng...

Awesome!  Many thanks Ram!  Look forward to connecting at Summit!  

Hi Ram, Thanks again for the review here.  Curious if the patch has been rolled out yet?  Cheers,  Brian 

Many thanks Ram!  Appreciate the follow up on this.  

Any thoughts on this?  

Hi there, I am having an odd issue where only "User Management" is available as an Integration service via the Adobe Target I/O API.  I need "Adobe Target" available.  Is there something that needs to be configured to make this available?  Thanks in advance!Brian 

The user. scripts are server side and cookies are client side.  Here is an easy example to do this: http://www.testandtargeting.com/demo/cookie/There is a function that is added to the mbox.js at the bottom and take a look what is added to the mboxCreate.  

You need to use mboxUpdate vs. mboxCraete because this offer seems to be pulling in code to the page after it has rendered.  

I'd have to look at the test setup but I imagine it is visitor requalifying for the test and since they qualify for the first experience they are sent there.  Think of it as a top to bottom approach.  As they re-qualify, Target will start with the targeting from Experience A and see if visitors meet...

Yes, change it to an A/B campaign from a Landing Page campaign.  Also remove your experience level target or recipe level targeting and simply apply that condition at the location or mbox level.  Because visitors are qualifying for that first experience (because the targeting is there), is why you a...