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 @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...

Thanks again RamH!I believe our flicker is a result of using a custom global mbox. We prevent flicker by setting the targeted content to '0' opacity, then change the opacity to '1' once Target fires--similar to what the Auto Created Global Mbox does, just not on the body.So, a few final questions:Do...

Thank you, Ram!We are currently using at.js, but still experience some flicker in tests.Considering the VEC and auto creating Global Mboxes, does the same apply with regard to the Form-based Composer? We use both VEC and FBC.It sounds like the best (only) way to avoid flicker is to use Auto Create?

Thank you snaomi705!I'm going to try one more thing. If that doesn't work, I will proceed with submitting a support ticket.