Not entirely a #getting-started question, but curious if anyone has found a naming scheme for metrics that they are particularly happy with? For example we have experiments that might look at varying conversion windows (24hr, 72hr, 168hr) or have an activation metric but are otherwise identical in terms of the SQL definition so just naming them by the conversion itself is insufficient. e.g. if we had a “purchase” or “revenue” metric and we wanted to evaluate conversion windows, activation, caps, converted users only etc we quickly have a lot of combinations of attributes. We’ve thought about adding short-hand/suffixes in the name perhaps something like “Purchase (CW: 24h)” or tags for some of the properties. Alternatively @fresh-football-47124 @future-teacher-7046 it would be great to have a default for some of those attributes but the ability to override or set them on a per experiment basis instead of requiring two metrics for different conversion windows etc.

@future-teacher-7046 did we add this option?

We did start adding the ability to override metric properties on a per-experiment basis. Right now, it's only conversion windows and risk thresholds, but we do plan to add more properties in the future.

We’re on the 2022-11-13 release (1.8.0), is that in a more recent build?

We're doing a 1.9.0 release soon and it will be included in that. It's available on the

latest

tag now. This feature also requires a commercial license key on top of the open source version.

Got it, thx!

Your idea of adding qualifiers like

(CW: 24h)

should work. It's a common problem and it's on our roadmap to figure out a more elegant solution. Adding more experiment override properties is just the first step.