Avatar for lwestermark

Chimp Charts Are Here!

Posted by Leif on


So, the Chimp Charts are here! You could just skim the page and see a bunch of charts, but if you look very, very closely you’ll see valuable information to help you better understand how to engage your subscribers and track your newsletters. You can even mouse over the chart for detailed performance.

So let’s take a look. The first two charts in our “Quick Insights” shows the email opens based on time of day and day in the week. The ‘y’ axis displays the percentage of opens on our tested data. This is an average per campaign rate and what the campaign can expect. It may look simple, but it’s very useful. (Scratching head) “So, what you’re telling me is Thursday around 3 pm is an awesome time to send my Morning Coffee Newsletter?” Not really. Keep in mind that you should use this data as a reference. You certainly don’t want to send your Morning Coffee Newsletter at 3 pm. That would be silly, but then again…some of us need a little afternoon pick me up.

Read More

Avatar for cmorris

Measuring Deliverability

Posted by Chad on


[Update from Ben: 02/08/2011] We wrote this blog post to show that current self-reported “deliverability scores” and “inbox rates” are hard to believe. You have to take the ESP’s word for it that they get “99% to the inbox”. What we need is a truly independent scoring system that anybody can use to verify ESP deliverability claims. We thought we found that (or got pretty darn close) in ReturnPath’s SenderScore.

The first few comments we got were understandably furious. But eventually, the conversation changed. We think we were on the way to a very constructive discussion. I really enjoyed the dialogue I had with people offline as a result of all this, and I want to thank all the email companies who commented here — CritSend, CampaignMonitor, PostMarkApp, and Al Iverson’s A-1 Super Awesome Home DSL Email Service. :-)   I mean, don’t get me wrong. We’re competitors. We’re not going to be singing Kumbaya around the campfire with each other any time soon. It’s just nice talking to people who know their stuff. I wish the discussion could continue.

But my patience has been worn down. ReturnPath is naggi—asking me politely to take this post down, because they “don’t want to arbitrate arguments between their partners.” [I didn't realize we were asking them to arbitrate] I suggested that, as an independent, unbiased scoring system, they should just do what I do: ignore the bastards. Actually, I suggested the complainers needed to “grow some” and that ReturnPath ought to tell them so. But that’s not how ReturnPath rolls (thankfully, I guess).

Anyway, some of the arguments we heard about our posted methodology seemed to go like this: “Your methodology is flawed, because SenderScore penalizes IP addresses that send very low volumes, and that don’t have a high reputation. For example, I have an IP address that has GREAT inbox rates (um, trust me) but that have a low SenderScore.”

Well, yes. We know that low-volume, low-reputation IPs can get great deliverability.

Buuuut we happen to think that an ESP’s very job is to send high volumes of email while simultaneously maintaining a good IP reputation. We send out tons of email through our infrastructure, 24/7. If it were a race car engine, SenderScore’s our tachometer. Does it show actual vehicle speed? No. But it’s extremely indicative of engine performance. If we see our SenderScore drop from 94 to 70, there’s a problem with the engine. It’s time to pull over and get that deliverability fixed.

So to people who say “SenderScore is a bogus number” we respectfully disagree. It may not work for all senders, but it works for ESPs. The ones who send high volume. And want to measure their reputation.

Obviously, I am not concerned with what other ESPs think, or how they respond. But personally, I think that ReturnPath’s naggi — um, polite requests for me to pull this blog post is actually going to work against them. I think they’re defending the very people who are disputing the validity of SenderScore. On the one hand, that concerns me. On the other hand, I’ve always appreciated irony. And I absolutely hate the blinking red voicemail light on my office phone.

So this awesome blog post, which attempted to highlight the usefulness of ReturnPath’s SenderScore, is now officially yanked — at the request of ReturnPath.


One of the hardest, dirtiest jobs we ESPs have to do is manage bouncebacks. We send a few bajillion emails out, and a kajillion bounces inevitably come back. Now, we have to scan every single one of those complicated email headers to figure out what type of bounce it was, then decide what to do with it. If we get a “hard” bounce, that usually means the account we tried to deliver email to doesn’t exist (and so we should clean the member from that list). If we get a “soft” bounce, that usually means the account exists, but we should try again later. Not to mention FBL parsing, and simply filtering out the spam that we get before we can even get to the bounces. It’s like sorting through a dumpster to find recyclables or something. Not very glamorous.

It would be all fine and dandy if people would follow delivery status notification best practices and guidelines. But they don’t. Sometimes this is a reaction to spam, and sometimes it’s just ignorance.

For example, some server admins insert snarky messages in their email headers, like “We don’t want your message. If you send email to us again, we’ll report you.” Well, that’s their prerogative and all, and we’re happy to never send to them again, but if they simply hard bounced the email, we’d be able to clean it from the list faster.

Then there are some ISPs who are downright deceptive with their bounceback codes…

Read More


delivery-doctor-thmOur inbox inspector will tell you if your email will get blocked by spam filters.

But diagnosing the exact reason your email was blocked can be extremely difficult.

The only way to really figure out why your message was blocked is to systematically test each variable: change your subject line, and send another test email. Go check all your test accounts. Did it get blocked again? Well, change this link. Still blocked? Change another link. Wasn’t your links? Swap out the images. Not it? Change your content. Over and over, till you find the culprit. Then, do all that again for the next spam filter. Complete p.i.t.a.

So we automated all that with our new Delivery Doctor tool. Push one button, and we’ll automagically slice and dice and analyze your email and run dozens of tests until we find the root of your block.

Then, we tell you what to fix…

Read More