This looks great, but if I can make a suggestion, a guide in your docs on how to use this with Matomo[1] would go far. Growthbook provides Feature Flag and A/B Testing, but you have to bring your own analytics. Matomo provides those analytics and is also open source and self hosted, and would be an excellent match. There's been an issue in about integrating since September[2], and having a guide with SQL examples for…
Thanks for the suggestion. We added MySQL support so we can work with Matomo now, but we're definitely lacking in documentation and tutorials. There's a similar issue with people using GA4, Snowplow, Segment, and anything else with a pre-defined schema. It should be way easier to use these systems with GrowthBook. Like there's no reason to even write SQL most of the time if we know the Matomo table structure in MySQL…
Launch HN: GrowthBook (YC W22) – Open-source feature flagging and A/B testing
41–47 of 47 posts
Re: Launch HN: GrowthBook (YC W22) – Open-source feature flagging and A/B testing
#42Re: Launch HN: GrowthBook (YC W22) – Open-source feature flagging and A/B testing
#43Personally, I am a happy user of PostHog (gitHub.com/posthog/posthog) which also supports experimentation and feature flags alongside product analytics.
Re: Launch HN: GrowthBook (YC W22) – Open-source feature flagging and A/B testing
#44Looks promising! Personally, I am a happy user of PostHog (gitHub.com/posthog/posthog) which also supports experimentation and feature flags alongside product analytics.
Re: Launch HN: GrowthBook (YC W22) – Open-source feature flagging and A/B testing
#45Isn't this a bad practice in general? Not only you split your (potentially limited) sample count, but it is very unlikely that there is ZERO interaction between A/B tests. Even if you test something on one page and another thing on a different page, there might be some interaction between the two changes.
Re: Launch HN: GrowthBook (YC W22) – Open-source feature flagging and A/B testing
#46> Can I run multiple A/B tests at a time? Yes! In fact, we recommend running many experiments in parallel in your application Isn't this a bad practice in general? Not only you split your (potentially limited) sample count, but it is very unlikely that there is ZERO interaction between A/B tests. Even if you test something on one page and another thing on a different page, there might be some interaction between the…
There are two ways to deal with the bigger interaction effects. First is to predict which experiments will meaningfully interact ahead of time and split the samples between them (making the tests take longer). Second is to run tests in parallel on all users and look at the data to determine interaction effects after the fact (and potentially need to invalidate some results).
In our experience, a mix of these approaches works best. It's really hard to predict meaningful interaction effects ahead of time, so save that for the really obvious cases (e.g. black text on a black background). For everything else, the benefit of running more experiments usually outweighs the cost of occasionally needing to throw out results because of interaction effects. It's much better to run 10 tests and need to throw out 1 than it is to run 5 tests.
Re: Launch HN: GrowthBook (YC W22) – Open-source feature flagging and A/B testing
#47Congratulations on the launch, guys. Over at Statsig we have tremendous respect for what you have been doing.
Hey Vijaye, will Statsig support diff-in-diff / SEO Experiments in the future? I saw that you got Multi-armed bandit out the door and I'm hoping to see more kinds of experiment pop up on your platform.