GrowthBook Version 2.6

Launch Checklists, Teams, Stale feature flag detection, and more!

· 3 min read
GrowthBook Version 2.6

We’re back from Thanksgiving with a new version of GrowthBook! Version 2.6 contains many highly requested features and improvements and results from a lot of hard work from the team and community. Check out some of the highlights below.

Custom Pre-Launch Checklists for Experiments

Top experimentation teams empower everyone at their company to design and launch their own A/B tests. Removing a centralized bottleneck is great for velocity but also tends to lower the overall quality of the experiments. With our new Customizable Pre-launch Checklists, you can now enforce your organization’s best practices around experiment design without slowing things down. There are a number of predefined options, such as requiring a hypothesis or screenshots, as well as the ability to add your own custom ones, such as creating a Jira ticket or alerting the support team. This feature is available to our Enterprise customers and you can read more about it on our blog:

Saved Groups Improvements

We’ve completely revamped Saved Groups and made them a first-class citizen for targeting feature flags and experiments to your users. In addition to Inline Groups, where a list of ids is added directly in the GrowthBook UI, there is now support for a new type — Runtime Groups, where group membership is determined within your application and passed into the GrowthBook SDK at runtime. We have much more planned for Saved Groups in the future, so stay tuned! You can read about the new improvements in our docs:


You can now organize your GrowthBook users into teams, each with their own set of permissions! When combined with projects, this gives Enterprises a really powerful way to manage their organization at scale. Teams are also fully integrated into our SSO and SCIM offerings so they can easily be synced from Okta, with more Identity Providers coming soon. Read more about teams in our docs:

Stale Feature Flag Detection

Feature flags are a fantastic way to reduce risk during deployments, but they can also be a source of technical debt. It’s common for engineers to forget to clean up feature flags from the code that aren’t being used anymore. In this release, we added some basic stale feature flag detection to help solve this problem. There is a new “Stale” column on the Features page that will highlight any features that we think are good candidates to be cleaned up (along with a reason why that appears on hover). Read more about this feature and our future plans on our blog:

Easier Installation on Low-Code Platforms

For users of low-code platforms like Shopify or Webflow, you can now drop a single script tag on your site and launch your first experiment within minutes using our Visual Editor. This pre-bundled script tag handles everything for you automatically — it stores a unique anonymous cookie id for the user, sets helpful targeting attributes such as deviceType and UTM params, and sends events to and GA4/DataLayer when available. View our dedicated guides for Shopify and Webflow for more info.

Other improvements

Plus many more changes and bug fixes which you can read about here:

Read next

Want to give GrowthBook a try?

In under two minutes, GrowthBook can be set up and ready for feature flagging and A/B testing, whether you use our cloud or self-host.