Thanks Suhail! I'd gladly compromise on convenience/ease of use to make it easier to build (I'm sure you're more careful about making those trade offs for the less technically inclined users though)
For instance, I'd be happy to manually designate a small number of events and properties as available for the revenue-like analysis. I could say "For all Amount properties on all Charge succeeded events, I want to be able to see the average value per user, the sum per user and the sum across all events on all users". Technically that doesn't seem much different from what you already built except I could maybe add two or three of my own events.
As for segmenting events by people properties, it seems like you already have most of the infrastructure in place. Events are indexed by distinct_id and I can use the People tool to retrieve a list of distinct_ids of people matching certain criteria. Tying that together would be huge.
The related but different functionality of segmenting events by the people properties as they were when the event occurred is less important to me (this is what I can already do by copying people properties into each event). I can see how this would be a bigger headache. On the other hand though, you're already allowing us to do this because there's no restriction on the number of properties on an event.
For instance, I'd be happy to manually designate a small number of events and properties as available for the revenue-like analysis. I could say "For all Amount properties on all Charge succeeded events, I want to be able to see the average value per user, the sum per user and the sum across all events on all users". Technically that doesn't seem much different from what you already built except I could maybe add two or three of my own events.
As for segmenting events by people properties, it seems like you already have most of the infrastructure in place. Events are indexed by distinct_id and I can use the People tool to retrieve a list of distinct_ids of people matching certain criteria. Tying that together would be huge.
The related but different functionality of segmenting events by the people properties as they were when the event occurred is less important to me (this is what I can already do by copying people properties into each event). I can see how this would be a bigger headache. On the other hand though, you're already allowing us to do this because there's no restriction on the number of properties on an event.