This message was deleted.
# contributing
w
This message was deleted.
f
For #1, I think long term we would make that a built-in dimension for Mixpanel (new vs existing). That requires a few other changes first like supporting user properties for dimensions. For #2, that's a good idea to have more context for the type and behavior of metrics. We're considering splitting that table into 2 views, a simplified one for non-technical people, and a data-heavy one. Right now, it's already pretty overwhelming to non-technical people so adding more info to the table might make it worse.
🙌 1
h
For #1: what I’m hearing is that we should try to use dimensions, which I could set with super properties on each event e.g. a user’s first app open. So there I can save you the trouble of supporting user profile properties. However, how would I convert a value that has a discrete distribution to a boolean (i.e. is before or after a certain time stamp)? For #2: sure something like that would be helpful. If there’s any small thing you can add that could help with specifically type of metric (especially differentiating between binomial and count) would be nice
f
In SQL, we have support for template placeholders, so you can add something like
WHERE date < '{{ experimentStart }}'
. I think we can do something similar for Mixpanel.
h
yeh if setting something like that up wouldn’t kill ya, would be great, because then I can use dimensions with the event super properties
f
I made a PR for this. https://github.com/growthbook/growthbook/pull/342 Doing some final testing now, but should be good to go soon
❤️ 2
🙌 2
157 Views