This message was deleted.
# announcements
w
This message was deleted.
f
Yes, segments are only really useful for stable user properties over time, not things that change per request or session. We have custom SQL filters for the experiment queries. We could add something similar for the impact estimate queries.
o
I need something that could cover scenarios like experiment sample estimates based on "users with more then 3 sessions who visited this particular page" or "users who visited this page and had more then 3 transactions". These kind of properties always change but can still be called user properties (at least that's the philosophy platforms like Amplitude use)
I am using dimensions when analyzing experiment results and it's actually beatiful how it's implemented (value distribution between groups, in particular). I expected something similar in the estimates report - where you can filter out certain pageviews based on their dimensions.
148 Views