"Thanks to Split, we were able to learn that the risky version actually had the highest adoption by our customers while keeping overall signup conversion steady."

"We use feature flags and run experiments a lot more because it’s easier now with Split. We can target a random sample size. We can increment the size of that sample really easily, and we can toggle it off immediately if there’s an issue."

“By decoupling experimentation decision-making from engineering Resources [with Dynamic Configuration], product teams become empowered to make fast and flexible changes to the product with little to no technical knowledge.”

"Split’s full-stack experimentation platform has been built with engineering and product teams in mind. Its robust architecture and rich feature set integrates into our internal platforms and helps power experimentation across our entire engineering organization."

"It’s powerful to think about all features launched before Split and how many of those must have cost us money that we don’t know about."

"As we improved our checkout process relying on Split to measure the impact of our changes, we saw an overall increase in conversion year over year, and that’s made a huge difference on our bottom line."

"With Feature Monitoring, our engineering team can deploy rapidly while ensuring that new functionality won’t negatively impact our core KPIs such as page load time and errors per user."

"90% of our changes are behind a split (feature flag)."

"The kill button is super easy. Now I just, ‘whoop’, kill it. If we are seeing something wonky, it makes it so easy to turn off. When we’ve triaged the feature we can go back and re-enable it."

"Split has transformed the way that we deliver software. Granular targeting of features to customers has made us more responsive, and data from Split gives us an audit trail in case any issues arise."

“The thing that’s great about Split is that you can change the behavior of the product outside of a code deployment.”

“Split has allowed Vida to test our mobile application in a way we wouldn’t be able to do otherwise.”

“If we built this in-house, most engineers would look at this and say ‘feature rollout, it’s not that hard’. But when you think about having multiple environments, having a UI, conditional filters, an impression data pipeline, all that—it’s a whole team working for a very long time to be able …

"Split's controlled release capability provides us a non-disruptive and dynamic way to ship features for testing and deployment. More importantly, it provides the data we need to quickly iterate on our product features in an informed manner.”

"A/B testing is a side effect of controlled release. That’s what I love most about Split."