OSEmail Repermissioning Campaign

From Open Source Ecology
Revision as of 19:17, 28 November 2018 by Marcin (talk | contribs) (Created page with "FYI, this article has a lot of good (and bad) examples of repermission campaigns from other organizations: * https://econsultancy.com/gdpr-examples-repermissioning-emails-ca...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

FYI, this article has a lot of good (and bad) examples of repermission campaigns from other organizations:

* https://econsultancy.com/gdpr-examples-repermissioning-emails-campaigns/

My take aways:

  1. We should make it as obvious as possible that the user must opt-in or (if they do nothing) they will be permanently blacklisted & receive no future newsletters
  2. The subject should very clearly indicate that their action is required. I recommend: "Opt-In Action Required for OSEmail" or something similar
  3. Rather than put the opt-in confirmation link as a hyperlink in the body of the text, we should actually make a huge green button titled "Yes, keep sending me the OSEmail newsletter" or something similar
  4. The top of the email should be about the opt-in. The normal OSEmail update should go below the big green button