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

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

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

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

“The integration with Amazon S3 helps us track all the events that happen offline. In our case, an example is someone investing money on our own bank account. That cannot be tracked through Segment, but we obviously aware of when someone sends us the money. An integration with Amazon S3 …

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

"Split has enabled us to move much faster. We can ship code straight through to Production knowing that our users won’t see it until we’re ready to show them.”

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

"It’s inherently collaborative and transparent, a rigorous and sound process based on the hard data we know about."

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

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