Disclaimer: this approach won’t be suitable for everybody, please factor in your particular requirements before using it.
The Why
Towards the end of 2018, our client started to move our codebase from AngularJS to Angular 7+ (now 8). While this, in itself, is a great move, it completely broke our A/B testing capabilities. (
What's A/B Testing?) Implementing deep changes to our Angular applications would be much more challenging. The methods we used to amend code on bootstrap of AngularJS applications are no longer available in Angular2+. If you are interested in A/B testing in AngularJS applications, you can
read about our previous approach and Adobe setup.
While some A/B testing can, and should, be done from the backend, this article will focus on the frontend approach.
07 August, 2019
/