Umami - open-source web analytics

Umami is an open-source web analytics platform designed to provide comprehensive user management, website tracking, and report generation capabilities. It combines a React/Next.js frontend with a Node.js/Prisma backend to deliver analytics services with a focus on privacy and simplicity. The platform supports multi-language UI, real-time user activity monitoring, and customizable dashboards, making it suitable for administrators, regular users, developers, and website owners.

• Provide a secure and user-friendly platform for web analytics.
• Enable real-time monitoring and reporting of website data.
• Support customization and flexibility in report generation and dashboard management.
• Ensure privacy and data security for all users.

• Increased user adoption and engagement with the analytics platform.
• High accuracy and reliability of real-time data tracking and reporting.
• Positive user feedback on customization and multi-language support.
• Low incidence of security breaches or unauthorized access.

• User Authentication and Role Management
  1. As user, I want to log in with my credentials so that I can access the application securely
  2. As admin, I want to manage user roles so that I can control access to different parts of the application
  3. As developer, I want to ensure that all API requests are authenticated and validated so that I can maintain application security
  4. As user, I want to log out so that my session is securely terminated
• Website Data Tracking and Analytics
  1. As website owner, I want to embed the Umami tracker on my site so that I can collect analytics data about my visitors
  2. As data analyst, I want to access real-time user activity data so that I can make informed decisions based on current trends
  3. As developer, I want to use the Umami API to retrieve website analytics data so that I can integrate it into custom reports
• Real-time User Activity Monitoring
  1. As website owner, I want to see the number of active users on my website in real-time so that I can understand user engagement and activity
• Custom Report Creation and Management
  1. As user, I want to create a custom report with specific analytics data so that I can analyze the data according to my needs
  2. As user, I want to update the parameters of an existing report so that the report reflects the latest criteria and data
  3. As user, I want to delete a report so that I can remove reports that are no longer needed
  4. As user, I want to download a report so that I can have offline access to the data, except for Revenue and Attribution types
• Multi-language Support for UI
  1. As non-English speaking user, I want to view the analytics dashboard in my native language so that I can understand and interact with the platform more effectively
  2. As global company, I want to provide my team with access to analytics in multiple languages so that team members can use the platform in their preferred language
• Dashboard for Data Visualization
  1. As user, I want to view website analytics data in a visual format so that I can understand the performance of my websites
  2. As user, I want to navigate through paginated data so that I can view all available analytics data
  3. As user, I want to interact with EventsTable labels to explore data interactively
  4. As user, I want to edit the dashboard layout and save changes
• User Login
  1. As user, I want to log in using my username and password so that I can access my analytics dashboard securely
  2. As system administrator, I want to ensure that login is disabled when necessary so that unauthorized access is prevented during maintenance
• Role Assignment and Management
  1. As system administrator, I want to assign roles to users so that they have appropriate access levels within the application
  2. As system administrator, I want to view the roles of users so that I can manage access levels effectively
• API Request Validation and Access Control
  1. As API consumer, I want my requests to be authenticated and validated so that I can ensure secure and reliable interactions with the Umami API.
  2. As administrator, I want to ensure that only authorized users can access or modify user data so that I can maintain the security and integrity of the system.
• Client-Side Tracker Script Embedding
  1. As website owner, I want to embed the Umami tracker script into my website so that I can capture and analyze user interactions
  2. As developer, I want to track custom events on my website so that I can gather specific user interaction data
• Server-Side Data Collection and Processing
  1. As system administrator, I want the server to validate and store incoming tracker data so that the data is accurate and secure
• Active Users Real-Time Monitoring
  1. As website owner, I want to see the number of active users on my website in real-time so that I can monitor user engagement and activity instantly.
  2. As data analyst, I want to have access to real-time user activity data so that I can make informed decisions based on current user behavior.
• Event Data Report Management
  1. As User, I want to create and view event data reports with specific filters and fields so that I can analyze event data effectively
• Funnel Report Management
  1. As marketing analyst, I want to create a funnel report so that I can understand the conversion paths on my website
  2. As product manager, I want to adjust the parameters of a funnel report so that I can analyze different user behaviors
• Goal Report Management
  1. As User, I want to define goals based on specific URLs or events so that I can track the progress towards these goals
  2. As User, I want to update or remove existing goals so that I can keep my goal tracking relevant and accurate
• Insights Report Management
  1. As data analyst, I want to generate an insights report with specific parameters so that I can analyze data trends and patterns
  2. As data analyst, I want to adjust the parameters of an insights report so that I can refine the data analysis to meet specific needs
• Journey Report Management
  1. As User, I want to create a journey report to analyze user paths so that I can understand how users navigate through the website
