You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users who leave CodeTriage for good force a hard delete of the data. This is good for saving space and privacy, but bad for understanding:
If a user left because their needs aren't being met or because they're "graduating" and no longer need the tool
Associated anonymous metrics with leaving users (i.e. is someone more likely to leave if they have subscribed to zero repos, my guess is yes). Could record: streak_ count, number of repos subscribed, age of the account
Any free-form user thoughts on why they wanted to leave.
Optional email if they would be willing to have a follow-up conversation about what they posted
I don't know if there's some kind of an acts_as_survey gem or not. We could code this up in as described and store to a new database table, which would make future metric extraction easier. The alternative would be to throw things in a google sheet. That would get lossy fast though or could rely on self reporting of metrics (not reliable).
A possible next iteration could be to implement a whole "before unsubscribe" wizard where we give them the option of reducing email frequency (one guess for deletions), then show the survey, then go to the actual deletion step.
The text was updated successfully, but these errors were encountered:
Users who leave CodeTriage for good force a hard delete of the data. This is good for saving space and privacy, but bad for understanding:
I don't know if there's some kind of an
acts_as_survey
gem or not. We could code this up in as described and store to a new database table, which would make future metric extraction easier. The alternative would be to throw things in a google sheet. That would get lossy fast though or could rely on self reporting of metrics (not reliable).A possible next iteration could be to implement a whole "before unsubscribe" wizard where we give them the option of reducing email frequency (one guess for deletions), then show the survey, then go to the actual deletion step.
The text was updated successfully, but these errors were encountered: