Mailer
  Navigation

Removes and Unsubscribes

How emails get added to the Removes list

  • User clicks on the unsubscribe link in their email of which brings them to a webpage where they enter their email address to be removed.
  • The system automatically adds fatal bounces to the removes list based on a system algorithm
  • An administrator adds an email to the removes list manually
  • An administrator imports a list of emails to be added to the removes list
  • The system adds all complaints (user clicks a spam button) to the removes list automatically

User Unsubscribes

Setup of Unsubscribe Page

Each email contains an unsubscribe link on the bottom of each email.  When a user clicks on this link they are sent to the mailer Unsubscribe page.  This page can be found in the Mailing Module > Setup > Action Pages > Unsubscribe.  This page has a system tag named sys:mailer-unsubscribe of which can not be removed.  This tag outputs the code for the user to input their email address to be removed.  

Styling of the Unsubscribe Page

Option 1) You can add design elements to the Action Pages > Unsubscribe page as desired.  The output of the sys:mailer-unsubscribe tag is output with CSS classes on the elements thus allowing you to style the output as you wish using inline CSS.

Option 2) If your installation includes CMS, you can redirect users to a CMS page so that the unsubscribe form is utilizing a site design template.  In the sys:mailer-unsubscribe tag in the Action Pages > Unsubscribe content, add a redirect value that points the user to the desired CMS url. Then on the CMS page, add the sys:mailer-unsubscribe tag for it function correctly.

Example code on Action Page for Unsubscribe: <sys:mailer-unsubscribe redirect="/email-unsubscribe"/>
Example code on the target CMS page: <sys:mailer-unsubscribe/>

How Unsubscribe Works

When a user unsubscribes to an email, it is added to the Removes list instantly.  If you add import recipients to a mailing afterwards the email will be removed from the list automatically.  

Note: If a mailing was created prior to the user unsubscribe, the email will not be removed from the mailing.  A work around for this is to import any single email from CRM, upon import it will run the entire list against the removes list.

Up Coming Feature:  When a mailing is scheduled, the system will automatically re-apply all removes to the list prior to sending.

Bounce Removes

If an email bounces due to a fatal error, the system will flag the email as "Bounce Remove" and add the email to the Removes list.  In the comments field of the remove you will see "Automatic Removal due to permanent bounce:"

Complaints

A complaint is triggered when a user click a button such as "This is Spam" in their email application or web interface.  This sends the system an email notifying us that this user feels this email is spam.  The system will automatically flag this email as a complaint and add it to the removes list with the text "Automatic FBL Removal: Spam Complaint" in the notes field of the remove.

IMPORTANT NOTE: A clean customer or subscriber list will get very few complaints.  If your list generates more than 1 complaint for every 4,000 emails sent, the system may pause the mailing and not allow you to continue sending until the account is reviewed.  If your list is not opt-in you will definitely have more complaints and your account may be terminated as a result.  You must not ever send spam using this system.   If you send a mailing to a purchased or harvested list that is spam, you will be banned from the system.  If you have a mailing list that needs cleaning, we have different solutions where you can use your own smtp server or we can provide you with a dedicated smtp server to use until your list has a reasonable user complaint level.  If you have any concerns, contact your system representative for more information BEFORE sending your mailing.


Please send us suggestions regarding this documentation page
If you would like to recommend improvements to this page, please leave a suggestion for the documentation team.

Be the first to write a comment...