chore: switch from gtag to plausible - #6680
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## unstable #6680 +/- ##
============================================
- Coverage 61.81% 61.80% -0.02%
============================================
Files 556 556
Lines 59050 59103 +53
Branches 1898 1898
============================================
+ Hits 36502 36526 +24
- Misses 22505 22534 +29
Partials 43 43 |
By that you mean this is from chainsafe, or something others within chainsafe use already? And who is managing this? |
|
@nflaig This is a request from ChainSafe marketing |
|
Will add additional context to this. Generally we should refrain from using overly excessive analytics trackers in our software at ChainSafe especially if it鈥檚 capturing data that we otherwise wouldn鈥檛 need to achieve our goals. Using some sort of tracker is useful to enhance our documentation to better understand how people navigate our docs and how to improve it. Alongside with understanding our reach as an indication of potential usage outside of staking metrics. #6549 was a stop-gap measure (because it was free and we anticipated v1.18 to be released much earlier) until marketing gave us some sort of direction on what they were using. It made sense to use a less intrusive platform and align with what marketing uses for other projects at ChainSafe. This PR aligns with the goal of being less intrusive and using common tools between ChainSafe projects. |
|
馃帀 This PR is included in v1.18.0 馃帀 |
Motivation
Use chainsafe analytics platform