What KPIs do we care about for the initial release?

[rishigupta9999]

Let's try to decide what KPIs we care about for the first release. This will drive what features we want to do, or punt to post-MVP. This was also drive where we should add analytics for the first release.

The relevant ones for me are:

• [ ] % ad clicks (how effective is the one line concept)
• [x] % of users to who click "Learn More"
• [x] % of users to click sign-in
• [x] % of users who sync Spotify information
• [x] % of users who click "Party"
• [x] % of users who invite one person
• [x] avg invites / person
• [x] % of users who return at least once
• [x] % of users active 3 days later
• [x] % of users who are in a party with more than just themselves
• [x] avg consumed linkto per user (after all that is the 1st step towards recommendation).
• [x] avg consumed question per user (we absolutely need feedback).
• [x] avg # of event users commit to (under event the user can select their level of commitment).

Given the feature set in the initial release, this is probably all we can realistically measure. But please put down the KPIs or metrics you would like to measure here.

[rishigupta9999]

For "avg consumed linkto per user" we will be able to do this in terms of absolute number. But we won't be able to answer things like "avg % consumed per users" or "avg % dismissed without viewing" until v1.1.

MixPanel won't be able to answer questions like that, we'll need to build a small telemetry dashboard in the admin panel to do those database queries and display the answers for us.

Not that big a deal, but shouldn't block ship because we still have quite a bit of data to sift through as is.

[rishigupta9999]

Moving this to post-MVP. I think we'll need some legit users going through the site to see if the way the analytics are setup is fine, or do we have to make some changes.