• Retention Report Management
  1. As User, I want to generate a retention report for a specific website and date range so that I can analyze user retention over time
  2. As User, I want to update the parameters of an existing retention report so that I can see how changes affect user retention
• UTM Report Management
  1. As Marketing Analyst, I want to generate a UTM report for a specific campaign so that I can analyze the performance of different UTM parameters
• Revenue Report Management
  1. As financial analyst, I want to generate revenue reports with customizable parameters so that I can analyze financial trends and make informed decisions.
  2. As business owner, I want to view revenue data in a visual format so that I can quickly assess the financial health of my business.

• Product kind: Mixed (UI + service)
• The platform must integrate seamlessly with existing website infrastructures using a client-side tracker script.
• The backend must efficiently handle data collection, processing, and storage while ensuring data integrity and security.
• The UI must support multiple languages and provide a consistent user experience across different devices.
• Umami combines a React/Next.js frontend with a Node.js/Prisma backend to deliver web analytics services.
• The platform supports user management, website tracking, and report generation, with a focus on privacy and simplicity.
• Package gap-fill: +0 candidates (kept first-pass list; model notes: The identified gaps in the src/assets/ and src/lib/ directories do not represent distinct product capabilities that would be meaningful to users or operators. These directories likely contain static assets and utility functions that support existing features, such as user interface elements or authentication logic, which are already covered by the existing candidates. Therefore, no new product capabilities are added.)
• Still without candidate anchors: src/assets (37), src/lib (26)
• Skipped public: Contains static assets and configuration files not directly implementing product logic.
• Skipped scripts: Contains utility and build scripts not directly related to product functionality.
• Skipped .github: Contains GitHub-specific configuration and workflows, not product code.
• Skipped cypress: Contains end-to-end test configurations and scripts.
• Skipped .dockerignore: Configuration file for Docker, not product code.
• Skipped .eslintrc.json: Linting configuration file, not product code.
• Skipped .gitignore: Git configuration file, not product code.
• Skipped .husky: Contains Git hooks, not product code.
• Skipped .prettierignore: Configuration file for Prettier, not product code.
• Skipped .prettierrc.json: Configuration file for Prettier, not product code.
• Skipped .stylelintrc.json: Configuration file for Stylelint, not product code.
• Skipped dockerfile: Docker configuration file, not product code.
• Skipped license: Legal document, not product code.
• Skipped readme.md: Documentation file, not product code.
• Skipped app.json: Configuration file, not product code.
• Skipped cypress.config.ts: Configuration file for Cypress, not product code.
• Skipped docker-compose.yml: Docker configuration file, not product code.
• Skipped docker: Contains Docker-related scripts, not product code.
• Skipped jest.config.ts: Configuration file for Jest, not product code.
• Skipped jsconfig.json: Configuration file for JavaScript, not product code.
• Skipped lang-ignore.json: Configuration file, not product code.
• Skipped netlify.toml: Configuration file for Netlify, not product code.
• Skipped next.config.js: Configuration file for Next.js, not product code.
• Skipped package.components.json: Configuration file, not product code.
• Skipped package.json: Package manager configuration file, not product code.
• Skipped postcss.config.js: Configuration file for PostCSS, not product code.
• Skipped rollup.components.config.mjs: Build configuration file, not product code.
• Skipped rollup.tracker.config.mjs: Build configuration file, not product code.
• Skipped tsconfig.json: TypeScript configuration file, not product code.
• Discovery review: Host soft-pass after 3 review cycles: layout breadth ok (7/7 packages), orientation has 5 major areas / 6 capabilities. LLM still incomplete: Host subtree gate: 9 product subtree(s) never read: src/app/(main)/reports, src/app/(main)/settings, src/app/(main)/websites, src/app/(main)/teams… · Package gap-fill: +0 candidates (kept first-pass list; model notes: The identified gaps in the src/assets/ and src/lib/ directories do not represent distinct product capabilities that would be meaningful to users or operators. These directories likely contain static assets and utility functions that support existing features, such as user interface elements or authentication logic, which are already covered by the existing candidates. Therefore, no new product capabilities are added.) · Still without candidate anchors: src/assets (37), src/lib (26)
• Product kind: Mixed (UI + service) (inferred — The codebase includes both a substantial human-facing UI (React/Next.js) and backend services (Node.js/Prisma) for analytics.)
• Stack: TypeScript, React, Next.js, Node.js, Prisma, SQL
• Integrations: The tracker script integrates with the website's frontend to collect data., The server-side APIs integrate with the database to store and retrieve analytics data., The feature integrates with the broader reporting and visualization components of the Umami application, ensuring that revenue data is presented in a consistent and user-friendly manner., The feature integrates with the state management system to save and update dashboard settings.

• Feature implementation drifts from PRD — Re-analyze the feature after significant code changes