Release Notes

Management Console

• Dynamic minimum detectable effect
  Split has now launched dynamic minimum detectable effect where statistically significant results can be obtained based on the dynamic relationship between the observed effect size and observed sample size of experiment metrics. For example, Split will indicate the sample size required for the given effect size to be statistically significant. Alternatively, we will also indicate the effect size needed for the results to be statistically significant with a given number of samples.
• Review periods
  Customers can now set how long an experiment should run before results can be reviewed. Split will produce a warning on the metrics impact dashboard if an experiment has not met the minimum period.

Read more about this release in our blog

Management Console

• Sample ratio check
  The Split platform will now perform a sample ratio check with each calculation update to monitor for a significant deviation between the targeted and current sample ratios.

REST API Enhancements

• New Tag and enhanced Environment endpoints
  Split has released new and modified existing endpoints on the Admin API to allow:
  • Creation of Environments
  • Updating Environment Names and Type
  • Deleting Environments
  • Updating Tags on Splits
  • Getting Splits by Tags

Security Framework

• US Privacy Shield Certification
  Split is amending and expanding our Privacy Policy to be US Privacy Shield compliant. Learn more in our blog.

Management Console

• Enhancements to Split’s experiment attribution & exclusion logic
  Users are now allowed to move between targeting rules once and are allowed one unique rule and treatment change. Before this change, a change in treatments caused users to be removed from the sample. With this change, it is now possible to target customers using an attribute that when changed will result in a different treatment. Learn more in our blog or in our documentation.