Implement basic analytics

[melinath]

We should provide basic user interaction analytics on dancerfly. Part of the trick will be figuring out the best way to cache the analytics data. Ideally we would put the data in a separate database, but for now same db should be fine. Analytics to implement in this sweep:

• [ ] Money received over time, broken down by payment type
• [ ] items bought over time, broken down by item type
• [ ] ???

[melinath]

I think there are more things that could be tracked - say, transfers, once we implement them - but it doesn't seem like folks are overly interested in this type of analytics. See also: https://www.facebook.com/stephen.r.burrows/posts/931366501944

[melinath]

If we wanted to go crazy, we could track things like:

• [ ] Every time a user views an event.
• [ ] Every time a user adds / removes something from their cart.
• [ ] Every time an attendee is created / deleted.

This could hypothetically let us know things like: how many people come look at the event without then buying anything.

When we do get to this ticket, we'll probably want to have a flag on the event as to whether we're tracking analytics for it. That way we just don't ever track anything for older events (rather than having incomplete data.)

[melinath]

I think it could be useful to track when carts are created and expire / check out & when items are added / removed. We could use this (for example) to figure out when people are starting carts and then abandoning them, never to return - or to re-create checkout processes when something goes wrong.

[melinath]

Um here's a thing that would actually be cool: How many people attend an event who also attended a previous event you ran.