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

“We had the intention to change the password field, but we didn’t have a way to know how good it was effectively, and to be able to control it in-house, within our product team. Split allowed us to do all of that and more.”

"Split gives me a lot of confidence in our releases as we are able to customize our rollouts, and even roll back quickly if needed. It also allows us to target certain segments that we’d like to release to prior to others.”

“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 …

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

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

"Our team uses Split feature flags to deploy quickly and experiment with new ideas. Feature Monitoring gives us a safe way to release features to our global user base with less risk."

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

“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.”

"Without Split it was hard to time the release of our web app, API, and mobile app – given app store approvals. Now we can group a change behind a feature flag, do a production dry run, and toggle it on for users."

"Split gives us an easy and fast way to pull the plug if something goes wrong without a heavy involvement from engineers."

"Split has made us more confident in our release process and also more confident in our data decisions."

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

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