Allow email subscribers to see all available communication preferences without logging in

Email subscribers need the option to unsubscribe from the solicit code they are in without globally opting out, even if they're not currently logged in.

This would be a quicker way to unsubscribe from emails for a certain event, because logging in won't be necessary. Currently, when a solicit code is used in a Communication Preference Form and placed in the Unsubscribe link of an event-registration form's email template, the email recipient (when not logged into the site) can click on the Unsubscribe link and view a page that only displays "Global Opt-Out". But if the email recipient is logged in, they are able to see both the "Global Opt out" and the "event email opt-out" on this page.

This Idea is to have the event opt-out be part of the Communication Preferences form that the email recipient sees after clicking the Unsubscribe link, even if this person is not logged in. So the Solicit Code of the Communication should be viewable by recipients not logged in (visiting as a non-constituent).

  • Guest
  • Jan 6 2016
  • Shipped
BBIS / BBIS
  • Attach files
  • Admin
    Samantha McGuin commented
    January 05, 2017 15:08

    Hi Erika,


    Today, anytime you are sending to a constituent list and a user clicks from the received email into the communication preferences form, they should already see all of the mail preferences setup on that form, preselected to their existing values, without logging in. Therefore this was marked as shipped prior to 4.0 (this has been around awhile, we are just not sure of which version this feature shipped.) Are you seeing something different, or interpreting this Idea differently than how I read it? (Which is very possible!)

    This will not occur for imported lists or anytime that your email recipient is not tied to a constituent record. 

    Thanks,

    --Sam

    samantha.mcguin@blackbaud.com




  • Erika Layfield commented
    January 03, 2017 18:04

    This idea has been marked as Shipped prior to 4.0.  Please explain. 

  • Guest commented
    January 06, 2016 23:08

    This is case 12836133