Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Looked at it.

I like this approach. Is closer to what web developers are used to: We included analytics on every page, we don't need to create reports until we find a problem or something to optimize... and we still can do forensics.

2 side notes:

– Asked who did this in our app, he told me it was really easy to add mixpanel on "every event". But anyway, he would prefer that it was automatic... and not having to do it again on every view we include.

– As said on my previous comment, for this you need it to be cheap. If not, im creating a problem instead of a solution. At this scenario, mixpanel' people looks less exprensive than heap' sessions.

A question:

Does a "pay for the metrics you use" model makes sense?

Collect everything, what you pay is some sort of multiplier of (metrics used in reports or segments per user). It would be great, at least for this scenario.

I read in the first comment (from mixpanel founder) that the hard part is not collecting data but making them work as formulas.

That makes you able to not storing the data that has not been included on any report or segment for more than a month or something like that if you want to reduce costs.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: