Hello community,I'm trying to locate version 1.6.3 of at.js to download. I've looked at the release notes and have been unable to locate this particular version.Any guidance is appreciated!- Brion

We believe it may have something to do with crossdomain cookie persistence. Will share here if more details arise.

delta.shayan​ - While the cause wasn't immediately obvious, the template string was being used within the test code. It was not associated with AT.js or our Bootstrap.js.

@mikewebguy - This is exactly what I'd expect it it were an XT activity type. However, this is definitely an A/B test. We're going conduct some internal investigation to see if we can determine the cause.

Hello community,I'm wondering if anyone has encountered an issue where they qualified for one experience on one page, and a different experience on a subsequent page, all within the same test activity and user journey?Our team launched a test and almost immediately we began seeing the ability to ent...

Hello @pratheep - I'm having a similar issue in which I'm unable to enter a test activity via Chrome Mobile (60+) using a Samsung Galaxy.I've added a Mobile rule specifying the device type (Mobile) OS matches (Android), with an AND condition for a Browser rule equal to Chrome.According to your comme...

No, that code is not present in our Bootstrap.js bundle.However, I discovered the problem. After running the code in console, I got an invalid character error. There was a template string being used, which is not supported in IE. Changing the `` to '' made all the difference. Thanks for taking the ...

@karandhawan - Our implementation is with Ensighten.Attached is a screen shot listing the errors I noticed this morning.Something I didn't notice yesterday, is the global_mbox is firing, but the test is not. I should point out again that we have been able to enter via Edge. However, for purposes of ...

Hi Karan,Yes, in dev tools, the Network tab in particular, I can see a reference to the my test/experience in the Response Body. However, I'm also getting "ttMETA object does not exist" in console.The errors I'm seeing are related to:SEC7120: Origin now found in Access-Control-Allow-Origin header.SC...

Hi all,I've got an A/B test activity in which I'm targeting Chrome, FF, Safari, Edge, and IE11. All browsers work with the exception of IE11.I can't determine what is wrong with my audience configuration. See attached.I've included an additional OR to include Browser Type equals IE and Browser Versi...