web-wallet: Add Sentry integration

[Daksh14]

Summary

💡 Add a clear and concise description of the reason why this needs to be worked on. Focus on the big picture rather than implementation details. What use case does it support? What is the expected outcome?

Analytics are interesting for click hotmaps and viewers

Possible solution design or implementation

💡 Add clear and concise description of concrete solutions you've considered. Include possible drawbacks. Add diagrams, pictures, description, code-snippets, or anything else that might help solving the issue. Consider adding different implementation alternatives with tradeoffs.

Use swetrix, GDPR compailant, privacy friendly

Additional context

💡 Add any other context information about the feature request here. Add related issues/PRs this issue is related to (i.e. depends-on/is-blocking/helps contextualize). Consider creating an RFC (possibly in the project's wiki) if the issue is about assessment or investigations.

⚠️ Important: Log any information, decision making, and discussion as comments to this issue, so they don't get lost. Also, open up a Draft PR as soon as possible to resolve the issue, and commit frequently. See the contribution guidelines for more information.

[nortonandreev]

After chatting with @Fulviuus post our planning session yesterday, we decided to rethink implementing Analytics, even though I was the one who suggested it in the first place.

The main reason is privacy. Even with a compliant tool, some users might not feel comfortable with analytics tracking. Also, I initially wanted analytics to understand user patterns — like which features are popular or causing issues. But, considering our Wallet app's size, we figured direct feedback from users might be enough to spot areas for improvement.

That said, I think it's best to be proactive and find ways to enhance the product and user experience where we can. I suggested we integrate a tool like Sentry for Application Performance Monitoring & Error Tracking. It's well-suited for SvelteKit apps

While Sentry is not considered an analytics solution in the traditional sense, I'll dig into it more to see how we can use it effectively and with privacy in mind. This way, we can make the most out of its features while respecting user privacy.

[Daksh14]

After chatting with @Fulviuus post our planning session yesterday, we decided to rethink implementing Analytics, even though I was the one who suggested it in the first place.

The main reason is privacy. Even with a compliant tool, some users might not feel comfortable with analytics tracking. Also, I initially wanted analytics to understand user patterns — like which features are popular or causing issues. But, considering our Wallet app's size, we figured direct feedback from users might be enough to spot areas for improvement.

That said, I think it's best to be proactive and find ways to enhance the product and user experience where we can. I suggested we integrate a tool like Sentry for Application Performance Monitoring & Error Tracking. It's well-suited for SvelteKit apps

While Sentry is not considered an analytics solution in the traditional sense, I'll dig into it more to see how we can use it effectively and with privacy in mind. This way, we can make the most out of its features while respecting user privacy.

Having analytics is a good practice and I remember @Fulviuus mentioned that we already use google analytics on our websites, so why do we have to think twice about privacy friendly, open source and GDPR compliant ones?

Besides I think its a good and idomatic practice to have analytics setup to also see if users are using the centeralized web wallet or not and where are the click hotmaps. These are all useful statistics we're currently losing out on

[nortonandreev]

After chatting with @Fulviuus post our planning session yesterday, we decided to rethink implementing Analytics, even though I was the one who suggested it in the first place.

The main reason is privacy. Even with a compliant tool, some users might not feel comfortable with analytics tracking. Also, I initially wanted analytics to understand user patterns — like which features are popular or causing issues. But, considering our Wallet app's size, we figured direct feedback from users might be enough to spot areas for improvement.

That said, I think it's best to be proactive and find ways to enhance the product and user experience where we can. I suggested we integrate a tool like Sentry for Application Performance Monitoring & Error Tracking. It's well-suited for SvelteKit apps

While Sentry is not considered an analytics solution in the traditional sense, I'll dig into it more to see how we can use it effectively and with privacy in mind. This way, we can make the most out of its features while respecting user privacy.

Having analytics is a good practice and I remember @Fulviuus mentioned that we already use google analytics on our websites, so why do we have to think twice about privacy friendly and GDPR compliant ones?

Besides I think its a good and idomatic practice to have analytics setup to also see if users are using the centeralized web wallet or not and where are the click hotmaps. These are all useful statistics we're currently losing out on

I don't disagree but it's ultimately @Fulviuus and Emanuele's call on if we should proceed with this.