Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add analytics to dappBooster.dev #34

Open
6 tasks
pragalli opened this issue Sep 16, 2024 · 3 comments
Open
6 tasks

Add analytics to dappBooster.dev #34

pragalli opened this issue Sep 16, 2024 · 3 comments

Comments

@pragalli
Copy link
Collaborator

pragalli commented Sep 16, 2024

Important

this issue depends on BootNodeDev/dAppBooster#97 to be implemented first

I want to implement an analytics system,
So that I can track the number of times each component is tested, identify which components are most used, and monitor the number of users connecting to the dApp and the external links they visit.

Acceptance Criteria:

  1. Component Usage Tracking:
  • Integrate an analytics system to log the number of times each component in the dApp is used.
  • Generate a report showing the most used components and their frequency of use.
  1. User Connection Monitoring:
  • Implement tracking to capture the number of users connecting to the dApp.
  • Ensure data is available in a dashboard accessible to developers for analysis.
  1. External Link Tracking:
  • Configure the system to track external links users navigate to from the dApp.
  • Store and display data about these external links in the analytics reports.
@fernandomg
Copy link
Member

and the details? 🤣

@pragalli
Copy link
Collaborator Author

Here it is! wolo

@fernandomg fernandomg transferred this issue from BootNodeDev/dAppBooster Oct 1, 2024
@fernandomg
Copy link
Member

@pragalli I moved it from dappbooster as it's requesting analytics for the lading page

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants