A/B Testing with TD
This guide has been reviewed and reformatted for Ruk-Com Cloud PaaS. Screens may vary slightly by platform version.
Click or tap a screenshot to view it at its original size.
Objective
This guide explains how to use A/B Testing with TD on Ruk-Com Cloud PaaS, with ordered procedures and practical verification points.
Before you begin
- Sign in with an account permitted to manage the relevant environment.
- Confirm the target environment, region and resources before saving changes.
- Create a backup or rollback plan before changing a production system.
A commercial website or application offers product purchase options, registration, payment versions. subscriptions, etc. The number of such actions initiated by end-users (which, if measured in percentages, is calledconversion rate) will depend heavily on the app's visual appeal, advertising copy, and other marketing strategies used. Comparing different versions of an application is aimed at determining which app version is better in terms of user conversion rate, called conversion rate.A/B testingThis process can help you find the best combination of attractions and other product characteristics that will help you maximize your revenue.
With the help of Ruk-Com CloudTraffic DistributorYou can easily apply this type of testing to your project - see details below.
1. In A/B testing, you need to use two different sample applications to perform better type analysis than checking to track triggering of desired actions (such as when the user clicks on the required button).
Tips:You can use any tool that allows comparing conversion rates, from simple code to counting server "scores" (e.g. through adding variables), to benefit specific third-party tests with a convenient interface. Analysis on graphs automatic rate calculation, etc.
2. Nextinstallyour Traffic Distributor or just configure it accordingly (if already created):

The main points that should be followed are:
- Routing Method- Select Sticky Sessions
- Traffic ratio- Set 50 to 50 for a fair analysis.
More:
- Do not use routing methods.Round RobinFor A/B testing, because this step assumes different content is available in your backend, some project elements may not be available on the server when specifically requested.
- In case you have a project that is already in production Let's learn how.Making a Traffic Distributorintelligently without interfering with the normal operation of the application
3. Once everything is set up, incoming requests will be routed equally to both versions of the application with their conversion scores maintained. So just share your Traffic Distributor entry link (e.g. environment orYour custom domain) between users and wait a certain amount of time for customers to try a given version of your app and collect some data about conversions.
4. The last step Analyze the results you collect to choose which project areas you need more work on. It is clear that the environment with the higher conversion rate wins and can be boldly used in production, while the other environment can be removed or modified for other testing purposes.
Tips:After you've revealed which version of the app is better, consider following the guide.Inject Traffic DistributorTo get started with Traffic Distributor for high availability andProtectionWhen an error occurs