41 Split Testimonials

"Split allows us to safely merge code with confidence."

"Split is incredibly empowering for product managers. The web console consolidates and provides transparency into every release, while also enabling teams to make changes dynamically without relying on engineering. With Split, engineering and product teams can collaborate to more efficiently to create, manage, and complete rollouts that much faster.”

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

“Split provides so much more than just a tool set change in that respect. You know, it sounds simple, feature toggles, but it’s transformative in nature. It’s transformative in terms of the teams, in terms of the culture that we adopt.”

“Split provided the platform and integrations we needed to run full stack experiments for key technical and customer experience questions.”

“Without Split, rollbacks could take a couple hours to a day. And after that, there might still be a lot of code cleanup. Split helped us increase our engineering velocity and code stability.”

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

"To balance rapid development with the high availability our customers demand, we needed total control over releasing new functionality. To build and maintain such a system would have taken extensive time and resources. With Split, we're getting the features we need today along with the help of a team of experts to support us as we continue to scale in the future.”

"Using Split with FullStory allowed us to humanize our experiments and empathize with our customers by validating the quantitative results with real user sessions that revealed how customers felt when interacting with our features."

“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 to do all of that.”

“If we build it we have to test it to make sure it’s doing the right thing. When we conduct backend experiments, we have to know the system will remain reliable. We have to make sure the backend behaves in a way that doesn’t impact the user experience.”

"One of our first experiments was a great learning experience. It prevented us from introducing something that we thought was good, but actually would have likely given us a negative impact. We’re now doing another iteration to get it right."

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

"The system is very reliable, it has a good number of integrations already in place and works nicely with CDPs. The support team is amazing and they answer questions in a very timely manner. Also very helpful are the governance tools. The python Admin API has also been very helpful in organizing experiments and building tools around Split.io's service."

“We have in total about 14 teams working on our digital asset management platform. All of the teams are using Split."