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.