Conductrics V3 vs. Statsig

Best suited for high tech companies, or companies with DEVs that have a lot of experience.

Incentivized

Statsig is well suited for running straightforward a/b tests on frontend deployments. We've actually used it to log events on our backend and used the HTTP API to integrate with tools like Hubspot to evaluate email campaigns

Incentivized

• Splitting traffic
• Customer support
• Advanced testing

Incentivized

• Clear experimentation insights and details
• Experimentation health and performance ratings
• Statistical analysis of in flight work

Incentivized

• Requires high technical abilities
• Setting up reporting metrics can be tedious
• Complex to link with other reporting sources

Incentivized

• Complex data science focussed UI

Incentivized

It's complex if you aren't sure what to look for, documentation is complex as well. But they have a great customer team that replies fast and is happy to help.

Incentivized

For the most part it is pretty easy to use. - There are some quirks with the javascript SDK (getExperiment().getValue?). - The Events vs. Metrics design pattern is complex, and creating new Metrics from Events can be frustrating if you are trying to use event metadata - It's really frustrating not to be able to link Static IDs (before a user signs up) to User IDs, in order to follow users all the way through onboarding, or to log events that occur for signed in users when you are exposing the experiment to users before they've signed up

Incentivized

Harder to use but better metric reporting when it comes to statistical significance and confidence reporting.

Incentivized

Incentivized

• Positive rev impact

Incentivized

• We uncovered several feature releases that were causing a negative impact on our product activation rate by running exclusion experiments

Incentivized