ABsmartly vs. Statsig

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
ABsmartly
Score 9.7 out of 10
N/A
ABsmartly is an A/B testing and experimentation tool for use across web, email, and apps, both server-side and client-side. The ABSmartly platform is designed for product teams and PLG-driven organisations who want to make data-driven decisions. The ABsmartly platform caters to various testing scenarios, including feature flags, split testing, multi-variant, multi-page, multi-platform, SEO tests, cross-device testing, among others. ABsmartly was founded by experimentation…N/A
Statsig
Score 0.0 out of 10
N/A
Statsig is a feature management with feature flags, pulse, holdouts, from the company of the same name in Bellevue.N/A
Pricing
ABsmartlyStatsig
Editions & Modules
No answers on this topic
Enterprise
Custom
annual pricing
Offerings
Pricing Offerings
ABsmartlyStatsig
Free Trial
NoNo
Free/Freemium Version
NoYes
Premium Consulting/Integration Services
NoNo
Entry-level Setup FeeNo setup feeNo setup fee
Additional DetailsABsmartly has an events-based pricing model, clients have unlimited experiments, metrics and platform users, and they pay per event. ABsmartly has no pricing tiers or packages, so all customers get all features, including the advanced Group Sequential Testing engine, real time data processing, and collaborative tools. ABsmartly handles the infrastructure costs and provides the platform, however if clients wish, they can handle the infrastructure on their side. ABsmartly's event-based plans start at €60,000/year for 50 Million events per month. ABsmartly includes onboarding, standard training and support at no extra cost. ABsmartly has 2 categories of billable events: Exposure events An exposure event happens every time a call is made to check which variant (of an experiment or a feature flag) to show a visitor. The number of exposure is dependent on the number of unique visitors, the number of experiments and the number of exposure per experiment. Exposure Events = {# unique visitors} x {# experiments} x {# experiment exposures} Goal events A goal event happens every time a goal is triggered by a visitor of an application. A goal is what is used to create an experimentation metrics and they usually represent an action taken by visitors, a click on a button, a conversion, a cancellation, etc. The number of goals events is dependent on the number of unique visitors, the number of goals and the number of goals exposures. Goal Events: = {# unique visitors} x {# goals} x {# goal triggers}
More Pricing Information
Community Pulse
ABsmartlyStatsig
Considered Both Products
ABsmartly

No answer on this topic

Statsig
Chose Statsig
Statsig is easier to use and has more tools for analysis, though we were working with the open source version of Flagsmith, merely to handle feature flags, and using Heap and homegrown tools for manual analysis, so the Cloud version may be different
Best Alternatives
ABsmartlyStatsig
Small Businesses
Convert Experiences
Convert Experiences
Score 9.9 out of 10
GitLab
GitLab
Score 8.7 out of 10
Medium-sized Companies
Dynamic Yield
Dynamic Yield
Score 8.3 out of 10
GitLab
GitLab
Score 8.7 out of 10
Enterprises
Dynamic Yield
Dynamic Yield
Score 8.3 out of 10
GitLab
GitLab
Score 8.7 out of 10
All AlternativesView all alternativesView all alternatives
User Testimonials
ABsmartlyStatsig
Likelihood to Recommend
No answers on this topic
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
Read full review
Pros
No answers on this topic
  • Clear experimentation insights and details
  • Experimentation health and performance ratings
  • Statistical analysis of in flight work
Read full review
Cons
No answers on this topic
  • Complex data science focussed UI
Read full review
Usability
No answers on this topic
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
Read full review
Alternatives Considered
No answers on this topic
Read full review
Return on Investment
No answers on this topic
  • We uncovered several feature releases that were causing a negative impact on our product activation rate by running exclusion experiments
Read full review
ScreenShots

ABsmartly Screenshots

Screenshot of ABsmartly platform overviewScreenshot of ABsmartly Group Sequential Testing time savings and efficiency gainsScreenshot of ABsmartly's Experimentation TemplatesScreenshot of ABsmartly interaction detection - interactions rarely happen but good to know if they doScreenshot of ABsmartly feature flag creationScreenshot of ABsmartly health checks