[WC analytics] Add tracking for V2 & connection type

Open
#668 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
analytics

Research direction

Start by locating the existing WalletConnect analytics tracking and the events that identify WC v1 and connection flows. Add tracking for WC v2 and distinguish copy/pasted links from scanned links; done means both connection methods and the v2 flow are represented in analytics.

Written by the indexing model from the issue text.

Description

Enhancement ✨

Description

After talking with the WC team they mentioned it would be interesting to know how the connection via the safe app is performed, either via copy/pasting the link or scanning it. I think it could make sense to add an analytic for this.

Also, with the release of WC v2 we may need to update our tracking to reflect v2 instead of v1.

Dominant language
TypeScript
Stars
116
Forks
84
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from safe-global/safe-react-apps

All issues in safe-global/safe-react-apps

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.