Email Address Shelf Life

by DJ Waldow on April 29, 2008 · 8 comments

Imagine the following (very real) scenario:

Your boss sends you a file that includes 50,000 email addresses. You import the list into your account (merging it with the rest of your house file) and “blast away.” Within minutes your IP address is blocked at several major ISPs.

What went wrong? All 50,000 email addresses are customers who’ve purchased in the past and opted-in. Upon sign up, you included a link to your privacy policy. You even have another file that lists the date and IP address associated with each opt-in. So, what happened?

On the surface, it appears that you’ve done it all by the book. You’ve satisfied the law (read: CAN-SPAM). You’re not a spammer. Why did this happen, if these are your customers?

Upon analyzing these subscribers, you uncover the following information about the 50,000 emails in the file:

  • 50% purchased over a year ago, but haven’t received an email since that first purchase.
  • 25% purchased in the past 6 months, but haven’t received an email since that first purchase.
  • 25% are repeat buyers (their last purchase < 1 month ago), but haven’t received an email in 6 months

Over the years, in speaking with prospects and/or clients, I’ve heard the entire gamut of list maintenance “strategies” from single opt-in, to double opt-in, to double-opt-in plus in-person signature/confirmation.

The question that is not asked nearly enough - both from ESPs and internally is:

When was the last time this subscriber was sent an email?

Mark Brownlow of Email Marketing Reports posed a similar question in March of 2008, Can email love survive a three-year gap? If you dig into the comments on that post, I argued that, “a 3-year hiatus between email communications is about 2 1/2 years too long.”

My guide is based on a continuum (see below):

The Shelf Life Continuum

What are the risks?

  • Honeypot/SpamTrap emails: An instant red-flag for ISPs
  • Hard Bounces/Invalid Recipients: One metric used by ISPs to determine list health - see what AOL had to say on this one (the comments are a must read)
  • High complaint ratios: Another metric used by ISPs

The three risks all negatively impact deliverability, getting emails into the inbox. But what about your brand? What about your customers? If you continue to send email to customers that is random and unexpected, there will be consequences.

DJ Waldow
Account Manager at Bronto

Related posts:

  1. Optimize Deliverability With A Dedicated IP Address We’re proud to announce the launch of our new Dedicated...
  2. How Well Do You Know Your Email List? I bet you review your key email marketing metrics...
  3. Best of the Blogosphere: Real-Life Examples Lead the Way to Better Engagement Customer engagement is the dominating theme this week as well...

{ 5 trackbacks }

How do I clean a 7-year old list with 2.8 million emails? | Bronto Blog
12.03.08 at 11:14 am
How Well Do You Know Your Email List? | Bronto Blog
02.10.09 at 10:05 am
CBSSports.com, March Madness, and Email Marketing | Bronto Blog
03.19.09 at 10:43 am
5 Tips for Testing Emails [Video] | iMarketwell
05.21.09 at 7:42 am
5 Tips for Testing Emails [Video] « Site2Next
08.28.09 at 3:53 am

{ 3 comments… read them below or add one }

1 Kyle James 05.01.08 at 9:51 am

Been in that situation and when the boss says do it your kind of stuck doing it even if you know the repercussions. I’d be interested in a follow-up of reasons to talk the boss out of doing this or what is the best way to do something like this that you know you shouldn’t. :)

Are there ways to qualify the addresses before sending?

2 Emily 05.01.08 at 4:59 pm

Great post! The timing is uncanny - I wrote on the same topic (http://www.viget.com/engage/wrestling-with-big-old-lists/) before I saw this. In my case it’s a client, not the boss, getting me tangled into this dilemma. I can see from the client’s perspective that those email addresses seem valuable, but when you get down to it the risks are huge. Thanks for spelling it out, DJ!

Kyle - my post has a link to a ‘validator’ - though I don’t know much about such services.

3 Linda Bustos 05.01.08 at 5:25 pm

Would staggering the deployment or “blast” help? Could you segment out the different subscriber types you described? (ie send the first batch to the most recent time lags, then send to the next time group etc)?

Leave a Comment

You can use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Previous post: Rendering in Outlook 2007 - Uncovering a Great Mystery

Next post: The Case for Remarketing