I already have a revenue property on all my users in mixpanel. It seems like this new feature does two things
1) It keeps track of a revenue property as a time series. I.e. you can later look at the changes of revenue for a user over time (in their HTTP API you use a new $append command instead of $set)
2) It allows you to look at aggregate values (such as sum and average) for all revenues of all people in a certain group
I'm curious if this is something that could be extended to arbitrary properties on users. I operate a phone service and track usage of minutes in a similar way. It'd be great if I could do a similar kind of analysis.
It would be even better, if people analytics and events tied in a little more closely. I'm already tracking a "Charge succeeded" event that's tied to a distinct_id. If I could segment events by people properties (i.e. show me the "Charge succeeded" events for all people with Source=x), I could use the aggregate functions of the segmentation screen to do a lot of what revenue analytics provides and much more. I also wouldn't have to redundantly attach people properties to all my events anymore. Currently all of my events contain all people properties (such as Revenue, Number of minutes used, etc), so that I can segment by them.
In case suhail or anyone else is following along this thread, it'd be great to hear your thinking.
Hi Jonas! You might be interested in our Mixpanel integration: At Bitdeli, you can create all the segments and metrics you need by running custom analytics scripts for all your raw historical data from Mixpanel - all without changes to your current setup.
We like to think our approach as best of both worlds: Get the beautiful interface and intuitive functionality Mixpanel provides with the ability to answer the occasional hard questions about your data.
Feel free to drop me a line at jyri@bitdeli.com and we can help you get started!
We hear you and we're thinking about how. It's a huge engineering/scalability challenge given the amount of data a single customer potentially can have.
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.
1) It keeps track of a revenue property as a time series. I.e. you can later look at the changes of revenue for a user over time (in their HTTP API you use a new $append command instead of $set)
2) It allows you to look at aggregate values (such as sum and average) for all revenues of all people in a certain group
I'm curious if this is something that could be extended to arbitrary properties on users. I operate a phone service and track usage of minutes in a similar way. It'd be great if I could do a similar kind of analysis.
It would be even better, if people analytics and events tied in a little more closely. I'm already tracking a "Charge succeeded" event that's tied to a distinct_id. If I could segment events by people properties (i.e. show me the "Charge succeeded" events for all people with Source=x), I could use the aggregate functions of the segmentation screen to do a lot of what revenue analytics provides and much more. I also wouldn't have to redundantly attach people properties to all my events anymore. Currently all of my events contain all people properties (such as Revenue, Number of minutes used, etc), so that I can segment by them.
In case suhail or anyone else is following along this thread, it'd be great to hear your thinking.