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

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

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

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

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

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

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

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

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

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

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