OSEmail Repermissioning Campaign: Difference between revisions
Jump to navigation
Jump to search
(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...") |
No edit summary |
||
| Line 9: | Line 9: | ||
#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 | #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 | ||
#The top of the email should be about the opt-in. The normal OSEmail update should go below the big green button | #The top of the email should be about the opt-in. The normal OSEmail update should go below the big green button | ||
=Repermissioning Email= | |||
Revision as of 01:05, 1 December 2018
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:
- 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
- The subject should very clearly indicate that their action is required. I recommend: "Opt-In Action Required for OSEmail" or something similar
- 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
- The top of the email should be about the opt-in. The normal OSEmail update should go below the big green button