Spec Document for Plausible Analytics

--- title: Spec Document for Plausible Analytics tags: magesmiths, product, analytics --- # 1. Objective The objective here is to list out the rationale for using Plausible Analytics, as well as the steps required for getting Plausible set up. # 2. Rationale ## 2.1 Why analytics? We currently does not have any analytics set up for usage information and trends, preventing us from making **data-driven product decisions**. A product analytics tool will show us how users are using the app on daohaus.club, helping to **increase the accuracy of our product and design decisions**. This is an important data input which can be **complemented with other on-chain data sources (such as Dune dashboards)**. At the end state, we will have a **birds' eye view of DAOhaus metrics**, enabling us to make better decisions from both off-chain and on-chain sources. ## 2.2 Why Plausible? Plausible was chosen because: 1. Open-source & built in the open [(roadmap here)](https://plausible.io/roadmap) 2. Lightweight (<1KB ) 3. Respects privacy (no cookies at all) The other alternative was Matomo and the Plausible team did a [comparison here](https://plausible.io/vs-matomo). At this stage, Plausible seems to be a better fit as it is **easy to set up, has features we need (page analytics + events tracking) and doesn't use cookies at all**. Pricing seems to scale more fairly too (Plausible's monthly cost is $12 while Matomo's $60 for a 100K monthly page view site) Given that there's a 30 days free trial, we should **set up Plausible, understand our actual analytics needs and then re-assess its suitability within the 30 days**. # 3. Steps to set up I can set things up, but here's an overview of the steps required. 1. Set up account 2. Paste script in <script defer data-domain="aaaaa.com" src="https://plausible.io/js/plausible.js"></script>