jessicaraygun
Joined 12 years ago
Joined 12 years ago
We're both here to answer any questions :)
I agree that it would be useful to be able to change the confidence level based on a site's specific needs - this is a feature I am looking to implement in Confidence.js soon.
I was in charge of the math here - I really appreciate your feedback. You seem really knowledgeable in this area and I would love to improve this A/B testing library.
If you have some time to chat, email me at [email protected]
We did a lot of digging and there aren't a lot of resources that are easy to digest - but this one really stood out to us:
http://visualwebsiteoptimizer.com/split-testing-blog/what-yo...
I'd love to write a summary of everything I've learned - maybe a blog post in the near future!
Thanks for bringing that to my attention - I agree that our explanation is a little more convoluted than it needs to be. I'll update that later today to be more "readable" ;)
Confidence.js comes from how we operate on A/B tests at sendwithus - we think of them as variants associated with results. While the code could definitely boil down to a few simple math functions, we find objects to be a good way to organize our data models.
Confidence.js is based on the A/B testing code that we use at sendwithus.
A/B testing math is hard and we've worked really hard on making this great. Let us know what you think!
Our Z-Test Method in Confidence.js pinpoints when results become statistically significant by calculating the required sample size at any given time using the standard error, zScore, and margin of error. If we have more samples than required, we can stop our test with confidence that we have statistically significant results.
We're still working out a way to do this with the new method - we have a hunch it might have to do with identifying when the confidence level becomes stable (as it does with more samples over time).