Disclaimer: this approach won’t be suitable for everybody, please factor in your particular requirements before using it.
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.
Web analytics tools are used to understand the behaviour of website visitors, and A/B testing is a technique that uses such tools to optimise a site. The tools facilitate this by giving you a means to measure and analyse site traffic and conversion.
Adobe Target is a real-time metrics-collection and reporting tool that is one of the most widely-used client-side analytics platforms available. In this blog, I'm going to talk about how to create an A/B test using Adobe Target and AngularJS, where the 'B' version is swapped-in using Angular decorators.
It’s being almost 3 months since I start implementing A/B tests for one of our clients and I have to say I am enjoying it a lot.
A/B testing is very powerful technique. Not only does it increase your web site conversion rates, it also promotes innovation and encourages data-driven solutions.
In this article I will give an introduction to A/B testing by asking an important question: what have scurvy, A/B testing and Barack Obama all got in common?