This section refers to a deprecated version of the product. The new version is FE&R. To access FE&R, contact your CSM.
πŸ“˜ To learn more, read the FE&R documentation.
LogoLogo
PlatformsPricingRessources
  • User documentation
  • Onboarding
  • Help Center
  • Release Notes
  • Flagship - Deprecated
  • Feature Experimentation & Rollout (ex-Flagship) is evolving!
  • GETTING STARTED
    • πŸ‘‰Managing multiple environments
    • Using the trial version of Flagship
  • First steps with Flagship
    • Quick start guide
    • Glossary
  • Implementation
    • Sending transactions from the AB Tasty Shopify app directly to Feature Experimentation & Rollouts
  • Integrations
    • Heap Analytics integration (Push)
    • Tealium AudienceStream (receive audiences)
    • FullStory integration (segment exports)
    • Heap Analytics integration (Pull)
    • Google Analytics integration (pull audiences)
    • Segment Integration (receive traits)
    • Mixpanel integration (cohort exports)
    • πŸ‘‰Retrieving your third-party tools’ audiences in AB Tasty - Feature Experimentation & Rollouts
    • Zapier integration
    • Segment integration
  • Steps configuration
    • πŸ‘‰Configuring Sequential Testing Alerts
    • πŸ‘‰Configuring your Flags
    • πŸ‘‰Using the scheduler
    • πŸ› οΈ[Troubleshooting] How to target a large number of users at the same time?
    • πŸ‘‰Configuring KPIs
    • πŸ‘‰Using the automatic rollback option
    • πŸ‘‰Targeting configuration
    • πŸ‘‰Dynamic allocation
    • πŸ‘‰Traffic allocation
  • Team
    • Access Rights, Teams & User Management
    • πŸ‘‰Defining rights per project
  • DEMO
    • AB Tasty - Feature Experimentation & Rollouts Demo - How to use it
  • Navigating the interface
    • πŸ‘‰Archiving use cases from the dashboard
    • πŸ‘‰Flags page
    • πŸ‘‰Running a search on the dashboard
    • Navigating the Flagship interface
  • REPORTING
    • πŸ‘‰Verifying your hit setup
    • πŸ‘‰Exporting reporting data
    • Understanding the "Chances to win" indicator
    • πŸ› οΈ[Troubleshooting] How can I know my test is reliable and my data significant enough to be analyzed?
    • Reporting - A/B Test
    • πŸ‘‰Using the reporting filters
  • API keys & Settings
    • πŸ‘‰Acting on your account remotely
    • πŸ‘‰Using Experience Continuity
    • visitor experiment option
  • FEATURES SETUP
    • πŸ‘‰Bucket allocation
  • SDKs integration
    • πŸ‘‰Managing visitor consent
    • πŸ‘‰Understanding the use of SDKs
  • FAQ
    • Can I make a comparison for each reporting?
    • Can I use Flagship even if my SDK stack is not available?
  • Platform integration
    • πŸ‘‰Webhooks page
  • Decision API
    • Decision API for non-techie users
  • Account & Profile
    • πŸ‘‰Configuring account restrictions with MFA
    • πŸ‘‰Configuring a FA on your profile
  • RELEASE NOTES
    • October - Flagship becomes Feature Experimentation & Rollouts
    • February - Release Notes
    • πŸ“…January - Release Notes
    • πŸŽ‰December - Release Notes πŸŽ‰
    • πŸ¦ƒNovember - Release Notes
    • September Release Notes 🎨
    • June Release Notes 🐞
    • 🍸May Release Notes β˜€οΈ
    • Flagship Release Notes April πŸ‡
    • Flagship February release notes πŸ‚
    • Flagship January release notes πŸŽ‰
    • Flagship November release notes πŸ¦ƒ
    • Flagship October Release Notes πŸŽƒ
    • Flagship September Release note πŸŽ’
    • Flagship August Release Notes 🐬
    • Flagship Release Notes July β˜€οΈ
    • Flagship Release notes June 🌻
    • Flagship Spring Release May 🌸
    • Flagship Release Notes: Fall
  • Use cases
    • πŸ‘‰Duplicating a winning variation
    • πŸ‘‰Configuring a Feature Toggle/Flag
    • πŸ‘‰Configuring an A/B Test
    • πŸ‘‰Configuring a Progressive rollout
    • πŸ‘‰Configuring a Personalization
  • VIDEO TUTORIALS
    • [Video Tutorial] AB Test
    • [Video Tutorial] Feature Flag
    • [Video Tutorial] Progressive Deployment
Powered by GitBook
LogoLogo

AB Tasty Website

  • Home page AB Tasty
  • Blog
  • Sample size calculator
  • Release note

AB Tasty Plateform

  • Login

Β© Copyright 2025 AB Tasty, Inc, All rights reserved

On this page
  • πŸ“– Definition
  • βš™οΈ Configuration
  • πŸ’‘ Use case

Was this helpful?

Edit on GitLab
Export as PDF
  1. Use cases

Configuring a Progressive rollout

PreviousConfiguring an A/B TestNextConfiguring a Personalization

Last updated 2 days ago

Was this helpful?

πŸ“– Definition

A Progressive rollout (or Progressive deployment) enables you to progressively release a feature to your users by choosing each deployment step and the proportion of traffic allocated to your users.

βš™οΈ Configuration

To configure a Progressive rollout, apply the following steps:

  1. From the dashboard, click Create a use case.

  2. Select the Progressive rollout template. [Basic information]

  3. Enter the name of your feature and its description.

  4. Choose the primary and secondary KPIs you want to follow.

  5. Click Save and continue. [Scenario]

  6. In the next step, define your targeted users for your progressive rollout feature & the flag's name, type (text, number, boolean, array, or object), and value that will control the deployment of your feature.

  7. Click Save and continue. [Steps]

  8. Then, configure each step of your feature deployment. You can choose between a classic and a statistical rollout. In the classic rollout, visitors are either assigned to a variation or untracked. No traffic is assigned to the original version, so no comparison is possible between the original version and the variation. In the statistical rollout, you can define deployment steps and configure a rollback KPI which enables you to define, for a specific event, a percentage that you don’t want to exceed from a specific number of visitors. When using this option, you avoid any type of product regression due to the deployment of your feature. For more information on the rollback KPI, refer to Using the automatic rollback option.

  9. Click Save and continue. [Overview]

  10. Check that every step has been configured correctly.

  11. (Optional) Notify your teammates that progressive deployment is ready to go.

⭐ Good to know

For each type of rollout, you must define the date, time, zone and % of users involved in the first wave of deployment. Then, you will have to choose between a deployment with fixed steps or customized steps by defining the % of users allocated and the frequency of each deployment step.

πŸ’‘ 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 want to keep your conversion rate above 8.2%.

To do so:

  1. Create a Progressive rollout use case on your Flagship account.

  2. Choose the KPI you want to follow. Here, you can select the conversion rate generated by your feature

  3. Configure the flag that will control your new feature.

  4. Set your targeted users to All users so that all your visitors can see the feature.

  5. Configure your deployment steps as a statistical rollout and with fixed steps of 10% of the users every week until you have reached 100%.

  6. 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.

  7. Select the < operator and enter the rate (8.2%).

  8. Enter the number of users from which the rollback can be done in case the conversion rate is lower than 8.2%.

  9. Check the overview of your Progressive rollout.

  10. Save and activate your use case via the dashboard.

Need additional information?

Submit your request at product.feedback@abtasty.com

Always happy to help!

πŸ‘‰