Using the Visual Experience Composer for A/B redirect test

[JonathanHi5]

I've created an A/B test activity that is being served on our site's homepage via a VEC activity. Half of the traffic is being redirected to a different URL while the other half should be seeing the default experience that is being loaded in via the global mbox.

What seems to be happening is there are other XT activities at a lower priority than the test and these are serving targeted offers on the homepage, so the control experience isn't what we want. Any suggestions on how to avoid this happening? Or best practices for executing a redirect test using a VEC A/B activity? 

[Vaibhav_Mathur · Accepted solution]

Hi @JonathanHi5 ,

To avoid potential issues with conflicting experiences in Adobe Target in case of a redirect test, a recommended best practice is to ensure that no other activities run on your control redirected page. When setting up a redirect offer for the control experience, consider appending the redirecting URL of the control page with the query parameter "?mboxDisable=1". This approach ensures that users are redirected to the intended control page without triggering any additional Target activities.

Best regards,
Vaibhav Mathur

[Pankaj_Sabharwal]

Hi @JonathanHi5 

To avoid conflicts in your A/B test, ensure your A/B test activity has the highest priority to override other XT activities. This prevents other activities from interfering with your test. Explicitly define audiences for your A/B test.

The other choice is you can set up exclusive rules for your activities to ensure that users in your A/B test aren't also targeted by other XT activities.

Verify that the global mbox is correctly configured to deliver the default experience without interference. This ensures that visitors who are not redirected are seeing the intended control version. Before launching, test the activity under various conditions to identify conflicts.

Please let me know if this helps.

Thanks.