Part 2 — Spam Filters & Preheaders
I learn a lot from my email work with clients. In Part 2 of my series on mistakes to avoid, I want to alert you to Mistake 3 and Mistake 4, which — when it comes to lifting open rates — you should never, ever ignore!
Using this CTA phrase (a spam filter favorite)
One of my clients was using the above phrase often in email text. Harmless, right? Wrong. To their horror, they discovered that many spam filters don’t like that innocuous phrase, making their emails prime candidates for the junk folder.
Here’s another phrase that we found to trigger spam filters:
1. Images don’t work everywhere on the email and
2. Images lose impact when an email is opened and the images are not displaying.
We try to code as much as possible in the email, including the buttons, to make sure an email is most effective. Play it safe, forget these spam filter favorites altogether. We like to use LEARN MORE or GO HERE for the call-to-action button. For the money phrase, that’s a little trickier since nothing beats those 3 classic words. We normally don’t include the money phrase in the email but make it prominent on the landing page. If you feel you must include the phrase in the email, then make it a graphic image — but make sure your developer leaves the alt tag blank.
Ignoring the preheader and its impact on opens
You and I know that, together with the sender (or “From”) name, the subject line has the biggest impact on whether your email gets opened. But, today, when you often have barely 3 seconds to get someone’s attention, my clients make sure to pair the subject line with another tool: the preheader, which can increase open rates sometimes up to 45% (Litmus statistic). In my example below, the preheader is the gray text that is circled.
SPECIAL NOTE: Some email deployment systems automatically add their own “view in browser,” which knocks your composed preheader out of the top billing spot. To stop this from happening, the “view in browser” function needs to be disabled in the deployment service software, and your developer will need to code this part by hand.