π Definition
The rollback option enables you to stop the deployment of a feature and to revert all the changes that have been made in order to ensure that your feature isnβt breaking your customer experience, thereby damaging your business.
For this, you must define the business KPI you want to track and which can be an indicator of the performance of your feature. To this KPI (of any type you want), you must associate a value (in %) which, if exceeded or reached, will trigger the rollback.
To make the rollback significant, you must define a specific number of visitors from which the rollback comparison will be triggered.
When the conditions are met, the progressive rollout feature will be rolled back, which means that no more of the targeted visitors will see the feature. You will be alerted by email.
βοΈ Configuration
The rollback option is available for Progressive Deployment only.
To access this option, go to the Deployment step of the Progressive rollout feature and select Statistical rollout:
The Define Rollback section appears after the Define deployment steps section.
- From the dropdown list, select the type of KPI you want as a rollback indicator.
- In the second dropdown list, enter the name of the KPI or select one that has already been created.
- Choose the comparison operator between less than (<) or more than (>) and enter the corresponding percentage.
- Enter the number of users from which the rollback KPI can be effective.
β Good to know In the reporting, the Rollback metric mention means that the rollback option has been enabled for your progressive deployment feature. |
π‘ Use case
Letβs say you want to develop a new feature, allowing your users to know the exact location of their package. To mitigate the risk, you want to deploy this feature to your users progressively. In addition, to avoid product regression, you know you must keep your conversion rate above 3,5%.
To do so:
- Create a Progressive rollout use case on your Flagship account.
- Configure the Basic information, Features and Targeting steps.
- Define your progressive deployment with fixed steps of 10% of the users every week until you have reached 100%.
- Configure your rollback KPI: Select Event as the KPI type and the name of the conversion rate measurement KPI you have chosen for your feature.
- Select the < operator and enter the rate (3,5%).
- Enter the number of users (10000 for example) from which the rollback can be done in case the conversion rate exceeds 3.5%.
- Save and activate your use case via the dashboard.
In this case, from 10000 visitors on the targeted page and affected to the feature, if the event clickOnLocateMyPackage falls below 3,5%, then the progressive deployment will automatically be stopped, meaning that no more visitors will see the variation(s).
Need additional information?
Submit your request at product.feedback@abtasty.com
Always happy to help!