Thank you Guaresh, I'll open a bug and see if we can figure out what's going on there. Liked/marked helpful.

OK, Surbgupt (hey you changed your username! ), we've deployed our Target installation into production.Our test is set up as an A/B. Both experiences purely just drop a console.log into the developer console. The default console log is 'tgt-dflt', and the test is 'tgt-tst'.https://www.endicia.comIf ...

*headslap* Surebee we won't be able to provide a test until target has been implemented in the environment we're working in and released into production. I'll need to come back to this when we've released.However, I can say that we implemented the fix from that old thread posted by the OP, and it cu...

I will need to get permission to set up a live activity on production so I can share it. I'll post back here when I get that going.

We have same issue. just upgraded to at.js 2.1.0We have an A/B test.All the code does is run a console.log.We see two console logs trigger.In other properties where we use at.js 1.x we do not have this problem.