Add distinctDaysUsedLastMonth to better detect user engagement levels#233
Merged
Add distinctDaysUsedLastMonth to better detect user engagement levels#233
distinctDaysUsedLastMonth to better detect user engagement levels#233Conversation
winsmith
approved these changes
Feb 17, 2025
Contributor
winsmith
left a comment
winsmith
left a comment
There was a problem hiding this comment.
Still not quite sure why this can't be done on the server, but I trust you :D~
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
distinctDaysUsedLastMonthto measure recent user engagement by counting distinct days used in the last 30 days. This provides better insight into active power users compared to the lifetime-based (still) existingdistinctDaysUsedmetric we had introduced recently.Fixes https://github.com/TelemetryDeck/PirateMetrics/issues/47.