Regular emails to increase user engagement

[roschaefer]

• I'm submitting a ...

  • feature request

• What is the current behavior?
  80% of all users have a login count of 1. Our users also never hear back from us.

• What is the expected behavior?
  There should be a monthly email. This email could inform users of new features, new broadcasts in the database and missed opportunities. E.g. if they signed up but never supported a broadcast, if they never distributed their budget or if there are many unseen broadcasts waiting for them.

• What is the motivation / use case for changing the behavior?
  Increase user engagement.

• If you want to request a whole new feature, please provide a user story (otherwise delete):

  • As a project owner
  • I want to inform my users every month with an email
  • So that user get engaged more often

[mz99]

I'm gonna take a stab at this issue. So will this monthly email be sent to all users or just the ones who signed up but have no other activity? "E.g. if they signed up but never supported a broadcast, if they never distributed their budget or if there are many unseen broadcasts waiting for them"

[roschaefer]

Hey @mz99 thanks for taking a stab at this issue. I would say, let's define a list of reasons why we would contact users via mail. Then I would suggest to email those who fulfill at least one of those reasons (let's find a better word here). Also, I would throttle the emails to timespan since last login. timespan could be e.g. 1 month. I would of course mention 1-2 out of the reasons for contacting them in the email text itself.

Does that make sense?

[mz99]

It makes sense, thanks for the explanation 👍

[mz99]

@roschaefer here are my thoughts and additional questions on the implementation:

List of reasons to email users:

1. New features
2. New broadcasts
3. Signed up but never supported a broadcast
4. Sign up but never distributed their budget
5. ...

The mailer needs to send the right template depending on the reason to send mail, I think we could create mailer methods like "new_features" and "ping_user" (need better method names) with respective templates for each of these themes and add more when more scenarios arise:

1. New features or broadcasts
2. Signed up but never supported a broadcast/budget

-What do you think? Or we can use only 1 mailer method instead and drop in templates depending on the reason?

Limit to users who have logged on the past 1 month:
-I did a search in the source code for "timespan", but it didn't turn up. Could you point me to which file it's in?