---
tags: Product
---

# Daohaus Performance Report

### Sections
- usage data
- ux insights
- AT: what kind of analytics are possible to get? Such as bounce rates/unique vs returning users. To brainstorm on - what kind of metrics or information provides insight into where new users drop off?
- SK:this is where we'll need to get most creative. the data we have access to is pretty limited to what we can get on-chain from transactions.
- so we can see # of unique addresses interacting with our contracts
- can do counts on new addresses each week
- maybe transaction counts each week too

there's been a lot of resistance to tracking user data, even if it's only used to try and improve the product. lots of push back in things like google analytics.
- i will research what other web3/decentralized focused projects might be using

need to think more on how we can see where user's drop off, but i think qauntitative data on this will be impossible at the moment

AT: that's what I expecected and absolutely makes sense. I'd like to do some qualitative data gathering talking to community members, so maybe I can gather some insights/inspiration for angles to gather data from that. Grabbed your transaction data points and added below.

- feature performance
- bug/fix reports
AT:
this information coming from clickup or github? Clickup looks like the 'bug' tag would need to be pretty accurately applied (new to clickup, so probably missing some things)

SK:
- yeah i'll make sure all bug tasks have the 'bug' tag and we can make reports off that
- we also have an error logger app that will give us a list of these and help us figure out sections of the app that are causing problems
- honestly this logger app could be expanded to get a little more usage data, will look into that a bit

## Metrics

### Some growth metrics - per month totals
- Number of new DAOs
- Per type
- Number of new Members  
- Active total
- Inactive total
- Jailed total

- Number of community participants < loot holders/receivers, not sure how these are classified
- SK: all we can see are members really. members can have shares, loot or both. only shareholders can vote.
- AT: I’m trying to articulate this question, might not make sense - would a percentage or #/# be useful for active voters/total able to vote type stat give us an indication of participation? Over time giving a kind of health metric for a DAO? It might be a per DAO stat though, which speaking of - should we also consider any metrics that are available in each DAO that help them determine the health of their community? ex. participation drop off, lot of people quitting, etc. I could see this misleading depending on the type of community someone is building, but just throwing the thought out there

- Number of Proposals
- No votes < would this help see spammy proposals? Maybe non-sponsored proposals as well?
- SK: yeah non-sponsored would be interesting - maybe especially if they've been unspronsored for a while.
- AT: should we change this to 'non-sponsored'?
- Per type
- Passed
- Per type
- Failed
- Per type

* Ragequit count
* Number of Boosts added to DAOs
* Number of new users in Discord

### Platform Overall Stats (month averages)
- Average number of proposals
- No votes/Non-sponsored
- Passed
- Failed
- Number of boosts across platform
- Average boosts used per DAO
- Average number of members per DAO
- Average loot holders per DAO < is this a metric that’s possible?
- SK: yep - let's think about how we want to report members (share holders/loot holders/both... wonder what is most useful)
- AT: if not difficult we could start with both, we can cut down on any stat that isn't providing insight after a few months
- Average number of DAOs a community member is part of
- total value into daos ($$)
- total value out ($$)
- number of unique addresses interacting with our contracts
- counts on new addresses
- transaction counts

### Usage Info
- Usage per Boost
- Outside of app
- twitter engagement
- medium/blog views/claps
- Error log report
- clickup bug report
- error log w/ app areas

What if we had a section for 'context'?
- thoughts on external activity that might be driving these stats?
- or just a section listing the newest features/updated areas of the app
- i suppose whenever we launch a new feature we might want to take a minute to figure out of we can measure it somehow
- or any new marketing initiatives that we could help measure effectiveness
- like if we sponsor a hackathon, can we measure impact from that?

AT: the context section sounds great, I think you mentioned in discord having this as a post-release step for feature development which makes sense.

Implemented

Total overview (whole life of the platform)
- daos created
- by network
- by purpose

- total value in/out

- proposals submitted

- member
- TBD: this isn't unique members just total in all daos
- TBD: counts any membe that ever had a share/loot

- minions
- TBD: generalize to boosts activated

tbd:
- maybe these link into sections ie) daos, proposals, members, bank