Posts Tagged ‘Email deliverability’

Don’t Let Compliance Lead to Complacency in Email Marketing

Posted by Dave McCue on April 15th, 2009

15If you climbed into the ring against a heavyweight boxer, wouldn’t you want more than just a mouthguard to protect yourself from harm? Email marketers should think of themselves the same way—CAN-SPAM compliance is your mouthguard, and that heavyweight opponent (in the form of thousands of email subscribers) is poised to start swinging.

Plenty of email marketers wisely learn the ins and outs of CAN-SPAM  laws early on in the process to protect themselves from harm, but too many mistakenly believe that adhering to the rules of CAN-SPAM means they don’t have to worry about SPAM complaints. This is far from the truth; as long as “Junk” and “Spam” buttons exist on every popular email client, any message being sent is at risk for SPAM complaints.

So what’s a marketer to do? Don’t get complacent just because you’re compliant; there are always gray areas.

Before every email marketing campaign, think carefully about any potential negative reactions the campaign might cause. Your standard approach may be enough to satisfy the law of the land, but the moment you set foot in a recipient’s inbox you are no longer in control. CAN-SPAM says you can email a recipient one time without his/her permission; does the recipient know that? Not only is it a mistake to assume that your audience knows what truly constitutes a SPAM email, but it’s even more unrealistic to believe they worry about the damage they could be doing to your reputation as a sender by marking your message as SPAM.

To put it simply, the best defense against SPAM complaints is common sense, but it’s an approach that is all-too-often pushed aside. Never forget that all of the email addresses on your mailing list, as well as any other addresses you “acquire,” represent actual people. Try their patience, and they’ll act the way people do.

To go back to the boxing analogy, if compliance is your mouthguard, let common sense be your headgear. If you find yourself justifying an email strategy by saying “technically, this is totally legit,” you’re going to want to stop and re-evaluate things. If it means sending less email—if it means sending to less people—it might help you take a lot fewer punches in the ring.

Post to Twitter Tweet This Post

  • Share/Bookmark

Using Personalization to Increase Deliverability

Posted by Nic Winters on December 23rd, 2008

I know what typically comes to mind when you think about personalization in relation to email – likely a “Dear First Name,” greeting or a “Great ways to save money at Company Name” subject line.

However, I’d like to remind you of two quick and easy uses of personalization that can be incorporated into your email campaigns to assist in increasing the delivery rates of your messages.

1. Include a request to add your From address to the recipient’s safe sender list/address book/whitelist to increase inbox delivery and image enabling. You can ensure that you are asking them to act upon the correct address by utilizing the personalization token related to From address (%sys_fromaddr% in SubscriberMail). However, please keep in mind that having your recipients completing this task will do you no good if you don’t keep a consistent From address (bouncing back-and-forth between From names causing the beginning of your From address to be altered).

2. Consider displaying the email address that you have on file for your recipients within your messages. Many of your recipients may be receiving your messages due to automatic forwarding from an old email address that could eventually expire. Your recipients may also have multiple email addresses on your lists causing frustration when they receive multiple copies of your emails. Including the email address you have on file in your messages boosts credibility and helps recipients receiving multiple copies to resolve this issue. You can ensure that you are including their correct address by utilizing the personalization token related to email address (%sys_email% in SubscriberMail).

Post to Twitter Tweet This Post

  • Share/Bookmark