Issue with A/B Test – Custom Code not delivering on Experience A
I created a new A/B test and added modification code (Mbox code) under Experience A using the Custom Code option. The changes saved successfully in the VEC editor.
However, during validation:
- Experience A delivers nothing (and appears empty in the VEC editor).
- Experience B, where I did not add any code, is unexpectedly delivering the Mbox code. The Mbox code is appended on Experience B, and when I open the VEC it shows up there.
Has anyone faced this issue before? How can I resolve it so that the custom code applies only to Experience A?



