The use case: how Swimply deploys Statsig
Swimply uses Statsig for full-stack feature flagging and A/B testing, covering front-end changes like landing pages and checkout flows and back-end changes to search and ranking. It pulls in existing Segment events for experiment analysis and uses feature gates to split traffic between shuffled search results and a predictive listing algorithm.
In the customer’s words
It came down to being able to trust in Statsig, and having time savings along with that. There's not a lot of things I have to configure or set up beforehand.Statsig users in Marketplace
Companies in the same sector, with public evidence.
See all Statsig customers
Go straight to the source
Based on Statsig’s published case study. We check the public evidence; the results are reported by the vendor.
statsig.com- Last checked
- Nov 13, 2026
Open source capture What the story claims, and what we checked
What we compared with the page.
- The figure: 20%Checked
Printed word for word on the page, near the name of Swimply.
- The passage quoted aboveChecked
Copied word for word from the page, near the name of Swimply.
- Swimply uses StatsigChecked
Confirmed line.
- The result itselfNot checked
We quote it; we did not measure it.
By leveraging Statsig's feature gates, Swimply was able to split traffic in a bandit framework between shuffled search results and an algorithm that predicts which listings users are most likely to engage with.