SparkPost SparkPost is the world’s #1 email delivery service. Mon, 19 Aug 2019 13:00:37 +0000 en-US hourly 1 9 Factors You Should Consider When Selecting an Email Vendor [Infographic] Mon, 19 Aug 2019 13:00:37 +0000 email vendorDiscover which factors matter most when "grading" email platforms with our new infographic: 9 Factors You Should Consider When Selecting an Email Vendor.

The post 9 Factors You Should Consider When Selecting an Email Vendor [Infographic] appeared first on SparkPost.


Whether you’re picking an email delivery vendor for the first time, or reevaluating your current provider there is no shortage of information out there to consider. To make an educated decision you not only have to learn all of the industry jargon (can you say Simple Mail Transfer Protocol 5 times fast?), but also sift through the biased reviews left behind by the email marketers of yesteryear. Once you’ve done all of that, you’ll have to narrow down the choices based on which factors are most important to your organization. But, what should those factors be?

In order to help you identify which factors you should use to “grade” email vendors and ultimately make the decision that is best for your business, we created the below infographic: 9 Factors You Should Consider When Selecting an Email Vendor. We hope that this infographic makes your selection process more streamlined and maybe just a little prettier!

While this infographic is certainly a helpful tool in its own right, we recommend using it in tandem with our brand new Buyer’s Guide to Email Delivery Platforms! The guide provides:

  • New trends in email technologies
  • Changes in email over the last 5 years
  • The core elements of email delivery
  • Questions you should ask email providers that you’re evaluating
  • Updated data, privacy and regulatory laws to be aware of
  • A comparison of features across the most reputable email providers

As a driver of nearly 18% of all business revenue, there is absolutely no doubt that email is integral to not only your business but likely your competitors’ as well. With such a great impact on your bottom line, it’s imperative that you select the right email provider the first time (or if you’re reevaluating your current provider…THIS time). More than that, email is often one of the primary ways customers choose to get in contact with businesses. With such a close relationship to the customer experience, email can be make-or-break for customers’ perception of your company. That’s a lot of pressure riding on your email platform!

The good news is that between our Buyer’s Guide and infographic…you’ve got this! We hope that these tools make selecting a provider a little less daunting. It’s time to start your decision-making process, good luck (not that you need it) and happy sending!

email buyer's guide

~ Erica

The post 9 Factors You Should Consider When Selecting an Email Vendor [Infographic] appeared first on SparkPost.

Spam Traps: Break it Down Fri, 16 Aug 2019 13:00:00 +0000 spam trapsFind and fix issues faster with our breakdown of spam traps now available as part of our Spam Trap Monitoring feature inside of SparkPost Signals.

The post Spam Traps: Break it Down appeared first on SparkPost.


Spam traps are email addresses that look real but aren’t. Instead, they are used by mailbox providers, blacklist providers and filtering providers as a way to measure the quality of a sender and as a way to catch spammers.

Sending to spam traps can damage your reputation and result in your mail being blocked or placed in the spam folder.

At SparkPost, we know how important email delivery is to your business, and we want to help you succeed. Back in January of this year, we rolled out Spam Trap Monitoring with a superset of existing networks, giving us the broadest visibility across both commercial and non-commercial spam trap networks in the world. In addition, we created automated processes that constantly discover new spam traps so we can provide the most accurate information.

But just knowing how many traps you’ve hit may not give you enough to find the source of your problem, whether it be low-quality sources, no validation, or bad list hygiene.

To help you dig further, we’ve added a breakdown of the type of traps you’re hitting to help you find and fix any issues.

Spam trap types

Knowing which type of spam trap you’re hitting helps you find where your email program may have an issue.
Starting today, you’ll see traps broken down by type: recycled, typo, and parked.

Recycled traps are email addresses that once were real, but have been converted into a spam trap. If you have these on your list it’s probably a sign you need to clean out old unengaged recipients. You can look at your engagement recency cohorts (EU) to see if you are sending to a lot of unengaged recipients.

Typo traps are email addresses hosted on a domain that looks like a real mailbox provider, like These usually get onto your list when a real person tries to sign up but “fat fingers” their email address and accidentally adds a trap instead. These addresses signal that you should work to improve your enrollment process. Using a tool like Recipient Validation can help solve this problem.

Lastly, are parked emails. These are email addresses hosted by a parked domain provider. These addresses can point to list quality issues, though they will not affect your reputation.

Our customers have asked about this after we first launched Signals, and we’re really happy that we get to release this today. So jump into the app (EU) now to find what types of traps you’re sending to! With just a few small changes, you can see improvements in your list quality.

As always, we’d love to hear your feedback. Send us an email to if you have any thoughts or suggestions for Spam Trap Monitoring or other Signals features.

Happy sending!

—Avi, Technical Product Manager

? Special thanks to George Schlossnagle, Daeyon Griffin, Michael Curtis, Aaron Shen, Brian Kemper, Cole Strode, Tonya Gordon and to all the Product, Engineering, Marketing, Sales, and Customer Success teams

The post Spam Traps: Break it Down appeared first on SparkPost.

5 Ways to Optimize Your Financial Services Emails for Mobile Devices Wed, 14 Aug 2019 13:00:52 +0000 mobile devicesDiscover 5 ways to ensure that your financial services emails are opened, read, and acted on by customers receiving them on mobile devices.

The post 5 Ways to Optimize Your Financial Services Emails for Mobile Devices appeared first on SparkPost.


Mobile devices account for 42% of email opens, according to a Litmus analysis of 10 billion email opens. In addition, Litmus found that 61% of emails opened on mobile are read for more than 8 seconds, a percentage that’s been on the rise since 2015, and the average reading time is 13.4 seconds, a 29% jump during the past 7 years.

However, if your emails aren’t optimized for display on mobile devices, your carefully crafted messages will likely be for naught: An email that doesn’t render correctly on a mobile device is likely to be deleted in 3 seconds or less, and up to 15% of recipients will simply unsubscribe in such a situation, according to Campaign Monitor.

With that in mind, here are 5 ways to ensure that your financial services emails are opened, read, and acted on by customers receiving them on mobile devices.

1. Implement a responsive email template

A responsive email template automatically adjusts to the recipient’s device when it’s opened, whether they’re on a desktop computer with a large display, an older generation smartphone with a small screen, or anything in between. People with plenty of display real estate won’t mind a non-responsive email template, but those on the other end of the spectrum likely won’t appreciate having to zoom in just to read your message.

If you can’t create a responsive email template just yet, then opt for a scalable template, which uses a single column with large text. It won’t look pretty on a large screen, but it will get the job done on mobile devices.

2. Use preheader (preview) text, but pay attention to the devices used by your subscribers

The text shown below the subject line on Apple Mail for iOS, Gmail for iOS and Android, and other mobile email clients is known as the preheader, or preview, text. If you don’t specify it, your customers will likely see the first several words from the email, which could be the alt-text from the header image, “Click here to view this email online,” or other non-useful information.

Think of this text as a second chance to get people to open your email, if the subject line didn’t quite do the job. Use the preheader to complement your subject line – for example, if you’re pitching an offer, use the subject line to present it and the preheader to emphasize the expiration date or another key selling point.

While your subject line shouldn’t be more than six words, or about 50 characters, you have a little more room with the preheader. Check your analytics and see which mobile email clients are more prevalent among your customers, since Apple Mail for iOS typically displays about twice the amount of preheader text as Gmail for mobile.

However, note that if your preheader text doesn’t fill the space provided by the recipient’s email app, it may pull in the first several words from the email to occupy the gap. To stop that from happening, check out the hack explained by Litmus – it adds white space after your preheader text to ensure that it’s all your customers see.

3. Keep your content lightweight

While mobile email reading times are on the rise, that 13.4-second average still isn’t much time to engage customers and get them to take action. Use short paragraphs that are just a sentence or two, with a few bullet points that convey key value props or other important information. Your fonts should be large enough to read on small screens – make sure you use ones that are broadly supported by the major email apps.

Don’t be afraid to use multiple CTA (call-to-action) buttons. You might want to include one in the middle, if your email is a little long, and don’t forget to make the buttons big enough that the user can easily tap them with a finger from the same hand holding their device. Your CTAs should complete the phrase “I want to…”, such as “Apply Now” or “Check My Account Balance.”

Keep your image file sizes down, since not everyone has access to fast download speeds and you don’t want to take up too much of their data plans. High-def images are perfect for logos and other key visuals, but the rest of the pictures can likely be lower-def and still look fine on a mobile screen. Make sure all of your images have alt-text, since many email clients turn off images by default.

This email from Paypal is a good example of a mobile-optimized message.

  • The text is short and to the point, with no more than 2 lines in any section.
  • You could read just the 3 sub-heads and get enough information to decide whether to tap that nice big CTA button, which is centered at the bottom.
  • The photos are nice but aren’t needed to understand the email.
  • The subject line, “[First Name], 3 Ways We’ve Made Shopping Easier,” is short and to the point.

4. Consider when you send your emails

Litmus’s state of email engagement report also notes some differences in the best time to send email, depending on which platform is dominant among your customer base. This is important because if you send a message when your audience isn’t likely to be checking their email, your email could end up way down their inbox when they download their messages.

Litmus says the difference also depends on where your customers live:

  • United States: While webmail and desktop opens start dropping after 5 pm, mobile opens are fairly steady between 8 am and 10 pm.
  • United Kingdom: Desktop opens are highest at 9 am but have a little jump between 2 and 3 pm, while webmail is fairly steady throughout the day. Mobile opens are heaviest between 5 and 7 pm.
  • Canada: Desktop and webmail opens peak at 9 and 10 am while mobile usage is heaviest between 9 and 11 am.
  • Germany: Opens on all 3 platforms are strongest between 8 and 10 am. While desktop opens start to decline around 5 pm, webmail and mobile opens experience a bounce around that time before starting to drop into the evening.
  • Spain: Mobile and desktop opens are neck-and-neck between 9 and 10 am. Both of them drop after that but bounce up again between 4 and 6 pm. Webmail opens are steady throughout the day.
  • Australia and New Zealand: Mobile opens have a morning spike at 7 am and another one between 3 and 6 pm. Desktop peaks between 8 and 10 am before declining for the rest of the day while webmail is steady all day.

5. Test your emails on a variety of mobile devices and optimize your landing pages, too

Even if you use a responsive email template, you’ll still want to test your messages on as many kinds of mobile devices and in as many apps as possible. There could be quirks in your code that might create issues.

In addition to making sure your links work, check their destinations on mobile too. Your landing pages should also use responsive design.

Deep links into specific places in an app are possible too – see this article in our Help Center to learn more.

~ Casey

The post 5 Ways to Optimize Your Financial Services Emails for Mobile Devices appeared first on SparkPost.

The Current State of Automated IP Warmup? Mon, 12 Aug 2019 13:00:34 +0000 Automated IP WarmupRead about some of the great results we’ve seen with our feature: Automated IP Warmup, designed to make adding a new dedicated IP a breeze!

The post The Current State of Automated IP Warmup? appeared first on SparkPost.


Checking in on one of our newest products that makes email easy.

Early in 2019, SparkPost released an Automated IP Warmup feature designed to make adding a new dedicated IP a breeze. We wanted to circle back around and share some of the great results we’ve seen with this product so far. First things first, if you’ve used the Automated IP Warmup feature or are thinking about using it in the future, I’d love to have a quick chat. Feel free to book me for a quick fifteen minutes to learn more or share your story.

Since releasing this feature, we’ve been able to warm hundreds of dedicated IP addresses with great results. As I’m writing this message, some 1,200 IPs are in the warmup process! Some of our customers have used the feature to warm up to just a couple thousand messages a day while others have gone all the way to stage 22 – that’s 1.75 million messages a day through their IP!

The really exciting part is that the deliverability and health metrics of these young IPs are just as good as the IPs that already exist in the pool! That means that we’ve been able to hone in on a good warm up pattern for most dedicated IPs. Whether you’re just getting started with email, growing your volume, adding a new stream, swapping out IPs, or transferring your traffic to SparkPost – we think you’re going to have a great experience!

We’ve gone through and taken a closer look at a couple accounts to see how their IPs are performing. Here are some great examples of a recent set of IPs that have been added and went through the Automated Warmup Process:

Sender A maintains a dedicated IP to alert customers of critical notifications. To add redundancy to their system, this sender added a second dedicated IP to their critical notifications IP Pool. At the time of writing this blog, the newly added IP is in stage 9 of warmup – capable of sending 50,000 emails per day before falling back solely to the warm IP. Here are the results of how the existing IP and the newly added IP are performing within the same pool for the last 25,000 messages:

Accepted % Hard Bounce % Soft Bounce % Block Bounce % Undetermined Bounce % Open %
Existing IP 98.28% 0.91% 0.40% 0.23% 0.19% 82.21%
Newly Added IP 98.33% 0.96% 0.36% 0.20% 0.15% 83.46%


Sender B added two dedicated IPs to an existing pool that previously only had one dedicated IP. Both of these newly added IPs have progressed to stage 8; capable of sending up to a combined 80,000 emails before solely relying on the warm IP. Here’s their performance recently:

Accepted % Hard Bounce % Soft Bounce % Block Bounce % Undetermined Bounce % Open %
Existing IP 99.98% 0.02% 0.01% 0.00% 0.00% 3.76%
1st Newly Added IP 99.97% 0.02% 0.02% 0.00% 0.00% 3.63%
2nd Newly Added IP 99.98% 0.02% 0.00% 0.00% 0.00% 3.97%


As you can see, in both situations the newly added IPs are performing just as well as the other IPs in the pool. This is great news and we’re thrilled to share these results.

Even though we’re excited about the results we’re seeing, we’re not done yet. Our goal is to continue to make email easy for our customers. Keep an eye out in the coming months for more posts and continued updates for our Automated IP Warmup product.

Happy Sending,
Harold and Balu

The post The Current State of Automated IP Warmup? appeared first on SparkPost.

Going Places…a Reflection on Ten Years at SparkPost Fri, 09 Aug 2019 13:00:19 +0000 ten yearsOur Vice President of Customer Success, Laura Rose, reflects on her first ten years at SparkPost from her first day until now.

The post Going Places…a Reflection on Ten Years at SparkPost appeared first on SparkPost.


Off and Away

Ten years ago on a warm August morning, I left my two young daughters at home with my husband and drove to Samuel Morse Drive for my first day at Message Systems.? I was carrying a new yellow Fossil bag and matching wallet and when I entered the building I really felt I had “arrived”. I was making a big step up from the field of IT consulting to a proper software firm!? I couldn’t believe that a company with technical powerhouses like George Schlossnagle and Dave Gray would actually hire me.? After I put my yellow bag on my new desk things moved very fast – my official start time was 10:00 am. All my forms were filled out and I was up and running on a Mac (another exciting step up) as a “Project Manager” by 11:07 am.? Little did I know then that my journey would continue to accelerate for a decade … never slowing down, always speeding up like a rock hurtling into outer space. It’s been an ever-evolving adventure full of excitement and challenges, laughs and tears, and many friends.

Steer Yourself

From the very beginning at Message Systems, I had complete control of my destiny and my customers’ destinies! Nobody told me what to do or how to do it. I had complete autonomy in managing customer relationships and getting things done. I went with what felt right, but I was able to do that and be successful because I knew my values were aligned with our company values. When I think back, though rather scary, this autonomy was an amazing gift and something many people don’t usually get in their career. I learned so much during this time and I found it deeply satisfying and rewarding. In terms of balancing work and home – again it was in my full control – never once was I questioned about hours worked, my availability or my commitment (many working parents are not so lucky).

Bang-Ups and Hang-Ups

I certainly didn’t always get it right and there many were stressful moments – especially when I felt the heavy burden of being the primary subject-matter-expert on customer deployments. In the summer of 2012, while on vacation in Colorado, I had to help resolve a production issue – no one else had the knowledge and experience to orchestrate the fix. That experience taught me the importance of having a solid backup plan, proper communication, and sharing risk. Whenever I made mistakes, I knew I would always be supported by our team and never feared I would be admonished. The focus was only on fixing the problem and how we could do better.

Another Chance

In late 2014 we started the transition to the cloud (the birth of SparkPost) and that’s when I began working as a “Technical Account Manager” (TAM). This was incredibly challenging because we had to figure out how to support customers in the cloud as we went along. We didn’t have a blueprint to follow but again leaned on some of our core values of empathy, transparency, and gratitude to get us through. That strategy served us well and during that time we developed symbiotic relationships with customers like Zillow (we like to call them “partners”) that still exist today.

As our cloud business grew, I took on a Team Lead role and gradually expanded the team of TAMs. What I looked for the most was a shared understanding of how to approach and treat customers – especially in tough situations. Using that strategy I assembled a strong team of TAMs with a great diversity of experiences, skills, and talents – many more than mine alone. Working tightly together we continue to keep our customers on track and moving forward.

In our SparkPost offices, you will find our values posted on the walls. In that physical context, they can seem abstract, but in our day-to-day world, they are very much alive. We try to consider our values in the smallest of exchanges (like how to phrase a response to a common support request) as well as large and complicated matters (like talking to customers about an outage). Perhaps the phrase “living our values” is overused but I believe relationships are built on the little things (saying “thank you”, a smile, a text message with an update, an extra loop around to pass someone’s desk) and I can’t think of a better way it can be described.

A Great Balancing Act

The past decade has seen my girls grow from toddlers to teenagers and fine lines develop at the corners of my eyes. I no longer have my yellow Fossil bag and we’re a SaaS company now. But things only move faster and now I have a new adventure – the role of VP of Customer Success. I’m excited and daunted by this new challenge but I’ll lean on my experiences of the last 10 years and this company that is now part of me.? And for that, I’m truly thankful.

~ Laura

The post Going Places…a Reflection on Ten Years at SparkPost appeared first on SparkPost.

Why Security Breaches are Personal Wed, 07 Aug 2019 13:00:49 +0000 security breachesOur Vice President of Compliance and IT Security, James Sipe, explains why security breaches are more about people than data.

The post Why Security Breaches are Personal appeared first on SparkPost.


A few years ago, previous to my current position,? I was recruited for a leadership position in IT Security and Compliance at a large private company. The position was newly created and included PCI and data compliance. As I was going through the interview process, I found that the company was in a post-breach PCI settlement negotiation. They, like many others in their industry, were an ongoing target for bad actors stealing both credit card data and Personal Identifiable Information (PII); and they, like many others, had suffered a significant breach with costly results both in fines and also in time spent remediating.

I later found out that the opportunity I interviewed for and accepted was a direct result of that breach event. The Board of Directors had instructed management to go on a nationwide search for someone who could not only continue to remediate the breach and run the department but also help ensure a breach event was not repeated.

I had arrived well after the beach was cleaned up by third parties hired by the cyber insurance firm but before substantial and needed technology changes were implemented. Like most IT Security professionals it was easy to identify the missing layers and weaknesses within the technology stack. Even without reading the post-breach report, which was inconclusive in its conclusions after the discovery and forensics process, it was obvious that the investment had not been made for many years in ensuring that there was proper visibility and control to combat the present threats and risks.

In the past, all efforts and security had been focused on the PCI environment since as a private company, in their opinion, they didn’t need to protect anything beyond the PCI scope. In fact, that approach led to creating easily exploited weak areas that could allow for lateral movement of escalated privileges and data. It actually made the bad actor’s job easier. Compliance is not security.

In the first 3-4 months, we replaced every piece of security technology with new technology and added tools where needed to create defense in depth.

We concentrated on making the solutions highly integrated, creating wide-ranging viability and alerting, and took advantage of automation.? We consciously balanced preventive tools with detective capabilities instead of one or the other.

Just four months into the job I asked to present a 3-year plan to our Board of Directors that included both a plan for technology and most importantly, a more mature IT governance and controls environment to support those tools.

In my presentation to the Board in the opening statements I said that “this will happen again despite my plan and the improvements.” We could conduct data classification, improve access control, do user education, encrypt data, buy new technology, however, it was extremely likely that an event would still occur in the future. Maybe not a PCI breach but some other kind of breach like PII or other sensitive information. The key was how soon we knew something had happened, how quickly we could react and stop it, and how resilient our technology was to recover from a catastrophic event. In the end, preventing a future breach actually had less to do with technology than you might think.

Having gone through and seen many events over the years including breaches, attacks, criminal activities, insider attacks and negligent behavior, the one common denominator was, and still is, people.

In my experience, you can buy all the shiny new technology, but it’s useless without solid processes and controls in both IT and the business. Breaches and attacks, regardless of if they are from the inside or outside hinge on the behavior of people. No technology can stop a motivated person with enough time and resources. It can prevent the majority but not plurality.

Specifically understanding people in your organization and if they embrace security is everyone’s responsibility. How well trained and aware IT, IT Security, and their internal business partners are; and how knowledgeable they are in identifying an event (“See something, say something”) — all of these things contribute to a low success rate for cyber attacks and breaches. The time from detection to stopping an event is directly related to the cost of that event.

The behavior of your adversaries (also people) and their motivations and their habits are key. Due to time zones, activities that take place in the middle of the night in Washington DC when people are fast asleep are actually happening in the middle of the day in some of the places of the world where concentrations of bad actors and organized crime reside.

Having highly skilled and dedicated security and compliance professionals (people) is essential. My team at that company was dedicated and over time well trained. I was lucky enough to be able to build on that and those people were the frontline defense.

Most importantly the biggest takeaway is a company’s responsibility to its customers (people) and the employees (people). The breach I described above caused a lot of sleepless nights and hard work for the employees but for the people who’s card data was stolen it was personal.

IT Security and Data compliance continues to evolve and become more complex it seems. But the most successful security approaches are focused on the most complex element, the people.

~ James

The post Why Security Breaches are Personal appeared first on SparkPost.

How to Set Up SparkPost as Your SMTP Relay Mon, 05 Aug 2019 13:00:58 +0000 SMTP relayA step-by-step guide to setting up SparkPost as an SMTP relay. Start sending emails quickly through any preferred email client with ease today!

The post How to Set Up SparkPost as Your SMTP Relay appeared first on SparkPost.

  • This blog post was originally published on 06/24/2016 and was updated on 08/05/2019

Note: If you’re using SMTP to route all of your personal mail through SparkPost, awesome! However, be sure to use an email address with a different sending domain (not one associated with your SparkPost account) for your account login. That way, if you ever run into any issues, you’re still able to contact us for help.

You know you need to send email, but you don’t want to spend a lot of time or effort on it — you just want something that works out of the box. It’s not too much to ask! Many frameworks, languages, and tools come with SMTP support, but the last step is the most important – an SMTP server. SparkPost fills that need with SMTP support and a simple setup process.

Today, I’ll be demonstrating how to set up an SMTP relay, so you can use your own email client to send emails from your personal domain. I’ll be using Gmail as my email client and as my sending domain.

Let’s get started!

How to Setup SparkPost as your SMTP Relay

There are a few things you’ll need before setting up an SMTP relay.

  1. A verified sending domain.
  2. An API key with the “Send via SMTP” permission enabled.
  3. An e-mail client or service which allows you to enable SparkPost as your SMTP relay.

For this walkthrough, I’ll be using Gmail. To begin, navigate to the settings.

navigate to the settings button smtp relay

From there, click on the “Accounts” tab.

click on the accounts tab smtp relay how to

Next, click on “Add another email address you own”.

add another email address you own smtp relay how to

In the pop-up menu, enter the (verified) email address and press next. I’d like to be able to send with “”, so that’s what I type in.

enter the email address you'd like to use smtp relay how to

Then, enter “” as the SMTP Server,“SMTP_Injection” as the username, and 587 as the port. Your password should be your API key with “Send via SMTP” enabled. This information can be found under Account -> SMTP Relay in your SparkPost dashboard.

enter your username and port smtp relay how to


Let’s get started!

Lastly, you’ll need to login to your inbox to confirm. After that, we’re done! Time to send some Shop With Kindness emails.

Other Resources

If it turns out that SMTP isn’t the right email solution for you, consider taking advantage of the SparkPost API. The API has many pros (and cons). Take a look at Dave’s blog for more information regarding the differences between SMTP and API.

Lastly, if you’re having problems setting up an SMTP relay, join our Community Slack channel or?tweet us!

~ Vincent

Dev Survival Guide Blog Footer

The post How to Set Up SparkPost as Your SMTP Relay appeared first on SparkPost.

]]> 2
Free Download: The Buyer’s Guide to Email Fri, 02 Aug 2019 13:00:02 +0000 Buyer’s Guide to EmailDeciding on an email vendor to deliver your messages doesn't have to be complicated.?Download The?Buyer’s Guide to Email Delivery Platforms today!

The post Free Download: The Buyer’s Guide to Email appeared first on SparkPost.


A Guide When Shopping for an Email Delivery Vendor

In the email industry, institutional knowledge in the form of blogs, guides, webinars, etc. can get pretty niche. As email marketers, email deliverability experts, and product professionals, we need and like to dig into the details. However, there’s a lot of information out there which can be daunting to sift through and cumbersome to find the right information to help make a decision on which email vendor will be most helpful for your needs.

That’s why we’ve put together this Buyer’s Guide to Email Delivery Platforms! This free download is a comprehensive guide to email delivery for those just getting started or those looking to reevaluate their current provider. We believe that while delivering email is complicated, deciding on an email vendor to deliver your messages doesn’t have to be.

Who this Guide is for?

This guide is for anyone who is looking for a new email provider or who would like to reassess their current provider. These roles might include (but are not limited to):

  • Email Marketers
  • IT Decision Makers
  • Product Managers

Why Read this Guide?

This Buyer’s Guide to Email Delivery Platforms will provide:

  • New trends in email technologies
  • Changes in email over the last 5 years
  • The core elements of email delivery
  • Questions you should ask email providers that you’re evaluating
  • Updated data, privacy and regulatory laws to be aware of
  • A comparison of features across the most popular email providers

As a driver of nearly 18% of all business revenue, there’s no argument that email is an important channel. It’s also often the primary way that customers experience your brand. That’s a lot of pressure riding on an email service to deliver your emails.

There are so many factors that go into delivering even a single email. When it comes to mass email communication to your customers, partnering with the right email vendor can be the difference between a so-so and great customer experience. Download The?Buyer’s Guide to Email Delivery Platforms now to find out which email delivery service is right for your business.?You owe it to your customers and yourself to get email right!

~ Jen

The post Free Download: The Buyer’s Guide to Email appeared first on SparkPost.

7 Reasons to OptIn’19 Wed, 31 Jul 2019 13:00:12 +0000 OptIn'19Head of Marketing, Tracy Sestili, dishes on why our brand new vendor-agnostic conference OptIn'19 is THE email event to attend this year.

The post 7 Reasons to OptIn’19 appeared first on SparkPost.


In the past SparkPost has held customer forums where we’ve only invited existing customers to participate. That seemed kind of exclusive and not reflective of our welcoming company culture. This year, we decided to do away with our customer forum and instead offer a vendor-agnostic industry conference where everyone can learn and benefit from the knowledge of industry pros.

I’m super excited to announce OptIn’19: The Email Intelligence Conference, we’re holding at the stunning Carmel Valley Ranch resort in Carmel, California on October 29-30, 2019. We have a great lineup of speakers and panels, a professional vendor-agnostic moderator, and plenty of networking time!

Through the course of the two-day event, we will discuss topics that explore how leveraging data impacts email, the customer experience, and marketing organizations as a whole, as well as email best practices.

Now I want to give you 7 reasons on why you should opt-in to joining us at OptIn’19.

  1. It’s vendor agnostic. We welcome competitors, peers, analysts, practitioners, and anyone else who is interested in email to thrive, learn, and connect with email. In fact, that’s our internal motto (TLC with Email) and we have shirts to prove it!
  2. Professionally moderated. We’ve hired former CNBC and Bloomberg journalist, Cory Johnson, to moderate the panel. He’ll be doing his own research and coming up with his own questions so it should prove to be nothing short of awesome.
  3. Diverse and inclusive. As part of this new initiative, the conference is offering Diversity and Inclusion scholarships. SparkPost is subsidizing two of those and will offer up to six more if sponsors are interested in subsidizing. The scholarship includes full passes, hotel, and airfare. If you’re interested in applying for a free ticket, hotel, and airfare, please apply here.
  4. Network like no one is watching. There’s a bit more time built into the schedule to network with folks you really want to hang out with and get to know better.
  5. Be a part of something that was first. This is the first email intelligence conference and the only conference that is centered around data and the future of email. We can’t wait to geek out with you over data and email. #emailgeeks
  6. Great speakers. We have a great speaker lineup so far with motivational speaker Michelle Poler, data scientist Hilary Mason, and a popular magician on Netflix. We also have speakers from Google, Women of Email, Virtru, 250ok, Kayak, and more.
  7. Carmel Valley Ranch. Need I say more? Not only is it super relaxing but as part of your registration, you get to experience one free activity of your choice. Choose from archery (who doesn’t want to be Katniss Everdeen??),yoga (namaste), cycling, cooking, hiking, and more.

So, what are you waiting for? Early bird registration ends August 16th. And, if you’re interested in an extra $100 off, you can DM me on Twitter for a discount code.

Need to convince your boss? No problem, here’s a letter for you to copy and paste in an email:

Hi {boss’s name}

I’d really like to attend the OptIn’19 the Email Intelligence Conference taking place on October 29-30, 2019, in Carmel, CA. The conference is vendor-agnostic and will be covering how data impacts email, the overall customer experience, and email marketing best practices.

Here are three ways in which I envision my attendance at OptIn ‘19 strengthening {your Company Name}:

  1. Many of the sessions will cover best practices in {list what will increase efficiency, reduce costs, increase engagement, e.g. email deliverability, email security, personalization at scale, Google AMP for email, and general email best practices} —all areas that we need to get up to speed on to grow our business.
  2. Interactive Q & A sessions and keynote addresses from email and data science industry leaders and experts will bring me up to date on new and developing tools, which will help us build a more realistic and cost-effective short and long-term technology plan.
  3. Networking is also highly encouraged, so I’ll have plenty of time to speak with other attendees and speakers about issues and challenges facing similarly-sized companies like ours.

The cost of the event is $899, however, there is an early bird registration discount of $200, which ends August 16th. There will be additional travel and hotel costs, but I’ll do my best to stay within a mutually agreed-upon budget.

I realize that this is a significant funding request, and would be happy to write a post-conference report or blog detailing what I’ve learned, and provide a schedule detailing how to best implement any new changes that I learned. You can learn more about the event at Please let me know if you have any questions or concerns; I do hope we can make this work as I would really like to attend this conference.

{Your Name}

Hope to see you there!


The post 7 Reasons to OptIn’19 appeared first on SparkPost.

How to use Natural Language Processing and Machine Learning in your Email Program Mon, 29 Jul 2019 13:00:50 +0000 Natural Language ProcessingDiscover how to implement AI-related technologies like Natural Language Processing and Machine Learning into your next email campaign.

The post How to use Natural Language Processing and Machine Learning in your Email Program appeared first on SparkPost.


Do we really need to remind anybody about the fact that email (and email marketing) isn’t going anywhere anytime soon? If we did, we’d just flash this study by The Radicati Group on them, containing such zingers as…

By the end of 2019, the number of worldwide email users will increase to over 2.9 billion. Over one-third of the worldwide population will be using email by year-end 2019.

For those of us who work in email? Stats like that are pretty temptacious, as the kids say. But today’s email isn’t your mom or dad’s email. The continuing success of email lies, in large part, to how its ability to evolve. Going mobile put email into a lot more pockets, for instance.?

Now, with the arrival of AI-related technologies, your email campaigns can become even more precise, engaging, and effective than they’ve ever been.

The arrival of email AI? That’s so 2018?

At the end of 2018, PwC said it had surveyed U.S. execs, and found 27% of them claiming to be already implementing AI in multiple areas.?

On the global front, 30% of companies worldwide will be using AI in at least one of their sales processes by 2020. But only 17% of email marketers considering automation tools gave any thought to incorporating AI.

The laggards might not realize the impact AI has already had on the email ecosystem. One very visible example was how Gmail handles email classification using Natural Language Processing (NLP) to filter incoming emails as Primary, Social, or Promotions messages.?

Here’s a pretty good explanation of how NLP does its job, presented as a primer for coders who want to hack up a spam filter. But if you aren’t interested in all the plumbing, that’s cool. One thing worth remembering, though? NLP and machine learning are only branches of the bigger, broader category “AI” and have specific goals.??

  • NLP is intended to read, decipher, understand, and make sense of human language in a manner that’s useful in machine-human interaction.?
  • Machine learning involves the application of algorithms and statistical models so computers can make decisions and perform tasks without explicit instructions by recognizing patterns in data and drawing inferences.

Right now, there are multiple tools and tactics where NLP and machine learning are being put to use to enhance email programs. Let’s look at some of the places where you could integrate them into your campaigns, shall we..?


With machine learning, you can now execute multi-armed bandit testing. If you’re used to split testing, brace yourself: Now you’ll be able to run tests continuously and put your findings to work immediately. Over time, you’ll gradually optimize your results, and simultaneously be able to test content and messaging while also sending your best-performing variant out to prospects or customers.

How’s it done? You set up a campaign and a few email variations, and machine learning does the rest, running tests throughout your campaign and fine-tuning it on the basis of test data. What can you test? Pretty much anything you’re already testing, from copy to design to images to timing.?


Machine learning and NLP – and its cousin, Natural Language Genration (NLG) – are being leveraged by multiple providers to deliver solutions that can actually generate subject lines and other copy.

Take a company like Persado, for instance: Its “message machine” applies its grasp of natural language to create copy that speaks in the marketer’s “brand voice,” leveraging a huge database of tagged and scored works in 25 languages, a database that evolves over time as machine learning delivers insights (and makes judgments) about which messages hold the most appeal for your target audience.

Touchstone, as another example, compares your subject line against a database of 21 billion emails, as well as industry trends, to predict its likely impression, click and conversion rates. automated the newsletter creation process, and uses machine learning to optimize content based on each recipient’s behaviors to provide 1:1 personalization that’s “tailored to your subscribers’ unique interests and personalities, without the time it takes to manually curate your emails.”


Want to pull off a little real-time content optimization to drive engagement? Cordial says it can “ingest and process customer event, behavior, and purchase data from virtually any source,” so messages can be dispatched across multiple channels, based on up-to-right-this-instant behavioral data. So onboarding, re-engagement campaigns, and other triggered emails can be aligned with what they’re interested in this very moment.

Another way to engage? Add a personal touch. Well, a virtual personal touch: Conversica proudly claims to deliver “personalized human touch at scale” through AI sales assistants that reach out to a user within minutes of him or her showing interest in your brand or inventory via email or SMS.?

If you’re worried the “conversation” reads like robo-copy, they claim the AI “empathizes” effectively by analyzing replies to tailor the right responses.? Moreover, the platform isn’t intended simply for initial engagement or onboarding but can handle routine dialogues throughout the entire customer journey.


For companies investing in customer data management platforms, being able to milk the greatest possible insight and benefits from big data to deliver highly personalized user experiences, especially in email, is an obvious concern.?

A machine learning solution that’s connected to these potentially enormous pools of data can do insightful segmentation in ways no human being – or boiler room full of human beings – ever could, making continual adjustments and uncovering new associations, even generating product new segments where none were visible before.? SimMachines is one of these providers, calling their particular flavor “dynamic predictive segmentation.”?

Predictive delivery

If you haven’t heard of it before, that’s because it’s a new wrinkle in applying machine learning to email. By analyzing the behavior of trillions of emails, predictive analytics and machine learning are able to optimize delivery and the overall health of an email program.

This means real-time insights are available about deliverability and performance issues, problems can be identified before they happen, and data-driven recommendations can be made about how to optimize engagement and performance.? Outages can be avoided – while ROI is maximized.

And if you’ll allow just one self-plug? It’s new to the game because this platform, SparkPost Signals, is the first and only email intelligence platform of its kind in the industry, and we’re proud to be offering it.

It’s an AI-for-email explosion

These are just a few of the areas where AI, NLP, and machine learning are making a present-day impact on email marketing. If you think it’s the tip of the iceberg – or the first trickle through the floodgates – you’d be right.

One way to see how feverish a new technology segment is getting is to see how many companies and startups have hung out a shingle, using investor or job sites like AngelList. Right now, a search for “email AI” there shows over 600 firms in the space, and there’ll be more to come.

In other words, there’ll eventually be an AI add-on for every facet of your email program.? In the meantime? Putting today’s existing AI tools to work already offers plenty of potential for discovering how NLP and machine learning can improve the way you’re using a veteran marketing channel that’s just as leading-edge as ever.

~ Erica

The post How to use Natural Language Processing and Machine Learning in your Email Program appeared first on SparkPost.

The Future of Email: Google Commits to BIMI Thu, 25 Jul 2019 21:56:01 +0000 bimi emailGoogle commits to BIMI! Learn what BIMI is and how it encourages legitimate brands and senders to adopt email authentication protocols.

The post The Future of Email: Google Commits to BIMI appeared first on SparkPost.


Google has announced support for BIMI (Brand Indicators for Message Identification). As the world’s leading mailbox provider—27.8% of worldwide mailboxes according to Litmus—Gmail can make or break a new email protocol or technology. This is a huge step for the BIMI working group and a sign of even greater things to come. Google is now the second major mailbox provider supporting BIMI. Verizon Media Group (Yahoo!, AOL) was the first, beginning their BIMI trial in 2018.

BIMI is a vendor-neutral standard that allows brands to display a verified logo in the receiver’s inbox next to fully authenticated emails. The intent of BIMI is to incentivize major brands to adopt proper email authentication—DMARC in particular—when sending mass messages to consumers. Senders who put in the effort to implement DMARC are rewarded with the display of their logo, similar to what appears for brands with a Google Plus profile.

Why do we need to “incentivize” this?

While setting up proper authentication as a sender isn’t rocket science, getting DMARC in place takes time, patience, and expertise. DMARC is a standard, open framework that allows brands (aka “senders”) to tell mailbox providers (aka “receivers”) what to do with mail that does NOT pass authentication on the sending domain.

The long-term goal for a sender is to enact a DMARC policy that specifically tells receivers to reject any mail that does not pass authentication checks on the sender’s domain, thus safeguarding against phishing and spoofing attacks which would otherwise appear to be “from” the domain in question. Because large businesses and major brands have many different streams of mail, there is risk involved: millions of emails could be rejected if this isn’t set up just right.

Feeling lost?

If you are new to email authentication, start by learning about SPF and DKIM, the building blocks of DMARC. These specifications are absolutely essential for any legitimate sender, especially if you have multiple different technology vendors sending email of any kind on behalf of your brand.

In addition to the resources linked above, SparkPost has the expert team to get your email up to snuff and on the road to beautifully branded BIMI emails! Contact us to get started today.



The post The Future of Email: Google Commits to BIMI appeared first on SparkPost.

Life at SparkPost: National Intern Day 2019 Thu, 25 Jul 2019 13:00:50 +0000 National Intern DayIn honor of National Intern Day, which falls every year on July 25th, we interviewed our amazing intern team about their experience at SparkPost so far.

The post Life at SparkPost: National Intern Day 2019 appeared first on SparkPost.


Here at SparkPost, we are so lucky to bring on an awesome team of interns every summer! In honor of National Intern Day, which falls each year on July 25th, we decided to interview our amazing intern team about their experience at SparkPost so far:

Tell us about a project that you were able to work on and the role you played.?

Isaac Luther, Engineering:?I worked on splitting two of our services off from each other. It was a great introduction to many of the services SparkPost uses since I had to set everything up for the new pipeline.

Matt Leifer, Engineering:?I was able to work on a project to create a new testing and validation system. I implemented part of the system, helped test the system, and helped monitor the system once it was rolled out. Being a part of this project during several different stages was an excellent learning experience.

Joseph Borden, Legal:?There are so many projects I could choose from, and all of my projects have
been rewarding! I wish I could share all of the work Jason has me doing, but there would be nothing to read by the time I finish redacting all of the confidential material.???

What’s the coolest new thing you have learned while being at SparkPost?

IL:?I’ve learned a lot about how different factors can affect productivity. My manager, Tim, has shared a lot of knowledge that he’s learned from books with our team, and it’s helped me understand the reasoning behind a lot of decisions.

ML:?I have learned how to work with several AWS services. I did not have much experience with AWS before this summer, and now I am much more familiar with how to use and maintain the services that AWS provides. With how prevalent and widely discussed cloud computing is today, it really has been exciting to work with it on a regular basis.

JB:?Working with Jason has been an invaluable learning experience thus far.? I have learned a plethora of new things, but the coolest has been learning exactly how legal suggestions/choices can positively impact a business.? For example, the use of a particular word or phrase in a contract can save a company thousands— perhaps millions— of dollars.? I knew lawyers could either anchor or sink a company; however, seeing the immediate impact of good lawyering first-hand has been a tremendous practical and learning experience.

What do you like about our culture?

IL:?I loved how close together everybody on my team was! I think everybody eating lunches together—especially in the office on Tuesday and Thursday—helps make a great team and company environment.

ML:?I really appreciate how willing everyone is to help other members of the SparkPost team. I always feel that I can receive help when I need it, and this has made me feel welcomed and comfortable.

Obviously, the office perks, such as the free lunches, are very enjoyable as well.

JB:?I love that SparkPost is inclusive and diverse; it makes for a great, comfortable workspace and environment.? SparkPost’s culture is what attracted me to apply for this internship and was a huge selling point when I decided to accept this internship.? I am happy to say the culture is better than advertised.

Matt – as a returning?intern?– can you share more about your experience coming back?

ML:?It has been a great experience coming back. Being able to start the summer in a familiar setting allowed me to start learning and working from day one. Also, working on projects that were not around last summer has provided me with many opportunities to learn about new technologies and ideas. Lastly, I really enjoy being around the same people as last summer and meeting new team members. Working with the helpful, friendly people of SparkPost every day makes me even happier with my choice to return this summer.

We also asked Isaac, Matt and Joseph’s respective managers to share their thoughts on our internship program as well:

Nate Durant, Technical Manager, Transmissions:?Interns at SparkPost provide a opportunity for not just or interns, but also our engineers.? They bring unique insight and new academic approaches to our team when dealing with technologies like machine learning and quality assurance.? Our interns, both new and returning, have a tangible impact on our products and are by no means limited to internal projects. I always look forward to their time here, and appreciate all their hard work and enthusiasm.

Jason Soni, General Counsel:?As valuable as my own?internship?experience was at SparkPost,?I’ve come to value the program more even more as a manager. ?While it’s certainly great to get some extra?work done around the house and mentor the next?generation of my profession, what I value most is that?interns?challenge “the?way we’ve always done it” mentality and bring fresh new ideas to the company.??Interns?are good at questioning processes and?can often see a better way of doing things that a manager might not.

Happy National Intern Day! Interested in joining our amazing team? Check out our open positions!

~ Michelle


The post Life at SparkPost: National Intern Day 2019 appeared first on SparkPost.

Getting Momentum in the Cloud Mon, 22 Jul 2019 13:00:36 +0000 cloudRead up on the ability to use any of the SparkPost products in a cloud environment either as stand-alone implementations or together as a hybrid solution.?

The post Getting Momentum in the Cloud appeared first on SparkPost.


This post is about the ability to use any of the SparkPost products in a cloud environment either as stand-alone implementations or together as a hybrid solution.

If you are a long time Momentum or PowerMTA customer deployed on bare metal in your own data center, you can use this guide to determine a path forward to migrating to a cloud service. If you are a new PowerMTA user wanting to deploy to one of the major cloud services, this is a good guide to a successful implementation.

For the past two decades, the Momentum MTA has been one of the fastest, most agile email engines on the planet.? Whether you know it as the original eCelerity MTA, or Message Systems Momentum, or as the core processing engine underpinning SparkPost, the world’s fastest growing cloud email service,? Momentum has had momentum for a long time. (see what I did there?)

?Alongside Momentum there lived another very similar product called PowerMTA (PMTA), which is equally capable and agile as well as being easy to install and support.? Momentum and PowerMTA were competitors for a long time, but several years ago, came together under one roof and now, along with the SparkPost cloud service, form a trio of email delivery engines that can satisfy any email transport need.

SparkPost lives natively in the cloud – it is built entirely on AWS.? Momentum and PMTA can be installed to run in a cloud platform if needed, but there are many things to consider before committing to a forklift into the cloud. There may actually be very good reasons for NOT doing it, so do your research carefully.

Look before you leap

Chris McFadden, our VP of Engineering wrote about our own journey to the cloud last year and made the very good point that many of the factors in your decision are not technology related at all.? Deploying to the cloud involves a new set of paradigms that you may not be ready for. Business processes may need to change and there may be privacy considerations that were not relevant in a bare metal infrastructure.??

Some time ago, our CTO and Co-Founder, George Schlossnagle wrote about some of the unique considerations for deploying email servers in a cloud service.? Cloud tech is designed for autoscaling and push button deployments that are ideal for stateless systems.? If you have a web service in the cloud, that is one thing, but running a stateful MTA on a cloud platform is a whole new ballgame.

When you deploy in your own data center, you control the environment and it is not unusual to see servers with no individual protection because they rely on the network firewall to protect them.? In a cloud deployment, doing that can be fatal. In the land of elastic computing, you need to be particularly diligent with security. It is extremely important to keep up to date with patches and updates.? Make sure your firewall is well maintained and close any open ports you don’t actually use. Deprecate weak ciphers, lock down ACLs, and remove any packages that are not required for the server’s purpose.

The last clear caveat we can offer is to be wary of the cloud provider’s DNS.? Remember that these systems were designed for web services and databases that only make periodic DNS lookups.? High volume email systems may perform millions of DNS lookups every hour and that has a tendency to break things.? Even running your own separate DNS for the unique needs of high volume email can lead to unforeseen problems.

Pick a cloud, any cloud…

There are many major cloud providers and even more lesser-known services to choose from when making the leap from hardware data centers to cloud services.? Even the concept of “cloud” varies between them. Here is a look at the most common ones we encounter working with our customers.

?AWS (Amazon Web Services)

  • We have the most experience here as SparkPost is built entirely in AWS fabric.
  • While you can deliver on port 25, you can only send very small volumes without attracting negative attention.? If you want to send volume mail, you will need explicit approval from AWS
  • AWS includes a marketplace of 3rd party services you can leverage

?GCP (Google Cloud Platform)

  • Google offers a development platform that enables you to build virtual servers in custom environments on the fly similar to Amazon’s EC2
  • Cannot deliver on port 25 without explicit approval
  • Marketplace of 3rd party services

?Azure (Microsoft’s cloud app platform)

  • ?Azure came later to the party, but has an equally refined tool set.
  • Similar offering to AWS and GCP including a marketplace of 3rd party services
  • Cannot deliver on port 25 without explicit approval

SAP, IBM, Digital Ocean, and VMWare Vsphere round out the list of common cloud environments we hear customers using.

There are some things to remember when moving (forklifting) from a hardware data center to cloud services. As you design your platform deployment, keep these in mind. Tackling these issues during your planning phase will save you a ton of stress and frustration in the long run.? For instance, you may find that your chosen cloud provider denies you access to port 25 under any circumstance.? In that case you need to change providers or consider a SaaS solution like SparkPost instead.

  1. Delivery over port 25 is limited or non-existent,
  2. 1 physical CPU != to 1 virtual CPU.
  3. IPs and MACs tend to change periodically; for instance, with AWS EC2, you have to allocate “elastic IPs” to be bound to your instances (or load balancers) to get stable addresses.
  4. Inter-node communication is not the same in the cloud

Before you decide on a cloud host, make sure you can actually deliver email from it.? Apply for any exception you need in advance because you may be denied – no matter how big a deal you think you are, Amazon, Google, and Microsoft are probably bigger.

Get full cost details on not only the compute instance that matches your needs, but also any additional charges for vCPUs, RAM, storage, in-bound bandwidth, outbound bandwidth, static IPs, and billing frameworks.? Each provider calls these something slightly different, but they exist and are often hidden costs unless you do the research.

?A case study

When building out a basic*?Momentum server, we recommend 8 cores, 32 GB RAM, and 600 GB of storage. Keep in mind that 1 physical CPU is NOT equal to 1 vCPU. When calculating virtual server sizes, each vCPU = 1 core.? We specifically quote our requirements in CORES for this reason. If you are building a cluster, you will want to enclose the instances inside virtual private cluster (vpc) with an attached elastic IP so you can control the public-facing IP without concern over whether the compute instance IPs change.? In the AWS universe, an M3 medium instance or larger is typically required.

?One interesting thing that the cloud host providers do not highlight, but has been our experience is that you can expect to see 20 to 30% less throughput in the cloud than with bare metal.? For instance, the Momentum deployment mentioned above should operate at ~1 million messages per hour on a physical server, but you should only expect 700,000/hour in a cloud host. This means you need to “supersize” your server deployment plan and overcompensate in the design.

?One last factor to consider is bandwidth cost.? Cloud host providers charge for outbound bandwidth just like most physical data centers do, but the cost calculations may differ from your expectation.? In addition, you may find that some bandwidth is exempt from billing. With Amazon, much of the bandwidth used within a region is not billed, though inter-AZ and inter-VPC is, and that can add up. If your message generation and delivery nodes are in the same region and you are running out of a single VPC, then you may see significant savings.? However, if your message generation is in the Ohio region and your delivery engines are in Oregon, you may find yourself paying bandwidth fees between those systems adding potentially unexpected costs.

?The above has been particularly important to our customers who use both our on-premises and SaaS solutions in a hybrid.? A customer moving their PowerMTA or Momentum cluster to the cloud and also wanting to use SparkPost SaaS delivery as a failover or alternate channel should be deployed in the same region as our SparkPost deployment for that part of the world.? The cost savings can be significant.

?We recently produced a webinar discussing this and also have blogged about our own journey to the cloud.? Here are some interesting links to those resources for some further reading.

*?A “basic” Momentum install is designed to delivery 1Million message per hour from a bare metal server assuming a 50k payload and 10Gb NIC.? A full hardware recommendation guide is available on request.

~ Tom

The post Getting Momentum in the Cloud appeared first on SparkPost.

The Risks of Sending Email to Inactive Users Fri, 19 Jul 2019 13:00:45 +0000 sending email to inactive usersOur SVP of Deliverability Strategy, Kate Nowrouzi, discusses the business risks associated with sending email to inactive users.

The post The Risks of Sending Email to Inactive Users appeared first on SparkPost.


When we onboard enterprise customers here at SparkPost, one of the topics we cover is list hygiene: removing inactive users from your mailing list. The definition of “inactive” really varies by email type (marketing, welcome, transactional) and industry (finance, marketing, employment, etc). For example “inactive” in the employment industry could be six months or more, meaning if a user seeking a new job has not opened or clicked on a piece of email sent by your company in half a year, they are considered inactive. But, for a company like Pinterest inactive could be 12 months, as some users might only check Pinterest during the winter months to get outfit ideas for their company’s annual holiday party. So, there is no hard and fast rule when it comes to defining “inactive” in the email marketing world.

The challenge is to convince the CRM team to remove inactive users as there can be push back since many see each email address a possible source of revenue. But, the risks of sending to a large population of inactive users are greater than keeping them for the sake of possible revenue.

Here’s why:

  1. ISPs turn old email addresses with no activity into spam traps after 12 months. Hitting too many traps will result in a lower IP/ domain reputation.
  2. Major ISPs take engagement into consideration for inbox placement. If a high percentage of the email addresses on your list have zero open rates in the past 12 months, this is an indication of poor list hygiene which will result in heavy spam foldering.

The truth is if you are sending email to the people who want to receive them, they have a higher chance of engaging with your emails. If they are not opening your emails, even if they signed up for them at some point, it means they are no longer interested. There is little benefit to keeping sending them on your list because there is a high chance that they will get annoyed with your company and could report your email as spam. A high complaint rate will damage your reputation. And, even if there is a small chance that a low percentage of these subscribers will open an email after 12 months of inactivity, the risks of hitting a trap are much greater than the revenue that can be generated from that user.

~ Kate

The post The Risks of Sending Email to Inactive Users appeared first on SparkPost.

Email Emojis: When & When Not To Use Them Wed, 17 Jul 2019 13:00:07 +0000 email emojisEmojis in email subject lines are becoming a "thing" - but are they the right strategy? Here are some tips on when you should use emojis, how to use emojis and some examples of what to do and what not to do.

The post Email Emojis: When & When Not To Use Them appeared first on SparkPost.

  • This blog post was originally published on 09/28/2016 and was updated on 07/17/2019

With the popularity of? Instagram, Facebook and LinkedIn’s reactions, Twitter, and text messaging, everyone is expressing themselves with emojis these days. In fact, 53% of Millenials believe using emojis and text together allow people to better understand each other. This?may be why you’re seeing more email emojis in subject lines lately. But is it the right strategy for your email marketing program?

Tips for using email emojis:

  • Be sure you have an emoji that is relevant to your message. For example, Home Depot falls flat when they use falling leaves to signify (I think) the fall season. It’s weak and lacks relevance. Yet, Recchiuti uses a chocolate chip cookie when talking about cookie recipes they crave – very relevant

Bad example
Bad example of email emojis - HomeDepotGood Example
Good example emojis in email - Recchiuti Cookie Emoji

  • Use if your message would benefit from some emotion being added to it. For example, VRBO adds a generic smiley with shades but it’s the effect when you see it in your inbox reminds you that you want to go on vacation somewhere

?Good Example
VRBO uses emojis in email

  • Do use when you think your audience will be able to relate. For example, I’m a big Reddit fan, but Reddit doesn’t use an emoji in their email every time. They use it sparingly. In this example, Reddit uses the apple emoji and the detective emoji when communicating to their audience that a teacher posed undercover as a student on his first day of teaching high school.
    ? ? ? ? ? ?

Good ExampleReddit uses emojis in email

  • Make sure your emoji is legible.?The devices we read email on can be small and emojis are even smaller. For example, Williams-Sonoma uses the number five in a circle, but it’s so small that it looks like a black blob. Not until you open the email can you actually see what it was supposed to be.

WilliamsSonoma-email emojiWilliamsSonoma Email Emoji

  • Don’t overuse email emojis. For example, Last Call Neiman Marcus not only sends generic and not very relevant emojis, but they tend to do it often. The first time I saw it, their message stood out in my inbox. But now, I don’t even notice it.

Neiman Marcus email emojis

  • Be sure to TEST IT. Not all email clients accept the use of emojis in email subject lines and sometimes emojis can trigger spam filters or worse, look like?□ this. Be sure to test your email before sending it out to the masses.

How do you add emojis to your email subject lines?

Believe it or not, you can just copy and paste your emoji into your subject line. Not all email programs are created equal so not all of them will work with emojis.

Here are a few resources you can try in your next subject line.

See you online!
~ Tracy

The post Email Emojis: When & When Not To Use Them appeared first on SparkPost.

The Differences Between Using SMTP or API with SparkPost Mon, 15 Jul 2019 13:00:44 +0000 SMTPSending email through SparkPost can be done through SMTP or using our API. We'll take you through the pros and cons of each method with some examples.

The post The Differences Between Using SMTP or API with SparkPost appeared first on SparkPost.

  • This blog post was originally published on 06/10/2016 and was updated on 7/15/2019

Sending email through SparkPost to your subscribers and/or customers can be done two different ways: using our API, or sending via SMTP. The deciding factor will usually be some combination of convenience for your use case, availability/cost of coding/hardware resources, and the relative priority for your business of things like sending speed and ease of migration.

There are pros and cons to both approaches. Naturally, we think our API is pretty great, and that it has advantages over SMTP, otherwise, we wouldn’t have it. Offering SMTP in addition to our API lets us support a wider range of use cases. Let’s take a look at the pros and cons for both SMTP and our API, as well as examples of each approach.

Sending via SMTP with SparkPost

Sometimes SMTP is the only choice that makes sense, given your constraints. Maybe your legacy system uses SMTP, and nobody is available to write the code to send via API instead. SMTP lowers the friction for this migration path. Common steps such as modifying existing messages by adding a?custom header to set the campaign for different message streams, or enabling open/click tracking tend to be significantly less effort than starting to use a new API.

Which is a nice segue to show a pro/con list for sending with SMTP:


  1. Platform-agnostic – SMTP is accepted everywhere
    • If you want to migrate again, it’ll be easier
  2. You have full control over your “mail merge” process
    • Can generate messages however you like
    • Continue to use existing tools
  3. SMTP failures are in-band and always include context
    • Failed command and error code tell you what failed and why


  1. SMTP is not accepted FROM everywhere
    • Some environments’ firewalls block ports commonly used for SMTP
  2. You have to build your own “mail merge” messages
    • MIME and the?various email RFCs can be tricky
    • This has a resource (hardware & bandwidth) cost, especially for bulk sends
  3. SMTP is a chatty protocol
    • Each message requires several round trips to our servers
    • This adds up to longer bulk send times

Here’s an example of injecting some test content into SparkPost with SMTP, using?swaks. The API key you substitute below will need the

Send via SMTP
?permission, or authentication will fail with
535 5.7.8 Sorry.

$ swaks --server \
	--auth-user SMTP_Injection --auth-password $SPARKPOST_API_KEY \
	--to --from \
	--h-Subject 'smtp via sparkpost'
=== Trying
=== Connected to
<-  220 2.0.0 ESMTP ecelerity r(Core: Wed, 08 Jun 2016 15:55:19 +0000
	-> EHLO test
<- says EHLO to
<-  250-STARTTLS
<-  250-8BITMIME
<-  334 VXNlcm5hbWU6
	-> U01UUF9JbmplY3Rpb24=
<-  334 UGFzc3dvcmQ6
<-  235 2.0.0 Authed. Go on.
	-> MAIL FROM:<>
<-  250 2.0.0 MAIL FROM accepted
	-> RCPT TO:<>
<-  250 2.0.0 RCPT TO accepted
	-> DATA
<-  354 3.0.0 continue.  finished with "\r\n.\r\n"
	-> Date: Wed, 08 Jun 2016 09:55:20 -0600
	-> To:
	-> From:
	-> Subject: smtp via sparkpost
	-> X-Mailer: swaks v20130209.0
	-> This is a test mailing
	-> .
<-  250 2.0.0 OK 7D/49-16644-7EF38575
	-> QUIT
<-  221 2.3.0 closing connection

Sending with the SparkPost API

We like our API, and we hope you like it too. We think you should use it, as there are quite a few advantages over SMTP for many use cases, for example, triggering mail directly from your app’s server-side code. Besides, with a paid account you’re really not getting as much as you could for your money without offloading everything from your systems onto SparkPost that you can, which the API allows you to do.


  1. HTTP is allowed by all but the most restrictive firewalls
  2. Generation AKA “mail merge” is handled by SparkPost
    • Removes load from your servers
    • Can mean generation hardware/horsepower is no longer needed
  3. One connection round trip per API call
    • No per-message latency
  4. Async sending and concurrency is handled by SparkPost
    • Up to 10k message batches for best performance
    • Reduces complexity (AKA things to break) in your app


  1. Using our HTTP API means writing code
  2. Replacing in-house generation may require refactoring
    • Things like pre-processing data to format dates differently
  3. Stats are generally out-of-band
    • Some sending errors are in-band (invalid email, for example)
    • Others require processing event data one of two ways:
  4. For larger sends (10k+ recipients) batching or concurrency is recommended
    • This is a performance sweet spot, not a hard limit

Here’s an example with the same test content as above, using cURL. The API key you substitute below will need the

Transmissions: Read/Write
?permission, or the API call will fail with
HTTP/1.1 403 Forbidden
, and
{"errors": [ {"message": "Forbidden."} ]}
? in the body.

$ curl -v -X POST -H "Authorization: $SPARKPOST_API_KEY" \
	--data '{
	"recipients": [
		"address": {
		"email": ""
	"content": {
	"text": "This is a test mailing",
	"subject": "api via sparkpost",
	"from": ""
**   Trying
** Connected to ( port 443 (#0)
** TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
** Server certificate: *
** Server certificate: RapidSSL SHA256 CA - G3
** Server certificate: GeoTrust Global CA
> POST /api/v1/transmissions HTTP/1.1
> Host:
> User-Agent: curl/7.43.0
> Accept: */*
> Authorization: YSBmYWtlIGFwaSBrZXksIG1hZGUgeW91IGxvb2sh
> Content-Length: 312
> Content-Type: application/x-www-form-urlencoded
** upload completely sent off: 312 out of 312 bytes
< HTTP/1.1 200 OK
< Cache-Control: no-cache, no-store
< Content-Type: application/json
< Date: Wed, 08 Jun 2016 17:53:12 GMT
< Server: msys-http
< Vary: Accept
< Content-Length: 109
< Connection: keep-alive
** Connection #0 to host left intact
{ "results": { "total_rejected_recipients": 0, "total_accepted_recipients": 1, "id": "102364612952283792" } }

So there you have it! As with most things in life, the answer to which will work best for you is (spoiler alert) “It depends.”. We recommend using our API unless there are reasons that won’t work for you, such as lack of development resources to make the switch. SMTP is there as a safety net to help support those cases.

Whichever way you choose, make sure you set up DKIM! Authenticating the source and content of your email is very important, and can have a huge impact on the deliverability of your email. Instructions for setting up DKIM are here.

What were the deciding factors for your choice between SMTP and our API? Let us know on Twitter at?@SparkPost?or in our Community Slack channel!

~ Dave

Dev Survival Guide Blog Footer

The post The Differences Between Using SMTP or API with SparkPost appeared first on SparkPost.

Be Our Guest: 4 Keys to a Great Welcome Campaign Fri, 12 Jul 2019 13:00:22 +0000 welcome campaignContent Marketing Manager at Iterable, Michael Huard, shares 4 welcome campaign strategies that will make your audience feel like the belle of the ball.

The post Be Our Guest: 4 Keys to a Great Welcome Campaign appeared first on SparkPost.


Put your emails to the test. When a customer subscribes, does your welcome campaign treat them like a valued guest?

The welcome campaign is your chance to show off the bells and whistles of what you have to offer. It’s a golden opportunity to kickstart a relationship with your audience.

It’s also likely one of your most successful campaigns, so it’s worth investing the time and effort to make it the best it can be.

But too often, brands are gruff, impersonal and, frankly, unwelcoming with their welcome campaigns.

That’s why we’re here to provide you with 4 ways to create a welcome campaign that treats your audience like the belle of the ball.

1. Properly Introduce Yourself

Treat the first email in your welcome series like the moment you invite a new guest into your home.

Introduce yourself. Be warm and express gratitude for them choosing your brand. Offer them a treat or gift as a token of your appreciation. After all, they gave you their personal information. That’s a big step for many.

In this process, make sure to fully introduce yourself and any iterations of your brand that may reach out. Establish your inbox identity by letting your customers know what addresses to keep an eye out for.

ISPs are monitoring spam like never before. Your welcome email needs to be clear with your sender identity for better deliverability.

Don’t be afraid to explain the differences between your brand identities. Your “From” name may change based on the type of email you’re sending, but as long as there is a clear connection to your brand, you can avoid the dreaded unsubscribe or spam folders.

2. Personalize by Their Signup Source

There are a variety of ways your customers can find themselves on your list.
Whether it’s a mobile app install, a first purchase, a contest entry, or gated content download, it’s important that you personalize your welcome campaign by the source of their subscription.

Incorporate the foundation of their subscription in your welcome email so they know exactly how you found them and why they are receiving a message. Let them know why you are in their inbox.

In doing so, you are letting the customer know you are paying attention to their actions. Providing relevant information keeps each member of your audience engaged and promotes interaction with your brand.

3. Give Them the Grand Tour

Your welcome campaign is more than an introduction; it’s the start of a tour of your brand. It kicks off the customer journey.

No matter how or why they subscribed, this is your chance to get them further involved in your brand in the ways that you choose.

Walk your customers through your brand experience. Let them know what it means to be a valued member of your community.

Try starting off with information about their account before describing the benefits of choosing your brand. Lead them to your mobile app and lay out the perks of being a member.

ASOS, a leading U.K. retailer, does a great job in their welcome email showing members how to navigate their product offerings by focusing on different categories (ASOS Brands, Labels you’ll love, Face + Body).

ASOS orients newcomers with their category-specific welcome email.

ASOS sells items from over 800 brands, but by giving customers a starting point, they guide them through the experience so they don’t become overwhelmed by all that the retailer offers.

There is a logical path—that you’ve likely set—to make the most of your brand’s offerings, so don’t make your customers search for it.

4. Incentivize Them to Take Action

The guided tour is an excellent addition to any welcome campaign, but what if you have a particular CTA? Perhaps you need customers to complete their profiles before moving further down their journey with your brand.

Hold their hand in this process. This cannot be stressed enough. Keep it simple, stupid. Don’t try to reinvent the wheel. Whatever phrasing will help you remember to not overdo this part of the welcome campaign.

If you want your new subscriber to take a certain step, then make it known. Make your CTA button to complete their profile big, central, and bright. The goal here is twofold: engagement and progressive profiling.

Expand on this concept by building a full welcome series that culminates in the completion of your desired action. Topshop, another popular retailer based in the U.K., incentivizes action in their welcome email with a discount code, information about a birthday treat, and a hashtag to find their styles on social media.

Topshop sweetens the deal with a first-purchase promo code and birthday treat.

The call to “Update Your Details” is a vital action for progressive profiling to be used in future personalization efforts. A good follow up to this email would be continued requests to update specific, highly valued profile details.

Remember, you’re the host. You don’t want your guests to get lost on the way to the snack table. Lay it out for them in simple, easy terms to keep them happy and satisfied.

Enjoy the Party

First impressions truly do make a difference when it comes to your brand. You don’t want to come off as rude, beastly, and unpleasant to interact with.

Your welcome campaign is the key. It’s the start of your customer journey and, as such, you want each and every customer to start off on the right foot.

If you do it right, then your guests might just decide to stay awhile and make themselves comfortable.

For advanced tactics to improve your welcome emails, download Iterable‘s guide, Unboxing Must-Have Marketing Campaigns: Welcome Emails, to learn more.

~ Michael


Michael Huard is a Content Marketing Manager at?Iterable. He is an experienced multimedia content creator having produced written, video, and photographic content for leading companies in technology and entertainment. Michael has a Bachelor’s degree in Linguistics from UC Berkeley and a Master’s degree in Specialized Journalism from the University of Southern California.

The post Be Our Guest: 4 Keys to a Great Welcome Campaign appeared first on SparkPost.

Building an Email Strategy to Connect with your Gen Z Customers Wed, 10 Jul 2019 13:00:19 +0000 Gen Z CustomersSenior Manager of Digital and Content Strategy, Jen Lacey, explains how to create an email program that will really resonate with Gen Z customers.

The post Building an Email Strategy to Connect with your Gen Z Customers appeared first on SparkPost.


It’s always seemed a little bit presumptuous to try to encapsulate an entire generation under a label like Baby Boomers, Generation X, and, now, Generation Z.? We want to avoid the trap of gross stereotyping, especially as marketers.

But there are, of course, real differences between these groups. And how you construct an email marketing strategy to engage any of them relies on knowing those distinctions. Gen Z, naturally, is a group that’s remarkably different from everyone who’s come before.

They’re more realistic than optimistic, more independent-minded than Millennials, and also more cautious about sharing personal data.

Without further ado, let’s get to a stat blast:

  • Born between the mid-1990s and the mid-2000s, Generation Z will include nearly 85 million Americans by 2020, about 24.7% of the population. Worldwide, they’ll total nearly 2.6 billion by then.
  • They already have $143 billion in buying power.
  • When they come of age, they’ll make up 40% of U.S. consumers.
  • 96% of U.S. Gen Zers own a smartphone.
  • In fact, most have never not known life without the web; 40% say working wifi is more valuable at work than working bathrooms.
  • They’ve got an average attention span of 8 seconds.

They aren’t abandoning email

One insight that should bring a smile to email marketers of every generation? Gen Zers really like email, in spite of the fact they also obsess over texting, social media, and other messaging platforms.

Still, they consider email important, too, especially as consumers; 46% of them say it’s a big factor in making their buying decisions, and they’re especially open to using email in the future. 48% see their use of email growing over time, while only 36% of Millennials and 23% of Generation Xers say the same.

58% of them check their email multiple times every day, and the same survey found that an impressive 28.5% of them had purchased something as a direct result of receiving an email.

In fact, the same survey found that while social media is their favorite way of engaging with brands, email ran a very close second, even ahead of face-to-face engagement.

Great news! Problem solved, right? Well, yes and no. They’re willing to embrace email, so long as email marketers are willing to work on their terms.

Be really, really straight with them

What matters to Gen Z consumers? Authenticity and transparency; they don’t want to be “sold” – that’s plain from their huge preference for ad blockers.

In terms of email, that means your copy has to be sincere, avoiding hyperbole and the kind of obvious shilling they’ll turn a blind eye to (or just send to spam). Be upfront and honest, and never, ever be tempted to use misleading subject lines; when you make a promise, it’s got to be kept, or they’ll hold your feet to the fire.

“Honesty is the best policy” may be an old platitude, but it holds for Generation Z like it never has before. Remember: if you violate their trust, they’ll be happy to let everybody they know hear about it.

Loyalty matters (a lot)

Many marketers are fearful that these upcoming consumers aren’t going to prove as loyal as previous generations. But it’s less about them having an innate lack of the “customer loyalty gene” as it is they’ve got a higher bar when it comes to their shopping experience. In fact, loyalty – your loyalty to them, and vice-versa – is a huge deal to Gen Z.

A bit further on, we’ll point to the fact Gen Zers expect a seamless shopping experience; they want to feel appreciated, with a customer experience, personalized messages, and offers that prove they’re valued by a marketer.

According to Accenture, 95% or so of Gen Z members want brands to “actively” court their attention (and dollars), and are most influenced by coupons sent via email or even snail mail. Channels like text messaging have their place in the mix, too, of course.

Personalize, but don’t overstep

Part and parcel of that active approached to engagement is the use personalized email campaigns that emphasize individual engagement, and your appreciation for their loyalty. Give respect, in other words, and they’ll give it right back.

But an important layer of this, says a study by IBM and the National Retail Federation? They also want individualization, where they can initiate and customize their own shopping and buying experiences.? Giving them more power to customize the content, offers, and frequency of emails they get from you can be one component of this, but it’s also about ratcheting up the relevance of every message you put in front of them.

At the same time, though, Gen Z consumers are reluctant about sharing personal data. Therefore, you’ve got to tread the line between delivering targeted messages and offers, and coming off as asking for too much personal information.? The best approach? Tell them exactly the data you’d like them to lend you, and explain precisely how you’re going to use it.

Show commitment to good causes

Email is a terrific channel for communicating commitment: Not just yours to your audience, but also to show off your commitment to good causes. That’s key with Generation Z, so much so it’s practically becoming table stakes for marketers.

Half of worldwide consumers see themselves as being belief-driven buyers, and Gen Z is likely to be even more disposed to look favorably on brands that show a commitment to making life better for others. They’ll also be willing to punish brands that don’t meet their expectations for social responsibility.

Email can be an excellent opportunity to show you’re willing to give back to the community, and it’s also a fine way to get recipients engaged in supporting those efforts.

Here’s an excellent example of that from one of the pioneers in this brand of conscientious capitalism, TOMS. Nobody else does a better job of tying their product marketing and sales pitch into the idea that a consumer can lend a direct hand in global betterment:

Go mobile or go home

If you haven’t figured this one out yet? There’s nothing else we can tell you.

Use video and other interactive tools

According to the research, they’re huge consumers of digital media, and 35% of them prefer viewing video on YouTube versus only 19% who prefer traditional TV.? In their world, video lives everywhere, and you’re a dinosaur if you’re not able to deliver it.

Embedding video in email is, therefore, practically mandatory in making your campaigns more engaging and interesting for this audience. Especially when you also realize how important seamless shopping experiences are to them.

So blurring the lines between online and inbox experiences can work in your favor, so long as it’s a smooth and consistent user experience, even for the more ardent channel-hoppers.

~ Jen

new rules email deliverability best practices

The post Building an Email Strategy to Connect with your Gen Z Customers appeared first on SparkPost.

What is Blockchain Email? Mon, 08 Jul 2019 13:00:57 +0000 Blockchain EmailBlockchain email has benefits that make it attractive to email marketers, but also has some drawbacks too that could make adopting the technology difficult.

The post What is Blockchain Email? appeared first on SparkPost.


The Pros and Cons of Blockchain Email

Like the cloud several years ago, cryptocurrency is the new tech buzzword that’s generated a lot of chatter while leaving many wondering if it’s much ado about nothing. The term “blockchain” often goes hand-in-hand with the cryptocurrency talk, but it has applications beyond that, including email.

It might seem surprising, but blockchain email is a thing, and there are a few projects in development that want to use it to disrupt traditional email systems. Because a blockchain is an open, distributed ledger that’s replicated across many computers and has no centralized point of access, it’s seen as immune to attacks by bad actors. Those features make it attractive for email, which has many weaknesses that can be exploited.

Figuring out a way to make email more secure is key because it’s not going away any time soon. According to OptinMonster, people send a staggering 102.6 trillion emails annually, and in the U.S., it’s used by more than 90% of everyone over the age of 15 (yes, even those who have never known a world without social media).

In addition, 60% of consumers join email lists to get promotional offers, compared to 20% of consumers who follow brands on social media for the same reason. And with a potential return on investment of up to 4400%, email marketing remains a strong growth driver for many businesses.

Blockchain email has benefits that make it attractive to email marketers, but it has drawbacks too, as we’ll explain.

The benefits of blockchain email

There are several reasons why blockchain email is an attractive prospect for anyone who wants to disrupt the status quo, including:

  • Each message would be authenticated

Because a blockchain is an immutable set of records that are authenticated by each of the computers that store copies of it, a blockchain email system would feature a message database that accurately reflects the sending and receiving activity of everyone using it. Despite the development of such security tools as SPF, DKIM, and DMARC, spam continues to plague our inboxes, and nearly all of us have been the recipients of phishing and spearphishing attempts by the bad guys.

However, blockchain email would provide a single source of truth for each message sent and received, allowing users to easily verify that everything they receive came from a trusted sender. Bad actors couldn’t impersonate others, and they would have a hard time sending spam, since their messages would need to be verified.

  • Users would (likely) have privacy

Putting email on a decentralized blockchain means that no single party would have control over users’ accounts and their messages. Today, many people “pay” for free email services by letting companies parse their messages for signals that feed advertising machines. Blockchain email would let them keep their messages free from prying eyes, even if those doing the snooping are silicon-based.

In addition, if someone wanted to shut down their blockchain email account, they could easily do so without worrying that their information won’t be completely deleted, unlike many free services that essentially put accounts in hibernation when users attempt to shut them down. If a single third party has control over the data, they can do what they want with it, but if a blockchain email database is copied across many computers, only users will be able to dictate how their information is handled.

  • No one would ever lose an email again (hopefully)

A blockchain email system’s database couldn’t become corrupt because there would be no central email server that could be damaged or experience a failure. Even deleted messages could be saved via a mechanism such as an off-chain node, allowing the creation of an archive that users could access when needed.

  • Email marketers could send more precisely targeted campaigns

Blockchain email could, in theory, result in a wealth of data about its users. Since each person’s identity would be authenticated and the blockchain would contain an immutable source of truth about their email history, email marketers could use artificial intelligence to sift through that data and more precisely target the right people for their campaigns.

While many people might groan at such a concept, it could provide a way to pay for a blockchain email platform. In addition, if people are going to see ads, isn’t it better for them to see ones that are targeted to their interests?

The downsides of blockchain email

However, there are some reasons why you don’t hear a lot of talk about blockchain email these days, including:

  • The staggering storage requirements

Bitcoin, the largest cryptocurrency by market capitalization, uses a blockchain that was 210GB as of April 2019. While that’s a big database, it’s still not much compared to the amount of space emails typically take up. The average email is 75KB – multiply that by the 102.6 trillion emails sent every year and you’ll see that a blockchain email platform with even a modest number of users would quickly have sizable storage requirements.

Since a copy of the blockchain needs to reside on each computer in the network (5 million of them, in the case of Bitcoin), that means a blockchain email platform could easily dwarf the storage requirements for cryptocurrencies. That’s a scalability problem that would intimidate even the most seasoned IT professionals, although a clever developer could potentially solve that problem by, for example, storing messages off the blockchain and only using it to verify senders and receivers.

In fact, Salesforce recently won a patent for a blockchain-based platform that would store only part of an email, so that the sender and recipient’s copies could be compared to determine whether a message is authentic. A discrepancy would result in the email being marked as spam.

  • The need for guaranteed user privacy

There are a few companies developing blockchain email, but it’s not clear that any of them are going to make their code open source. Any company that can’t make their code available can’t necessarily guarantee user privacy, which would be a deal-breaker for something as sensitive as email.

  • The possibility of creating “walled gardens”

At least one blockchain email service currently in development only lets its users email each other, leaving anyone on another platform out in the cold. It’s reminiscent of the old days, before the web became dominant, when people on AOL and CompuServe couldn’t send messages between the two services.

However, this limitation doesn’t seem to be in place for every blockchain email platform that’s in the works, so it’s possible that this problem could end up being nonexistent.

The prospects for blockchain email

Blockchain email currently lags far behind cryptocurrency when it comes to adoption and interest in the long-term prospects of the technology. It also seems to be gaining less traction than messaging, in-app payments, contract creation, and other use cases.

However, the possibility of using it to combat all kinds of fraud is very attractive to businesses, so it’s likely that blockchain-based like the one Salesforce is developing could win out in the long run. Even if blockchain can’t provide an end-to-end, all-encompassing email solution, it can likely supplement the current environment.

~ Casey

The post What is Blockchain Email? appeared first on SparkPost.

How to Start Sending Mass Email Fri, 05 Jul 2019 13:00:26 +0000 Start Sending Mass EmailGetting started with SparkPost is super easy. Check out these step-by-step instructions on how to start sending mass email in minutes!

The post How to Start Sending Mass Email appeared first on SparkPost.

  • This blog post was originally published on 10/23/2015 and was updated on 7/05/2019

Are you brand new to email and not sure where to start? Unfortunately, sending mass email is actually a pretty complicated science. Fortunately, we’ve put together this guide so you can tackle the initial steps of sending with SparkPost and fill you in on some of the jargon you’ll need to know when building out your email program.

  1. Are you sending transactional email or marketing email? Sending transactional emails can be considered as a part of doing business so you may not need opt-in consent. If you are sending marketing emails you will need your recipients to opt-in or your emails could be considered SPAM.
  2. Are you sending out immediately or scheduling a “bulk send”? Think about sending limits. Your “bulk send” amount could go over your sending limit.
  3. Make sure you are sending expected content. This could include the copy for your ‘password resets’ to the content of your newsletter. Newsletters should contain something that’s relevant to your audience and in line with expectations for when they signed up for your newsletter. If you said you’d send company news once a month, you shouldn’t start sending promotions once a week. That will generate spam complaints and poor deliverability. Deliverability consists of all the issues involved in getting your emails delivered to the expected recipient. Unexpected content could cause poor deliverability and block your email from being delivered.
  4. Next step is to set-up your sending domains. Sending domains are used to identify you as a sender, help you build a sender reputation with ISPs for better inbox placement, and allow you to send more messages on our system. Find out more about how to set-up your sending domain here.
  5. You will also need a Template. A template defines the body of your email. It is also the place to define where substitution data will go in your emails. Find out more about creating a template here.
  6. Finally, you will need is a recipient list. Recipient lists are lists of email addresses you want your emails delivered to. Again, make sure you get opt-in permission from your recipients. You should never add people to your list who have not opted-in as this can affect your deliverability. More information on setting up recipient lists can be? found here.

You can also set-up email using SMTP. Simple Mail Transfer Protocol (SMTP) is an Internet standard for electronic mail (email) transmission. Here is a video to explain sending via SMTP:

If you are sending via SMTP or REST APIs you will need an API Key. The API key is used to authenticate you acting on behalf of your account with tools outside of SparkPost. Steps to create and API key can be found here.

?While building a mass email program can certainly be a daunting task we hope that these steps point you in the right direction. With a little elbow grease we’re sure you’ll become a full-blown email pro!?


new rules email deliverability best practices

The post How to Start Sending Mass Email appeared first on SparkPost.

Email Tips for Cannabis Companies Wed, 03 Jul 2019 13:00:58 +0000 cannabisEmail marketing may fall into an unclear green area when it comes to marketing Cannabis but SparkPost's Messaging Policy does not.

The post Email Tips for Cannabis Companies appeared first on SparkPost.


Amidst the recent expansion in legalized recreational and medical Cannabis industry, one of the biggest challenges businesses face is how to advertise and promote without violating state and federal regulations. This is especially difficult due to the fact that Cannabis is classified as a Schedule 1 substance.

Standard marketing techniques are no longer applicable due to heavily regulated advertising laws, which vary drastically in different states. Nevertheless, email marketing falls into an unclear green area when it comes to marketing Cannabis.

However, before it is possible to go into Cannabis and Email Marketing the first thing to be considered is the SparkPost messaging policies.

SparkPost’s current policies state the following:

In compliance with the Law, Customer’s use of SparkPost Services must comply with all applicable laws, rules, regulations, ordinances, and court orders of any kind of any jurisdiction applicable to Customer, SparkPost, and to any Recipient.

For the sake of simplification purpose, the use of Washington state as the state law example. Below is a simplified outline that most apply to Cannabis Email Marketing:

(2) General. All marijuana advertising and labels of useable marijuana and marijuana-infused products sold in the state of Washington may not contain any statement or illustration that:

(a) Is false or misleading;
(b) Promotes overconsumption;
(c) Represents the use of marijuana has curative or therapeutic effects;
(d) Depicts a child or other person under the legal age to consume marijuana

(5) All advertising must contain the following warnings:

(a) “This product has intoxicating effects and may be habit forming.”;
(b) “Marijuana can impair concentration, coordination, and judgment. Do not operate a vehicle or machinery under the influence of this drug.”;
(c) “There may be health risks associated with consumption of this product.”; and
(d) “For use only by adults twenty-one and older. Keep out of the reach of children.”

Based on these regulations and policies, it would seem that Cannabis businesses are extremely restricted on their ability to promote brands and products. On the other hand, there is some flexibility in this legal haze.

When speaking with our Manager of Deliverability and Compliance Operations as well as the SparkPost Legal team, the following types of Cannabis messages will be permitted on the platform:

  • Transactional Mail (receipts, order confirmations, password resets, and etc.) For a detailed explanation on what is considered transactional, please refer to the following post:
  • Political messaging on the legalities and the current climate of Cannabis regulations
  • Informational messaging about new products and/or Cannabis Strains

The exceptions to the conditions above are as follows:

  • Content being sent out from Cannabis recreational and/or medical stores will need to reviewed and approved by our SparkPost Compliance team on a case by case basis.
    • If your store is interested in becoming a SparkPost customer, please reach out to for approval
  • Messages to states where Cannabis is not legal will not be tolerated
  • Attempts to sell Cannabis or include accessible links in messages for purchasing Cannabis products in legalized and unregulated states will be reported to the respective governing authorities.

When navigating the legalities of Cannabis advertising and marketing, SparkPost is willing to work with a range of Cannabis businesses and brands, as long as said businesses and brands are able to provide engaging and legally abiding content.

*The information provided on this post does not, and is not intended to, constitute legal advice; instead, the information in this post is for general informational purposes only.

~ Amara

new rules email deliverability best practices


The post Email Tips for Cannabis Companies appeared first on SparkPost.

5 Ways to Personalize Your Next Financial Services Email Campaign Mon, 01 Jul 2019 13:00:21 +0000 financial services email campaignHere are 5 powerful ways you can personalize your next financial services email campaign beyond simply inserting someone’s first name in the subject line.

The post 5 Ways to Personalize Your Next Financial Services Email Campaign appeared first on SparkPost.


Asked by The Financial Brand for their brand’s biggest digital marketing opportunity in the coming year, optimizing the customer experience was the top choice of marketers. Email personalization is one of the best ways to improve your customers’ experience because it helps them feel like your company is speaking directly to them about things they personally care about.

However, modern email marketing requires more than simply inserting someone’s first name in a subject line and in the body of the message. Here are 5 powerful ways you can personalize your next email campaign.

1. Develop customer personas

Just as you change how you speak when addressing different people in various areas of your life, you should consider creating different ways of talking to your customers in emails. Start by segmenting your customers according to various factors, such as age, gender, location, income, and other characteristics that you know about them.

Then try to see your company through the eyes of each segment. What’s important to those people? What are the biggest obstacles they’re facing, and how can you help them solve those problems? You may want to rely on outside research to discover what your customers are likely experiencing, depending on their age, income, location, and other factors.

Each segment can be as broad or as specific as you want it to be. For example, you could slice your customer base by generational divides and talk to them that way. If you do that, keep in mind that PwC Financial Services found that while Millennials, Gen-Xers, and Baby Boomers are all concerned with saving for retirement, their secondary goals are saving for a home, getting out of debt, and ensuring financial stability, respectively.

You could then tailor your next email campaign around those secondary goals and send each generational cohort messaging that resonates with them. An easy way to sub-divide those cohorts is by their stage in the customer journey. For example, you might talk to Millennials about strategies for saving for a home different ways if they’re new to your business compared to customers who have been with you for a few years.

2. Personalize your imagery

In addition to talking to your customers in specific ways, make sure the photos and other images in your emails match those personas. That includes not just their ages (such as using photos of people in the same age bracket) but also potentially customizing your pictures by location and other factors.

For example, you can use pictures that feature prominent landmarks or notable geographic features in an area where people in a specific cohort live. Campaign Monitor ran a test with images personalized to the recipient’s country (US, UK, and Australia) vs. location-agnostic pictures and found that the former increased the email’s click-through rate by 29%.

3. Personalize your offers

Rather than using a one-size-fits-all approach to offers, such as messaging everyone on your list about a new type of account that doesn’t have any fees, try tailoring those messages to people in a more specific way. For example, using PwC Financial Services’ previously mentioned research, you could limit a special deal on a debt consolidation loan only to a Gen-X cohort.

You could also personalize offers based on past behaviors. For example, you could offer a special type of savings account to people who previously opened checking accounts, particularly those who have seen their balances dip precariously low and could use overdraft protection. Or you could put a generational spin on the offer and aim it at Millennials who want to save money to buy a home.

4. Create triggered emails based on the customer journey

In addition to creating customer personas, you should map out a customer journey that starts with the onboarding process, which is how you welcome new customers. At a minimum, you’ll want to send them a thank-you email that’s personalized based on any information they gave when signing up. For example, based on their address, you could dynamically insert the address of your company’s nearest office or branch location, or give them the contact information for an agent in their area.

In addition to creating triggered emails that alert customers to suspicious sign-in attempts, transaction problems, and other important events, you can also craft messages that are based on other kinds of behaviors. For example, if someone hasn’t logged into their account for a specific amount of time, you could send them an email that prompts them to log in. Try to give them a reason why, such as checking an account balance or viewing certain activity.

Other potential triggers include:

  • Reaching an account anniversary: Wish the customer well and perhaps add in a cross-sell or upsell based on their persona and account history.
  • Hitting a transactional threshold: Such moments might also be a good time for a cross-sell or upsell.
    Engaging customer service representatives through certain channels: Some people like an in-person experience while others prefer phone calls, email, website chats, social media messaging, and so forth. Paying attention to how and when your customers engage with your company gives you an opportunity to nudge them toward other channels if you have a reason to do so. You can also send follow-up emails to ensure that people are happy with their customer service experience.
  • Expressing interest: Maybe someone asks questions but doesn’t create an account, or they fill out a form requesting more information. That’s an opportunity to not only supply what they need but also create triggers that send emails after a certain amount of time has elapsed and they’re still not a customer. Based on what you know about them, try to personalize the message as much as possible to seal the deal and turn them into a new customer.
  • Needing a reminder: When people engage in a cyclical activity, such as providing the information needed to complete a tax return, you can create triggered reminders that prompt them to re-engage with your business. For something like a tax return, you can start sending reminders in January and keep sending them past the deadline, so you can catch the stragglers.

Paying attention to the customer journey is key because 81% of financial marketers surveyed by Adobe and eCounsultancy said that optimizing it will be “very important” over the next few years.

5. Consider who’s sending the email

One aspect of personalization that’s often overlooked is who’s sending the email. That includes not just customizing the from name and reply-to email address, but also the body of the email. Instead of sending the email from your company, it could come from a specific (but fictional) employee. That employee could vary, depending on the cohort being addressed.

HubSpot tried that technique, testing an email sent by the company versus one sent by a marketing manager. It found that the latter generated a higher click-through rate as well as more overall clicks.

~ Casey

The post 5 Ways to Personalize Your Next Financial Services Email Campaign appeared first on SparkPost.

Pride 2019 at SparkPost Fri, 28 Jun 2019 13:00:59 +0000 PrideBusiness Operations Administrator, Matthew Slasten, recaps how SparkPost celebrated Pride Month this year.

The post Pride 2019 at SparkPost appeared first on SparkPost.


To many, Pride evokes thoughts of rainbows, parades, and celebration. Even as I sit at my desk right now, I think of the rainbow flags flying on Market Street and the crowds of people that will descend on the Civic Center this weekend for the SF Pride Parade. And, I also think about what all of this means to me as an LGBTQ individual. Like many, I kept my identity hidden for most of my teenage years for fear of acceptance. Seeing a rainbow flag or any sign of support meant the world to me. And, while I’ve become comfortable with and proud of my identity over the years, it still means so much to me when I see any effort to make the LGBTQ community feel welcomed and celebrated.

As a SparkPost employee, I’ve been fortunate enough to work at a company that celebrates its LGBTQ community. This last month, we’ve hung a rainbow banner in the office, been given Pride t-shirts and pins, and had a special movie afternoon where we watched “Milk”. Our social team also created and promoted a Slide Share that gives viewers “A Brief History of Pride.”

Now to some, this may seem like a corporation taking an opportunity to promote its brand during Pride. We’ve all seen the special rainbow swag and designs that many companies are promoting. While there may be some truth in that, I’d rather not make a negative out of a positive. For many years, Pride came and went, and wasn’t cause for celebration at SparkPost. In fact, it never crossed my mind that it was something to be celebrated at the office at all. But there’s something about seeing your company take the time and the effort to make specially designed swag, hang a rainbow banner, and set aside a whole afternoon to watch a movie about a historic LGBTQ pioneer, that really makes an impact. Like those flags on Market Street or the upcoming parade, these small gestures make me feel welcome and fill me with Pride.

So thank you SparkPost for putting in that extra effort to make your LGBTQ community feel recognized and welcome!

~ Matthew

The post Pride 2019 at SparkPost appeared first on SparkPost.

What is an SPF Record? Wed, 26 Jun 2019 13:00:59 +0000 SPF RecordInterested in implementing the Sender Policy Framework (SPF) but not sure where to start? Check out our guide to learn how SPF records work.

The post What is an SPF Record? appeared first on SparkPost.


Are you interested in implementing Sender Policy Framework (SPF) but not sure where to begin? Check out our guide to learn how to get started with SPF and how SPF records work:

What is SPF?

SPF can help protect email senders and recipients from spam, spoofing, and phishing. In addition to safeguarding against email risks, properly configuring your email authentication can positively impact your deliverability. SPF is a form of email authentication that defines a way to validate that an email message was sent from an authorized mail server, in order to prevent spam and to detect forgery. SPF was introduced as a supplement to SMTP which by itself doesn’t offer any authentication mechanisms.

What is an SPF record?

SPF establishes a way for receiving mail servers to verify that an incoming email was sent from an authorized host. It works well when used in tandem with the Domain Name System (DNS). DNS takes the domain names people use to search online (like “”) and finds the corresponding Internet Protocol (IP) addresses so that internet browsers can load information.

An SPF record is included in an organization’s DNS database and is a specially-formatted version of a standard DNS TXT record. It looks something like this: ? TXT "v=spf1 ~all”

Following along from left-to-right this SPF record says that any email that claims to be from “” should be validated with SPF (

). The part of the record that is labeled
?specifies that the records for “” and “” should be included when validating email from This indicates that other domains are authorized to send on the’s behalf.? Finally,
?indicates that any other servers claiming to send mail on the domain’s behalf should be marked as questionable, and possibly fail the SPF test.

Commercial businesses sending transactional email should definitely implement at least one form of email authentication. We recommend implementing, SPF, DMARC, and DKIM for a more complete approach to authenticating your email.

Luckily, SparkPost actually handles SPF automatically— so, if you send with us all email from your account is already SPF authenticated!

~ Erica

The post What is an SPF Record? appeared first on SparkPost.

Once Upon a Time in Email Land… Mon, 24 Jun 2019 13:00:24 +0000 success storiesDirector of Customer Success, Tom Mairs, shares some of SparkPost's customers' greatest success stories using our product.

The post Once Upon a Time in Email Land… appeared first on SparkPost.


For me, as a Sales Engineer, it is all about the story. I could drone on for hours about how awesome our product is and the billions of bytes of code we wrote and the awards we’ve won, but really – who cares? Do you know what people care about? They care about how other people use it. They care about success stories and diving saves. They care about how we can make them be a hero to their peers and their customers.

People want to hear about that time we were able to predict a service outage two days before it happened using crazy data science. Or that time we identified a problem with a customer’s signup form using engagement recency charts. They want to explore how our real-time analytics data identified a failing generation node and prevented thousands of lost messages.

The SparkPost team and their customers can tell you a wide range of stories about how using the right tool can reveal interesting things you didn’t know about your own email sending practices. For 20+ years, we have been the underlying infrastructure of the email space, fueling the vast majority of Email Service Providers and high volume senders. Our visible data footprint covers 37% of the entire world’s commercial email traffic so we have definitely seen a few things.

We have seen customers leverage our flexible API Key management system to allow 3rd party fraud prevention tools to filter bad contacts without exposing access to the messaging engine. API Keys can be very granular to allow send-only or report-only functions as well as provide direct manipulation of the embedded suppression system.

Many customers have taken advantage of the real-time data webhook feed to trigger specific business automation processes like real-time list hygiene and FBL processing for CAN-SPAM compliance. This data feed is also ideal for something often referred to as “Assured Delivery” where you can reroute message to an alternate channel in the event of an initial delivery failure. Mailbox full? No problem, let’s just resend that to the alternate address we have on file.

Customers share exciting stories with us all the time about how they improved business results by doing the unexpected. A great example of this is the sender who we counseled to send LESS mail to get a better result. That may seem strange for a company whose model is to bill on volume, but our primary focus is customer success and in this case, that is what was needed. We identified which users were actually engaging with email and in turn generating revenue. Targeting only those users resulted in eliminating 70% of the outbound volume but increased their open rates by 4x and in turn resulted in higher profits and a more efficient operation.

In a similar way, we could share the story of a customer who came to us in need to migrate off another provider but only had 11 days for a full migration. Most deliverability people will tell you it takes several weeks to warm up IPs to the point where you can send any appreciable volume– so 11 days sounds like an impossible task. Yet we were able to leverage SparkPost technology and decades of experience to meet the challenge.

We would love to hear your story. If you are a SparkPost, PowerMTA, or Momentum customer, we welcome you to share your success story with us. If you have not had the pleasure of using any of our tech yet, please give us a chance to make a diving save, give you a more efficient platform, or resolve a messaging crisis. Your story awaits.

~ Tom

The post Once Upon a Time in Email Land… appeared first on SparkPost.

17 Ways to Improve Email Deliverability Fri, 21 Jun 2019 13:00:45 +0000 improve email deliverabilityHere are 17 things you can do to increase the likelihood that your email message will get into your recipients’ inboxes, so they can open, click, and engage with you and your brand.

The post 17 Ways to Improve Email Deliverability appeared first on SparkPost.

  • This blog post was originally published on 12/14/2015 and was updated on 6/21/2019

According to research from Return Path, US email reaches subscribers’ inboxes only 83% of the time!?Are you doing everything you can to ensure that your messages aren’t part of the 17% of emails that never make it to the inbox?

Check out our list of 17 deliverability best practices that can help increase the likelihood that your email message will get into your recipients’ inboxes, where hopefully they will open, click, and engage with you and your brand.

  1. Use double opt-in. Double opt-in is compliant with laws like CASL and CAN-SPAM. It generally requires that the recipient clicks on an activation email that you send. It can also set up a pattern of engagement.
  2. Make your from and subject line explicitly you and true to the message. If the message is not “from” your brand, it should be from a person at your brand. The subject line should also clearly reflect the content of the message.
  3. Segment your list. All your recipients are not alike. Segmenting your list by interest and modifying frequency accordingly can drive more engagement.
  4. Implement Sender Policy Framework. By using SPF, you provide ISPs with the?assurance you are who you say you are, making them more likely to deliver your message to the inbox.
  5. Prune your list. When it comes to your email list, more is not always better. If the recipient hasn’t engaged with you in 6 months, target them with a special message and if that doesn’t drive engagement, remove them from your list.
  6. Let someone help you avoid bouncing. Hard bounces should be removed from your list. At SparkPost, we add those to your suppression list right away so you don’t see more bounces, but it’s still up to you to remove those addresses from your list.
  7. Watch out for spam traps. Spam traps are emails created by ISPs to find spammers.
  8. Check your reputation. One tool you can use is Sender Score to find out where you stand with respect to your sending reputation.
  9. Don’t add emails from contests and giveaways. You’ll probably get multiple signups from the same email address. If you do these types of promotions, make sure you vet the resulting emails carefully before adding them to your list.
  10. Check blacklists. Make sure your organization isn’t on a list that automatically sends your emails into a black hole instead of the inbox.
  11. Consider the source. Where did you get that email address? Some sources are much more reliable than others. As a general rule, buying lists is a bad idea.
  12. Make unsubscribing very easy. If unsubscribing is difficult, in frustration, recipients may mark your email as spam as a way to stop receiving your email. If recipients cry spam, ISPs listen and you can quickly land on a blacklist.
  13. Register for feedback loops (where you can). How can you find out if a recipient is marking your email as spam? By subscribing to relevant feedback loop reports from ISPs. One notable exception is Gmail, which only sends feedback loop reports to email service providers.
  14. What’s the frequency? Pay attention to how frequently you are sending email and what kind of responses you get. Send email too often and you risk being ignored (or deleted without opening, which harms deliverability). Send too infrequently and recipients may forget about you. It’s a balancing act.
  15. Keep frequency consistent. Once you settle on a frequency, stick with it. Erratic sending patterns are considered a marker of spam.
  16. Study your metrics. Real-time analytics is the best way to drive your email marketing strategy. SparkPost offers numerous real-time reports and webhooks that you can leverage to drive engagement and improve deliverability. Pay attention to clicks and opens. If you’re having trouble with blacklisting, SparkPost can often work with you to help you get removed from those lists. And, if you’re really ready to step up your email game, be sure to check out SparkPost Signals, our brand new email intelligence platform designed to help you identify and address issues before they start impacting your business.
  17. Work to improve your open rate. Deliverability is clearly important, but it’s not the end game. You want to drive engagement, to have recipients open and click on your email. That happens with engaging content, a subject line that tantalizes followed by summary text that draws them in further.

~ Sparky

new rules email deliverability best practices

The post 17 Ways to Improve Email Deliverability appeared first on SparkPost.

5 Email Strategies MarTech Companies Need to Ditch Wed, 19 Jun 2019 13:00:58 +0000 Email Strategies MarTechRead about five email strategies MarTech companies need to scrap, eighty-six, pink-slip, kick to the curb, or otherwise get out from under ASAP.

The post 5 Email Strategies MarTech Companies Need to Ditch appeared first on SparkPost.


When it comes to email marketing strategies, plenty of very shrewd marketers make mistakes. Even, shockingly, MarTech providers.

Sometimes it’s just a matter of picking the wrong strategy in the first place. Other times, the mistake lies in sticking by a strategy that’s been successful in the past, and may still be generating results. But they’re paltry results when compared with the ROI of smarter, more up-to-date approaches.

And if your competitors are pulling ahead while you’re standing pat, those “proven” practices are doing you more harm than good.

Here, then, are five email marketing strategies that MarTech companies need to scrap, eighty-six, pink-slip, kick to the curb, or otherwise get out from under ASAP.

#1: Emailing the unengaged

To extract the most from your lists, you need to monitor engagement at a granular level. You may be sending out high-quality emails, but you’re seeing declining CTRs and open rates. What’s the problem? You’re sending to unengaged recipients – listees who haven’t interacted with any of your emails over an extended period.

“What’s the harm?” you might ask; so long as your messages aren’t being shunted to spam, you might not think it’s a cause for concern. Some senders just re-double their efforts, or re-calibrate and re-re-calibrate their messaging in an attempt to rouse some reaction.

What you’re doing, though, is simply increasing the amount of graymail you’re putting out – email that doesn’t fit the definition of spam. But over time, recipients lose interest in these mailings, and actually become more likely to flag you as spam. In fact, it’s estimated by some that up to 75% of what gets flagged are actually legitimate newsletters, notifications, or other emails recipients were once interested in getting. Now, though, they’re happy to just send them to spam, rather than go through the hassle of unsubscribing (this is another reason to have a very visible “unsubscribe” option in every email).

How to combat this? Simple: Track engagement, and exclude anyone from your active list who’s failed to engage with the last 10, 15, or number-of-your-choice emails you’ve sent. Some platforms even allow you to set this number as an automated function.

#2: Buying lists

The advent of the GDPR and CCPA may put a lot of list brokers out of business anyway since it’ll be harder for them to compile quality lists. Not to mention that just using one of their lists will mean you’re breaking the law.

In the old batch-and-blast days, though, marketers would try to stock up with “leads” generated through pretty indiscriminate mass emailings. Even today, when ABM and precise targeting is supposedly the order of the day, data vendors still shill “quality” lists of “contact” that, all things considered, are still as cold as a baked Alaska.

If you’re prospecting, the secret to identifying the right email targets is to collect and analyze the right data. What’s that entail? Capturing data from people who are specifically interested in your company or products (by tracking interactions with your website and content, for starters), then applying analytics tools (including AI/machine learning platforms) that can help give you far more accurate and predictive insights about which of them are likely to be true prospects…and what messages will succeed in engaging them.

Here’s how HubSpot does it, with a very personalized email with a smiling human face and details drawn from the prospect’s behaviors:

#3: Putting product before solution

In flighting your email messages, an important thing to remember? Always put the customer’s needs ahead of your desire to pitch the product.

We know it’s hard to resist showing off all the shiny bits, like the upgrades or new features your customer should embrace, or the really cool case study jammed full of praise-you-to-the-sky testimonials a prospect really owes it to him/herself to peruse.

But building a relationship means knowing that what they probably want, first and foremost, is answers or insights pertinent to their real “need state” – which is to find solutions to current problems or requirements. Provide relevant content and you’re on the way to a deeper relationship since this instance of content engagement gives you important data about them or their company.

Zapier does exactly that in the example below. A user has begun using one of their connectivity “Zaps,” so it’s a prime moment to offer them tutorials on how to expand their skills. ?And it’s from Wade, a co-founder – talk about service!

#4: Focusing on the title, not the role

Targeting strategies rely on segmentation to succeed, and taking that a step further, on building actionable marketing/sales personas of everyone you need to engage who’s part of the decision-making process at a prospective or current MarTech customer account.

Too often, marketers fall into the trap of relying on outdated segmentations that don’t accurately reflect how their target audience has evolved, in general, or within specific accounts. But even when segmentation is up-to-date, they make another mistake: Targeting their email messages on the basis of a person’s job title, rather than their actual role.

The responsibilities of an individual with the title “Marketing Technology Manager” may seem roughly similar company-to-company. The actual variations between what’s involved in their real jobs, and their role in the purchase or decision-making chain, though, can be significant. Company A may have a different market, different IT architecture and digital footprint, and different MarTech goals from Company B, with a different internal procurement hierarchy.

So the seemingly tailored emails you send to MarTech Manager A, who does have a deciding influence over purchases and implementation strategies within the organization, won’t necessarily resonate with MarTech Manager B, who may not.

The solution here? To do the hard work of understanding each target’s real role within the context of their organizations. Sometimes, that information can be easy to come by: Just ask them. Tell them you can service them and their company better by having a clear idea of their relationship with your product.

#5: Providing only superficial personalization

Back in 2014 (I know, it seems like a decade or two ago!), FastCompany sent out 1,000 cold emails to see what the “best practices” should be for effective cold prospecting campaigns.

The results are applicable today. Even when it comes to how you communicate with existing customers as part of your retention efforts. The big takeaway, then and now? Personalization always wins.

But “personalization” is a continuum. Merging a person’s name into an otherwise stock message is one end of it…the low end. It’s cheaper and easier, but it also fails at exploiting a golden opportunity.

Leveraging data-driven insights about their product use, behaviors and interests, the context they’re considering or using your product within, and offering up information or solutions fine-tuned to their potential needs or preferences? That’s where personalization rises to its fullest potential for driving a customer’s loyalty and expanding their lifetime value.

For MarTech providers, there’s also the buff it gives to your reputation. Delivering that level of personalization verifies you in the eyes of each customer as actually practicing what you preach.

Here’s an example of how Grammarly gets it done, using weekly email updates to give users an idea of just how much keyboard-pounding they’re up to, and ranking them against other users. It’s a pat on the back and a useful productivity digest.

~ Craig

The post 5 Email Strategies MarTech Companies Need to Ditch appeared first on SparkPost.

5 Email Missteps That FinTech Companies Need to Avoid Mon, 17 Jun 2019 13:00:04 +0000 FinTech CompaniesStudy up on five all-too-common mistakes that many FinTech companies make when it comes to email but which you should be able to easily avoid.

The post 5 Email Missteps That FinTech Companies Need to Avoid appeared first on SparkPost.


You can have the best products and services on the market, but if you don’t craft and execute a strong email strategy, your customers will likely look elsewhere. Email is still one of the most-used communication channels in the world, according to Statista, which says that 269 billion emails were sent and received daily by 3.7 billion people in 2017.

Here are 5 all-too-common mistakes that many companies make but which you should be able to easily avoid.

1. Not creating an onboarding series

It’s important to create a welcome email that brings new customers into the fold. However, making that a one-and-done experience leaves you susceptible to high customer churn rates. You’ll want to craft a series of triggered emails that guide new customers through everything they need to know about your product or service.

Here are some best practices to keep in mind:

  • Get the viewpoints of designers and/or usability experts: Colors, font sizes, icons, button placement, the amount of text, and overall design are all key elements to consider when developing an onboarding experience. Ideally, you should also have an onboarding process in an app and/or on a website, and your emails should complement that flow.
  • Consider simple incentives: Gamification is a great way to reward new users as they move through onboarding. For example, a progress bar or percentage complete can help them understand how much more they need to do and minimize frustration.
  • Create triggers tied to inactivity and other behaviors: In addition to creating triggered emails that are sent out at specific intervals, consider crafting triggered messages that are tied to specific behaviors. For example, if someone fails to complete a step in the onboarding process, create a follow-up email that’s sent after X number of days of inactivity. You can also send follow-up messages when people fail to open onboarding emails.

Make sure you kick off your onboarding series with an opt-in email, which confirms that the customer supplied the correct email address (sending messages to the wrong addresses harms your deliverability). It also serves as a “You wanted to create this account” reminder and lets you opt them in for future emails.

2. Not prioritizing security

Everyone wants to keep bad actors from accessing their company’s data, and we all know about the eye-popping costs of phishing, spear fishing, and spoofing attacks on employees’ email accounts. However, it’s also important to consider the damage done to brand trust when consumers receive malicious emails purportedly from companies they’ve done business with, or might do business with.

That’s why you should spend the resources to set up three free email security standards that can help stop spammers from impersonating your company, as well as alert you to such efforts.

Step 1: Implement SPF (Sender Policy Framework)

SPF is an email authentication standard that defines a way to validate that an email was sent from an authorized mail server. It was designed to supplement the SMTP (Simple Mail Transfer Protocol) protocol that’s used to send email because SMTP doesn’t include any authentication mechanisms.

SPF also piggybacks on the well-established Domain Name System (DNS) that maps web server names to IP (Internet Protocol) addresses. It’s a standard TXT file that resides in your domain’s overall DNS records and defines your authorized mail servers. Inbound mail servers use that file to compare the IP addresses of email senders with those authorized mail servers. The SPF record tells those servers how to handle messages that fail the comparison.

Step 2: Create a DKIM (DomainKeys Identified Mail) Signature

DKIM adds a digital signature to the headers of an email message, allowing an incoming mail server to validate it against a public cryptographic key in the sending organization’s DNS records. While SPF defines the mail servers that can send messages on behalf of your domain, it doesn’t offer a mechanism to verify whether the message headers or body have been altered or forged while in transit. That’s why you want to use DKIM too.

Step 3: Add DMARC to the Foundation Created by SPF and DKIM

DMARC (Domain-based Message Authentication, Reporting, and Conformance) allows you to define your email authentication practices and provide instructions to inbound mail servers for enforcing them. It wraps around the SPF and DKIM authentication standards to enable a complete email sending solution.

Since neither SPF nor DKIM alert you to malicious messages that managed to bypass both safeguards, DMARC gives you that information so you can act on it.

3. Not developing good email habits

In addition to watching for bad actors who are trying to impersonate your company, you want to ensure that your emails reach people’s inboxes. You do that by maintaining a strong sender reputation, which tells mail providers like Gmail whether they should put your emails straight into users’ inboxes, mark them as promotional or spam, or even outright reject them.

You can keep develop a good sender reputation by:

  • Keeping people engaged: The more people open your emails and click through from them, the higher your engagement rate will be. Use subject lines that are short and to the point, and ensure your emails are mobile responsive, which means they automatically adapt to the device screens they’re viewed on.
  • Creating, authenticating, and warming up sending domains: Use different sub-domains for different types of email and warm up new ones by methodically adding email volume week by week. Inbound mail servers want to see consistent volume and frequency.
  • Exercising good list maintenance: Immediately remove email addresses that hard bounce, but keep an eye on soft bounces too and suppress the addresses that keep returning that result. Pay attention to engagement rates too: consider removing people who never engage with your emails, or send them a “Would you like to stay on our list?” message every so often.

In addition, peruse the details of the CAN-SPAM law in the United States, GDPR in the European Union, and other important pieces of legislation. Note that GDPR can affect your company even if it’s not based in the EU.

4. Not considering the little details

There are several elements of email sending that are easy to overlook, such as:

  • Preheader text: This is the text that email clients, including all mobile ones, display below the subject line. If you don’t specify it, recipients typically see the first several words of the email, which isn’t optimal. Use the preheader to complement the subject line and give people another incentive to open your message.
  • The footer: That’s where you want to include any legally required language, as well as an unsubscribe link. Don’t make people hunt for the unsubscribe link – you’ll risk them marking your email as spam so they can get off your list, and that will hurt your sender reputation.
  • Opt down preferences: When people click the unsubscribe link, take them to an email preference center that lets them choose less frequent emails, or different types of mailings. That way they can remain on your list.

5. Not choosing a reliable email service provider

Selecting the right email service provider (ESP) can pay dividends for years to come. Choose wisely, though, because it can be costly and time-consuming to switch to another provider. Here are some questions to consider:

  • Are they cloud-based? On-premise solutions are quickly becoming outdated for all but the largest organizations. A solid cloud-based ESP can quickly scale to meet sudden extra capacity needs.
  • What kind of support do they offer? Some ESPs assume that knowledge base articles and an online forum are enough, but that doesn’t work when a critical problem brings your business to a standstill and you need to get someone on the phone.
  • Do they incorporate security by design? In addition to supporting SPF, DKIM, and DMARC, they should provide security at the email content, protocol, and network layers. And you can’t go wrong if they run on a rock-solid cloud platform like Amazon Web Services.
  • Can they ensure your emails will hit inboxes? An email shouldn’t be considered delivered if it hits a spam trap, but some ESPs look at it that way. They should be able to optimize your deliverability rates by adjusting your email sending based on real-time feedback from email providers.
  • Do they offer a strong API (application programming interface)? They should support message injection and sending protocols including SMTP, REST, SMPP and MM7, as well as data integration protocols including ODBC, LDAP and PostgresSQL.
  • Do they supply real-time data and analytics? A good ESP will not only supply send, open, click, bounces, and other metrics in real-time but also give you access to a detailed event history for each message.

You can’t go wrong if you decide to go with SparkPost, which is a cloud-based ESP that runs on Amazon Web Services, offers 98% deliverability rates, features a RESTful API and other key protocols, and gives you all the real-time analytics you need.

~ Casey

The post 5 Email Missteps That FinTech Companies Need to Avoid appeared first on SparkPost.

5 Ways to Personalize your Next MarTech Email Campaign Fri, 14 Jun 2019 13:00:50 +0000 next MarTech email campaignRead up on our tips for personalizing your next MarTech email campaign, and how these strategies can help you nurture your relationship with your customer.

The post 5 Ways to Personalize your Next MarTech Email Campaign appeared first on SparkPost.


For a MarTech provider, initial engagement is obviously just the start of the customer’s journey – and of a relationship that ought to bear profitable fruit for both parties for a long time to come. Nurturing that relationship with personalized emails is pretty much a cornerstone of that future success.

In a previous post, we pointed at five MarTech providers who were doing an exceptional job of self-marketing to prospects and customers. You can bet each of them considers personalization to be central. That’s not in the least because being on the receiving end of personalization is ever more important to buyers, too. As one study shows, there’s a primary reason many buyers have limited engagement with B2B vendors: They’re being sent too much irrelevant content.

So in using email marketing to support your MarTech product, “personalization” has to go well beyond just knowing your customer’s name and title. Messages need to be relevant and contextualized so they – and your product – show immediate value to the recipient.

Triggered emails

They’re the bedrock of marketing automation nowadays, and they’re an excellent way to personalize your campaigns. By responding to specific customer actions with messaging that’s punctual and suitable for the situation, you can open up new opportunities.

The number and types of triggers you activate against are nearly endless: content downloads or browsing behavior on your website, for instance; registration for a webinar or user event; the inception or conclusion of a new campaign using your product; making a core update, or adding a plugin or other new functionality.

HubSpot does a good job of this in the example below, where a user’s behavior has triggered a message that will, hopefully, catch them at a moment when their interest in researching social media marketing may be a clue they’re interested in launching a campaign of their own, or upgrading the efforts they’re already making.

Show you know their stack

It’s also vital to demonstrate you know what type of tech stack a customer or prospect is working with, so you’re able to grasp what that says about their marketing objectives and personalize email messaging accordingly. Are they invested in AI? Are they transitioning to ABM? What CRM platform are they relying on? Do they leverage a business intelligence tool?

Understanding a customer’s tech stack gives a MarTech campaign planner the opportunity to demonstrate how their particular offering fits into it, and how it complements or enhances the customer’s existing components. So when you release upgrades that help with cross-platform integration with that customer’s existing solutions, you can make sure they know you’re always improving your own product on their behalf.

When it comes to taking a similar approach in prospecting for new business, or onboarding a new customer without having to grill them about their tech stack, there are new tools that can help do the job. Notablist, for instance, analyzes the email campaigns sent out by marketers to provide a window into what technologies are being used by their brands.

P.S. Notablist uses the tagline “Sending Insights for Closers” — you can easily picture Alec Baldwin spitting it out in Glengarry Glen Ross, right?

Get in sync with their business cycles

One key to personalization is “right time, right message,” and in maintaining engagement with your customers, it’s good to know their business, marketing, and sales cycles. Why? Because by doing so, you’re able to make your messaging more timely and relevant.

If you’re trying to prompt them to use your platform or upgrade to new features, being able to anticipate a marketing cycle where those might be useful means you can hit them with reminders or announcements that play perfectly into their upcoming campaigns.

You can ask for a sneak peek at their marketing/sales calendar, of course, but it’s not always going to be available, or gathering that data is too manually intensive. Here, too, there are analytics tools that can automate the gleaning of insight: Moat is one. By tracking where and how a marketer is investing its marketing resources, in what channels, and the length and breadth of marketing cycles, you’re able to plan your campaigns appropriately.

Encourage and educate

You can put the “personal” in “personalization” by putting a human face on your interactions with customers. They’re investing good money – and their professional standing – in your product, so you should help them along the way by recognizing them reaching individual milestones or other trigger points with pats-on-the-back, by offering tutorials or other skills-building content, or even by giving “power users” exclusive access to new feature demos and the like.

The triggers can revolve around their use of the product, completing tutorials, gaining proficiency ratings, trying out new features, participating in user groups, or any other accomplishments that they can feel good about – and give you a chance to deepen your bond with that customer.

Here’s an example of offering up kudos on reaching a milestone from engagement platform Sleeknote that’s, unsurprisingly, very engaging – particularly since it hails from the CEO, who sounds like a fun guy to hang with.

Let them provide some personalizing

Customers love empowerment, so one way to deliver that – and to help you personalize your relationship with them – is to judiciously give them the power of choice in responding to your campaign.

Newsletters are a classic tool for building a customer profile by tracking the links they click on in each issue, as their choices provide solid data about their interests and needs. Yet there are even more imaginative and expansive ways to accomplish that, as shown in this ProductPlan onboarding email.

ProductPlan isn’t a MarTech provider (they offer roadmap visualization tools), but the idea here translates easily. They’re giving the new customer the power to choose where and how they want to start their onboarding process.

Those choices, naturally, can help a marketer further customize future messages or complete campaigns/tracks. In the moment, though, the customer’s decisions let you direct them to personalized content you can segment as much as necessary to give them a more satisfying engagement.

~ Craig

The post 5 Ways to Personalize your Next MarTech Email Campaign appeared first on SparkPost.

The Five Email Love Languages Wed, 12 Jun 2019 13:00:55 +0000 email love languagesExplore how to create a multifaceted email program that allows you to communicate with customers in their respective email love languages.

The post The Five Email Love Languages appeared first on SparkPost.


If you’re familiar with Gary Chapman’s 1992 tour de force, The Five Love Languages: How to Express Heartfelt Commitment to Your Mate, then you know that a lifetime of love can be easily attained through reading a self-help book. In his masterwork, Chapman outlines the 5 types of communication necessary to create a love that lasts. They are: Words of Affirmation, Acts of Service, Receiving Gifts, Quality Time, and Physical Touch. While strong and open communication of all sorts can certainly be used towards building a loving relationship with a significant other, these love languages obviously parlay themselves into how to communicate with someone even more important than your soulmate…your customer!

Check out how you can apply the five love languages as communication and engagement strategies with your customers:

Words of Affirmation: Welcome and Onboarding Emails

Your customers deserve to know that they’ve made a great choice by signing up for your product or service. In fact, Stripe explains that welcome and onboarding emails can drive three times the transaction and revenue per email than any other promotional email! That’s right, welcome emails not only serve as digital words of affirmation to your customer but can also do wonders for your bottom line!

Acts of Service: Triggered Email

When customers make payments to your company or updates to their accounts, it’s absolutely imperative that they are notified of the change via email. Triggered email does just that! A triggered email is a timely, relevant, and individualized email automatically sent in response to an action taken by a recipient, or to a data point about that recipient. These sorts of emails help to serve the customer by notifying the customer of changes before they even ask!

Receiving Gifts: Deals, Deals, Deals!

Customers that opt-in to your emails deserve to be recognized for their loyalty! One of the best ways to communicate your gratitude to devoted customers is by sending them marketing emails that contain discount codes and free gifts! Not only do consumers love free stuff, but these sorts of rewards can help keep your clientele engaged with your email messages and create positive buzz about your brand.

Quality Time: Sending Messages at the Right Time

When this love language is applied to a lover or significant other, it generally means spending A LOT of time with that person. However, when it comes to spending time with your customer it needs to be done on their terms, at a time that is convenient for them. This means that when sending marketing or triggered messages, the content needs to be timely to the customer. There’s nothing worse than receiving a marketing email with a discount code for a sale that has already ended or a “Forgot My Password” email hours after the fact. By focusing on sending your messages at the right time, you can build trust with your customer and create a frictionless customer experience.

Physical Touch: Don’t

Okay, my stretch of a metaphor ends here. Please don’t touch your customers.

Keeping these five strategies in mind can help you create a multifaceted email program where you are able to communicate with customers in their own email love language.

~ Erica

P.S. Interested in finding out which love language you speak? Check out this quiz!

The post The Five Email Love Languages appeared first on SparkPost.

[Webinar] Retail Banking: How to Optimize the Customer Deposit Lifecycle Mon, 10 Jun 2019 13:00:09 +0000 retail bankingJoin us on June 20th at 2:00 PM EDT, for a live discussion of the importance of personalization in the retail banking customer journey.

The post [Webinar] Retail Banking: How to Optimize the Customer Deposit Lifecycle appeared first on SparkPost.


It’s not the same bank your parents used – digital is a game changer

Thanks to the digital world, there are new ways to market to today’s financial services customers. New marketing technology presents challenges and opportunities in how we engage with customers and create more personalized experiences, tailored to their needs.

With technology solutions like Novantas and SparkPost, you can use advanced segmentation to learn the value derived from lifetime activities and use analytics and metrics to optimize the customer’s lifecycle with your retail bank, creating a personalized banking experience that results in customer loyalty.

Pump up your Marketing Game

The game has changed. Retail banks used to wait for the customers to come to them.

“Did you know that since 2015, the impact of the branch on new-to-bank checking acquisition declined by roughly 10% while marketing’s impact on the same category has increased 10% and is still growing?” – Hank Israel, director, Novantas

Now, banks need to reach out to use marketing and MarTech acquisition tools to build their clientele. Marketing spend is on the rise.

The Right Marketing Tools Can Set You Apart from your Competition

According to Acquisition IQ Insights, the top priority for many banks will be getting the data and marketing technology to help them gain insights into what consumers want from their bank. Then, they can build it with personalized programs that fit their needs. Analytics and data show the ‘who’ based on engagement and refining those customer lifecycles, allowing the banks to deliver a more personal and continuous journey with the customer.

Novantas offers a range of analytically oriented solutions for banks: pricing, risk, distribution analysis, product development, complemented by personalization, segmentation, and strategy implementation expertise – tools to help them figure out who to target and who to say what to.

Add to that, SparkPost, the #1 Predictive Email Intelligence Platform which unifies email deliverability and email analytics and you are building the right set of tools.

Register for the Webinar to Learn More

Marketing has become a dominant force for revenue growth in the battle for retail bank relationships. As consumer preferences continue to shift rapidly to digital channels, there is both a great challenge and opportunity to create a customer journey that is more personalized and engaging.

In this joint webinar from SparkPost and Novantas, we will explore the evolution to customer-level treatments within retail banking, the challenges of current processes, and how advanced segmentation can be applied to optimize the impact of your marketing efforts in customer acquisition.

Join speakers Tom Mairs, Director of Customer Success at SparkPost and Hank Israel, Director, Novantas in an interactive conversation about:

  • A customer case study illustrating best practices one customer used to enhance engagement
  • The importance of personalization and analytics to highlight data and offer health score
  • How to benchmark your campaigns and marketing spend across others in the industry

Register today!

~ Erica

The post [Webinar] Retail Banking: How to Optimize the Customer Deposit Lifecycle appeared first on SparkPost.

AMP for Email: Coming Soon to an Inbox Near You Fri, 07 Jun 2019 13:00:52 +0000 Google I/O 2019Technical Product Manager, Isaac Kim, talks about his experience presenting on AMP for Email at Google I/O 2019 and what he covered during his presentation.

The post AMP for Email: Coming Soon to an Inbox Near You appeared first on SparkPost.


Recap at Google I/O

On May 8th, Aakash Sahney, Filip Stanis and I had the opportunity to talk about AMP for Email and what’s possible in email when up-to-date content, quick actions, and interactivity are added through live implementations and demos. ?As a first-time Google I/O attendee, it was amazing to see the sheer number of developers, Google enthusiasts, and people enthusiastic about being ethically responsible with their data footprint – all converged together for three days. During our AMP email office hours, it was an awesome experience getting to talk with so many people passionate about email and excited about what can be possible with AMP email.


Throughout the forty minute session, we covered various topics, including what AMP email is (0:25), how to build an AMP email (14:12), and how to scale an AMP email for mass send (32:06).

What’s New with AMP Email?

The first big announcement is that Gmail lifted the same-zone DNS requirements for AMP emails, meaning that

? and
?can now use any HTTPS endpoint that has the correct CORS headers. Previously, the HTTPS endpoint was required to have alignment with the sending domain used. Otherwise, the AMP content would break and only the HTML or Text version of the email would render in the inbox. ?This update makes it easier for developers to quickly draft, test, and validate using Gmail’s AMP for Email Playground. Although the same-zone DNS requirements have been lifted, don’t forget to meet the following conditions for your AMP email to be delivered successfully:

  • Meet the AMP for Email security requirements
  • Email must contain a fallback HTML (text/html) or plain text (text/plain) in addition to the
  • AMPHTML MIME part (text/x-amp-html). The appropriate fallback version is displayed when the AMP part cannot be displayed
  • Must use valid AMP content in the AMP MIME part
  • Include the AMP MIME part before the HTML MIME part
  • The AMP MIME part must be smaller than 100KB

The second big announcement is that, in early June 2019, the Gmail engineering team will begin enabling AMP email on mobile devices (Gmail app for Android and Gmail app for iOS). The release will be gradually rolled out to all users over the few weeks after this date. No further action is required to enable recipients to receive AMP emails. For email marketers, this should be music to the ears! According to Litmus, mobile opens accounted for 46% of all email opens, followed by webmail opens at 35%, and desktop opens at 18%. With AMP email making a positive impact on engagement with desktop opens, I can’t wait to see the engagement uplift with the rollout to mobile devices!

Stay Tuned – Exciting Features to Come!

As announced at the end of the Google I/O presentation, we at SparkPost are cooking up a lot of really great features to make creating AMP emails manageable and more intuitive. Without giving too much away, keep an eye out about our new template side-by-side code editor! Get started with AMP email on SparkPost, and if you ever have feedback, I’d love to hear it, so please share!


The post AMP for Email: Coming Soon to an Inbox Near You appeared first on SparkPost.

Deliverability: Half Art and Half Science Wed, 05 Jun 2019 13:00:33 +0000 half art and half scienceOur SVP of Deliverability Strategy, Kate Nowrouzi, explains why deliverability is half art and half science and how to get emails into the inbox in 2019.

The post Deliverability: Half Art and Half Science appeared first on SparkPost.


Deliverability is half art, half science. The art part is where creativity, relevancy, and frequency come into play. The science part is how well your infrastructure is set up. This varies from proper authentication (SPF, DKIM, DMARC) to domain alignment in the header (MailFrom, d=domain, FromAddress). The science part is the easy one– most popular ESPs have the science part down. The challenging part is the art of deliverability.

Today’s definition of email marketing is different than what it was 10 years ago. The batch and blast days have shifted to triggered messaging. Still, email remains one of the best channels for personal communication and continues to be a great way for brands to increase their marketing ROI. Many successful brands exclusively send personalized messages to their subscribers, and as emails that are not personalized may end up in the ISP’s spam folder. The one-to-many campaign days are long over now.

Personalization makes people feel special. When customers know that they matter, they’re more likely to engage with an email. And, if you can make note of this type of customer behavior, you can easily modify your future campaigns for greater success.

It is very important to remove inactive users from your mailing list. Inactive has a different definition in each industry, it could be 30 days for one company while it could be 12 months for another. If someone has not opened or clicked your mailing in 12 months, it is best to remove them from your future mailings.

Major ISPs such as Gmail and Yahoo take engagement into consideration for inbox placement. At SparkPost we encourage our customers to segment their traffic based on engagement on separate IPs/ domains/ sub-domains and into 3 groups:

  • Active (opens in less than 90 days)
  • Semi-active (90-180 days engagement)
  • Non-engaged (opens in 6-12 months)

If you have chosen a solid ESP and pay close attention to how customers interact with your emails, you will rock 2019 and beyond.

Happy Delivering!

~ Kate

new rules email deliverability best practices

The post Deliverability: Half Art and Half Science appeared first on SparkPost.

FinTech Email Onboarding: Are You Doing All You Can With Your Campaigns? Mon, 03 Jun 2019 13:00:13 +0000 fintech email onboardingTake a look at some of the biggest challenges of building a FinTech email onboarding program and best practices to address those challenges.

The post FinTech Email Onboarding: Are You Doing All You Can With Your Campaigns? appeared first on SparkPost.


There’s no denying that financial technology – fintech – is booming these days.

Just last year, multiple fintech companies added billions in both revenue and funding, and analysts are nothing but positive about the future. With their high growth potential and investors’ hunger for disruptive innovation, Goldman Sachs estimates that fintech startups will swipe $4.7 trillion in revenue and $450 billion in profit from traditional financial services companies.

There’s no denying the future looks bright. But even as they take off, they face many of the same challenges as their unsexy brethren when it comes to marketing and growth. Like how to optimize their use of email, especially when it comes to mounting successful onboarding campaigns.

As fintech provider Stripe explains, welcome emails are important. So important, in fact, that they can drive three times the transaction and revenue per email than other promotional emails. That’s a substantial chunk of future revenue, so maximizing onboarding is vital.

With that in mind, let’s look at a few of the biggest challenges fintech companies face in doing onboarding, and the best practices that can help onboarding emails overcome them.

Drip them in!

Onboarding shouldn’t just be a one-shot email drop, especially if you’re trying to acclimate a new user to using a fintech solution’s features (and making upgrades). A classic example from the brick-and-mortar banking world that still proves a good point: Armed Forces Bank elected to experiment with doing a series of onboarding emails, six in all, in lieu of just one.

When they sent out the series with timing that accommodated the schedules of their customers – military servicepeople – they saw a 40% lift in new savings accounts, versus those who only got a single onboarding email. And these customers also increased their account balances and kept more of them open.

This onboarding “drip” approach will work in fintech, too. Why? Because you’re gradually building a relationship with the user, and showing respect for their life and its demands. Earning that respect earns you the chance to send them more messages.

The lesson? Extending the messaging and gradually growing a relationship with users can drive stronger business results compared to a single email.

That’s why fintechs like PayPal make onboarding a journey, not a blip, as you can see in the select emails below. Each new message puts extra reasons to use PayPal in front of the user, educating over time instead of overwhelming all at once.

Be sensitive and authentic

It’s no secret that finance can be a touchy subject with plenty of people.

According to a recent survey of over 1,000 U.S. adults, 85% of us are sometimes stressed about money, while a whopping 30% of Americans admit they’re constantly stressed about money. You’d think they’d jump at any chance of alleviating this stress. But the truth is more nuanced.

According to Wells Fargo, 44% of Americans felt personal finances are the single most challenging topic for them to discuss with others. With such emotion and insecurity being attached to the very word ‘finance’, it can be hard for a marketer to make a good first impression.

So your first order of business is to make your recipient feel comfortable with your message. While constructing your onboarding email, it’s important to bear these sensitivities in mind. Expressing your thanks for them signing up with you is the first order of business, but avoid getting treacly or falsely sentimental about it.

If they’ve signed on with you, they probably responded to branding and key messages that you ought to follow through on. GoBank takes a wry, cut-to-the-chase approach with the thank-you message below, which aligns with their positioning as the oh-so-friendly provider who’s going to defeat fears about how to manage your money by making banking fun! Welcome to the party!

Make it relatable

While it may be a misconception, many people view “finance” as synonymous with “boring” and “complicated.” It’s your job to prove otherwise.

Technical jargon and detailed explanations can exhaust the reader, or drive them to simply delete your email and move on. Or, worse yet, force a change of heart as they consign you to the Spam folder and delete the app. While it may be tough, coming up with creative ways to make the onboarding experience energizing and motivating, not deadly dull, are critical.

Take another look at the GoBank example above. Or this Facebook ad by Wealthsimple. While it’s not an email, the idea is the same – they’re targeting by customer segment.

The ads feature an influencer from a popular TV show, but with an angle that’s relatable and appealing for its intended audience. It’s built around a personal anecdote the target can understand, not any kind of a hard sell.

Make it visual

Another good way to stand out from the crowd? Including images in your emails that give your reader a graphic idea of what they’re signing up for. 65% of the population are visual learners, so it’s worth playing to this.

Rather than communicating via copy, offer images that tell the story – a visualized walkthrough on how to use your app, for instance. This is particularly important when you consider that over half of us access our email via mobile devices. Storytelling via good graphic design should take precedence over “wall-of-text” copy they have scarce time – or inclination – to wade through anyway.

This clean and simple-to-understand email from ExpenseIt does exactly that, and its own clarity reminds them why they wanted the app in the first place: Because of its ease of use.

Excite them early about using the product

Stoke their early enthusiasm for your product by building a few early – and surprising – messages into your onboarding flow that spotlight the product’s functionality. Send a hearty “congratulations!” when they first try out a new feature, for instance, and add pageantry and flair to even your most mundane, baseline functions. In short, the gamification that makes apps appealing to users should extend into your emails.

See what Credit Karma does in the notification below? As a user, of course you’re using the platform to keep track of – and improve, one hopes – your credit score. Credit Karma makes a big deal out of the fact the user’s score has gone up with this triggered alert, and drives them to check to see whether or not they can get a loan approval for that superyacht (actually, a 2016 Camry) they’ve got their eye on.

Another version of this tactic? Send them actual rewards for using features, like FREE! upgrades or promotional incentives. Remember, you want them as fully engaged as possible as early and often as possible.

Remind them they’re missed

If there’s a hiccup in their onboarding flow, or they stop using your product, never let them go without a winback message of some sort. It never hurts to send them a gentle, or funny, or even urgent reminder that they’re a valued user and you’d love to see them back in the fold, as Simple did in the message below.

Mint are experts at onboarding, and their re-engagement message to delinquent users is no exception. The subject line it uses? “We miss you already.” Nothing like tugging at the heartstrings while also reminding people of the pragmatic reasons they were interested in you in the first place.

And if all else fails, there’s that other carrot you can offer– incentives to come back that take the form of discounts, free upgrades, or other lures.

Get on board more effective onboarding

Email is a powerful component in the onboarding flow, and a natural complement to in-app notifications and SMS messaging. The best practices we’ve just walked through are just cornerstones for a more customized, fine-tuned approach to building strong bonds with a user base.

But getting the blocking-and-tackling right first is essential. Only then can a fintech marketer set itself up for further success by optimizing future campaigns.

~ Casey

The post FinTech Email Onboarding: Are You Doing All You Can With Your Campaigns? appeared first on SparkPost.

5 Email Tips Insurance Providers Should Keep in Mind Fri, 31 May 2019 13:00:28 +0000 insurance providersRead up on five email best practices insurance providers should keep in mind when building an email strategy to communicate with customers.

The post 5 Email Tips Insurance Providers Should Keep in Mind appeared first on SparkPost.


Like many industries, insurance has moved away from face-to-face interactions and has become a business where many transactions are handled online. However, email remains a key channel for activity, as evidenced by email marketing’s strong ROI of 42:1 on average, according to Litmus’ 2019 State of Email Survey.

Here are 5 tips to keep in mind when building an email strategy for your insurance business.

1. Use triggered and transactional emails to keep customers engaged

Insurance may be a “set it and forget it” part of people’s lives, but you can still use email to maintain a relationship with customers and earn their trust. Triggered and transactional emails are a great way to do that.

  • Triggered emails alert customers to events, such as suspicious log-in attempts, upcoming due dates for premiums and other payments, and monthly reports.
  • Transactional emails are sent in response to customers’ actions, such as premium payments, claim initiations, new account creations, and password resets.

You should set up both types of emails. While many of them aren’t useful for marketing purposes – customers don’t want to be sold on getting another policy while dealing with a claim or a password reset – monthly reports are one kind of triggered email that you can bundle with additional information, such as related insurance products that you offer.

You can also use monthly reports to give customers useful information that’s not sales-related but which can build trust. For example, you can offer seasonal maintenance tips to people with homeowners insurance policies. Doing so helps make your emails more valuable and can increase engagement rates, which is useful for building a positive sender reputation with email providers.

And don’t forget to set a regular reminder to review all your triggered and transactional emails to ensure they’re still current. That review should include everything from the types of policies you offer to the fine print you need to put at the bottom of every message.

2. Give a warm welcome to new customers

According to Campaign Monitor, welcome emails have a 50% open rate, which makes them 86% more effective than other emails sent to customers. That’s why a welcome email should be the first transactional message you send to new customers. Some things to keep in mind:

  • Forget sales pitches: Welcome new customers in a friendly, straightforward way. Keep the message as simple as possible and don’t try to do any upselling or cross-selling in the email – that’s not an optimal way to build trust.
  • Set expectations: Let people know how often they’ll hear from your company, and don’t try to hide the mandatory unsubscribe link at the bottom of the email. You can always offer some options on your unsubscribe page, so people can choose to stay on your list but hear from you less often.
  • Consider multiple welcome emails: Many companies like to build an onboarding experience that walks new customers through their products or services. You might want to do the same, especially for complex types of insurance. You can also use emails after the first one to let new customers know what else you have to offer.
  • Keep it short: Don’t use a welcome email to dump a lot of little details on new customers. Use your website for hosting deep dives into policy features and include a relevant link in the welcome email for customers who want to learn more.

3. Keep an eye on security and compliance regulations

The U.S. insurance industry operates in a fragmented regulatory environment that’s handled mostly at the state level, so it’s important to be aware of which laws affect how you email your customers. There’s likely some fine print that needs to be at the bottom of every message, and you should take care to keep sensitive personal information out of emails.

In addition, you’ll want to ensure your emails are in compliance with the federal CAN-SPAM law in the United States as well as GDPR, which can affect businesses based outside Europe. And don’t forget to do regular email list maintenance: honor unsubscribe requests immediately, and remove addresses that bounce as well as ones that have stopped engaging with you.

You should also be aware of three free security standards that can help ensure your messages are delivered to your customers’ in boxes and you’re notified about any suspicious messages that are sent to spam folders or quarantined.

  • Sender Policy Framework (SPF) enables mailbox providers to verify that an incoming message was sent from a host IP authorized by the sender’s domain administrators.
  • DomainKeys Authenticated Mail (DKIM) uses a private key to create a unique digital signature for an email’s header and content. The key is added to the message’s header and validated against a public key in the sender’s DNS records.
  • Domain-based Message Authentication, Reporting, and Conformance (DMARC) enables a company to publish their authentication practices, advise receivers on how to treat messages that don’t validate against SPF and DKIM, and to request that notifications be sent to the business when a mailbox provider encounters non-authenticated messages.

When you implement those three standards in unison, you can dramatically reduce the likelihood that a bad actor will successfully impersonate your company in a phishing email and compromise some of your customers’ accounts.

4. Segment your email list

Email list segmentation involves splitting your customer list into sub-lists based on different attributes. Doing so lets you send more targeted messages to those segments, such as offering a bundled discount on homeowners insurance to people who have vehicle policies. You can vary your imagery and text by segment too, such as using lifestyle photos that match customers’ ages and speaking to them in different ways.

Segmentation can be a powerful way to drive email performance:

  • Revenues can increase by 781% (Jupiter Research)
  • Average click-through rate was 12% higher for emails sent to segmented lists, according to a HubSpot analysis

There are several ways to segment your email list, including but not limited to:

  • Customers’ ages (insurance needs can vary by age)
  • What your customers own, such as homes, cars, boats, and so forth
  • Marital and/or family status
  • Types of insurance policies they have with you (this one and the previous two items can be used in tandem for upselling and cross-selling)
  • How long they’ve been customers (useful for offering special deals for long-time policy holders, or simply thanking them for their loyalty)
  • How much they spend per month or year (helpful for ROI calculations for different segments)
  • How they’ve engaged with your emails in the past (for example, you might want to try a different strategy with people who typically open your emails but don’t click through)
  • Lapsed customers (you should develop a strategy for bringing them back)
  • Sales cycle stage (it can be helpful to create a segment for sales prospects who haven’t become paying customers yet)

You can conduct surveys to get more information about your customers, if you don’t have enough data to create useful segments.

5. Drive healthy open and click-through rates with personalized messaging and strong content

First name personalization is fine, but that’s just a start. You can rely on other kinds of personalization to engage customers too, such as:

  • The types of policies they have
  • Their location (helpful for also including the contact information for your nearest office)
  • Payment acknowledgements (“Thanks for your premium payment on [insert date].”)
  • Their interactions with you (“Thanks for your [phone call/email/letter] to our office last week.”)

Next, pair your personalization with strong content. Subject lines should be simple – try including at least one power word to drive the kind of emotion you want to convey. It can be helpful to think about your subject lines as if they’re headlines, like you’d see on a website. Copyblogger has a useful e-book about writing magnetic headlines, which you can apply to subject lines.

You should complement the subject line with your preheader, which is the text that email clients, including nearly all mobile ones, display below the subject line. If you don’t specify a preheader, the recipient will typically see the first several words of the email, which could be something unhelpful like, “To view this email in a web browser, click here.” Your preheader should offer people an additional incentive to click to open.

And don’t neglect the “from” address and name. Avoid a generic “no-reply@” address that uses the name “Insurance Policy” or something similar. Use a name that makes your customers feel like someone is reaching out to them personally, and use a reply-to address that’s functional and sends the message somewhere useful, such as the customer’s CRM record. Even if you don’t want people to reply to your emails, some will try anyway, so it can be helpful to capture what they have to say.

Finally, prompt the action you want with the body of your email. Make sure all your emails are mobile responsive, which means they’ll automatically adapt to the devices used by your recipients, whether they’re on small-screen phones or computers with widescreen displays. The text, image sizes, and layout will adjust on the fly to offer the best possible experience.

Finally, consider that at least 50% of emails were opened on mobile devices in 2018, according to Campaign Monitor, so in addition to a responsive layout, make sure you use short pieces of text and as many bullet points as you can. Try to deliver one key message per email and include a clear CTA button that indicates what you want people to do, such as “Pay My Premium” or “View My Monthly Report.” Here’s a trick: Say “I want to…” when writing your CTA text to consider it from your customers’ point-of-view.

~ Casey

The post 5 Email Tips Insurance Providers Should Keep in Mind appeared first on SparkPost.

7 Types of Fintech Email Notifications Wed, 29 May 2019 13:00:33 +0000 Fintech email notificationsDiscover the 7 types of Fintech email notifications companies use to communicate and build relationships with their customers.

The post 7 Types of Fintech Email Notifications appeared first on SparkPost.


Financial technology providers are right at the forefront of finding relevant ways to deploy transactional and triggered email. ?That only makes sense, since they’re in constant search of new growth surfaces.

The best of their efforts combine a great grasp of what constitutes “customer service” with a keen understanding of customer psychology. Many people get anxious when it comes to dealing with finances, and the seven examples we’ll share below are each crafted to make the customer experience warmer and more personalized, giving them the sense that they’re the ones in control of the relationship.

And each plays its part in delivering a well-designed customer experience that has continuity and clarity for the customer. As our own Brent Sleeper recently noted, that’s key to making customer engagement a happy place – and not a source of annoyance.

Account Balance Alerts

For users of basic banking services – that checking account or credit/debit card, for instance – it’s always good to be on top of their balances. So using email alerts, triggered by events like getting too close to a credit limit or an overdraft, is a service they appreciate.

The DISCOVER example below from a few years ago is a classic example of how to do this perfectly. To start off, the subject line makes it totally clear what the message is about – and even reminds the customer that they set the alert up in the first place.

In a subtle touch, the pitch for the mobile app is at the end of the message – not intrusive, but a logical place to set this call-to-action to the customer in an email that’s just reminded them how important it is to control their finances.

Stock Market/Trading Alerts

To stay on top of the markets, an investor has to be aware of any shifts that might impact their money – or their chance to make more of it. So emails, either to their regular inbox or to an app inbox, can be set to be triggered by specific developments: a particular stock hits a threshold, the market averages do the same, or reminders to sell off shares on a certain date for tax reasons.

Trading apps have excelled at using email alerts to keep clients on top of movements in the market or key dates. Another trigger? Tracking browsing behavior through the app to deliver relevant content; if a client shows an interest in Apple (though they haven’t watchlisted it), news updates about the company (or other tech stocks) can be dispatched their way.

Onboarding & Nurturing

Once you’ve got a user signed up for your Fintech platform or product, it’s important to onboard them effectively so they’ll begin making use of it – and then nurture them through increasing levels of usage and proficiency, getting them to embrace more features (and eventual upgrades).

Here’s a great instance from QuickBooks, based on the profile they’ve built of the customer using their in-app and browsing behaviors. In this case, that user is self-employed, so QuickBooks encourages them to make use of its business expense management features – and dangles the opportunity to save on his or her taxes as a carrot.

Another tactic for deepening engagement during this part of the user lifecycle? Sending them a survey or questionnaire about how they use the product, what features they like the most, what they’d like to see added, and so on. This works in later stages, too, as a way of showing a provider is interested in their user community. Not to mention how it generates invaluable personalization data.

Winback/Re-engagement Messages

Okay, maybe even the very best onboarding and retention efforts weren’t able to keep a customer from drifting away from using an app or service. In that case, fiserv providers can be pretty adept at sending out win-back emails aimed to bring delinquent users back into the fold.

Those can take many forms, but one of the most effective can show the ex-user “what you’re missing!” in terms of new features, and throw in some testimonials to boot. Mint, from Intuit, does of fine job of exactly that, as it frets about the fact the recipient is “missing all the buzz” about those improvements.


Another tactic for deepening engagement during practically any part of the user lifecycle? Sending them a survey or questionnaire.

So long as it’s relevant and well-pitched, you can ask them about how they use the product, what features they like the most, what they’d like to see added, and so on. This works practically any stage as a way of showing a provider is interested in their user community. Not to mention how it generates invaluable personalization data.

It’s important to follow the rules, though, since financial services markets are among the most heavily regulated around. And new laws like the GDPR and CCPA make data privacy compliance vital.

Here’s an offbeat example of how one fiserv platform uses a survey. Kabbage provides small business funding, and in this case, gives users a chance to offer feedback to the Federal Reserve. Not only does it make Kabbage look like a bigger player, but also they’re helping give their users a voice with banking system bigwigs.

Order Confirmations

Sending a customer quick and precise order confirmations with some useful features attached is an email tool of many fiserv providers, and it not only builds reassurance with those users but even an expectation of just that kind of reliable contact.

If you haven’t heard of AliPay, you will; it’s the third-biggest online payment solution in China and has seen staggering growth. One of its key strengths is its ability to let users make cross-border payments in any of 16 different currencies. As you can see from the example below, which is a demo for store owners on how AliPay order confirmations work, it’s also an expert in leveraging email.

The message is short and direct and throws in the option of accessing order status and package tracking. These may be just elementary blocking-and-tackling, but they’re the kind of touches that maintain customer loyalty. And, in AliPay’s case, help it sell itself to retailers.

Suspicious Activity Alerts

With the amount of financial black-hattery that happens constantly, it’s reassuring to the customer to know their provider is on top of things. As, for instance, sending them alerts triggered by suspicious activity on a credit card.

The best examples of these (like the one below from Bank of America) are crisp, clean, and to the point: The recipient quickly sees a list of the suspect transactions with enough detail to help them remember if they’d used the card at that location, and can use big YES or NO buttons to let the card provider know if the charges are legit or not.

One extra feature some have suggested? ?The power to put a “temporary hold” on a card if the customer isn’t sure about the charges, and needs to check that office or kitchen drawer full of receipts.

~ Casey

The post 7 Types of Fintech Email Notifications appeared first on SparkPost.

4 Ways FinTech Unicorns Drive User Growth With Triggered and Transactional Emails Fri, 24 May 2019 13:00:03 +0000 FinTech unicornsExplore 4 examples of the ways current FinTech unicorns are using triggered and transactional emails to help drive their growth.

The post 4 Ways FinTech Unicorns Drive User Growth With Triggered and Transactional Emails appeared first on SparkPost.


FinTech (Financial Technology) is one of the hottest sectors in the technology field. In fact, FinTech set a record for venture capital funding in 2018, with almost $40 billion raised in 12 months. That frenzy of activity helped create nearly 40 VC-backed FinTech unicorns, or companies worth at least $1 billion each, by the first quarter of 2019.

How does a start-up experience the hyper-growth that turns it from a foal gingerly making its way down a path to a gleaming unicorn galloping through the forest? There are plenty of factors driving that kind of success, but one undeniable element is the use of triggered and transactional emails to accelerate user growth.

Another reason to craft a strong email strategy is the fact that email marketing also yields strong ROI of 42:1 on average, according to Litmus’ 2019 State of Email Survey. That ROI increases with user growth, too: companies with at least 500,000 email subscribers see 44:1 ROI, and at the 10 million-plus mark, ROI hits 46:1.

And don’t forget that triggered and transactional emails are a great way to create and nurture customer relationships, as well as build trust, which is crucial when people expect a business to safeguard some of their most sensitive personal information.

  • Triggered emails alert customers to events, such as suspicious log-in attempts, upcoming due dates for bills and other payments, and monthly reports.
  • Transactional emails are sent in response to customers’ actions, such as bill payments, deposits, new account creation, and password resets.

Here are 4 examples of the ways current FinTech unicorns are using triggered and transactional emails to help drive their growth.

1. Welcome new customers to your merry band

Robinhood has reached a $5.3 billion valuation on the strength of its commission-free stock trading app, which is popular among customers who view old school brokerages as stodgy businesses. It may seem obvious, but one trick Robinhood has used to help it reach more than 6 million users is to acknowledge them when they sign up.

The first onboarding email they send is simple, which is the best way to handle such messaging. You don’t want to inundate new customers with upsells, cross-sells, and other promotional material.

You want to let them know their account is ready to go and give them the basic information they need to get started, which in this case includes links to the mobile apps. Robinhood also adds a couple of sentences about setting up a Trusted Contact Person, which is presumably a key part of their user accounts since no one wants to leave their loved ones without a way to access their financials.

Robinhood also includes social media buttons that are integrated into the layout, rather than standing out in an obviously promotional way. In addition, the entire email maintains the company’s official color scheme, which is a key part of brand identity. They close with the required regulatory disclosures, which are unavoidable, and an unsubscribe link.

2. Celebrate customers’ purchases

Many people are still trying to figure out how cryptocurrency will fit into our daily lives, but Coinbase has successfully navigated that space to become a major wallet provider and exchange. They’re valued at $8 billion, or 8 shiny unicorns.

The transactional email they send in response to a purchase matches their bright position in the market, starting with a sparkly congratulatory GIF that strikes the right celebratory tone. The checkmark, a key element of behavioral science, tells the user, “Great job! You just accomplished a task.”

The rest of the email spells out the specifics of the transaction, which are important for countering fraud, and includes a CTA (call-to-action) nudge to set up a recurring buy. It’s okay to do that in this kind of email, since it can turn a one-time or part-time customer into a regular one. The “Learn more here” link goes to a Coinbase blog post that offers helpful insight into why someone might want to set up a recurring buy.

3. Keep account change emails simple

When people make changes to their accounts, you want to take a “Just the facts” approach and give them nothing more than what they need in the email, which should be sent as soon as possible. This is crucial to helping mitigate fraud.

That’s the approach taken in this email from Credit Karma, a $4 billion unicorn that wants to make financial planning easier for everyone. This change of password notification lets the user know what happened and gives them a direct line to the support team in case a bad actor accessed the account.

There’s no need for splashy GIFs, cheeky language, upsells, or cross-sells here. Any of those things will likely irritate the user and potentially erode customer trust.

4. Open the communication line when customers make major decisions

Sending money to a friend to pay for part of a dinner is one thing. Making investment decisions is another. Even closing an account that contains sensitive personal information can be a nerve-wracking experience for customers. They want their request handled quickly and efficiently, and you have to balance the need for security and adherence to financial regulations.

Social payments and investments are both part of the business model at Circle, which is currently valued at $3 billion. It offers two apps, Circle Pay and Circle Invest, for customers in those sectors.

Circle makes it fairly easy to set up an account, but closing one requires sending them a message (users can do so from the app) that triggers the two emails shown below. They do a good job of managing customers’ expectations while giving the company time to ensure that the request isn’t fraudulent.

Like other emails of this type, they wisely leave out promotional messaging. They also refrain from saying things like “Are you sure?” No one wants a company begging them to reconsider when they’ve decided to close their account. Yes, you should have a strategy in place for winning back users, but those emails should be saved for later.

The first email, received immediately after a request to close an account, lets the user know that the support staff is aware and a ticket number has been generated. The decision to include the text of the message that the user sent, along with a date and time stamp and information about the app and device used, helps protect against fraud.

Letting the user reply to the email gives them a chance to add more information to the support request, which is handy in case they forgot something. This is the kind of situation where they don’t want to wait for a response from the support team before they can offer additional crucial details.

The second email, which was received right after the first one, gives the customer a quick follow-up to reassure them that a review is underway. It also sets expectations: It might take a couple of business days to complete the review, a caveat that gives Circle some wiggle room in case fraud is involved.

The link on the support ticket number lets the user click or tap to see the customer support conversation on Circle’s web site. It’s a second chance to add more information to the conversation while the company is initiating a review.

~ Casey


The post 4 Ways FinTech Unicorns Drive User Growth With Triggered and Transactional Emails appeared first on SparkPost.

Email Deliverability 101: 4 Tips for the Financial Services Sector Wed, 22 May 2019 13:00:48 +0000 Financial Services SectorDiscover 4 best practices for the financial services sector for maintaining a sterling sender reputation and keeping email deliverability strong.

The post Email Deliverability 101: 4 Tips for the Financial Services Sector appeared first on SparkPost.


Email remains one of the most-used communication tools on the planet:

  • There were 3.7 billion email users globally in 2017 (Statista, 2018)
  • That number is expected to reach 4.3 billion in 2022 (Statista, 2018)

Email marketing is also a strong performer for the financial services industry, with an open rate of 18.23% and a click-to-open rate of 14.1%, both of which are higher than the average email benchmarks for all industries. (Based on an analysis of over 30 billion emails sent through Campaign Monitor in 2018.)

With that in mind, it’s important to keep an eye on email deliverability along your customer journey, including welcome messages, triggered, transactional, and promotional emails, unsubscribe confirmations, and more. Your emails might be perfectly crafted, but if you have deliverability problems, many people might never see your messages.

Sender reputation is the number one factor that impacts your ability to reach your customers’ inboxes. Just like there are people whose emails go straight to your trash when they arrive, there are sending domains that are viewed with caution by incoming email servers.

It’s important to note that even if an email is accepted, it may be automatically diverted to a spam folder or it could simply vanish. A high acceptance rate is nice, but it doesn’t guarantee a correspondingly high deliverability rate, if a company’s sender reputation is poor.

Here are 4 ways to maintain a sterling sender reputation and keep your email deliverability strong.

1. Keep people engaged

Transactional emails, which are the messages sent when customers do things like pay bills, make deposits, and create new accounts, tend to drive the bulk of ROI, with 8X more opens and clicks and 6X the revenue generation (Experian). Since they’re emails that people typically want to receive and open, they’re a good way to keep your engagement numbers up.

That also means you’ll want to put extra resources into triggered emails, like monthly reports and upcoming due dates for bills. If you don’t, your overall engagement rate could suffer, and email providers and ISPs can start to sour on senders who don’t seem to do a good job of sending their users messages they care about.

Here are a few things to keep in mind to get people to open your emails:

  • Use a friendly “from” address that makes customers feel like you’re talking to them personally.
  • Keep your subject lines short and to the point and try using personalization other than first name, such as their recent account activity.
  • Use complementary messaging in the preheader text, such as a deadline for them to take action.

When crafting the body of the message, consider these tips:

  • It’s key that your emails are mobile responsive, which means they’ll automatically adapt to the devices being used by your recipients, whether they’re phones with small screens or computers with large displays.
  • Include high-resolution images, since HD displays are quickly becoming the norm on most mobile devices.

This email from Acorns is a good example of a message crafted for high engagement rates.

  • The subject line – “Dollar Shave Club wants to invest in you” – is short and snappy and invites a little intrigue. They want to invest in me?
  • The “from” name makes it clear what Acorns is all about: saving found money.
  • The body of the email is short and gets right to the point: Sign up for Dollar Shave Club and 5% of every purchase goes into the customer’s Acorns account.

2. Create sending domains, authenticate them, and warm them up

Set up different domains for various types of email, like one for account activity and another for promotional newsletters. Set them up as sub-domains that make their purpose clear, such as alert.[business name].com and newsletter.[business name].com.

You can also increase the trustworthiness of your sending domains by implementing three free authentication standards:

  • SPF (Sender Policy Framework): This requires creating an SPF record that defines which mail servers are authorized to send email from that domain. Inbound email servers can then compare the IP address of the email sender with the authorized mail servers defined by the SPF record to determine if a message is trustworthy.
  • DKIM (DomainKeys Identified Mail) Signature: This adds a digital signature to the headers of an email message, allowing the incoming mail server to validate it against a public cryptographic key in the sending organization’s DNS records.
  • DMARC (Domain-based Message Authentication, Reporting, and Conformance): This is a policy that tells inbound email servers whether to accept, reject, or otherwise flag an email, depending on whether it passes the tests established by SPF and DKIM.

Finally, you’ll want to warm up your new sending domains by methodically adding email volume week by week – check providers’ guidelines to see what they recommend. Make sure you maintain consistent volume, frequency, complaint, and bounce levels to establish patterns and send the signal that inbound email servers should trust your sending domains.

You should also create a list of only your most highly-engaged subscribers and use them for the warm-up period, which can help build trust because you should see good engagement rates.

3. Exercise good list maintenance

It’s crucial to stay on top of your suppression list, which consists of email addresses that have consistently bounced as well as people who have unsubscribed and other problematic addresses. If you fail to do so, you’ll see a swift negative impact on your sender reputation, which will quickly harm your deliverability rate too.

You should also pay attention to your engagement rates at granular levels. Do some people never open your emails, or do others usually open them but never click anything? There’s nothing wrong with sending them an email asking if they’d like to stay on your list – if they say “No,” immediately put them on the suppression list. And if they never reply to that message, you should probably add them to the suppression list too.

4. Figure out what your customers want

Most people are fine with receiving transactional and triggered emails by default, since there’s comfort in knowing that a deposit went through and seeing a monthly snapshot of account activity. However, it can be helpful to ask customers what their messaging preferences are, since some people might, for example, want a quarterly update of their account activity rather than a monthly one.

Those preferences can also help you avoid sending people promotional emails that they may have no interest in – and that indifference can cause your deliverability to suffer. It can be useful to give customers an option for more or less frequency with promotional emails too, so you don’t completely lose the opportunity to send marketing messages.

~ Casey

The post Email Deliverability 101: 4 Tips for the Financial Services Sector appeared first on SparkPost.

AMP for Email: Sending PHI and PII to your Customers Mon, 20 May 2019 13:00:56 +0000 sending hippaSenior Messaging Engineer, Jeff Goldstein, discusses if AMP for Email is a solution for sending HIPPA and PII information to customers.

The post AMP for Email: Sending PHI and PII to your Customers appeared first on SparkPost.


Email best practice is to minimize sending sensitive information to your customers via email. In the past, email clients were fairly wide open applications with little to no security and data was often sent over unsecured internet connections. This made it very easy for a hacker to either sniff the email while in transit and/or get into your email inbox and find sensitive data.

But I’m starting to wonder if we are approaching a new era where more personal data can, in fact, be sent via email; there are two reasons for this conclusion:

  1. Today, most email clients need a username/password and many even support multi-factor authentication methods.
  2. Google’s recent launch of AMP for Email.

Over the years in my job as a Messaging Engineer at SparkPost I have spent a lot of time telling people not to send sensitive information in an email to their customers; but to use email as a way to send a ‘call to action’ to their customer; one that typically brought them back to their website. Taking this approach kept sensitive data safe and secure behind the corporate firewalls and whatever login mechanisms they deployed. But the tide has changed in the last few years, and most new email clients force similar security as these applications deploy. In fact, many aspects of email lead to even greater security than those applications. Here are a few examples:

  1. Most of my email clients notify me if my email is accessed from a new device.
  2. While not a perfect security mechanism, I can typically see if my email was read. If the email was read before I got to it, I may have an issue.
  3. Two-factor authentication is widely used to log in to your email client.

Taking all of these items together, give me a fairly high degree of security if I choose to use them.

So what about the email itself. ?Most Internet Service Providers mandate that you send your email using an internet cryptographic protocol called TLS, and most of them use version 1.2 that has been around for almost a decade and has been proven to be very secure. But admittedly, I’m still a little cautious about sending sensitive data like names of my prescription over email. This is where Google’s new AMP for Email comes in. Here is a description on AMP for Email by google:

AMP for Email allows senders to include AMP components inside rich engaging emails, making modern app functionality available within email. This dynamic email format provides a subset of AMPHTML components for use in email messages, that allows recipients of AMP emails to interact dynamically with content directly in the message.

What AMP does is allow emails to act very much like an application. Every time a user opens an email built with AMP components, it has the ability to call back to a server and display the latest information to your customer in that email. Maybe it’s when their next appointment is, or what prescriptions are due for refills. While not typically sensitive information; I like the idea of opening up an invoice and having it show me the latest shipping information without having to press a link and go to some third party sites like DHL or UPS!

From a security perspective, all communications from the email client to the server when retrieving the data is done across secured lines, just like the ones you use when logging into a secure web application. So is there really any significant difference between new AMP emails and our current HTML based applications? I’m thinking not.

If we start extrapolating the possibilities of AMP for Email, future email clients may morph from what we have today into a portal listing both normal emails and new AMP emails that take the role of micro applications with very specific functions. ?This new email client may be similar to what many companies attempted in the earlier days of the internet when companies like Netscape, Lycos, TopTier and Yahoo attempted to be a one-stop shop Portal page into all things internet. Instead of your typical email client where there is a list of emails that have been streaming through your inbox over the last several days, your email client may have a list of micro applications that perform small tasks that typically were done after going to the website. I would expect that users would select, or pin which AMP enabled emails they want at the top of their list; similar to what Hotmail implements now by pinning important emails to the top of the email list.

Leveraging this microservice approach within emails will also help fight spoofing and typosquatting. Once the user has an email that they trust, they can continue to leverage that email each time they want that service without having to worry if a new email they think is from that company was spoofed or they accidentally typed a bad web address that is actually going to a typosquatting URL.

When taking all of these security measures together we are on a solid trajectory to changing the way our users interact with email and potentially sensitive data like PCI and HIPPA data. To be clear, there are regulatory hurdles that need to be considered and/or modified in order to have this vision come true. PCI DSS prohibits merchants from sending emails that have full credit card numbers or primary account number unless using stronger encryption than TLS; so those numbers will have to be masked or only sent through a stronger encryption mechanism during the AMP callback to fetch data via HTTPS. Email clients may also need to be smart enough to delete sensitive data that it’s at rest in an email after it’s been fetched and displayed to the user.

This is really just the tip of the iceberg when it comes to compliance regulations that need to be thought through; not only for PCI and HIPPA but other regulations around the world.

Until regulations around sensitive data get addressed, AMP for Email still has the ability to change the way we work with email; creating a more secure environment against phishing and spoofing in the #1 communication channel between business and customer.

Happy Sending,



The post AMP for Email: Sending PHI and PII to your Customers appeared first on SparkPost.

Life at SparkPost: Take Our Daughters and Sons to Work Day 2019 Fri, 17 May 2019 13:00:49 +0000 Take our Daughters and Sons to Work Day 2019HR Generalist and Benefits Manager, Michelle Cunningham, gives a recap of this year's Take our Daughters and Sons to Work Day!

The post Life at SparkPost: Take Our Daughters and Sons to Work Day 2019 appeared first on SparkPost.


Here at SparkPost, we are always looking to share our story. Usually, it’s with customers and prospects but on the third Thursday of April, we share our story with a group of people very near and dear to our hearts– the kids of SparkPost!? We host a full day of Take Our Daughters and Sons to Work Day in both our San Francisco and Columbia offices as well as send out kits to the children of our remote employees that work around the globe.

This year, the kids were able to hear from our CEO, Rich Harris about why it’s important to try out different careers until you find what fits you.? He shared his personal story of starting out cutting grass as a kid, a dishwasher, to scooping ice cream, being a litigator, a professor, and now a Technology CEO.

George Schlossnagle, CTO and Founder of SparkPost shared the types of people we look for to join SparkPost. He shared our four values with the kids and why having people with those values makes our company awesome. Technical Product Manager, Avi Goldman, presented data, analytics, and email in kid speak! Members of our SF office shared their roles with the kids, including our Social Media Manager, Erica Weiss.

In addition to learning about coding, and marketing concepts – the kids had a chance to learn about and help us support two local charities that we support throughout the year. As part of community service commitment, Our Columbia, MD office assembled three housewarming kits for Grassroots in Howard County, MD and our San Francisco, CA office learned about and assembled 30 hygiene bags for Simply the Basics.

We love hearing feedback from our team.? Principal Software Engineer, Dave Gray’s, daughters mentioned that they “loved the scratch games – especially the chase game” in reference to the game in which the kids made a cake chasing and eating a donut. He also said, “They’ve asked to come to work with me every day since then.”

HR Specialist, Angie Parise’s, son Carter, shared that “it was great seeing my friends that I met last year, and the coding was really cool and the ice cream truck was epic!”

Senior Director of Engineering, Balu Pillai’s, son, Rohan, clearly liked Avi’s talk on how SparkPost helps deliver emails. It resonated well with him as his school sends emails via SparkPost and he is very keen on knowing when his school opens late.???

Our day would not have been successful without the help from businesses in our communities.? A special thanks to Howard County Fire & Rescue for their CPR lesson for kids, Magician Pravin, The Cow, and Code Ninjas for helping to round out our day!

SVP, Head of On-Premises, Joal Barbehenn, shared that?Take Our Daughters and Sons to Work Day “has easily become my favorite work-day of the year!”

We look forward to 2020!

~ Michelle

The post Life at SparkPost: Take Our Daughters and Sons to Work Day 2019 appeared first on SparkPost.

SparkPost Signals: The World’s First Predictive Email Intelligence Platform Tue, 14 May 2019 19:00:02 +0000 SparkPost SignalsRead up on the amazing features of SparkPost Signals, the world's first data-powered predictive email intelligence platform.

The post SparkPost Signals: The World’s First Predictive Email Intelligence Platform appeared first on SparkPost.


Today we are so excited to introduce SparkPost Signals, the world’s first data-powered predictive email intelligence platform. Signals has helped senders drive 4x higher engagement while sending 70% less email. At SparkPost we know that the future of email is data-driven. Using a predictive model powered by the world’s largest email data footprint, Signals alerts you when issues arise so that you can quickly find and fix email issues before they impact your business.

Signals measures the pulse of your email health using a machine learning model that monitors engagement and delivery data including opens, bounces, clicks, unsubscribes, complaints, plus dozens of other metrics. SparkPost has the world’s largest email data footprint from sending 37% of all B2C and B2B email. Signals leverages this data to predict future engagement and delivery issues, much like how your doctor monitors your heart rate, blood pressure, and cholesterol to understand your health and predict future problems. Medical advice must be individualized and email health management is no different. Instead of scoring your email health based on generic thresholds, Signals is able to look across our footprint of trillions of data points and give you tailored advice based on the historical activity of other senders that match your profile. Moreover, our team has back-tested against real-world historical performance and outages data to predict future performance and give you early warning of issues before they arise.

Powerful Insights for Supercharged Email Optimization

Signals brings you detailed metrics and an email Health Score, Spam Trap Monitoring and Engagement Recency reporting. Additionally, we’re excited to bring a new level of visibility with enhanced features, including:

Mailbox Provider Faceting

One of the first things our customers asked for when they saw the Health Score was a breakdown by who they were sending to. We’ve heard this loud and clear and are happy to report that this is now available! With Signals you can slice your Engagement Insights and Health Score by this new filter. You can examine all major mailbox provider families, including Gmail, Verizon Media, and Microsoft. You can also see regional breakdowns to help you understand regional differences.

Health Score Alerts

With Health Score alerts you can get updates in your inbox about changes to your Health Score so you can jump in and correct issues before they cause major outages. You can watch for changes in your Sending Health to Gmail, the Health of a specific IP Pool, and any of the other filters Signals provides. Watch for drops below dangerous levels, or shifts day to day, or week to week to alerts for any concerns that require your attention. With this feature, we are also including support for our alerts about monthly sending limits so you can keep an eye out on your total volume. We are excited about this first release with plenty more in the works to help you monitor your sending.

Engagement Insights

Understanding who you’re targeting is one of the first steps to evaluating the health of an email program. Engagement Insights gives you that view into your sending. We decided to take it a step further – now you can start to understand not only your engagement cohorts, but also how each cohort is behaving, including their engagement, unsubscribe, and spam complaint rate. With this view into your recipients, you can see how successful your mail is at re-engaging churned subscribers, analyze which cohorts drive your complaints, and peek into whether your mailing frequency is leading to unsubscribes.

Improved User Experience

With our?custom date ranges in Signals, you can dive into historical sending with the same directed experience as if you had sent the emails yesterday. We’ve also put a focus on helping you understand your Health Score with grading lines on each chart and an overall account Health Score to help you see how your total health score is trending over time.

Health Score V2 (Coming Soon)

Our next iteration of the Health Score doubles down on the fact that at the end of the day, what matters most is your engagement. Not only is it a major factor in your sender reputation at most major ISPs, but it also drives the ROI of your email program.

With our new health score model, we’ve added a wider set of features to our model for 50% greater accuracy.

We’ll be rolling this update out over the next two months, along with better recommendations and clearer insights to help you understand the unhealthy areas of your sending.

Available on All SparkPost Platforms

Signals is now available on SparkPost Cloud, and to customers using our Momentum and PowerMTA on-premises email delivery platforms. On-premises users can take full advantage of Signals’ detailed analytics without costly and time-consuming overhaul of existing email infrastructures.

SparkPost Signals gives us a holistic view of our campaigns across all our brands. Visibility into our deliverability health score means we don’t miss critical changes in performance and can quickly take action when issues arise.

– Justin Farris, Dir. Product Management

With Signals, you don’t have to leave email optimization up to hunches or trying to extrapolate data from third-party add-on tools. Signals is powered by real-time engagement data from your email sending to provide you with actionable insights to predict and optimize email performance to drive inbox opens and clicks.

Simplify email performance management.
Maximize performance with data-driven insights.
Accelerate email optimization to predict and mitigate risks. Get email delivered to the inbox on time, every time.

Schedule a demo with a SparkPost Signals expert and start digging into your email health score to get optimizing and boosting your engagement and ROI.

Happy Sending!

~ Avi

The post SparkPost Signals: The World’s First Predictive Email Intelligence Platform appeared first on SparkPost.

Predictive Email Intelligence – The Next Wave in Email Delivery Performance from SparkPost Tue, 14 May 2019 13:15:37 +0000 Email IntelligenceLearn more about SparkPost Signals, our new email intelligence platform that analyzes trillions of emails to predict email engagement and delivery health.

The post Predictive Email Intelligence – The Next Wave in Email Delivery Performance from SparkPost appeared first on SparkPost.


Being able to predict things in the future – when you think about it – is pretty amazing.

In today’s data-centric world, where machine learning and data behavior capabilities are advancing so fast, being “predictive” is now transforming many industries for the better.

Today, we are pleased to bring the first data-driven, predictive email intelligence platform to our own industry, with the launch of SparkPost Signals.

We felt strongly, and our teams worked hard, to bring email delivery and deliverability analytics forward to be more in line with leading-edge technologies in fields like ad-tech, financial services, and consumer marketing.

With SparkPost Signals, we now offer an email intelligence platform that analyzes the behavior of trillions of emails to predict email engagement and delivery health. Our early customers can attest to how it helps optimize email delivery based on predictive analytics and machine learning to maximize revenue and avoid costly outages.

Here’s what our friends at Zillow have to say:

“SparkPost Signals gives us a holistic view of our campaigns across all of our brands,” said Justin Farris, director, product management at Zillow. “Visibility into our email health score means we don’t miss critical changes in performance and can quickly take action when issues arise.”

I think you’ll agree it was time we had a platform to offer predictive engagement alerts to email health problems before they cause business interruption, delivery problems or email outages.

You can learn more about the key features and functions in today’s news release.

At a high level, here are some new insights we now offer to ensure optimized email performance:

  • Real-time insights into deliverability and performance issues – based on the behavior of trillions of emails
  • Actionable delivery health alerts – identifying potential problems before they happen
  • Recommendations to optimize email engagement and performance
  • Industry email delivery performance benchmarks to gauge and improve against

The reason Signals stands up to its claim as “first and only” lies in the fact it is powered by a massive email data footprint, based on our company sending more than 37 percent of the world’s B2C and B2B email. In many ways, we see Signals crossing and combining categories – email delivery and email deliverability analytics – to provide stronger insights than products on either side.

Today, SparkPost Signals is available on our three platforms: SparkPost Cloud, plus PowerMTA and Momentum for on-premises email delivery.

Bringing “predictive” into the world of enterprise email, by unifying delivery, deliverability, and analytics is an important step forward in the data-driven future of email.

SparkPost Signals is our first phase in making email performance better and more predictive. I encourage you to check it out and, of course, I’d love to hear your thoughts on this major step forward for the company and the industry.

~ Amie

The post Predictive Email Intelligence – The Next Wave in Email Delivery Performance from SparkPost appeared first on SparkPost.

Isn’t Email Supposed to be Dead? Fri, 10 May 2019 13:00:09 +0000 email deadMany have written obituaries for email for years, but now it’s more central and vital to people’s lives than ever. Discover why email is far from dead.

The post Isn’t Email Supposed to be Dead? appeared first on SparkPost.


Isn’t email hanging on by a thread, shambling toward the boneyard, ready to breathe its last?

If it is, then someone forgot to tell its 3.8 billion worldwide users last year. In fact, by the end of 2020, we expect to see almost 255 million email users in the U.S. alone.

So one place email certainly isn’t headed? Extinction.

I recently sat down for a podcast with Benjamin Shapiro to drill down on some of the reasons email isn’t just alive, but thriving. ?Some of those?

Email is as Old as Time

For those that grew up in the Internet era, email has remained a constant, reliable, familiar form of communication. It was one of the first things people adopted once dial-up Internet became widespread.

Persevering through the rise of different messenger apps, from AIM to Facebook Messenger to WhatsApp (and others too numerous to mention), social media channels like Twitter and Instagram, and even good old SMS, email has stubbornly held its ground. And even gained ground, when you examine the facts.

Part of this success is owed to how email has already been such an integral part of modern communication. For anyone who grew up using email, moving to an entirely new platform presents a daunting – and seemingly unnecessary – challenge. It’s much easier to have both your Messenger app and your Gmail account cooking simultaneously, used for separate purposes.
This reluctance to move away from email, in turn, forces the next generation coming along to use it if they hope to keep lines of communication open with…well, everybody else.

Similarly, email has the prospect of a long life in front of it because it’s not run or owned by a single entity. Unlike Facebook Messenger, for instance, there’s no single email service provider that has a complete monopoly on the channel. The fact that there’s competition among a variety of providers drives both email’s entrenchment and innovation.

More than Alive – It’s Evolving

While it most certainly is not declining in popularity, email is evolving. As just one example of email technology’s forward march, the arrival of artificial intelligence and machine learning are taking it to new levels.

AI is helping to plan and automate marketing campaigns. The IoT (Internet of Things) leads to more data being collected, which means more app-generated and transactional email.

On yet another level, the rise of voice search technology has a significant impact on email, particularly for marketers’ content and copywriting. The fact that emails can now be read aloud to a recipient means the copy needs to work in both written and verbal form – an intimidating consideration when it comes to making puns!

As email develops and becomes more sophisticated, recipients also will shift their standards about what is acceptable and what isn’t. Gone are the days when spam was something people simply shrugged off – irrelevant email is now flagged immediately, whether by the inbox owner or the increasingly smart spam filters deployed by ISPs and corporations. As their expectations of personalization increase, the window of relevancy may narrow and be in constant flux.

And as people flex these new boundaries about what’s acceptable? Email marketing keeps up by becoming more targeted and relevant. ‘Spray and pray’ campaigns? A thing of the past. 34% of consumers mark some email messages as spam, but 76% of subscribers make purchases based on email marketing – which depends, of course, on that marketing having personal pertinence.

Successful email marketers aren’t squandering budgets targeting the wrong audiences anymore, but are putting metrics and analytics to work as never before. The movement beyond even predictive analytics to prescriptive analytics, where intelligent machines advise human marketers on the best decision to make, is one example. The evolution of email marketing toward greater accuracy and relevance is a win-win for both recipients and marketers.

Stressed About Social Media?

It’s true, social media may have seemed like a threat to email back in the day. There’s always panic about the Next Big Thing, but email is a cornerstone of contemporary communication – it isn’t going anywhere.

As time passed, both email and social channels settled into their respective roles. The most glaring proof? The fact many social media platforms require an email address to sign up.

Social and email work hand-in-hand in countless instances. LinkedIn may be a great way to inquire about a job opening, but any potential employer is most likely to conduct further communication through email. Can we imagine a jobseeker who doesn’t have an email address in this day and age?

Another way in which email has cemented its place? By becoming a centralized storage center. While LinkedIn may be the professional counterpart to Facebook, email has remained untouched as it houses personal to professional communication in one private place. There’s a purely personal aspect to email that derives from the fact that it’s not shared with the world; the digital equivalent of a trunkful of letters in the attic.

Another unique aspect of email is the level of control it offers. That unsubscribe button can be your best friend, so most email marketing campaigns now allow you to pick exactly what frequency or type of communication you want to engage in. Daily, weekly, monthly – it’s all in your hands. Taking it a step further, as with Gmail’s ‘Promotions’ and ‘Updates’ tabs, means your inbox is becoming an automated organizer, helping you keep track of connections and interests and promotions more easily and efficiently.

With newer collaboration tools such as Slack entering the market, one may wonder if email will become less crucial. However, as Techcrunch noted a few years ago, these tools tend to rely on email instead of diminishing it. Notifications get sent through email because platform designers know that’s the best bet for ensuring participants don’t miss anything important.

An Interactive Future

Since email clearly isn’t going anywhere, what’s going to take it to the next level?

Interactive emails are on the rise, where the recipient can interact with the brand directly within their inbox. Google, for instance, is now supporting AMP for Email, in the hopes of making emails look and respond like portable Web pages.

By keeping the interaction within the email, marketers avoid the frustration and time of loading landing pages. The emails are already customized to their targets, making it a more pleasingly personalized experience for the end user.

Has it been worth the effort? According to research, just adding videos to your emails can boost clicks by up to 300%, while interactive content increases CTOR by a whopping 73%.

Check out the podcast

To hear what I have to to say about the lively and far-from-zombified state of email, listen to Part 5 of the “Email Week” series of the MarTech podcast?with Benjamin Shapiro.

~ Tracy

The post Isn’t Email Supposed to be Dead? appeared first on SparkPost.

We’re Heating Up! SparkPost’s Automated IP Warmup Feature is Live Wed, 08 May 2019 13:00:18 +0000 IP WarmupRead up on our new Auto IP Warmup feature which slowly increases the amount of traffic sent over an IP each day to help you build trust with customers.

The post We’re Heating Up! SparkPost’s Automated IP Warmup Feature is Live appeared first on SparkPost.


Experienced email senders know that a great sending reputation is essential to delivering messages where they’ll actually be opened and read: the inbox. Building a good reputation takes time—but SparkPost has just made one part of that process a lot easier.

We’ve released a new Auto IP Warmup feature for SparkPost customers who add dedicated IP addresses to their account. Auto IP Warmup uses a stage-based approach that slowly increases the amount of traffic sent over an IP each day that you send email to help you build trust. And during this warm-up period, we overflow any excess traffic to your existing, warm IPs, so you won’t experience any downtime in your ability to send.

Bottom line? As a sender, you won’t have to worry about the impact of cold IP addresses on your ability to connect to your customers. Auto IP Warmup uses a proven process that ensures a good level of trust can be built for your IP in about a month. As long as you’re sending high-quality email to an engaged customer base, you’ll be good to go.

You can learn more about SparkPost’s Auto IP Warmup feature in our Knowledge Base. And if you’d like to dive deeper, our deliverability experts wrote a fantastic article about IP warmup best practices that was invaluable reading when I was just learning the ropes.

Auto IP Warmup makes it easy to get up and running quickly with a dedicated IP address—so you can spend your resources on creating great emails your customers will love, rather than the nuts and bolts of managing the tedious and technical process of ramping up trust for a new address.

Please reach out to share your feedback and any questions.

Happy Sending,
Harold Vass
Technical Product Manager

The post We’re Heating Up! SparkPost’s Automated IP Warmup Feature is Live appeared first on SparkPost.

Building AMP Email with SparkPost Templates Just Got Easier Mon, 06 May 2019 13:00:36 +0000 AMP PreviewOur first enhancement to the AMP experience, AMP Preview, gives the ability to preview and render AMP content as you build out your email template.

The post Building AMP Email with SparkPost Templates Just Got Easier appeared first on SparkPost.


Preview AMP Emails in SparkPost with Our Enhanced Template Feature

Make way for AMP Preview!

I’m happy to announce our first enhancement to your AMP experience: AMP Preview. AMP Preview brings the ability to preview and render AMP content as you build out your email template. This is an effective way to verify that your AMP content is valid and will render as expected in the recipient’s inbox. You can now preview all three MIME parts of your email (HTML, AMPHTML, and Text), as well as send a test message to yourself, all from the Preview Page.

We’re ridiculously excited about AMP email and what it means for our customers and the future of email! We’ll be at Google I/O this year to present about AMP for Email on May 9th on Stage 5 at 12:30 pm pt, and will be participating in several office hours throughout the developer festival to provide some hands-on AMP email assistance and knowledge sharing. If you’re attending as well, we’d love to talk with you about AMP for email!

Wait, what’s AMP email?

Google and the publisher ecosystem spearheaded the open source AMP (Accelerated Mobile Pages) Project to help publishers develop fast web pages that are optimized for mobile clients. Since its launch in 2016, AMP has had a large impact on the mobile web user experience and engagement.

Launched on March 26th, AMP for Email (also known as AMP email) adapts the AMP technology to the unique needs of the email inbox. AMP email gives senders the ability to enhance messages with interactive and data-driven features that have the potential to transform the way recipients interact with messages. It seeks to enhance and modernize the email experience through added support for dynamic content and interactivity while keeping users safe.

AMP for Email provides email developers with a set of rich components that include carousels, responsive form elements, and—maybe most exciting of all—the ability to dynamically retrieve fresh content that updates even after a message has been sent. Email recipients can view and interact with AMP components directly in the email, without leaving their primary inbox experience. This means you can now make purchases directly in the email, acknowledge a security alert, submit an RSVP to an event, schedule an appointment, reply to a document comment, and fill out a survey or questionnaire…all without leaving your inbox!

Go get started! More AMP fun is on its way!

Check our AMP Preview documentation on how to get started and start sending some AMP messages to your inbox starting right now! We hope you have a ton of fun creating AMP content and exploring new and exciting AMP use cases!

We’ve been busy supporting AMP email from day 1 of the official launch and helping our customers get started with AMP. We’re now focused on continually adding new features and enhancements to make the adoption of AMP emails even easier and faster! Here’s what’s coming really soon:

Enhanced UI/UX for Templates, including:

  • Full-screen code editor with live preview
  • Inline AMP validation
  • Mobile device preview
  • Improved Templates management page

Enhanced Recipient Lists:

  • Interactive list upload
  • Improved Recipient Lists management page

We Always Want More Feedback!

Hopefully, you’re equally as excited about AMP for email as we are! I’d love to get direct feedback from you on whether or not you plan to send AMP email and any awesome use cases you’ve come up with. Please share your thoughts with me via survey?(use the QR code below to take you straight there)! I’ll be checking the responses and will get back to those who request a follow up with me to talk through getting started on AMP or integrating onto SparkPost!

~ Isaac


The post Building AMP Email with SparkPost Templates Just Got Easier appeared first on SparkPost.

Building an Email Archiving System: Reporting – Part 5 Fri, 03 May 2019 13:00:38 +0000 reportingIn the fifth installment of his blog series on building an email archive, Senior Messaging Engineer, Jeff Goldstein covers reporting.

The post Building an Email Archiving System: Reporting – Part 5 appeared first on SparkPost.


* This blog is addressing the process(s) in green

In what I expect to be my last installment of this project, I’m going to describe what I’ve done for reporting. Admittedly, if you look at the code which I have placed in the step4Reporting folder within this GitHub repository you?will notice that I have made changes throughout the code base just on the principle of building a better product. Some of the changes are around aesthetics, some on usability, others are around security and then of course reporting.

Compared to the previous blogs in this series, this one will be rather short since most of the work on reporting was done in previous steps; thus only a few coding additions to support reporting were necessary. The first change I’m going to discuss was something that I should have done earlier and simply didn’t think of it until someone pointed it out (ok, I guess I never thought about it); I added code to store (then display) the headers of the archived email. In a perfect world, what we really would want are the headers of the rcpt_to email; but we can’t get those, so this is the second best thing. I decided to store the headers in its own string field in the same table that holds all of the other archive data that was captured in the first development step. Now that I have that information stored, I was able to add the headers into the details section when the email body is being displayed.

At first glance, I wasn’t really happy with how that looked. Depending on the sending and receiving platforms, there can be a lot of headers. An email can easily have 20-30 headers! So in my sample project, I decided to also add code that allows the user to display or hide the headers as they wish. This is definitely a personal issue and an option that many of you may think is going overboard and definitely not worth coding!

Now that I have the header information like I should of in the first place, I started to think about the actual reports. So how would an auditor want to see, print or export this data? I decided on four different ways:

  1. Simply print the page. That one was easy, not a thing to do for that one!
  2. Print the detailed email that was being reviewed.
    • Wide view – In the previous development step where I built the inbox display UI I decided to display the email details in an alert box, but I was forced to change that to a new browser window for this step. The changes were minor but I had to do that in order to have the browser print just the email details. When using an Alert box, the browser would attempt to print both the Alert window and the underlining browser page at the same time; that is not the result I was looking for, and thus changed it to a pop-out window. All-in-all, I think it also produced a better-looking product as well.
    • Collapsed view – This was a little trickier. The email body and details are displayed in a table cell next to the events in the UI. So printing the email details would mean printing out the UI page; not just the specific email.?So I decided to add a button that the user would select when they wanted to print the details while leveraging the collapsed view. This action would produce a separate page for printing; just like in the wide view. In order to keep display/print consistency between the two views, collapsed and wide; anytime I create the email body and details output, I store the whole thing in a hidden field. Then when I want to display the details in a new window for printing, I simply grab that field and display it. Now when the auditor wants to print out the details, they simply use the browser print functionality for that new window.
  3. The last reporting option is to create a CSV file for all events still being displayed in the UI (not filtered events). Since there are two different formats for the UI, collapsed and wide, I decided the easiest way to do this was to call the database again and retrieve the data that matches the filter entries. The PHP application grabs the data from the database, creates a CSV file, then passes it back to the ajax call in order to have the file downloaded to the clients desktop. This does create a temporary file on the server so I have a process that removes the files every 24 hours.

So I think this concludes the “Archive for Audit Purposes” project. I described the problem and proposed the solution in the first blog. Then, I built the solution and documented it in the next four blog posts. While I think this is the end of this post series; after showing this code to a few people, I may take this code base and mold it into a more general use display and search tool for all historical SparkPost events. Many SparkPost customers build their own inbox displays similar to this one in order to support their customer service team and I think this project with a few tweaks can be a great start on that project.

Happy Sending.

~ Jeff

The post Building an Email Archiving System: Reporting – Part 5 appeared first on SparkPost.

Writing Email that Converts into Business Results Wed, 01 May 2019 13:00:46 +0000 writing emailHead of Marketing, Tracy Sestili, discusses best practices for writing email that converts into business results and drives email marketing ROI.

The post Writing Email that Converts into Business Results appeared first on SparkPost.


If you’re running email marketing campaigns, chances are you’re grappling with the same issue as 54% of marketers out there – how to increase engagement rates.

Email marketing can be far more nuanced than it first appears. Especially since as technology evolves, so do consumers’ expectations. I drilled down into the details of this evolution in a series of podcasts where I chatted about how mastering the details can make you the email marketing guru your business really needs.

Here’s a rundown some of the key details I touched on, and what makes them vital to email marketing success and campaign ROI.

It’s all about first impressions

Awareness-driving emails: the main goal here, when you’re first reaching out to your target, is open rates.

Sounds simple, right?

According to PR Daily, the number of worldwide emails sent and received per day stands at 205.6 billion. 66% of consumers unsubscribe from emails because they aren’t relevant, and 34% of consumers mark email marketing messages as spam.

The competition for their very narrow, very self-interested attention? That’s very real. So how do you avoid that dreaded red “spam” flag? ?Through personalization, relevancy, and brevity.


You want to catch the consumers’ attention, which means standing out among all the other email they’re receiving.

Personalizing subject lines and addressing the recipient is a baseline expectation in today’s world, frankly. Mentioning company names, first (or last) names, and the consumers’ roles are good ways to pique their interest, but they’re worth very little without relevant content to back them up.


As the statistics above indicate, we live in a time of email – and information – overload.

Go one step further when personalizing and ask yourself: What’s your reader’s role? ?What are the day-to-day hurdle or headaches they face? And most importantly, how can your content help them solve these pain points?

The main reasons people will engage with your content is because it entertains or helps them. By ensuring your content is relevant, you’ll please your readers and see your engagement levels soar.


With the sheer amount of content available online and being delivered to consumers, people don’t have the time to read through everything that lands in their inbox. Everybody skims – which means your content needs to be brief, concise and easy on the eyes.

How to avoid TL;DR (see what we did there?): Embrace bullet points and short highlights.

The old rules don’t apply

Despite what many would-be direct marketing guides may say, the rules on subject lines – your number one attention-grabbers – are constantly changing.

For instance? The use of emojis in email marketing messages increased 775% between 2015 and 2016. Why? Because, well, they work. And when something works, it tends to re-write the rules.

Staying current with changes like this isn’t impossible, but the only way to know what works for your audience is to constantly test and measure your campaigns.

Another rule that’s changed over time? Don’t be afraid to make your emails appealing – even in B2B – by using images.

As email becomes more interactive and fun across the board, recipients expect to receive more than a B&W, text-only email. Using design templates, images, or videos may very easily drive up your engagement rates – but you won’t know until you try by testing to see what design approaches work best with different email types and audiences.

The news on newsletters?

Newsletters, like email marketing in general, are indispensable to marketers of all types. For example? In B2B content marketing, 77% of companies surveyed used email newsletters to support content efforts – and 40% said email newsletters were the most critical tactic in their content marketing.

As a marketer, you want to ensure that your audience is engaged with (and hopefully enjoying) the content you’re sending. There are two basics to cover if you can make sure your newsletters are having the impact you’re aiming for: frequency and (again!) personalization.


Segmenting your audience within an email marketing campaign is a necessity. With newsletters, as with drip campaigns or any other email marketing, figuring out the optimal frequency for each segment is key.

Each recipient will have a different threshold, and the frequency of your emails must be tweaked accordingly. If you send weekly messages to a consumer who wants to hear from you once a month, they’ll be quick to unsubscribe. ?One way to make sure your frequency is right? Give them the chance to control it by tweaking send settings during the opt-in or onboarding process.


Executing the perfect newsletter campaign demands you build datasets and mine insights based on engagement levels within newsletter content. That’s how you comprehend what different segments – or even different individuals – are responding to best.

Setting up separate newsletter campaigns tailored to different audiences and optimizing them as your database expands will result in higher engagement and fewer unsubscribes or (unfortunately, it even happens with opt-ins) the dreaded spam flaggings.

Hear more on the podcast

For more on writing and executing email marketing campaigns that drive real business results, listen to me on ?Part 2 of the “Email Week” series on the Martech Podcast with Benjamin Shapiro.

~Tracy, Head of Marketing

The post Writing Email that Converts into Business Results appeared first on SparkPost.

5 MarTech Companies Bringing Their Email A-Game Mon, 29 Apr 2019 13:00:38 +0000 martech companiesDiscover 5 MarTech companies that are bringing their A-game when it comes to educating, onboarding, and engaging with current customers via email.

The post 5 MarTech Companies Bringing Their Email A-Game appeared first on SparkPost.


“Physician, heal thyself,” the old maxim goes. In a landscape like the one mapped below, it’s important that martech providers lend it their own spin: “Martech company, market thyself.”

Drawn up by martech pundit Scott Brinker, here’s the 2019 edition of his annual Marketing Technology Landscape which includes?7,040 martech companies.

It’s no wonder there’s a gold rush of startups and seasoned competitors alike when it’s estimated the martech market could be worth upwards of $34 billion. With plenty of headroom: One study claimed that 50% of brands had no martech tools in place.

To survive, let alone thrive, in this increasingly crowded marketplace, martech companies need to excel at marketing themselves to potential customers. The best of them have always made this a priority, and it’s no surprise they’ve relied on the best available platform for targeting and engaging B2B prospects: email marketing.

Using the entire toolkit

We could belabor a lot of stats around the efficacy of B2B email marketing, but we’ll stick to just two: 73% of B2B marketers say email marketing is vital to growing their business, according to Salesforce, and HubSpot cites how 59% of B2B marketers say it’s their most effective channel for generating revenue.

Making B2B email marketing deliver optimum ROI, though? That’s a matter of leveraging all the tools in the email toolkit. From deploying welcome and onboarding emails through transactional, account updates, milestone, or real-time-triggered emails, the martech companies that have surged to the front of the pack have made a habit of putting together fully integrated campaigns that hit all the right marks. Here are a few examples.

Onboarding on the right foot

HubSpot does a superior job of bringing new customers into the fold, just like you’d expect. It’s not just because of what they do right; it’s what they carefully avoid that makes a difference, too.

Here’s a ?welcome email that goes out to a new customer immediately after they’ve confirmed their HubSpot Marketing Free account. Friendly and conversational, and offering ways for the customer to get started ASAP – but hey, no pressure!

The next day, another onboarding email shows up that does something important: It puts a human face to the HubSpot brand, giving the user the idea they’re getting personal(ized) service.

One thing that doesn’t happen during the onboarding period with HubSpot? New customers aren’t bombarded with a blizzard of messaging trying to push them into using HubSpot.

It’s a wise strategy in a couple of ways. First, it doesn’t inspire annoyance on the part of the customer, unlike some onboarding cadences we’ve seen that seem to want to shame new users into action (“Do you know what you’re missing?”).

Second? It may actually help filter truly interested users from less-committed ones since more of the initiative falls on them to make the first move. That way, reps like James get a better idea which free users are willing to follow through – who be migrated into paid accounts.

But if a martech company wants to prompt new users to begin using the product, it helps to give them inspirational cheerleading like that in this Campaign Monitor example to nudge them into action by focusing on ease of use, friendly support, and feel-good case studies.

Triggering deeper engagement

Triggered emails can be used in any range of ways, and can drive martech customers to engage on any number of fronts. ?Here’s a for-instance from Kissmetrics.

Let’s say you’ve sent out an email to existing opt-ins much like the second one above from HubSpot, providing links to resources, to learn about products, etc. A subscriber clicks on one, or you’ve tracked them at your website hovering on a product page or downloading related content.

Any of those scenarios can trigger an email that offers up a free demo of your product, and who can resist that? Especially if you can tailor the email with additional personalization based on other data you might hold about the recipient.

As Marketing Sherpa once pointed out, 72% of people like receiving promotional offers via email.

Announcing yourself

If you’re in martech, you’re probably making regular product upgrades, releasing studies or white papers, appearing at industry events – newsworthy developments you can announce to your subscribers via email.

(If you don’t have anything worth announcing? You’ve got problems that even email marketing won’t fix.)

Here’s an example of how MailChimp announced the addition of a new feature to its mobile app.

The secret sauce here? Be judicious. Not every new feature or event appearance is worthy of an announcement, or follower fatigue will quickly set in. ?Save these emails for real news and valuable information they’ll find interesting and useful.

Uniquely proving your product

It’s an imaginative way to demonstrate your offerings’ value, and it won’t work for every platform or solution. Yet you should always look for outstanding ways to use email to tangibly bring home your advantages or benefits.

Here’s an interesting example from demand gen provider True Influence for its Account Based Marketing (ABM) platform, InsightBASE.

First, they used InsightBASE to find decision-makers who were visiting sites and pages related to ABM across the web. Then they sent those targets emails like this one to clearly prove what the product was capable of: it had identified the recipients as prospects, exactly as those recipients could use the product to find their own high-quality leads.

~ Craig

The post 5 MarTech Companies Bringing Their Email A-Game appeared first on SparkPost.

SparkPost’s Boomerang Employees: Why They Came Back Fri, 26 Apr 2019 13:00:39 +0000 boomerang employeesHR Generalist, Christina Corey, shares insights as to why some of SparkPost's boomerang employees decided to rejoin the SparkPost team.

The post SparkPost’s Boomerang Employees: Why They Came Back appeared first on SparkPost.


When talking about the employee experience, most people think of the lifecycle from recruitment to onboarding all the way through an employee’s departure. That’s all fine and good, but in reality, the relationship doesn’t stop there.

Alumni employees have the power to be ambassadors for your organization. They can speak to your culture and share insights into opportunities for learning and growth. They have firsthand experience about what it’s like to work for your organization, and that means they can provide a very accurate picture for people in their network.

When you nurture the relationship with your alumni employees and they recall their experience a positive light, they are more likely to recommend you to their friends as an employer of choice. ?Even better, they may have enjoyed their time with you so much that they would consider coming back! Enter: the “boomerang employee”.

The great thing about boomerang employees is that they already know what it’s like to work for your organization and the experience was likely a positive one the first time around. The separation, however long, can allow the boomerang a chance to try new things. And, when they come back they will bring with them new knowledge and skills as well as experiences that can most likely only benefit your organization. Even better, they will come back to old friends, familiar processes, and can more quickly jump back into the day-to-day.

Here at SparkPost, we have had quite a few boomerang employees throughout the years. ?Sharing their experiences are Kristen Breidenbach (Sr. Manager of BizOps), Tracey Crawford (Lead Deliverability Analyst), and Brian Kemper (Sr. Software Engineer).

Tell us what about SparkPost’s culture that drew you back.

KB: My mentor, Carol Sullivan, brought me back to SparkPost. I realized that I was not done learning from her extensive experience in Sales Operations, and there was still a lot of room for me to grow professionally at SparkPost. I also liked the flexibility with work/life balance at SparkPost and really enjoy all the people I work with in the SF office.

TC: I have always liked SparkPost, even when I wasn’t working here. I like the open environment, food perks, work from home policy, and relaxed atmosphere. ?Everyone is willing to help each other out and the overall vibe is positive.

BK: The entrepreneurial spirit at SparkPost is energizing. ?Every day is exciting. We are here to win.

What is the best part about being a boomerang employee?

KB: Being gone only about 8 months, I don’t really feel like I ever left. I suppose the best part is that I got experience somewhere else that I can now apply here regarding tools and sales process.

TC: For me, the best part of being a boomerang employee is coming back to the coworkers that I once worked with. From day one, I received warm welcomes from everyone (even flowers on my desk) and was able to reconnect with old friends.

BK: Perspective. ?I know what SparkPost has to offer. ?I know what other companies have to offer. ?It was an easy decision to come back.

What is your biggest accomplishment/most exciting project you have had or hope to have the opportunity to contribute to?

KB: My biggest project and goal is to enable our Sales team to be as successful as possible by providing them with the most effective tools and processes as well as accountability reporting.

TC: I have always loved deliverability, so I hope my addition to the deliverability team will be impactful. I would also like to be more active in M3AAWG and post blogs on the SparkPost website.

BK: Rebuilding of our web application with ReactJS was very exciting, but pales in comparison to the features and products we have/are built/building. ?(e.g. Snippets, Signals, support for AMP, etc.)

We’re so grateful to have our returning employees joining us once again! ?They are making huge strides in moving our company forward. If you have worked for us in the past or would love to see what all the fuss is about, check out our Current Openings!

#boomerangemployees #SparkPostLife #careers

~ Christina

The post SparkPost’s Boomerang Employees: Why They Came Back appeared first on SparkPost.

What is an Email Seed List? Wed, 24 Apr 2019 13:00:38 +0000 seed listOur SVP of Deliverability, Kate Nowrouzi, explains the purpose of seed lists and the potential challenges of using a seed list during an IP warm up.

The post What is an Email Seed List? appeared first on SparkPost.


What is an Email Seed List?

An email seed list is a list of test email addresses created for the purpose of monitoring where messages will land when sent. These lists usually contain test addresses at major providers such as Gmail, Yahoo, AOL, and many other ISP domains.

Senders can add seed lists to their upcoming campaigns to measure inbox placement at various providers. A seed list allows you to test where an email will land?across different email clients and devices as well as see how your campaigns are rendered in different browsers and email clients.

Email Seed List Challenges

In recent years, many major ISPs such as Gmail, Verizon Media (AOL, Yahoo, Verizon) and Outlook domains have begun to take engagement into consideration for inbox placement. Because of this, senders cannot necessarily rely on seed list results alone to determine inbox placement as the insights gained from seed testing may not present a complete picture of how successful an email campaign was.

Because the email addresses in seed lists are test accounts, there is no engagement associated with them. As a result, ISPs see these accounts as inactive. Emailing to an inactive account can affect a sender’s IP/ domain reputation and can result in heavy spam foldering. This can also add another layer of complexity when?warming up new IPs. Since Gmail expects senders to start with really low volume during the first couple of weeks of ramping up email sending, hitting a relatively large number of inactive addresses will complicate building a good reputation on new IPs. We always recommend that our customers send traffic to their most engaged users for the first 4 weeks of a ramp up.

Our recommendation is to avoid using seed lists during the warm-up period. And, if you decide to use seed lists after you have established a solid reputation with the ISPs, then use them as one of many other factors to determine whether or not your campaigns are successful.

Monitoring open rates can provide more accurate data points when determining whether your emails are making it into the inbox. Of course, the open rate may vary based on the type of traffic (welcome, transactional, marketing) but the average open rate for Marketing emails is about 20%, this rate is higher for transactional traffic or triggered messages.

Happy Delivering!

~ Kate

new rules email deliverability best practices

The post What is an Email Seed List? appeared first on SparkPost.

5 Ways to Replace Snail Mail with Triggered and Transactional Emails This Earth Day Mon, 22 Apr 2019 13:00:06 +0000 earth dayLearn why triggered and transactional emails are a great way to replace notices that used to be sent via snail mail to save paper this Earth Day.

The post 5 Ways to Replace Snail Mail with Triggered and Transactional Emails This Earth Day appeared first on SparkPost.


Despite a push toward paperless offices during the past 15 years, the average employee uses over 10,000 sheets of paper annually, which costs $80-100, and the typical company spends $2.5-3.5 million per year trying to find information and recreating lost documents. In addition, Forbes notes, more than 400 million metric tons of paper were used in 2017, and that amount is expected to surge in the coming years.

It’s not enough to turn paper-based internal systems into electronic ones to cut back on paper use, though. Triggered and transactional emails are a great way to replace notices that used to be sent via snail mail.

  • Triggered emails alert customers to events, such as suspicious log-in attempts, upcoming due dates for bills and other payments, and monthly reports.
  • Transactional emails are sent in response to customers’ actions, such as bill payments, deposits, new account creation, and password resets.

In honor of Earth Day 2019, here are 5 ways you can use triggered and transactional emails to help lessen the strain on the planet and save money on printing, handling, and mailing costs.

1. Acknowledge an investment

Wefunder, which calls itself “Kickstarter for investing,” lets average folks put money into early-stage start-ups, thanks to the Regulation Crowdfunding law that went into effect in 2016. Before then, you had to be an accredited investor to get in on the ground floor of a new company.

They also handle everything electronically. In addition to the expected updates from companies a user follows and suggestions for new investments, Wefunder delivers financial information via transactional email too. For example, the message below confirms a user’s pledge in a start-up called Legion M, which says it’s “the world’s first fan-owned entertainment company.”

The email leads with key details before flowing into an investment summary headlined by a prominent checkmark that confirms funds are in escrow. The summary uses information blocks to lead the recipient through key details, including the required legal disclosures. A block at the end contains important information about canceling an investment, which is likely to be on the mind of a few users who might be nervous about their decision.

An attached PDF contains the electronically-signed contract for the pledge. Nothing was sent via postal mail for the transaction.


Later that year, Legion M used Carta to issue the stock certificate for the investment. Again, not a single sheet of paper was delivered via a fossil-fuel-burning, 30-year-old truck – the user signed the certificate on the Carta website and an electronic copy of it was stored in their online account.

2. Issue event tickets

Ticketing has felled entire forests in decades past, but today, it can be completely handled electronically, as this Eventbrite email demonstrates. The attendee can manage their registration in the Eventbrite mobile app or save the ticket attached to the email as a PDF file. The ticket has a QR code, so it can be scanned off a mobile device.

The email’s information blocks highlight text from the event organizer, the order summary, and an “About this event” section that has key links for mapping the location and adding the event to a calendar.

Two promotional blocks close out the email. They’re saved for last because users don’t want that kind of messaging interfering with important information, especially if they’ve arrived at the event and are scanning through the email to find what they need.

3. Provide important tax information

Tax time has likely been responsible for more trees being cut down than event ticketing. In 2018, 90% of individual taxpayers filed electronic returns, an all-time high, so it makes sense to provide the supporting documents they need in a digital format too.

The email below from Great Lakes alerts a student loan borrower that the amount of interest paid on their loans will be available soon. They helpfully note that the amount could be deductible on their taxes, and they clarify the exact time span, down to the hour on Dec. 31, for interest on payments received to qualify.

They make the relevant tax form available electronically, and they point out that the customer just needs the interest amount for their tax return, not the form itself, which will save them the cost of printing it.

4. Send a monthly bill

Triggered email is perfect for sending the kind of information that used to show up in an envelope with a clear plastic window. The email below from Dish Network lays out the basic information about the recipient’s monthly charges, along with handy links that go straight to the main tasks that people typically perform on the company’s website.

5. Process an insurance claim

Insurance claims have typically consumed a lot of paper, between physical photos of damage and reams of forms that need to be filled out. Allstate, however, has figured out how to make the process as paper-free as possible, as shown by the email below.

Insurance claims can be stressful, especially when the customer sees phrases like “Date of loss” (luckily, this one was a fender-bender), but Allstate makes it clear they’re ready to help with a triggered email that includes plenty of personalization. It even includes a link to a personalized video that explains the process.

Personalization is key in these kinds of emails because it makes the customer feel like the company is paying attention to their individual situation, rather than sending them a one-size-fits-all message. That includes not just the customer’s name but also relevant information like a claim number and the name and phone number of the claim representative.

After giving the customer the information they need, along with a nice big “Check Claim Status” button, Allstate includes links to learn more about their mobile apps and the customer’s claim payment options. Allstate’s mobile app offers a seamless, paper-free way to handle a claim, including taking and uploading photos of damage, viewing documents, one-tap agent access, and electronic payments.

Allstate’s mobile app even features digital proof of insurance cards, so a driver doesn’t have to fumble around in their glove compartment when pulled over.

From these examples, it’s not hard to see the positive impacts of triggered and transactional email on our environment. Happy Earth Day!

~ Craig

The post 5 Ways to Replace Snail Mail with Triggered and Transactional Emails This Earth Day appeared first on SparkPost.

What to Do When You’ve Been Listed on Spamhaus Fri, 19 Apr 2019 13:00:36 +0000 Spamhaus listingOur SVP of Deliverability Strategy, Kate Nowrouzi, explains what you should do if you've been unfairly listed on Spamhaus.

The post What to Do When You’ve Been Listed on Spamhaus appeared first on SparkPost.


Bad things can happen to good people. No matter how good of a sender you are, you may wake up one day to a Spamhaus listing. Many Internet Service Providers (ISPs) in the US and around the world take Spamhaus listings very seriously as?Spamhaus is one of the leading organizations that track spam-related email activity. Founded in 1998, Spamhaus protects consumers from companies and other entities that knowingly use email to send spam.

Spamhaus listings can affect both your IP addresses and domains (SBL, XBL, PBL, DBL, DROP, ROSKO).

Sparkpost’s amazing team is always available to assist you with resolving Spamhaus listings when they occur. We have automated checks in place to alert our team 24/7 when a Spamhaus listing happens. Of course, you can also choose to deal with Spamhaus directly if you prefer.

If you do end up taking matters into your own hands, here are the steps one should take when dealing with a Spamhaus listing. Do not email Spamhaus and request removal before you have identified the cause of the block and have an action plan in place to address the mistake.

  1. Email the Spamhaus team and let them know you are investigating what caused the block.
  2. Look into your logs. Usually, the bounce message received from the ISP has the IP and the listing included.
  3. Check messages that went out from that IP and see if you see anything suspicious.
  4. When you find out the reason that had triggered the listing, fix it immediately or if it is a wider issue, figure out a plan.
  5. Communicate the fix or the plan with the estimated time for implementation to the Spamhaus team.
  6. Once all of this is done, you can request removal by emailing Spamhaus. Your listing will not clear until you have secured your network– no exceptions!
  7. Make sure you have a solid plan in place to avoid future occurrences and communicate this with Spamhaus team as well.

Generally speaking, if you only target people who have opted-in to receive your email communications, you should not experience any Spamhaus listing. We highly encourage our customers to practice double opt-in to reduce the risk of mailing to misspelled email addresses which can ultimately trigger a Spamhaus listing.

Happy Delivering!

~ Kate

new rules email deliverability best practices

The post What to Do When You’ve Been Listed on Spamhaus appeared first on SparkPost.

Customer Acquisition and Loyalty in the GDPR Era: What Retailers in Europe Think [Survey] Wed, 17 Apr 2019 13:00:23 +0000 customer acquisitionDiscover some of the insights on customer acquisition and loyalty you will learn about in the new eTail Benchmarking Report.

The post Customer Acquisition and Loyalty in the GDPR Era: What Retailers in Europe Think [Survey] appeared first on SparkPost.


In Q1 2019, WBR Insights surveyed 100 Directors of Commerce from across Europe to find out more about the challenges they face and the innovative solutions they bring to the table. This month, WBR Insights released the eTail Benchmarking Report: Personalisation, Automation and Internationalisation, which reflects the retailers’ views on matters like customer acquisition and loyalty, business development and expansion, and operations.

According to the results of the survey, customer experience emerges as a defining factor for success for retail businesses in Europe, and investments in technologies and processes that can positively affect CX are on the list of their priorities for the coming year (47 percent for artificial intelligence for customer care, 41 percent for faster delivery, 29 percent for omnichannel enablement).

When asked to rank channels in order of priority for creating the optimal customer experience, web and email ranked first and second respectively. Email is proven to be a highly responsive and effective component of the marketing mix, impacting every step of the customer journey, and Retailers in Europe seem to believe that as well.

While email is considered a trustworthy ally, GDPR remains a concern for retailers in Europe. Almost one in two of responders (47 percent) believe that GDPR is the greatest threat to their eCommerce business. A year after implementation, the regulation is still perceived as an obstacle to the businesses’ commercial development plans, even a bigger issue than fraud (18 percent) or Brexit (22 percent). Things could be different though. As SparkPost’s Head of Marketing, Tracy Sestili, points out, “there is a hidden gem here; a unique opportunity for businesses to improve the quality of their database, focus on customers who are really active and engaged, and improve their email deliverability, as well as the efficiency and ROI of their marketing programs.” At the end of the day, trying to reach out to consumers who are disengaged or indifferent about the business’ products is unproductive, inefficient and can well be a waste of time and valuable resources.

Retail businesses are looking for ways to optimize their performance and efficiency without increasing expenditure. When it comes to driving customer acquisition, 43 percent of the respondents agree that email marketing is a significant tool for their business, while the decreasing conversion rate is their most common challenge. Another common challenge appears to be the increasing costs of current channels and tools used for new customer acquisition.

There was a surprising finding in this report. When asked about the methods currently used to encourage customer loyalty, personalized offers were mentioned by only 29 percent of respondents. Given the increased interest in customer experience and concerns about engagement and conversion, it is clear that retailers in Europe can look into segmentation and personalization to improve the overall effectiveness of their marketing campaigns.

You can download the full report here.

Happy reading!

~ Silvana

The post Customer Acquisition and Loyalty in the GDPR Era: What Retailers in Europe Think [Survey] appeared first on SparkPost.

Building an Email Archiving System: Searching and Displaying the Data – Part 4 Mon, 15 Apr 2019 13:00:41 +0000 email archivingIn the fourth installment of his blog series on building an email archive, Senior Messaging Engineer, Jeff Goldstein explains phase one of the Archive UI.

The post Building an Email Archiving System: Searching and Displaying the Data – Part 4 appeared first on SparkPost.


In the fourth installment of this blog series and the third in the coding phase, I’m discussing the first phase of the Archive UI (yes, I just said that). Leveraging the UI, an auditor can search for all activities for a given email address filtered between two dates; that will include the original rcpt_to address events and optionally, the cc and bcc events as well. That includes retrieving the email body and a boatload of other fun facts that SparkPost delivers with each event like subject text, campaign name, IP locations, client type used when opening, and much much more.

Just like previous blogs, the code for this version is available in my github repository. For this version, look at the step 3 folder. ?The diagram below depicts what part of the process this code is addressing; in this case, the UI (Viewing Application).


* This blog is addressing the process(s) in green

The look, feel and capabilities can and typically are vastly different for each designer. In my case I decided on a few principles before building my UI:

  1. I do not support paging. I’m assuming that an auditor is looking for specific emails and will want to see an exact email along with all of its details. Because of this, there is a configuration setting that will limit the number of entries that can be returned. That means that all of the corresponding data will be displayed on a single page; so be cognizant of the amount of data you will display in the browser tab so you don’t cause memory issues.
  2. Allow for in table filtering in order to limit calls to the database.
  3. Leave reporting for the next phase
  4. While I don’t show all the data that is captured by SparkPost, be sure to pull all of the data so it’s easy to display any data. This practice will also cause a lot of memory to be used by the browser.
  5. Since this is an auditing tool, it probably won’t be used very often so DON’T spend a lot of time building the UI; (Keep It Simple S****d , KISS method of design and development)

So with those simple principles, I have created an easy user interface that starts out with the user entering in an email address, a start date, and an end date. The system will then make a call to the database and compare the number of rows returned to the configuration setting that limits how many rows can be displayed. If the number returned by the database is lower than the limit; it builds the HTML table that is then displayed in the UI. Because I like to cause headaches for myself, I did dirty the waters up a bit by allowing the user to see the data in two different formats. One is just a simple table across the page, and the second is a condensed format that actually shows a little more data. Here are two small samples of the UI:

The one on the left is the wide version while the one on the right is the collapsed version. For the most part, they do show the same data, but I was able to get a few more items into the collapsed version without it looking too busy. The collapsed version uses a fixed iframe to display the HTML body along with the selected metadata for that event while the wide version displays the body and event data in a floating window.

Once displayed, the user can filter the displayed rows by typing into any of the five filters. ?I chose to allow for filtering on the subject, injection time, campaign, event type and UID fields. These filters do NOT care about upper/lower cases and do NOT care about placement. You can think of these filters as a contains filter. If the text is anywhere in that field, I’m happy and will keep that row.

If you examine the s3.php file, you will see that I added code for storing the HTML body of the email along with the EML object. ?After playing around with PHP email libraries in order to display the stored HTML portion of the EML?object; I didn’t like the results and came to the conclusion that storing the HTML body into s3 for displaying would be a better approach. This has worked out nicely and in the reporting phase of the project, I plan to support a download process for the EML?body from s3, in order to allow the auditor to display the email in their favorite email client.

Overall, the code is fairly straightforward except for the filtering code. Because I have two formats, and the collapsed format has a table within the table, finding the fields to filter on became a little messy. If you choose to make changes in that code, you will have to do some hunting to get to the correct fields.

So that’s a review of the UI. I have tried to keep it fairly simple and light since I don’t expect it to be used very often. The next phase, reporting may force me to make some changes, but that will be discussed in the next blog.

Happy Sending.

~ Jeff

The post Building an Email Archiving System: Searching and Displaying the Data – Part 4 appeared first on SparkPost.

Emailchella: How Music Festivals Send Email Fri, 12 Apr 2019 13:00:26 +0000 music festivals send emailCheck out a few examples of how some of the leading music festivals send email before, during, and after their respective events to facilitate great CX.

The post Emailchella: How Music Festivals Send Email appeared first on SparkPost.


A 2018 study found that a whopping 74 percent of Americans (millennials or otherwise) prioritize experiences over products. While there is no shortage of experiences to spend on, it’s hard not to associate the rising popularity of experiences with that of music festivals. In fact, forty percent of 20-29 year olds say they are interested in attending a music festival. And, since such events can cost a pretty penny it’s no surprise that festivals like Life is Beautiful, Outside Lands, and Coachella rely heavily on triggered and transactional email to keep attendees in the loop about just how much they’ve spent and to collect feedback about customers’ purchases. Check out a few examples below of how some of the leading music festivals use email to facilitate a great digital customer experience before, during, and after their respective events.

Before: Life is Beautiful

You’ve just spent anywhere upwards of $600 for your festival ticket, now what? Don’t worry– Life is Beautiful has got your back. As you can see in the below example, the Life is Beautiful organizers will send you a receipt confirming your purchase letting you know when you can expect your wristband in the mail. Additionally, they provide the answers to some wristband FAQs in their email template for your convenience. There is nothing worse than making a major purchase online and having nothing to show for it. Though the memories you make at Life is Beautiful may last a lifetime, the fear of not having a receipt for your pricey ticket should not. A quick transactional message letting you know your payment was received can provide a sense of reassurance that you did, in fact, purchase your ticket from a legitimate site.

During: Outside Lands

Like many music festivals, Outside Lands, gives festival attendees the option to load money on their wristbands rather than pay with cash or a card to keep food and beverage lines moving. While other festivals may be more opaque as to how those wristband funds can be spent,?at Outside Lands every time an attendee charges an item to their wristband balance they receive a transactional email. Between the festival ticket, travel expenses and tons of other charges it is easy for festival attendees to go over budget. Outside Lands’ quick transactional emails provide a digital paper trail for attendees who want to keep close tabs on their budget and for those who might be a bit too intoxicated…by the music to crunch their spending numbers on the spot.

After: Coachella

The end of a festival doesn’t mean it’s the end of an email program. While you’re busy editing your latergrams and perfecting captions like “take me back ??”, Coachella organizers are already at work strategizing on how to improve next year’s experience. In the below example, Coachella contacted attendees who had taken a shuttle to and from the festival grounds to collect feedback about the ride. This message triggered by the close of the festival shows the ability for email to contribute to a customer’s experience even after the event is over. More than that, the message allows attendees to give their two-cents about the shuttle which will allow the event organizers to address concerns and make next year’s festival even better.

While we tend to think of music festivals as memorable in-person events, triggered and transactional email serve to augment such experiences by keeping customers in the know digitally. With such a seamless customer experience to look forward to, all you have to do now is hit the mall to find that perfect pair of denim cut-offs to match your flower crown. Happy festival season!

~ Erica

The post Emailchella: How Music Festivals Send Email appeared first on SparkPost.

Breaking up the Monolith Monotony Wed, 10 Apr 2019 13:00:05 +0000 monolithTechnical Manager - Transmissions, Nate Durant, discusses the challenges of supporting an established monolithic code base.

The post Breaking up the Monolith Monotony appeared first on SparkPost.


Have you ever supported an established monolithic code base— we’re talking 5 to 10 years established? ?I think a decent amount of us have at some point in our careers. I’m not saying it’s bad, as monoliths have their benefits, but it can be difficult to present new opportunities and learning experiences with such an established code base. It also comes with its own unique challenges, such as slow deployments, limited testing framework, and other complexities. But it also comes with many benefits, such as performance, established policies, and flexibility. Many of SparkPost’s newer services are built using a microservice architecture with established testing frameworks, quick development and deployment times, and increased reliability. SparkPost has had great success with this architecture model and it is where our team is and wants to be.

For this discussion, I’ll focus mostly on our Transmissions API. This is by far our largest API endpoint in terms of requests, and also complexity. Since the API was completely written in our monolith, it was the main driver for the project for reasons I’ll touch on below.


I came on to my team about a year and a half ago as the Technical Manager. The team was a single, large, multi-manager group working out of one massive repository.? Although it was a monolith, the team had been very successful in developing a performant and extendable system for injecting and delivery email.

When I joined, the company was coming to the end of a multi-year re-architecture project encompassing many services and teams. ?Code deployments to production were going out about twice a week with the updates all done in-place. This, coupled with a complex and limiting test framework, lead to slow development pipeline.? This was hurting our velocity for new features, specifically around our Transmissions API and templating engine.

Getting Closer

About 8 months ago, two events coincided that really got the ball rolling in the right direction. ?The first was an engineering re-organization towards service based engineering squads. This broke up the one large multi-manager team I mentioned above into two smaller serviced based squads that had more control and autonomy over specific services in the monolith. ?One team took on the services as they related to the injection of mail, with the other team focused on mail delivery and policy. This lead to some issues as both sets of services were still in the monolith and a single repo, tying us together as far as deployments, bugs, and reliability. ?On the other hand, we had more ownership and responsibility for our specific services. This gave us more power to look at untying ourselves from the monolith and other teams.

The other event was the completion of the large, multi-year re-architecture of our software and environments that I mentioned above. This greatly reduced our operating costs and complexities. We no longer had to support tens of environments, but rather just a handful. The negative and real determining factor was that our monolith was hitting some scaling limits on the Transmissions API. We spent months trying to tweak, tune, and rework our system to increase stability and satisfy customer expectations. ?Although we did stabilize, we felt it was time to press forward with microservices, and received strong support from upper management.

How We Are Moving Forward

We’ve been on this journey for over 9 months, and I want to share some of the key steps we took that set us up for success. Our first decision was what tech stack to use. Our company has a large background in Node.js from other teams already building microservices, including a lot of tooling. On the other hand, we did have some engineers who wanted to look into Golang. We eventually went with what we knew, and while it may be obvious, try to stick with a single tech stack across your engineering organization. ?Having tooling and engineering know-how really lets the team hit the ground running versus stumbling through a whole new stack.

Next, we had a team of engineers that had been working in low-level languages (C/C++) for multiple years, and we wanted them to start building microservices in Node.js. Everyone was very excited to dive into something new, but we needed to establish good habits and best practices out of the gate. To help with this, we seeded the team with two very experienced Node.js developers from other teams (and eventually added two more). ?They provided training and guidance during the initial development. This was key to getting the team off on the right foot.

Now it was finally time to start breaking the Transmissions API out from the monolith. Instead of diving into our ultimate goal of replacing the complex services of the Transmissions API, we started with one of our simple CRUD API endpoints: Tracking Domains. We knew this could be broken away easily into a microservice and we needed to get the team trained and comfortable with the new architecture. We rotated in different engineers onto the new work while the others supported the existing service to ensure everyone had a chance to work on the microservices architecture and gain experience.

Where We Are Now

As of now, we’ve completed and released our new Tracking Domains API endpoint, built multiple new features using microservices, and are on our second phase of a complete architecture overhaul of our Transmissions API. ?We have completed a seamless migration to our phase one architecture into microservices for our company’s largest API, and are well underway into phase two. Given the extensive scope of the project, we broke it up into phases. This was essential to adhere to one of our core engineering tenants: always be shipping. Although our first phase required a full migration of customer traffic, it has put us into a great position to do incremental development of features directly into our new pipeline as we pull functionality away from the monolith.

To address some of the limitations stated earlier, our team is now deploying multiple times a day using AWS CodePipeline, versus our old twice a week deployments. All of our new features are in containers, with support functions in AWS Lambdas. Testing is seamless and actually somewhat enjoyable compared to our legacy framework, which is one of the highlights for the engineers. The best part, in my opinion, is that team morale is the highest it’s been since I started. Everyone is enjoying the flexibility microservices provide and finally moving our services to a modern architecture. We’ve even had a couple more transfers to the team because more people want to get involved with what we’re doing.

I hope some of these insights into how we are handled our transition are helpful. One good takeaway is to always set your team up for success. We ensured that the team had resources, training, and guidance to make the necessary transition to microservices. As such, the team morale is high, productivity is high, and our new architecture allows for faster product development. For our customers, this translates to an increase in the cadence of new features, scalability, and reliability, while decreasing our time to fix bugs and error rates.? Ultimately, this will lead to more growth both for our company and our customers while providing new and exciting work for our engineers.

~ Nate Durant
Technical Manager – Transmissions

The post Breaking up the Monolith Monotony appeared first on SparkPost.

Looping Event Booth Videos: Lights, Camera, Action! – Part 2 of 2 Mon, 08 Apr 2019 13:00:41 +0000 event boothOur step-by-step guide will teach you how to make your event booth video file play on a low-cost device such as an Amazon Fire TV Stick.

The post Looping Event Booth Videos: Lights, Camera, Action! – Part 2 of 2 appeared first on SparkPost.


In Part 1, we reviewed the who, why, and how of preparing good quality video for your event booth. Now we’ll take that video file and make it play on a low-cost device such as an Amazon Fire TV Stick.

Here are the steps we’ll follow:

  • Get your content ready, optimizing file size/quality
  • Fire up the TV stick
  • Install apps
  • Prepare for content download using a local web-server
  • Download video to the stick
  • Check the videos play in a loop
  • Stop the local web-server
  • Play video at the event

OK, that seems a lot – it will probably take you at least a couple of hours elapsed time, but it doesn’t need your total attention while doing updates, for example. Let’s dive in!

1. Get your content ready

In Part 1, we mentioned the tool MediaInfo, for checking video file formats in detail. Here’s what it says about our original file:

It’s a broadcast-quality file with a high bit rate of 43 Mbps. It’s over 350 megabytes for just over a minute duration. Apart from using lots of space, it will take a while to transfer to the stick – a pain if you’re stuck in the creative review/edit process.

Let’s recode that using the free command-line tool FFmpeg, to have smaller file size, yet good quality:

ffmpeg -i "Sparkpost-GDPR-original.mp4" -c:v libx264 -c:a copy -preset slow gdpr.mp4

Parameters here specify the input file, the video codec (libx264), the audio codec (copy-through). The “slow” preset is a shorthand way to say “give me the best compression”, and finally the output file. You can see the difference in input and output file size here:

-rw-------@ 1 stuck  staff   355M  6 Aug  2018 Sparkpost-GDPR-original.mp4
-rw-r--r--  1 stuck  staff    17M 15 Feb 12:05 gdpr.mp4

I saw no obvious quality difference between the original and the re-coded file, and it plays perfectly on QuickTime and VLC. MediaInfo shows it as:


2. Fire up the TV stick

Firstly, follow the instructions to get your stick connected to wifi. I suggest using a guest network rather than your personal or corporate wifi, for security reasons. That way your main wifi access point (SSID) and your password never needs to go on the stick. There’s no need to “save wifi passwords to Amazon” when you’re asked this.

Register with an Amazon account. Leave plenty of time for this, as the stick will probably download and install updates first. You can create a specific new Amazon account just for this task, or use an existing one.

After going through the built-in intro videos and skipping the usual streaming apps, you get to the home screen. You don’t need a Prime account for this project.

Using local storage on the stick

The Fire stick, in a domestic situation, is usually connected to stable wifi, streaming content from commercial services such as Prime Video, Netflix, or YouTube. Here, we are not going to rely on wifi or streaming to play the videos, We will only need wifi to download content to internal storage.

We’ll use an app that can download content to internal storage, and an app that can play content from it.

3. Install apps

Get VLC app

Go to the Home screen, select the Search icon. You might have to press “left” to get it to appear. Search for, and install the video player app VLC.

Get AFTV Downloader app

Older sticks have an SD card slot, which you can use to transfer content; the newer ones have internal Flash storage but no way to access it physically. Mine has around 4.5GB of internal storage, which is enough for a lot of video.

Follow these instructions to get the AFTV Downloader app. This will enable you to download files from a URL you enter using the remote.

4. Prepare for content download using local web-server

I’ve tried the usual file-sharing methods, however, the simple browser on the downloader app doesn’t make it easy to enter the needed long URLs, usernames and passwords.

There is a pretty simple solution to this: use your own local web-server, with a nice short URL and no usernames/passwords. If you already have a public server, then just drop your video file on there, enter your URL and download. The risk, of course, is that anyone (including web crawlers) could potentially find your file. You may not care – after all, the video is about to be seen by everyone at your event – but at least you know.

The simplest and most secure way is to run your own web-server locally. While this used to be a geek thing, it’s now simple. I recommend using a package such as MAMP (free version), available for both Windows and Mac OS X. If you run Linux, you probably know how to set up a web-server already!

MAMP is easy to install and configure. It supports PHP and MySQL, but here we will just use it to serve static files. You go to Preferences and select the specific folder to serve your files from. I recommend using a separate folder with nothing else in, as you are exposing the contents of that folder to anyone on your network.

As an additional safeguard, I connect my computer and the Fire TV stick only to my phone’s wifi hotspot at this point. This is protected with a password. The hotspot also gives my machine an IP address from a specific range.

As an additional check, my phone tells me exactly how many devices are connected, and I can shut down the hotspot as soon as we’re finished downloading. This doesn’t even use your phone’s data allowance, because the traffic is local.

Put your finished video file into the selected folder. Check your machine’s IP address, and open your browser at this address + the port number MAMP is using (the default is 8888). You should see something like this:If you click on the file, the video will play in your browser. Congratulations! You’re nearly there.

5. Download video to the stick

Ensure your Fire TV stick is on the same wifi network as your computer. Open the Downloader app and type in the same URL of your computer’s MAMP server, using the remote control, for example:

Download your file:

When it’s downloaded, you can choose “open” and VLC will play the video.

You can set a single video to repeat via the menus:

Next time, you can just open the VLC app, choose the file, and play. If there’s no obvious thumbnail of your video shown, you can find files in the “Downloader” folder, under “Internal Memory”.

6. Stop the local web-server

Now you can ramp down your ?MAMP by selecting “Stop Servers”.

You could leave your stick still able to access your phone personal hotspot in case you need to adjust things at the event, but this is not strictly necessary – you could remove wifi credentials from the stick to be sure. ?As an extra precaution, shut down your phone’s personal hotspot. You’re now ready for your event.

7. Play video at the event

On startup, the stick may nag you to connect to wifi. You can simply ignore this, but it becomes a nuisance trying to get to the home screen. If your stick still has your hotspot credentials, you can briefly enable your phone hotspot to get the message to go away; but there is another, better way. Just go to Settings / Applications / Manage Installed Applications / VLC / Launch Application. This works when you have no wifi connection.

Choose your video file, play, and set the repeat options.

Multiple videos in a loop

If you have multiple videos and want to play them in a loop sequence, go to the Video folder, press Play, and you’ll get a “Play All” option. Set the Repeat option but without the “1” in the middle:

You should see each video play in sequence.
It’s a wrap!
We’ve gone through a lot of steps here, so let’s summarise what we did, from start to finish:

? Get your content ready, optimizing file size/quality
? Fire up the TV stick
? Install apps
? Prepare for content download using a local web-server
? Download video to the stick
? Check the videos play in a loop
? Stop the local web-server
? Play video at the event

That’s it for now! Happy eventing.

~ Steve

The post Looping Event Booth Videos: Lights, Camera, Action! – Part 2 of 2 appeared first on SparkPost.

Don’t Commit: A Guide to Avoiding Distractions While Coding Fri, 05 Apr 2019 13:00:41 +0000 avoiding distractions while codingManager of Software Engineering - Analytics, Robert Wenner, shares his tips and tricks for avoiding distractions while coding.

The post Don’t Commit: A Guide to Avoiding Distractions While Coding appeared first on SparkPost.


Multitasking is good for processors but bad for people. Each interruption breaks concentration and flow. Each context switch is an interruption. According to Tom DeMarco and Timothy Lister’s classic book Peopleware, it can take up to 15 minutes to get back into the flow after an interruption. As a programmer, how much work do you get done when you’re constantly interrupted? How many interruptions until your workday is fragmented into tiny pieces of frustration?

Maybe it’s not even others interrupting you– maybe it’s the code itself. You look for something in some part of the code and notice an odd method. Should that still be here or is it dead code? You skim some function body and wonder if it covers a special corner case that comes to mind. While programming, we keep many details in our heads. How can you not lose all those details? How can you keep in the flow, and at the same time not forget about what just caught your attention?

Get a good-ole to-do list! Leave yourself notes, but not on paper– that would be a medium switch, and even looking for pen and paper may disrupt your flow. On top of that, you may lose notes on paper or forget about them. What use is the note if you don’t come back to address it? Preferably you’ll want to check your notes before you commit your changes and/or decide if the notes merit a separate commit.

Here’s where DONTCOMMIT comes in. Just put a comment in the code, mark it with DONTCOMMIT, and leave yourself enough explanation on what you wanted to do here. For example:

// DONTCOMMIT do we still need this?
// DONTCOMMIT doesn’t seem to handle -1

Then go back to what you were doing, without breaking flow or concentration. It’s like the TODO and FIXME items you probably already have, only better.

These special DONTCOMMIT comments stand out in the code. If you happen to have DONTCOMMIT somewhere else in your code, feel free to pick something else. You now have a unique marker for these notes. You can

?for that marker in the shell. Your IDE can probably be configured to highlight and show the markers as todo items. For example, in Eclipse, go to Preferences and search for “todo”. You’ll find it in? Java -> Compiler -> Task Tags, where you can define your new tag. Once that is done, Eclipse will put a blue marker on the right-hand side of that line, and a little icon on the left. Your new tag will also show up in the Tasks list (Window -> Show View -> Tasks).

IDE is nice, but it’s still easy to forget those DONTCOMMIT items. Luckily, version control systems support hook scripts, so you can register a hook script that looks for your marker (e.g., with

?) and rejects the commit if it finds the marker. Automatic reminders!

For example, in Subversion you’d place a script like the following in your repository’s

? and call it from
?or just put the following in
?(and make it executable):

set -u
while read file
???for bad in "DONTCOMMIT"
???????found=$(svnlook diff --transaction "$TXN" "$file" | grep "$bad")
???????if [ -n "$found" ]
???????????echo "Found $bad in $file:" >&2
???????????echo "$found" >&2
???????????exit 1
done < <(svnlook changed --transaction "$TXN" "$REPOS" | cut -c 4-)
exit 0

For git, the hook scripts go in

?and look like this:

set -u
while read file
???for bad in "DONTCOMMIT"
???????found=$(git diff --staged "$file" | grep "$bad")
???????if [ -n "$found" ]
???????????echo "$bad found in $file:" >&2
???????????echo "$found" >&2
???????????exit 1
done < <(git diff --staged --name-only)
exit 0

While your hook is already looking for DONTCOMMIT, have it do more! You should also check for DONTCOMIT, DONT_COMMIT or any other “creative” spellings. If you want to take a quick note you shouldn’t be bothered to get the tag name exactly right. Keep in the flow, let the hook script take care of it by adding your favorite spelling errors.

Another idea is to flag your username so that you don’t check in hardcoded paths that only work on your machine. Reject?

, and other forgotten printf debugger statements. Reject any
// IDE generated stub
, and so on.

Mark your code, keep in the flow and let your version control system do the grunt work for you.


The post Don’t Commit: A Guide to Avoiding Distractions While Coding appeared first on SparkPost.

The Anatomy of a Successful Financial Services Email Wed, 03 Apr 2019 13:00:21 +0000 successful financial services emailWhen writing a successful financial services email consider how the head, body, and footer of your email work together to help deliver the results you want.

The post The Anatomy of a Successful Financial Services Email appeared first on SparkPost.


Whether you’re sending someone a transactional email that confirms an action they’ve taken, or a promotional message that informs them about a new financial services product or a special offer, you’ll want to consider how the head, body, and footer of your email work together to help deliver the results you want.

That’s important because incoming email servers will perform checks on your email when they arrive, and you’ll have just a few seconds to convince recipients to open your message when it hits their inboxes. That process is not unlike the way people make an assessment of someone when they enter a room, based on the way that person dresses, acts, and talks.

Your Email’s Reputation Will Precede It

Just like a person’s reputation affects how others interact with them, each email you send will be impacted by the cumulative impression made by your previous messages. Sure, you’re not a spammer, but there are still a couple of things you need to keep in mind to ensure that your emails put their best foot forward, so to speak.

Build your sender reputation

When recipients don’t bother to open your messages, your emails bounce back, or people report your honestly legitimate emails as spam, your organization’s sender reputation suffers. That means your messages will have a harder time getting past the gatekeepers at Gmail, Yahoo!, and other email providers.

Keep best practices in mind by:

  • Honoring unsubscribes as quickly as possible
  • Adopting an opt-in policy
  • Pruning dead email addresses
  • Looking closely at bounce codes
  • Making your emails worth people’s effort to open them and click a link or two
  • Creating and executing a warm-up plan before you start sending emails from a new IP address

Create trust in your business

Even if your sender reputation is okay, consumers’ trust in your organization can suffer when they receive malicious phishing emails that seem to be from your company. Implement SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail), both of which are authentication standards that help incoming mail servers verify that messages are coming from a legitimate source.

Don’t stop there, though: Top them off with DMARC (Domain-based Message Authentication, Reporting, and Conformance), which unifies SPF and DKIM. It allows you to declare how an email should be handled if it fails an authentication test, so you can stop fraudulent messages from getting through. DMARC also gives you the ability to receive reports that help you troubleshoot authentication issues and identify malicious domains.

Make an Introduction With Your Header

After your email makes it to recipients’ inboxes, you need to make a great introduction and give them a reason to open the message.

Choose personable “from” and “reply-to” addresses

Avoid a generic “no-reply@” address that says it’s from Online Sales or something else equally bland. Your “from” address and name should be friendly and make customers feel like you’re talking to them personally. Make sure you use a “reply-to” address that’s functional and sends the reply somewhere useful, such as the customer’s CRM record.

Get attention with a strong subject line

There’s an art to a great subject line.

  • Keep it short: six words, or about 50 characters, at the most
  • Use more than first name personalization – try referencing their activity, their location, or an account balance
  • Emojis can add some fun, but use them very sparingly and double-check your choices at a site like Emojipedia to ensure they render properly in various email clients
  • Create urgency with a deadline
  • Try a straight-forward approach for transactional emails

Don’t neglect the preheader text

The preheader is the text that email clients, including all mobile ones, display below the subject line. If you don’t specify what it should be, the recipient will often see the first several words of the email, which are usually something like, “To view this email with images, click here.”

Since that’s a poor experience, you’ll want to use the preheader text to help sell the introduction to your email. Don’t simply repeat the subject line – offer complementary messaging, such as the deadline for your special offer or a key feature of the new software someone just installed.

It’s okay to try again

Just like someone can do everything right when walking in a room but not make the connection they desired because of reasons beyond their control, it’s possible for your emails to get lost in the shuffle because something like a major news event was occupying people’s attention.

If your open and click-through rates are poor but you think your content was good, you can always send your email again, but make sure you change the “from” and “reply-to” addresses, the subject line, and the preheader text. No one wants to hear the same introduction twice.

Prompt the Action You Want With the Email Body

Getting someone to open your email is simply the first step in a successful interaction with a customer. Now you need to seal the deal by giving the recipient a reason to click at least one of the links.

The first thing you’ll want to do is make sure all your emails are mobile responsive, which means they’ll automatically adapt to the devices being used by your recipients, whether they’re phones with small screens or computers with large displays. Everything, including text and image sizes and layout, will adjust on the fly to offer the best possible experience.

You’ll also want to include high-resolution images since HD displays are quickly becoming the norm on most mobile devices.

Examples of successful marketing emails

Both of these emails are simple but effective. They use small blocks of text and employ bullet points as much as possible – big chunks of text are hard to read and can be tedious on a mobile device. These emails also rely on basic layouts and a couple of key images to get their messages across, so they’re easy to digest.

This Wells Fargo marketing email’s goal is to inform customers about a new feature and encourage them to sign into their accounts and give it a try. It even goes out on a limb a little with a fun subject line that plays off the idea of snapping a photo.

This email also doesn’t distract the recipient with multiple calls-to-action and a barrage of information. It has one CTA button and includes a few useful secondary links.

This message from Toyota Financial Services uses Giving Tuesday, the first Tuesday after the Thanksgiving holiday in the US, as a springboard for promoting the company’s charitable efforts. Like the Wells Fargo email, it focuses on a single call-to-action and makes all the other links secondary. It also ties into a well-known event, which can help increase open rates.

Take Care of Little Details in the Footer

No one wants their customers to walk away, but giving them the ability to do so, as well as offering a way to for them to contact you, is legally required in many places. You also need to include a clear statement that explains who sent the message and why it was sent since sometimes people forget how they ended up on your email list.

When customers say “Don’t email me, I’ll email you”

It doesn’t feel good to know that a few people will click the unsubscribe link at the bottom of your email, but you don’t want uninterested subscribers on your list. They’ll not only hurt your open rates, but they can harm your sender reputation too.

Make sure the unsubscribe link is on its own line and uses a font size that doesn’t require zooming in to see. No one appreciates it when a company tries to hide its unsubscribe link, and doing so just increases the chance that people will report the email as spam to get off your list.

However, when people click the unsubscribe link, there are a few strategies you can use to keep the relationship going in some fashion.

  • Encourage them to opt down: Offer an email preference center that lets customers choose less frequent emails or different types of mailings. Maybe they’d rather have a monthly product update rather than a weekly sales piece.
  • Give them other channels to stay in touch: Make sure your unsubscribe page includes links to your social media accounts, as well as other places where they can stay in touch in a more informal way, such as a blog.
  • Ask why they’re leaving: Did they sign up by mistake? Are they not interested in what you’re offering? Give unsubscribers a short survey that can help you surface other communication options for them. And even if they still leave, you’ll still get valuable insights to help your marketing strategy.

Keep Your Customers Happy

Even if you do everything right and a customer opens your email but doesn’t take the action you desire, your relationship with them will still be in good standing. They’ll remember that it was a satisfactory experience, and maybe next time you’ll seal the deal.

~ Casey

The post The Anatomy of a Successful Financial Services Email appeared first on SparkPost.

Sending Personal Health Information (PHI) with SparkPost Mon, 01 Apr 2019 13:00:18 +0000 PHIRead up on how healthcare organizations might consider sending Personal Health Information (PHI/ePHI) to maintain HIPPA compliance.

The post Sending Personal Health Information (PHI) with SparkPost appeared first on SparkPost.


I was recently asked how a healthcare organization can send PHI/ePHI (Personal Health Information) safely through SparkPost. The quick answer to that is really pretty simple — please don’t. Email is inherently insecure and no matter how many solutions we (or others) provide, at the end of the day, that email is still going to end up in someone’s unsecured, unencrypted mailbox.

If you need to send PHI, we recommend you email a call to action for your customers to log into your own secure web portal to retrieve the sensitive documents, rather than sending the actual data. Send your customers a quick note that says something like this instead.

????“Hi Bob, Your documents are available for review. Please click <here> to login to your secure portal to view.”

On your end, the smaller message will be sent faster, is less likely to be blocked as spam, and contains no PHI. As a result, the requirements of HIPAA (Health Insurance Portability and Accountability Act of 1996) are not triggered and thus no Business Associate Agreement (BAA) with SparkPost is required. Additionally, your customers will appreciate your sensitivity to their secure data. The smaller message is easier for the customer to read and is more accessible on multiple devices which is an important factor in today’s mobile world.

On the topic of sending sensitive information, the SparkPost team has created many ways to send a secure email. Our top priority is our customer’s email and security is one of the highest considerations on our checklist every time we deploy a new feature. All email from our system is sent with opportunistic TLS security enabled by default – no matter who you are. We are fully SOC2 (SSAE-16) compliant in all domains. We were months ahead of the industry with GDPR compliance. We support and have had seats on boards and steering committees that guide our industry in matters of security, compliance, and anti-abuse efforts. If anyone is going to find a solution to the email security problem, it will be this team.

Earlier this year, my colleague Steve Tuck completed a 5-part series on how to implement S/MIME using SparkPost. This is one of the oldest email security solutions and has been largely forgotten by the industry as a whole, but it still works, and it puts the end-to-end security in the hands of the sender and recipient. A health care agency wanting to send encrypted and/or digitally signed messages using our service should be able to deploy that solution with relative ease. Steve walks you through all aspects of understanding how it works and how to integrate with your SparkPost account.

Some time ago, I also wrote a piece about our partnership with the security company Echoworx. ?In that blog post, we introduce you to how SparkPost can accept mail from Echoworx to deliver to your end users in a secure way without any complex integration. Echoworx provides a middleware solution that empowers you to control who can see the message and attachments and when. You also have the ability to REMOVE access to an email you have already sent.

SparkPost leads the industry in security efforts and we are constantly adapting to the shifting threat landscape. ?Please review the referenced links above and don’t hesitate to ask anyone on our team if you need more information.

~ Tom

The post Sending Personal Health Information (PHI) with SparkPost appeared first on SparkPost.

What Does It Take to Send Billions of Emails? Wed, 27 Mar 2019 13:01:20 +0000 high-volume emailHigh-volume email can be mind-boggling to someone who isn’t steeped in the business. Here’s some real-world advice for tuning Momentum email infrastructure.

The post What Does It Take to Send Billions of Emails? appeared first on SparkPost.

  • This blog post was originally published on 2/24/2016 and was updated on 3/27/2019

When it comes to transactional and marketing email, there are email senders, there are high-volume email senders, and then there are really high-volume email?senders. Most of us can grok the amount of email that a small or medium sender generates in a typical month, but the volumes at the higher end of the spectrum can be a little mind-boggling. Especially to someone who isn’t steeped in the business of email deliverability.

Setting aside the bad guys like spammers, there’s nothing inherently untoward about sending very high monthly volumes. Just think for a minute about large e-commerce retailers that generate several email notifications (order confirmation, shopping cart abandonment, shipping notification, etc.) for each transaction. Or a social network that sends emails in response to activity and engagement (friend requests, likes, retweets, etc.) on their platform.

It’s really a question of basic math. When you have a large number of users (5–20 million) who receive multiple messages per day, or a really large number of users (40–50 million) receiving one message per day, you’re in high-volume email territory. And that’s just to get past the velvet rope; the highest volume senders like Facebook or Twitter send 1–10 billion emails per day. (I tend to hear Carl Sagan’s voice in my head: “billions and billions of emails…”) The numbers add up really, really quickly.

To be sure, it’s an exclusive stratosphere of senders who reach the very highest monthly volumes, but the tools and practices they’ve developed to do it are applicable to all senders who rely upon email to drive their business. It’s a multi-dimensional challenge: complexity and scalability of message generation, throughput of sending, and deliverability on the receiving end. And it’s a challenge my colleagues and I spend a lot of time helping senders solve. Here are some of the best practices we’ve learned that could help you, too.

First, Pick the Right Platform

As I suggested above, a company’s particular characteristics and business needs have a big impact on what its email looks like. But, in my experience, senders tend to fall into four basic groups:

  • Low volume/complexity who want a cloud solution
  • High volume/complexity who want a cloud solution
  • Low volume/complexity who want an on-premises solution
  • High volume/complexity who want an on-premises solution

For purposes of this framework, “low volume” means sending less than 10 million messages per month, while “low complexity” means business logic like filtering, routing, or content manipulation aren’t performed in the messaging layer. “High volume” and “high complexity” suggest the opposite. (Clever nomenclature, right?)

Here, I’m going to step back and make a small product plug: One of the real advantages of our SparkPost cloud offerings is that our cloud is highly elastic and will scale to meet nearly any load. The efficiency of that model for most senders is really hard to overstate. Just as importantly, SparkPost’s operations team—not your own staff—deals with the details of managing messaging performance, scalability, and deliverability, letting you focus on business differentiation and strategic value.

Now, having said that, we know that not every business is ready to use the cloud today. Some may elect for a hybrid cloud/on-premises architecture. Awesome. Others will want to keep email infrastructure completely in house. We get it. Different businesses have different needs. That’s why SparkPost offers a solution for each of these four categories of sender.

If you use PowerMTA, be sure to check the wealth of PowerMTA resources at Port25 to optimize your installation. And, of course, SparkPost customers get the benefit of these best practices and many more courtesy of our cloud infrastructure and crackerjack ops and deliverability teams. But for the rest of today’s post, I’m going to give some love to folks that are using Momentum.

Making the Most of Momentum

I’m just going to say it: Momentum users really get what high-volume email is all about. (And, by the way, the Momentum platform is a core underpinning in the SparkPost cloud.) Over the years, our services team and our expert customers collectively have developed a lot of expertise about what it takes to optimize this ultra-high performing email platform.? Here’s what we’ve learned works in the real world.

  • Parallelize Processes
  • Remove Bottlenecks
  • Optimize Queues
  • Be Scientific

I’ll touch on each of these areas below.


The Momentum platform was designed as a parallel solution, and there are several areas that benefit from being parallelized when working with Momentum:

  • Inject messages using multiple parallel processes. The scheduler-based architecture leveraged in Momentum provides maximum performance when handling incoming traffic from multiple sources. Injecting across multiple connections will provide maximum performance.
  • Send across multiple IP addresses. Not only will many ISPs have a limit on how much traffic they will accept from a given IP address, but separating traffic streams in to separate IP pools can also help with deliverability.
  • Scale horizontally. Our recommended installations start at three nodes per role to ensure redundancy and availability, and each role can be scaled independently as needs increase from either a sending or reporting perspective.

Remove Bottlenecks

With the right platform, and sufficiently parallel injectors and sending IPs, the next key to sufficient performance is to remove common bottlenecks that can affect platform performance. The most common areas are hardware and network bottlenecks, and will be covered in the next sections.


With the 3.6 release of Momentum, a new performance benchmark was achieved through the introduction of the new SuperCharger architecture. With SuperCharger, the scheduler-based architecture that enables Momentum’s performance was parallelized to allow for multiple schedulers to operate in a single Momentum instance. The new SuperCharger technology allows for significantly improved vertical scalability, with a properly provisioned supercharger-enabled Momentum instance able to send several times the volume of a non-supercharger instance.

The development of SuperCharger has continued to improve performance through Momentum 4.2 and now into the imminent release of Momentum 4.3.

With the use of SuperCharger, Momentum instances can leverage multi-core server architectures, moving the hardware bottleneck to disk IO. Physical disks in a RAID-10 configuration can provide performance in the range of 2-4 million messages per hour, while SSDs can double that, and PCIe-based SSD systems such as FusionIO can help reach performance in excess of 10 million messages per hour.

In addition, Momentum’s caching system improves performance and can leverage a large amount of RAM; typically we recommend 4GB of RAM per core.

Performance can be increased through additional cores (with accompanying memory) and higher performance IO systems. Investments in larger systems can be balanced against scaling horizontally with more servers, leveraging the clustered capabilities of Momentum.


With the increased performance available through the SuperCharger architecture, it becomes increasingly important to ensure that the supporting network is capable of handling the bandwidth generated by a Momentum instance, let alone a cluster of nodes.

The following recommendations are made regarding network bottlenecks:

  • Isolate network connections for injection, delivery, and administrative traffic. By separating inbound and outbound traffic you effectively double the available bandwidth to the server.
  • Move to 10GigE Ethernet. A fully provisioned server with PCIe SSD technology can push enough traffic to saturate Gigabit Ethernet.
  • Use bonded NICs to increase availability and to increase the available bandwidth. For many senders bonded Gigabit NICs with separated injection and delivery pathways can provide sufficient bandwidth without a move to 10GigE.

Optimize Queues

As mentioned earlier, spreading traffic across multiple IP addresses has multiple benefits:

  • Each IP address will be assigned to its own Binding, meaning that messages will be isolated to their own queues, helping to prevent queue collisions.
  • Multiple IPs allows you to send sufficient traffic to ISPs that have restrictions on incoming traffic on a per-IP basis.
  • Separating message streams to their own IPs and bindings enables Adaptive Delivery to be more effective at automated traffic shaping by giving it more granularity.

While the number of IPs you will need varies based on sending reputation, at a minimum make sure that you separate out traffic into bulk and transactional. A general guideline is to use one IP address per 100,000 messages per hour you will be sending.

When configuring multiple IP addresses for the same mail stream, take advantage of the Binding Group capability of Momentum to allow for common configuration and easy round-robin IP assignment by assigning to the group.

Be Scientific

As you work with the recommendations in this article, focus on making one adjustment at a time and measuring the results before making further changes. For example, when adjusting the number of injectors, try adding five connections at a time and measuring throughput in order to identify the ideal number.

Similarly, with some of the tunables, start by reviewing data to identify current throughput, then calculate an appropriate setting before testing.

Common Performance Pitfalls

In addition to the overall best practices I described above, I’d like to make special note of a few issues for senders looking to highly tune their infrastructure to improve performance.

Memory Tuning

There are three key memory settings that are often overlooked and left at their defaults:

  • Max_Resident_Active_Queue
    ?: Controls how many messages are cached in memory on a per-queue basis. Set to either -1 or a larger number like 10,000 if you have sufficient memory.
  • Max_Resident_Messages
    ?: Controls how many messages are cached in memory on a server-wide basis. Set to 90-95% of RAM divided by
    ? (default 16k). I.e. 96GB / 16k = 6,000,000
  • Growbuf_Size
    ?: Configured the size of memory chunks used to cache messages.? Ideally we want the average message loaded in a single chunk. Set to larger than your average message size (but not to your max message size).


One key advantage of using Momentum is the ability to implement policy scripts to achieve complex message and server manipulations using automation. In older versions of Momentum, policy was implemented using a scripting language called Sieve++, an extension of the Sieve filter language used in several messaging tools.

With Momentum 3, we introduced a new option for policy scripting in the Lua scripting language. Lua provides a more robust and extensible scripting language that is better optimized, and which supports the multithreaded SuperCharger architecture. All users looking to leverage SuperCharger and generally increase performance should migrate their policy scripts to Lua.

In Version 4.x we went a step further and made significant improvements to Lua so that Sieve can (and should) be replaced entirely to maximize performance.


In recent releases of Momentum we have introduced support for OpenDKIM as a module. The advantage of OpenDKIM signing is that is has multi-threaded support, enabling higher performance when used with SuperCharger. Moving to OpenDKIM is quite straightforward and requires minimal configuration changes.

Headers in Custom Logs

One advantage of Momentum is the ability to use the custom logger module to create log files that contain only the data you need, in the format you prefer. One logging macro available to senders is

?, which will capture a named header and place its content into the log line.


? macro comes at a cost: It parses the whole message on each event to find the header and record its contents. A better-performing alternative is to use a Lua script to read the header and place its value into a context variable, then use the
?macro to load the context variable into the log.

An even more efficient option is to write those header values as metadata directly instead, using the SMTP-API introduced in Momentum 4.x. This way the message is consumed to the reporting bus immediately and can be pushed as a real-time webhook to automation and reporting services directly.


I can’t tell you how cool it is to see how Momentum and SparkPost are being used out in the real world by high-volume/complexity email senders. I’m thrilled to be able to share these recommendations to help optimize a Momentum installation for maximum performance.

By the way, want to learn more about getting the most from your email infrastructure? The SparkPost Support Center has a wealth of operational advice. And, if you’re interested in learning more about hybrid on-prem/cloud email solutions check out our guide: The Best of Both Breeds: 5 Use Cases for Hybrid Email Infrastructure.

~ Mike Hillyer


The post What Does It Take to Send Billions of Emails? appeared first on SparkPost.

]]> 2
AMP It Up: AMP for Email on SparkPost Is Here Tue, 26 Mar 2019 16:01:50 +0000 amp for emailGmail has launched AMP for Email, and we’re very excited to announce that SparkPost customers now have the ability to send AMP emails from SparkPost.

The post AMP It Up: AMP for Email on SparkPost Is Here appeared first on SparkPost.


Over the past several months, SparkPost, in collaboration with the Gmail team at Google, has been working with senders like Pinterest and to empower them to develop engaging, interactive emails using AMP for Email technology. Gmail officially launched AMP for Email today, and we’re very excited to announce that SparkPost customers now have the ability to send AMP emails from SparkPost.

To mark the occasion, I wanted to share some of the reasons we think you’ll be excited about this new capability, too. Read on to learn:

  • What AMP for Email is all about
  • Some great examples of how SparkPost customers are innovating with AMP for Email
  • How to get started with AMP for Email on SparkPost

What is AMP for Email?

Google and the publisher ecosystem spearheaded the open source AMP (Accelerated Mobile Pages) Project to help publishers develop fast web pages that are optimized for mobile clients. Since its launch in 2016, AMP has had a large impact on the mobile web user experience and engagement.

Now, AMP for Email adapts the AMP technology to the unique needs of the email inbox. AMP for Email gives senders the ability to enhance messages with interactive and data-driven features that have the potential to transform the way recipients interact with messages.

AMP for Email provides email developers with a set of rich components that include carousels, responsive form elements, and—maybe most exciting of all—the ability to dynamically retrieve fresh content that updates even after a message has been sent. Email recipients can view and interact with AMP components directly in the email, without leaving their primary inbox experience.

AMP for Email Compared to Past Forms of Interactive HTML Email

It’s true that the idea of interactive email per se is not new. After all, senders have had the option of using HTML to engage email audiences with compelling and eye-catching content for some time. But, HTML support in email has always been a limited subset of what we expect from the web. And perhaps most limiting, once a message was sent, the content was more-or-less frozen in time.

Just consider an airline ticket receipt. If you’re like me, you’ve often saved these to keep track of flight details. But that information isn’t fixed—for example, flights are late, and gates frequently change. More often than not, the information in my original flight confirmation email is stale.

So one of the big leaps we think AMP for email brings to senders and recipients alike is the ability to include live, up-to-date content directly to the email. Gate change? Next time I open my receipt, that info can be presented.

Another area where we think AMP could be a game-changer is better alignment with users’ expectations of security and privacy—i.e., eliminating some of the ways crude HTML makes phishing more likely. While there’s no bulletproof solution against this sort of risk, AMP for Email does include modern phishing and spam mitigation strategies not possible with straight HTML. We’ve found it also implements a relatively conservative subset of AMP functionality, an important aspect of containing overall exposure to risk.

SparkPost Customers Innovate with AMP for Email

It’s not hard to come up with compelling use cases for AMP for Email. An email from a social app, for example, might allow users to react to shared posts just as they do within the app, but without leaving the email. In fact, Pinterest is enabling just that. Pinterest’s AMP emails allow Pinners to view and save items to a board with a great user experience very similar to what they’d experience in the Pinterest app.

Example of Pinterest AMP-enabled email also is implementing AMP for Email by focusing on content and interaction models that their users would expect to find on their mobile app or website. An example of that is using AMP to display rich content and preview destinations directly within the email.

Example of AMP-enabled email

But rather than take my word for it, listen first-hand to the teams at Pinterest and Zillow as they share how they plan to implement AMP for Email.


How to Get Started with AMP for Email on SparkPost

SparkPost has been working with the Gmail team to make sure that our customers who wish to use AMP in their messages can hit the ground running. Our initial implementation provides support for AMP in several ways:

First, we make it easy to send AMP-enabled messages. The SparkPost Transmissions API supports a new optional field in the content JSON object: content.amp_html, a UTF-8 encoded string representing the AMP for Email HTML content. SparkPost will insert this as a text/x-amp-html MIME part in the appropriate location of the MIME tree, perform engagement tracking (if enabled), and insert substitution data as expected.

(What if you inject messages via SMTP but want to send AMP-enabled messages, too? No problem! Be sure to use the proper MIME structure; text/x-amp-html must be a descendant of multipart/alternative, and live alongside at least one of text/html or text/plain MIME parts.)

Second, SparkPost has AMP-specific engagement metrics. Basic engagement tracking for opens and clicks are supported through an AMP-specific tracking pixel. As a result, senders can separately report and compare AMP opens and clicks with traditional HTML opens and clicks in SparkPost analytics, Events API, and Webhook events. Down the road, we may provide additional, advanced engagement tracking for AMP messages, depending upon our customers’ needs.

Last, but not least, we have added support for AMP in SparkPost templates, including metadata and substitution data in a template’s AMPHTML MIME part. In other words, SparkPost templates make it easy to implement AMP content, and we treat AMP content as a first-class citizen along with regular HTML and plaintext.

Additional, hands-on detail about implementing AMP for Email in SparkPost supports AMP for Email can be found in our Knowledge Base.

Share Your Thoughts!

I’d love to hear what you plan to do with SparkPost’s support for AMP for Email—and how you’d like to see from AMP for Email and our capabilities evolve as we move forward.

—Isaac Kim
Technical Product Manager

The post AMP It Up: AMP for Email on SparkPost Is Here appeared first on SparkPost.

Building an Email Archiving System: Storing the Email Log Data – Part 3 Mon, 25 Mar 2019 13:00:36 +0000 In part 3 of his series on email archiving Senior Messaging Engineer, Jeff Goldstein, explains the process of storing log data associated with the email.

The post Building an Email Archiving System: Storing the Email Log Data – Part 3 appeared first on SparkPost.


* This blog is addresses the process(s) in green

In the third installment of this blog series and the second in the coding phase, I’m diving back into the process of storing the log (event) data associated with the original email. This step will give us the information around the email injection, delivery and behavioral actions by the email recipient(s). While this blog is similar to the blog I wrote recently on storing all event data for an email, there is enough of a twist in order to support the archiving of the email body that I decided to keep the two blogs separate. This blog will also offer up some sample code for storing the data into a MySQL table. (Please refer to the following Github repository)

When an email is created, SparkPost logs each step of the email and makes the data available to you for storage via API or Webhook technologies. ?Currently, there are 14 different events that may happen to an email. Here is a list of the current events:


Bounce Click Delay
Delivery Generation Failure Generation Rejection
Initial Open Injection Link Unsubscribe
List Unsubscribe Open Out of Band
Policy Rejection Spam Complaint

* Follow this link for an up to date reference guide for a description of each event along with the data that is shared for each event.

Each log event that corresponds to our archiving project will have a special tag named uid within the metadata block. As described in the previous two blogs, the uid is an application generated field which is generated by your email injection systems during the email send process and placed into the X-MSYS-API header and the email body via a hidden html field. ?The uid field in the email body will be the only id that survives through all emails and logging events and thus is needed to pull everything together (remember that the inbound event data does not have the UID metadata, that is why we must hide the id in the email body). But all of the event log data in this step will have the UID entry that we need.

"raw_rcpt_to": "",
"rcpt_meta": {
	"UID": "0093983927113301"
"rcpt_tags": [],
"rcpt_to": "",
"rcpt_type": "archive",
"recv_method": "esmtp",

SparkPost webhooks have the ability to allow the user to pick which events they want to be delivered to their endpoint (collector), but they don’t have the ability to filter specific events given specific data. For example, what if you sent welcome emails to your new customers and you only want open events with the subject line of ‘Welcome’ sent to a specific endpoint? Nope, can’t do that. You can filter on the click event, but not on given data within the subject field. That means that our endpoint will get all events of a given type (open, click, bounces, etc) and we need to filter out the data that has nothing to do with our archive process. To filter out the noise, we will search each event for the UID field within the metadata block. If the event has the UID field, then we care about that data; otherwise, we skip that data event (that also means, that the field name that you use for the UID needs to be unique to this project).

* Note: SparkPost does have the ability to filter events for subaccounts. To simplify the storing code, you could send all emails that need to be archived through a specific subaccount. ?That would allow SparkPost to filter out the events for just that subaccount and only send those events to your collector. ?It won’t save you a lot of code, but this is an option.

In this phase of the code, I have an endpoint that captures and stores all events from SparkPost into a directory. That is all the work the endpoint does. This follows the best practice of doing as little work as possible within the endpoint, so it can keep up with how fast SparkPost may be delivering data to that endpoint (this is the retrieveWebhook.php code). Being honest, this is NOT the approach I did with the first phase of the project when I stored the archive body. I do plan on going back to fix that at a later date.

The next step will be for a cron job or group of cron jobs that will read the directory of files and start processing them (this is the processOutboundWebHooks.php code).

In order to support high volume sending, I expect that this code may have multiple instances running in parallel. ?So I have the code read the list of files within a directory and try to lock the file it wants to process. If the lock process works, it will proceed; if the lock process doesn’t work, then it’s assumed that another process is working on that file and skips that file and go onto the next one in the list. Once your code has a file, we need to turn the data into an array and start to process each event separately. But remember, we only want the ones with the uid field; that tells use that this data belongs to the archive process and we may want to store that data. In my code, I loop through each event pulling out specific fields that I know I want to store.

Also for filtering purposes, there is an important key/value pair that I’m paying special attention to, it’s the rcpt_type key/value pair. ?When an email is sent out using either the cc, bcc or the archive feature, each event will have a corresponding rcpt_type of either ‘cc’, ‘bcc’ or ‘archive’. ?My design allows for the email administrator to decide if they want to keep or filter those out by placing the appropriate values in the config file.

The PHP code to decide on if this event should be stored or not looks like this in my project:

if ($uid)
	switch (true)
		case ($rcpt_type == "original" | $rcpt_type == "archive"):
			$store = true;
		case ($rcpt_type == "cc" && $logCC):
			$store = true;
		case ($rcpt_type == "bcc" && $logBCC):
			$store = true;

By setting the $store flag to true; the rest of the program will store the corresponding data for that event.

So, in short, we have gone through the following steps:

  1. The collector gets the data from SparkPost and places into a directory (retrieveWebhook.php)
  2. Another process(s) will read the directory of files saved by the collector and try to lock the file from other processes. ?If successful, it will continue with that file. If not, it will continue down its list of files until it runs out or finds a file that needs processing. (processOutboundWebHooks.php*)
  3. Since the file may have many events; we create an array of each event.
  4. Looping through each event, we pull data we are interested in. ?the rcpt_type and uid are necessary to decide if we care about this event.
  5. If we decide to store this event; we proceed with saving the data to our SQL table.

*This is a truly bad name, but I’m trying to describe the process that is storing the webhooks data coming from SparkPost outbound versus the archive inbound process

In this project, some of the more significant fields that I decided to use for indexing are: campaign_id, subject, timestamp, template_id and of course the rcpt_to field which holds the target email address.

This leaves me with a table with the following fields:

  • Connector Id
  • Rcpt To
  • Campaign Id
  • Subject
  • Timestamp
  • Template Id
  • Raw (a copy of the full data event)

I’m not going to assume that these are the only fields or the best fields for your implementation, but they are what I’m using for this sample project. ?The code to store our fields in SQL and a text file log is similar to the one in phase 1:

// Create connection
$conn = mysqli_connect($servername, $username, $password);

    // Check connection
    if (!$conn) 
        	if ($loggingFlag) $archive_output = sprintf("\n\n>>>>>MySQL connection failed
     connecting to MYSQL to log S3 entry:%-200s\nTo: %-50s\n From: %-50s\n Subject: %-200s\n 
     InjectionTime: %-42s\n UID: %-38s\n Event Type: %-38s\n ArchiveFileName: %s>>>>>", 
     $conn->error, $rcpt_to, $friendly_from, $subject, $injection_time, $uid, $event_type, $currentFile);
    		$deleteFile = false;
        	$sql = "INSERT INTO (campaign_id, friendly_from, 
     injection_time, rcpt_to, rcpt_type, subject, UID, event_type, raw) VALUES ('" . $campaign_id . "',
     '" . $friendly_from . "', '" . $injection_time . "', '" . $rcpt_to . "', '" . $rcpt_type . "', '" . $subject . "
     ', '" . $uid . "', '" . $event_type . "', '" . $raw . "')";
        	if ($conn->query($sql) === TRUE) 
            		if ($loggingFlag) $archive_output = sprintf("\n\n>>>>>To: %-50s\n From:
     %-50s\n Subject: %-200s\n InjectionTime: %-38s\n UID: %-38s\n Event Type: %-38s\n 
     ArchiveFileName: %s>>>>>", $rcpt_to, $friendly_from, $subject, $injection_time, $uid, $event_type,
            		if ($loggingFlag) $archive_output = sprintf("\n\n>>>>>MySQL insert
     failure to MYSQL Event Table:%-200s\nTo: %-50s\n From: %-50s\n Subject: %-200s\n
     InjectionTime: %-38s\n UID: %-38s\n Event Type: %-38s\n ArchiveFileName: %s>>>>>", 
     $conn->error, $rcpt_to, $friendly_from, $subject, $injection_time, $uid, $event_type, 
            		$deleteFile = false;
    	file_put_contents("eventLog.txt", $archive_output, LOCK_EX | FILE_APPEND);

Without dragging this on, that is all we need to review for this portion of the code. ?As you can see, most of the work was done in the previous steps so all we have to do is retrieve the data, check to make sure it’s data we care about, then log it.

The next code drop will have a sample viewer with something similar to an inbox. Until then, it’s up to you to come up with some ways to view the data. ?If you have something to share, I’m sure everyone will be happy to see your work.

Happy Sending.

~ Jeff

The post Building an Email Archiving System: Storing the Email Log Data – Part 3 appeared first on SparkPost.

The Benefits of a Great Unsubscribe Page Fri, 22 Mar 2019 13:00:26 +0000 unsubscribe pageLearn about the value of creating a clear and streamlined unsubscribe page and why unsubscribes can actually be a good thing for your email strategy.

The post The Benefits of a Great Unsubscribe Page appeared first on SparkPost.

  • This blog post was originally published on 6/3/2015 and was updated on 3/22/2019

In the course of my day, I see a lot of good, bad and the proverbial ugly. Recently, I ran across something I’d call really good: Frank & Oak’s email unsubscribe page. Frank & Oak is an Internet retailer with a mobile app that requires you to log in with your email address to see their products (SMART! Now they can connect the app user to an email address). After receiving emails from the company for months and not purchasing anything, I decided it was time to shut down the mail stream. I clicked the unsubscribe link in their email and was taken to a rather refreshing and paired down page:


Frank & Oak’s unsubscribe page allowed me to decide if I wanted fewer emails or if I wanted to completely want to turn off the tap. There is nothing extraneous, there is no login required, the shut-off valve isn’t hidden 2-3 pages down, or buried under a metric ton of encouragement to stay—it’s right there, highlighted in red. Red suggests danger/attention but that’s not what’s happening here.

Let me explain.

Unsubscribes are your friend

That’s right, unsubscribes are your best friend because the alternative is your worst enemy: spam complaints. Users who unsubscribe from your email feed might someday come back, or as in my case, be delighted to see a simple page that gives me choice and the ability to control my inbox’s fill rate.

If a user can’t unsubscribe easily from your newsletters or promotions because you buried one or two clicks down from the initial page, or obfuscate the unsubscribe mechanism in some other manner then the easiest alternative (to make the mail stop) is to click the spam button. Enough spam complaints and your email may begin to deliver to the spam folder en masse. If enough spam complaints happen on a given domain or IP in a short span of time then the rest of the email may be routed to the spam folder.

So which would you rather have? A customer that dials down how often and how many emails you send them or a spam complaint?

The choice is yours, however, consider the age in which we live: we’re living among empowered consumers—this includes you. You have a tremendous amount of power to control the conversation that brands have with you. You can shut off their marketing, choose their rivals, never visit a store, or complain on social media and bend the ear of the world. Since the power structure of consumption and advocacy has shifted from the brand to the consumer, you have to apply customer-centric tools and marketing, like this light, efficient and delightful page to let customers quickly make the right choice for their lifestyle (and your brand), versus punishing you for being overzealous in your approach. There’s an old saying: If you love someone, set them free. If they come back they’re yours; if they don’t they never were—that’s what you need to keep in mind when designing your unsubscribe page.

~ Sparky

The post The Benefits of a Great Unsubscribe Page appeared first on SparkPost.

3 Predictions for MarTech Email Strategy in the IoT Era Wed, 20 Mar 2019 13:00:59 +0000 For MarTech providers and marketers, how will the amazing growth of the IoT impact email strategy in the not-too-far-future?

The post 3 Predictions for MarTech Email Strategy in the IoT Era appeared first on SparkPost.


The Internet of Things (IoT) is growing everywhere.

Technically, the “IoT” encompasses everything linked to the Internet. But it’s typically used to refer to devices, from an Apple Watch to a Nest thermostat to even automobiles, that communicate with each other.

And nearly every ubiquitous device seems to be joining the IoT. ?Not only the everyday thermometer, but your egg tray and your infant’s changing pad. Each year at CES there’s a new medley of IoT offerings, from startups and evergreen brands alike, being pitched.

It’s anything but vapor-wear

You’ll be wearing IoT nodes soon, and not just as a smartwatch or fitness tracker. ?Last year, packaging and materials giant Avery Dennison announced a partnership aimed at launching the “world’s largest IoT deployment,” adding 10 billion apparel and footwear products from leading brands to the IoT over three years.

Analysts’ forecasts predict the IoT to keep skyrocketing. The North American IoT consumer market alone will surge from $90 billion in 2017 to $180 billion in 2022, a CAGR of 12.25%. That’s in addition to dizzying growth in industrial, infrastructure, healthcare and other segments.

How many total devices are we talking about? Hold your breath: one prediction claims we’ll see 30.7 billion installed IoT devices by 2020, and 75.4 billion by 2025.

What does the IoT mean for MarTech?

Anyone who’s seen or used an Amazon Dash button knows exactly why marketers and martech providers are rushing to exploit the IoT.

First of all, it’s obviously a way to extend actual brand-to-consumer engagement into a new variety of everyday moments and locations. But it also opens up an incredibly rich trove of consumer data to use in an email marketing strategy, a vein the right marketing tech tools can mine to power campaigns more personalized, precise, and effective than ever before.

So what are three ways we predict the IoT will impact martech email strategy?

Extreme personalization

Consumers expect and demand personalization, and martech’s ability to collate data like a user’s geolocation, daily routines, even health data, will take this several steps further over the next few years.

For instance? A fitness enthusiast – let’s call her Sheila – who’s partial to workouts at home or anywhere but a local gym (an insight gleaned by analyzing her geolocation and fitness wearable data) can be targeted with a membership offer featuring content customized to her exact behaviors – running, swimming, biking, tae bo, or whatever. ?Plus, the email gets timed to a daypart where Sheila has historically shown a higher CTR.

With the analytics allowed by the IoT, the best martech platforms will be able to accurately segment the Crossfitter from the couch potato, and engage each via a perfectly personalized email strategy.

An evolving emphasis on “mobile first” marketing experiences

In a recent survey we conducted among email marketers, one crucial concern they cited? The need to provide responsive design that works across multiple devices and enables greater user interactivity.

The IoT will only multiply that challenge, because it multiplies the number of different devices and channels to contend with. Email strategy and execution will need to be optimized for a desktop, a smartphone, a smartwatch, an auto infotainment display, possibly even for smart glasses that will try to avoid Google Glass nerditude.

So it’s fair to predict that MarTech platforms, agencies, and clients who invest in responsive design and interactive email solutions will gain a very real advantage in the era of the IoT.

More app-generated and transactional email

That rich trove of consumer IoT data we mentioned earlier? It’ll provide marketers with more data points than ever, as well are more opportunities than ever to deploy app-generated and transactional email to deepen customer engagement and loyalty.

It makes sense that an IoT wearables company, Fitbit, is already leveraging this approach. They’ll send a customer an email alert when the battery in his or her’s wearable is running down – along with instructions on how to replace it.

Let’s say Sheila, the fitness enthusiast we mentioned above, decides to take us up on a trial gym membership. At a basic level, the data she’s sharing from her wearables (or from a membership app she downloads) can trigger emails offering loyalty rewards for making a certain number of visits.

But the IoT can take it to a more granular level: Via her wearable and its connections to other IoT devices, we can identify when she’s taken a spinning class and capture data from the stationary she rode. So Sheila’s session data can be used for an email that recaps her performance and gives personalized coaching – great incentives for her to stay a post-trial member.

The state of transactional email will change enormously, even unpredictably, as the IoT evolves over the next several years. For martech users, staying on top of that game means investing in transactional email technology that’s flexible and scalable enough to rise to the opportunities the IoT presents.

And as we’ve seen, those might be as limitless as the IoT itself.

The post 3 Predictions for MarTech Email Strategy in the IoT Era appeared first on SparkPost.

4 Strategies for Getting Maximum ROI From Your Tax Season Emails Mon, 18 Mar 2019 13:00:48 +0000 tax seasonTax season’s looming April 15 deadline is the perfect date to work backward from when planning triggered email campaigns.

The post 4 Strategies for Getting Maximum ROI From Your Tax Season Emails appeared first on SparkPost.


Tax season is a great time to set up triggered emails that are sent out when fintech customers take certain actions, or fail to do so, such as providing documents for filing their tax returns. Triggered emails can also be scheduled to go out on certain dates tied to major tax season events.

In fact, triggered emails have 8 times better open rates and drive more revenue than regular bulk emails, according to Experian. They’re a great example of sending the right message to the right person at the right time, and tax season’s looming April 15 deadline is the perfect date to work backward from when planning triggered email campaigns.

Here are 4 strategies you can use with your triggered tax season emails.

1. Get a head start with current customers

You want to grow sales every year, and acquiring new customers is a valid part of achieving that goal, but the people who have used your service in years past should factor into your marketing strategy too. You can’t assume they’ll return this year, so you should schedule a triggered email that goes out at an opportune time to catch their interest.

This email from Credit Karma was sent in early January, a time when people are likely thinking about doing their taxes but possibly haven’t decided who will take care of that task for them this year. “Welcome back” is used in the subject line and in the email body to remind the recipient of their past relationship with the company, and the “100% free plus our Accurate Calculations Guarantee” value prop is the main message here, with the goal of enticing the client to click the Learn more button.

Note the use of the recipient’s name in the email body. According to Experian, personalized emails deliver 6X higher transaction rates.

2. Catch the procrastinators, as well as the stragglers

Despite modern technology making it easier to electronically file tax returns and have refunds sent straight to bank accounts, plenty of people still put off what needs to be done. Set up a deadline-themed triggered email that will go out a specific number of days before April 15 to get the attention of procrastinators.

It doesn’t hurt to also get in touch with non-responders after the deadline and let them know that it’s better to file late than never. Add increased urgency to your messaging so they know that penalties are accruing with each day that passes.

This Credit Karma email sent on March 1 does a good job of upping the urgency a little without pushing too hard, since the recipient still had roughly six weeks to file. The use of the person’s first name helps cement the connection, which is smart since people are 26% more likely to open emails with personalized subject lines, according to Campaign Monitor.

The three value prop bullet points add some enticement to the message, and the GIF of someone snapping a shot of their W2 with a smartphone helps drive home how easy it is to file a tax return with Credit Karma.

3. Tie your triggered emails to specific activity

People like to receive emails that acknowledge certain actions, such as an order being shipped. In the financial technology industry, you can keep customers happy by setting up triggered emails that let them know you’ve received their paperwork, their tax return is ready, their return has been filed, and so forth.

Those confirmations also help reduce support costs, since financial transactions typically cause anxiety that can lead to “What’s happening?” emails and phone calls if customers feel like they’re in the dark. A short, friendly email is usually enough. And keep upsells and cross-sells out of the message, since people don’t typically like to be asked to spend more money when they’re trying to find out if their sensitive documents have been received.

This email from Intuit uses a trigger based on the availability of the customer’s W2. They not only came up with a catchy, hashtagged name for their promotional email (#W2sDay), but they let the user know that all they have to do is sign in and Intuit will pull in last year’s information.

The progress bar complements the “You’ve got a head start” messaging to make it clear that all they have to do is click the Go button to get a jump on this year’s filing. The customer quotes give the recipient an additional nudge to click through and get started.

4. Segment your customer list to drive better response rates

Campaign Monitor has noted that segmented email campaigns can drive a 760% increase in revenue. They’re one of many companies whose solutions enable email marketers to segment their customer lists by demographic information, purchase history, and other attributes.

For example, you can segment your list by the types of tax returns your customers file: a simple 1040; a 1040 with a Schedule C for business income; a corporate tax return; and so forth. Then you can send a different email to each group, also known as a cohort, and acknowledge what kind of return they filed last year. You can also customize the list of documents they need to provide to get this year’s return completed.

Apply that segmentation to your triggered emails to create a series of messages tied to different kinds of tax returns. Doing so also lets you include relevant tips, such as best practices for organizing business receipts, that can drive additional engagement. Customers like knowing that a company they’ve done business with isn’t just sending them generic, one-size-fits-all emails.

~ Casey

The post 4 Strategies for Getting Maximum ROI From Your Tax Season Emails appeared first on SparkPost.

Boosting Email Engagement and Conversion with Send Time Optimization Fri, 15 Mar 2019 13:00:39 +0000 send time optimizationOur SVP of Data Science, Daniel Chalef, explores whether send time optimization results in a meaningful lift in customer engagement.

The post Boosting Email Engagement and Conversion with Send Time Optimization appeared first on SparkPost.


User engagement is critical to the growth of any product or service and email is a key channel for driving engagement. An increase in email engagement can boost monthly active users, conversion rates, and revenue. In this blog post, I explore whether optimizing when emails are sent to recipients results in a meaningful lift in engagement and outline an approach to optimizing these send times.

While this approach is fairly simple, the model performs quite well in backtesting, resulting in a significant 43.3% lift in email engagement.

If you’re a SparkPost customer, you can utilize our Events API to collect data in order to run a similar analysis to mine below. If you do so, see the caveats section at the end of this post regarding data sparsity.

Sampling and Cleaning the Data

In this analysis, I have the benefit of being able to look at recipient engagement across SparkPost’s customer base. As SparkPost delivers email for many of the largest senders in the world, this offers a reasonably high resolution of recipient engagement but also means the dataset is extraordinarily large. As a result, this analysis uses a smaller sample of 2.2 million US-based recipients.

All of these recipients have exhibited some engagement behavior in the sample period from October 1, 2018, to November 30, 2018. We define engagement as opening an email or clicking on a link in an email.

As with all data science projects, the data needed to be cleaned and outliers noted or removed. In this dataset, system-generated emails (such as alerts sent by software for consumption by IT or development teams) were removed. So too were recipients who received high volumes of email (over 1,000 emails a day) or where I noted recipients opening emails from more than 6 timezones (which I believe may be group email addresses or role-based email addresses such as sales@ or info@ addresses).

Exploring Recipient Behavior

Before diving into building a model for optimizing send times, I wanted to understand the feasibility of building such a model. Getting a sense for recipient behavior and determining whether there were patterns we could potentially model was a useful exercise. For clarity, the exploratory data analysis below is limited to recipients located in the US EST timezone.

In the charts above, we’ve plotted the following for each hour of the week (in EST):

  • Mean Time to First Engagement: The mean time, in hours, from delivery of an email to a recipient’s first engagement with that email. Lower is better.
  • Mean Engagement Rate: The mean engagement rate, where the engagement rate is the count of emails engaged with over the total number of emails sent. Higher is better.
  • Mean Email Deliveries Per Recipient: The mean number of emails sent to recipients.

It’s clear that there are some interesting patterns here, particularly late night, early mornings, and over weekends. The early morning drops in mean time to first engagement and increase in engagement rate are phenomena familiar to many marketers, and so too the significant drop in engagement over weekends.

It’s also possible that the peaks in engagement are being driven by sender behavior i.e. emails sent late at night to night owls are driving high late night engagement rates, rather than this being an organic, recipient-driven behavior.

This is definitely worth digging into further.

Optimizing for Conversion

When we send emails to recipients, we’d often like the recipients to engage as soon as possible: buy something in a sale, attend an event, purchase a plane ticket, read a news article, or start using our app. However, the email time to engagement distribution is highly skewed, with a very long right tail. You can see this depicted in the histogram below, where the right tail is bounded by the sample period of 61 days.

The engagement data for recipients with mean engagement in the long right tail are not ideal for use in optimizing for engagement (and in turn, for conversion). It would be worth calculating the engagement rate for recipients as:

But what should we make?x above? It’s clear from the histogram that the majority of recipients engage with an email within hours. In the table below, it looks like approximately 70% of emails are engaged with, and almost 60% of recipients engage with emails, within 12 hours. This seems like a reasonable number to use for determining an “immediate” engagement rate.


TTF Engagement for Messages

(percentiles | hours)

TTF Engagement for Recipients

(percentiles | hours)

25% 0.67 25% 2
50% 3.46 50% 8
70% 11.70 60% 13
95% 114.04 99.5% 525
max 1456.84 max 1439


I’ll use this “immediate” engagement rate for the rest of the analysis below.

Per-Recipient Engagement “Probability Distribution” and Clustering

I’d like to understand a recipient’s propensity to engage per hour of the week in order to further explore the phenomena we saw above and to potentially optimize recipient send times.

To do this, I mapped every email delivered to a recipient over the two month sample period to an hour of the week, tallied how many were “immediately” engaged with and calculate the hour of week engagement rate.

I did this for every recipient and ended up with a probability distribution of sorts similar to the table below (rows are recipients, columns the hour of the week). In hour 11, recipient 0 has an engagement rate of 0.67.

Clustering is a great exploratory tool. In the next step of the analyses, I used a?k-means algorithm on the per-recipient “propensity to engage” dataset to cluster recipients, hoping to surface a higher definition view of recipient engagement behavior. Once I clustered the recipients, I calculated the mean engagement per hour of the week for each cluster and plotted this on the charts below.

The results are super interesting. Many of the clusters exhibit a clear engagement bias. Cluster 3 to evenings ET, Cluster 5 to late night / overnight (night owls or night workers?), Cluster 1 and 6 to mornings to mid-afternoon (with a bias to mornings).

You’ll note that Clusters 0 and 4 have significantly lower engagement rates to the other clusters. In the chart below, I’ve modified the y-axis to give us a better look.
Despite this being a very large dataset, I still have fairly sparse engagement data for many recipients. In particular, I don’t have much data for recipients in Cluster 0: engagement is low and there isn’t a clear pattern, other than a bias to daytime engagement.

I may have to exclude these recipients from our optimization or make a best guess based on some general patterns I’ve observed in the data.

Modeling Engagement Lift from Optimizing Send Time

Clearly, there are recipients that have a higher propensity to engage at a specific time or day of the week. What if I had used this information to modify the time that the emails were sent?

Modeling this is fairly straightforward. I used a Window function (available in Apache Spark and most SQL engines) to look a number of hours prior and ahead of the real-world send time in order to determine if there was a better time within this window to send an email. I defined a better send time as an hour in this window during which the recipient had a higher hourly engagement rate than during the actual send time.

For my model, I used a fairly narrow 8-hour window (4 hours prior to the delivery hour and 4 hours ahead). I was also careful to exclude data points where only a single email was delivered and subsequently engaged with (resulting in a 100% hourly engagement rate).

I ran the entire dataset (all US timezones) through the model and the mean engagement rate results are below. The findings show that had SparkPost’s customers sent these emails to recipients during their optimized engagement hour, they would have seen a mean uplift of 43%. This is really compelling. Imagine what this might do for your monthly active users, conversion, and revenue numbers!


Mean “Immediate” Engagement Rate Mean “Optimized” Engagement Rate Uplift
15.7% 22.5% 43.3%

Some Caveats to this Analysis and Model

This approach to send time optimization is exciting and compelling. Some caveats to the analysis and model should, however, be noted:

  1. Purely transactional email such as password resets, shipment notifications, and alerts was not removed from our analysis (our data privacy safeguards limit our ability to do this). In a real-world implementation, we’d probably want to exclude these emails from optimization.
  2. Teasing apart phenomenon driven by sender behavior (i.e. when we send emails) from organic recipient behavior can be challenging, and, given sufficient data sparsity, may not allow us to determine actual recipient behavior. This was, however, somewhat mitigated by the number of senders we included in this analysis.

Additionally, if you’d like to explore this for your message streams it is important to be mindful of data sparsity issues (mentioned in (2) above), i.e., not enough engagement data to make meaningful adjustments to send time. This may not result in a performant model and may even result in a drop in engagement.

~ Daniel

The post Boosting Email Engagement and Conversion with Send Time Optimization appeared first on SparkPost.

The California Consumer Privacy Act and its Impact on Email Senders Wed, 13 Mar 2019 13:00:05 +0000 California Consumer Privacy ActRead up on how the California Consumer Privacy Act (CCPA), a sweeping new data privacy law in California, impacts email senders.

The post The California Consumer Privacy Act and its Impact on Email Senders appeared first on SparkPost.


2018 was a big year in the data protection world, with EU’s General Data Protection Regulation (GDPR) taking up most of the spotlight with its myriad of privacy-related requirements and potential for high fines. However, while companies may continue to be focused on the GDPR at the moment, it is also important to keep an eye on new privacy laws on the horizon in order to avoid last-minute compliance exercises. Among these new laws is the California Consumer Privacy Act of 2018 (CCPA), which was enacted by Governor Jerry Brown on June 28, 2018. The CCPA is a sweeping new law that establishes an array of new rights for California residents regarding the collection, use, and disclosure of personal information. While the Act goes into effect on January 1, 2020, it will not be enforced until the Attorney General publishes regulations, which are not required by law until July 1, 2020. Additionally, since the CCPA was rushed through the legislature to meet the deadline imposed by the backers of the ballot initiative, it is anticipated that it will be subject to amendments prior to 2020 (in fact, at the time of this post, the CCPA has already been amended once). Accordingly, businesses falling under the CCPA should also anticipate some changes to the law before it becomes effective and enforced. In the meantime, below is what we know.

Who does the CCPA apply to?

The CCPA defines “business” as a for-profit legal entity doing business in California that collects personal information of California residents, or on whose behalf the personal information is collected, and that determines the purpose and means of processing the personal information. A business only needs to meet one of the following thresholds for CCPA to apply:

  • Annual gross revenues in excess of $25 million;
  • Annually buys, receives, sells, or shares for commercial purposes, alone or in combination, the personal information of 50,000 or more California residents, households, or devices; or
  • Derives 50% or more of its annual revenues from selling California residents’ personal information.

Certain businesses are out of scope by virtue of being covered by certain other state or federal privacy laws. For example, the CCPA does not apply to the extent it conflicts with the Health Insurance Portability and Accountability Act (HIPAA) or the Gramm-Leach-Bliley Act (GLBA).

What is “personal information” under CCPA?

The CCPA greatly expands the definition of “personal information” – previously this term primarily referred to contact information when it was coupled with some other sensitive information such as bank account numbers, social security numbers or health account numbers. Now, personal information is defined broadly as “information that identifies, relates to, describes, is capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular consumer or household.” Examples include obvious personally identifiable information such as name, phone number, email address, social security number, driver’s license number, etc. But the Act also includes less obvious “personal” information such as biometric, geolocation, IP addresses, and professional or employment data. ?Notably, the definition includes households. While the definition of personal information may be further clarified by the Attorney General, or even reduced in scope by future legislation, it will likely continue to be broader in scope than any existing law or regulation – including GDPR.

Despite the breadth of the newly defined term, personal information does not include publicly available information. However, the definition of “publicly available” is very limited. ?The CCPA provides, “publicly available means information that is lawfully made available from federal, state, or local government records.”

What are my obligations under CCPA?

In brief, the law requires businesses to provide California residents with the right to:

  • Know what personal information is being collected and how it is being used. Consumers will have the right to know the personal information a business has collected about them, its source, and the purpose for which it is being used.
  • Know whether and to whom their personal information is sold or disclosed, and to opt-out of its sale. Companies that provide or make consumer data available to third parties for monetary or other valuable consideration are deemed to have sold the data and will need to disclose this. Subject to certain exceptions, consumers will then have the further right to opt out of the sale of this information by using the “Do Not Sell My Personal Information” link on the business’s home page. This link is required by the Act. Moreover, those individuals 16 years and under must opt-in to have their information sold.
  • Access their personal information. Consumers will have the right to request certain information from businesses, including the sources from which a business collected the consumer’s personal information, the specific elements of personal information it collected about the consumer, and the third parties with whom it shared that information. Once the request is made, businesses must disclose the requested information free of charge within 45 days, with extensions of time available in certain circumstances.
  • Not to be discriminated against for asserting any of the rights granted by the law. The CCPA gives consumers the right to receive equal service and pricing from a business, even if they exercise their privacy rights.
  • Sue for a data breach. The new right of private action for a data breach will likely result in significant class action litigation.

What are the penalties for CCPA non-compliance?

Fines for violations include:

  • $2,500 for unintentional violations and $7,500 for intentional violations of the Act. However, for now, only the California Attorney General can pursue these penalties.
  • $100 to $750 per incident, per consumer — or actual damages, if higher — for damage caused by a data breach.

While these fines may appear relatively low, it is important to note that they are per violation. It is not uncommon for a data breach to affect thousands or tens of thousands of consumers, in which fines and damages could easily reach millions or hundreds of millions of dollars.

How is CCPA different from GDPR?

While there are a number of similarities between CCPA and GDPR, there are also many differences. The table below provides a brief comparison. Companies that implemented GDPR-level compliance can leverage parts of their program to meet CCPA requirements, but additional program development for CCPA will still be required.


Scope Transparency, individual rights, enforcement Broader and all encompassing
Personal Information Broader definition by including households Information relating to an identified or identifiable natural person
Transparency Specific requirements for disclosures Less prescriptive
Rights Broad rights to access and deletion Similar rights
Sale of Data Specific requirements for selling data and opt-out Processing requires lawful basis
Enforcement Attorney General and plaintiff’s attorneys Data protection authorities
Security Not included General requirements for protecting information
Breach Notification Not included (addressed separately in another CA law) 72 hour requirement
International Transfer Not included Restrictions on data transfers outside of countries that do not provide “adequate protection”
Privacy by Design Not included Required
Data Protection Officer Not required Required if certain criteria are met

What should an email sender do in light of the impending changes under CCPA?

We recommend email senders that will be subject to CCPA take time in the coming months to evaluate the new California law carefully and assess the potential impact to the business as it relates to its email sending practices. As initial takeaways, emails senders should consider the following:

  • Review existing privacy disclosures to evaluate potential updates mandated by the CCPA.
  • Commence planning to implement the “do not sell” requirement, including cataloging data sales and reviewing vendor agreements for other types of data sharing that will amount to a sale under the expanded definition in the statute.
  • Initial planning for an inventory of data concerning California employees, customers, contractors, mobile app users, website visitors, and other residents to start feasibility planning for fulfillment of access, deletion, and ‘do not sell’ requests.
  • Identify key vendor contracts and evaluate for compliance with California standards.
  • Update vendor privacy language to implement flow-down terms for the new California privacy rights.


The CCPA requires companies that rely on collecting and processing personal information to further advance their data protection program. Prior to this law, in most cases, information like IP addresses, Internet usage, and browsing histories were not considered personal information – particularly when they were not linked to other information of a more personal nature. Under the CCPA, all of this information is now automatically personal information – effectively granting California residents the equivalent of a Droit Moral in their personal information, which is akin to the fundamental personal privacy rights of EU residents. By combining these sweeping privacy changes with new statutory damages rights, the CCPA is a significant force in privacy law requirements in the United States.

SparkPost is GDPR compliant and will be CCPA compliant by the time it takes effect. As a result, SparkPost will be ready to assist our customers to meet their CCPA obligations when it comes to their email sending.


Disclaimer: This blog post is meant as a general set of questions and answers and is not legal advice and cannot be relied upon for any legal purpose. You must consult your own professional advisors for your specific facts and circumstances before taking, or refraining from taking, any particular course of conduct. This blog post is not an amendment or supplement to any agreement between SparkPost and you.

~ Jason

The post The California Consumer Privacy Act and its Impact on Email Senders appeared first on SparkPost.

The Challenges of High-Volume Senders Mon, 11 Mar 2019 13:00:52 +0000 high-volume sendersJoin us for our upcoming webinar on March 26th with Blueshift and LendingTree where we will discuss and address the challenges of high-volume senders.

The post The Challenges of High-Volume Senders appeared first on SparkPost.


For High Volume Email Senders, The Struggles Are Real

Email is the backbone for the vast majority of consumer brands’ marketing initiatives. As marketers, we rely on it to send promotions, deliver the latest newsletter, drive revenue, increase loyalty, and so much more. However, with this reliance comes a number of hurdles, pitfalls, and downright showstoppers that keeps us marketers up at night and often panicking over our performance metrics.

For high volume senders of email, the issues compound upon each other and can lead to overall deliverability issues, inbox placement, and even SPAM. The common struggles faced by high volume senders include:

IP Reputation: Every email marketer has to keep IP reputation as a priority. For high volume senders, it’s an even larger issue due to the sheer volume and often different types of emails that get sent. For high volume senders, multiple IPs are often required to handle the various message types.

Ramping: You cannot send a high volume of emails immediately. Beyond simply “warming up an IP address” you have to consciously scale your sending volume to avoid potential IP reputation issues. Whether you have dedicated IPs or shared IPs, this is an issue you will face.

Burst Rates: Trying to send a high volume of emails all at once causes headaches for marketers and their engineering teams. Often these emails can be throttled and spread over hours, which could be an issue for limited time only promotions or other timely messaging.

Personalization: From product recommendations to predictive “next-best” offers and up-sells, personalization can become an issue for high volume senders. Some senders simply show “trending” or “top rated” content, but building true personalization can add delays with throttling or even massive downswings in volume sends.

Rendering: As mentioned in personalization above, adding complexity to your emails has side effects with high volume senders. From building uniques personalizations (like weather, next-best recommendations, etc) to adding in too many images, your email can be hindered both with delivery windows and even actually rendering of the content within the email itself.

As customers begin to demand more and more personalization and relevance in their emails, high volume senders face all of these issues (and even more that may happen down the road). With tighter restrictions on customer data as well (seen with the recent passage of GDPR), high volume senders have plenty of issues to consider.

The best practice is to forecast out your needs and keep a strong eye on your backend and front end metrics constantly. Build out a great team and give them the technology needed to handle and overcome these struggles.

Knowing these issues exist is part of the battle. Attend our upcoming webinar featuring LendingTree’s Senior Director of CRM, Chris Kachel, in a conversation with Sparkpost and Blueshift, as we discuss how LendingTree overcame these issues and how you can set a plan to avoid these pitfalls.

~ Shannon

Shannon Johlic is the Director of Marketing at Blueshift, delivering regional, national, and global marketing programs with measurable impact, spurring action from targeted audiences by leveraging over a decade of experience in demand generation.


The post The Challenges of High-Volume Senders appeared first on SparkPost.

Celebrating International Women’s Day 2019 Fri, 08 Mar 2019 14:00:46 +0000 International Women's Day 2019SparkPost's CEO, Rich Harris, interprets the theme for International Women's Day 2019, “A Balanced World is a Better World," in his own words.

The post Celebrating International Women’s Day 2019 appeared first on SparkPost.


I’m very happy we are celebrating International Women’s Day (IWD) and highlighting the achievements of the women of SparkPost. The theme of IWD is “A Balanced World is a Better World.” This theme can be interpreted in different ways, and I would like to share what this means for me.

I have been in the technology industry since 1997 (yes, I’m old). My experience for the first 20 years of my tech career was completely dominated by men. At the time I don’t think I was aware of how male-dominated my world was. I assumed it was the norm that for virtually every company with which I was involved, the entire board of directors and the full management team was male. I really didn’t have any perspective of whether or not this was a problem, or fine, or even worth thinking about.

It was not until I joined AddThis in 2013 that I woke up to what I was missing. I remember when I first started with AddThis I met the then Head of HR, Bhavna Dave. She asked me how I think about HR and culture and how it fits into strategy. My first thought was, “good question because I haven’t spent much time thinking about HR as part of our strategy.” Bhavna went on to help us turn culture and HR into a true competitive advantage for AddThis. We were able to recruit incredible people, develop a high performing team, have fun and reach success beyond all of our expectations.

Bhavna introduced me to my executive coach, Caroline Miller. When I started coaching with Caroline my goal was simple, I wanted to become a more inspirational leader. Caroline transformed the way I communicate with people and groups. She turned my thinking upside down about how to motivate people and introduced me to the power of understanding character strengths, gratitude, and mindfulness. Caroline has helped me focus on what matters, develop more meaningful relationships, and work to be my best self.

Bhavna also helped us recruit Claire Alexander to be Head of Marketing. I recall a 1:1 meeting with Claire a few months after she started. She sat down in my office and began the meeting by saying, “Rich, I don’t think you are doing your job, and here is why…” At first, I was somewhat shocked, but I quickly realized that Claire was giving me feedback to help me and the company be successful. She was so passionate about her ideas she had to let them out in the most direct way possible. I truly came to appreciate Claire’s courageous and direct style, and she absolutely helped me become a better leader.

Caroline, Claire, and Bhavna added new perspectives and ideas and helped me think about things in a totally new way. They are just 3 examples of many women at AddThis who had a tremendous positive impact on the company. I see the same thing here at SparkPost. In my short tenure, I have already experienced the value of different views and perspectives from many women, including Julie Acri, Amie Durr, Kathryn Schutz, Laura Rose, Tracy Sestili, Michelle Cunningham, and many others. We are fortunate to have these woman as part of our team and we will be more successful as a result of their powerful ideas and contributions.

Here is how these women have contributed to SparkPost in their own words:

~ Rich



The post Celebrating International Women’s Day 2019 appeared first on SparkPost.

3 Free Email Security Standards That Can Help You Preserve Brand Trust Wed, 06 Mar 2019 14:00:57 +0000 email security standardsLearn about three email security standards that can help stop bad actors from impersonating your company and alerting you to such efforts.

The post 3 Free Email Security Standards That Can Help You Preserve Brand Trust appeared first on SparkPost.


The financial costs of data breaches from phishing, spear phishing, and spoofing attacks on employees’ email accounts are eye-popping:

However, those numbers don’t address the damage done to brand trust, particularly in the financial services industry, when consumers receive a malicious email purportedly from a company they’ve done business with, or might do business with. If someone clicks a link in an email and a bad actor wreaks havoc on their life, the experience can leave them wary of that business, even though the company didn’t send the message.

There’s a high likelihood that someone who receives an email that looks like it came from your company will be fooled: According to a survey conducted by Intel Security, 97% of respondents worldwide couldn’t correctly identify a phishing email. And bad actors are getting more sophisticated at creating emails that, at first glance, seem legitimate.

In addition, email isn’t going away any time soon. The Financial Brand found that 70% of all consumers (and 72.1% of older Millennials) think email will still be around in a decade, more than any communication channel they were asked about, including cable TV and Facebook. There will be many future opportunities for consumers to be fooled by malicious emails.

The Damage That Bad Guys Can Do to Your Brand

You’ve likely put in the hard work to secure your company against direct attacks through training, code reviews, third-party penetration testing, infrastructure security, and more. You’re ready to deal with direct attacks on your business, but there are plenty of bad guys who aren’t interested in that: they’d rather impersonate your company and trick consumers into giving up personal information.

For example, they may send a phishing email like this one:

It probably won’t come as a surprise that the return email address in the header has been spoofed since it’s relatively easy to send an email from one address but make it look like it was sent from a different one. In addition, the account unlock link, as well as the customer service email address link, go to a malicious website that looks like Really Big Bank’s website, another trick that’s not hard to pull off. These days, many bad actors are using HTTPS in their links to make them appear more trustworthy.

If the recipient clicks one of those links and ends up having their bank account emptied, they’ll be unhappy with whoever scammed them, but there’s a good chance they’ll also direct some frustration toward Really Big Bank for allowing the impersonation to happen in the first place. If they’re a Really Big Bank customer, they might rethink their choice to have an account there, and if they’re not a customer, they’ll probably be wary of that brand in the future.

However, there are three email security standards that are free to use and relatively easy to implement. They can help stop bad actors from impersonating your company and tricking consumers into allowing their accounts to be compromised. Now more than ever, consumers will take their business elsewhere if they think a financial institution is so lax about security that it can’t be bothered to safeguard its email.

3 Steps to More Secure Email Sending

These may seem like small steps, but they can add up to a big impact on trust by helping stop bad actors from impersonating your company and alerting you to such efforts.

Step 1: Implement SPF (Sender Policy Framework)

SPF is an email authentication standard that helps protect senders and recipients from spam, spoofing, and phishing. It defines a way to validate that an email was sent from an authorized mail server and was designed to supplement the SMTP (Simple Mail Transfer Protocol) protocol that’s used to send email because SMTP doesn’t include any authentication mechanisms.

SPF also piggybacks on the well-established Domain Name System (DNS) that maps a web server name, such as, to an IP (Internet Protocol) address usable by a computer. It works like this:

  • A domain administrator publishes a policy, called an SPF record, that defines which mail servers are authorized to send email from that domain. The SPF record is listed in the domain’s overall DNS records.
  • When an inbound mail server receives an email, it looks up the rules for the Return-Path domain in the DNS records. The server then compares the IP address of the email sender with the authorized mail servers defined by the SPF record.
  • The SPF record lists rules used by the receiving email server to decide whether to accept, reject, or otherwise flag the message.

An SPF record isn’t difficult to create: it’s simply a specially-formatted version of a DNS record created as a standard TXT file. It looks something like this: ???TXT “v=spf1 ~all”

Reading left to right, this record says:

  • Any email that claims to be from should be validated with SPF, per the “v=spf1” prefix.
  • It also specifies that the SPF records for should also be included when validating email from This is typically done to indicate that other domains are authorized to send email on behalf of the primary domain, such as when an organization sends messages from a subsidiary and/or splits its transactional and marketing emails between different domains. Multiple domains can be listed.
  • The “~all” command tells the incoming mail server that any other servers sending email on behalf of should have their messages flagged as questionable.

SPF records can be more complicated than this example, but the basic mechanism remains the same. You can learn more about the specifics of implementing one in an explainer we created.

Implementing SPF helps keep bad actors from sending emails that look like they’re coming from your business, but you should add DKIM and DMARC for a complete email authentication solution.

Step 2: Create a DKIM (DomainKeys Identified Mail) Signature

DKIM is a technical standard that uses public key cryptography to verify that an email was sent from an authorized mail server. It adds a digital signature to the headers of an email message, allowing the incoming mail server to validate it against a public cryptographic key in the sending organization’s DNS records.

This is important because while SPF defines the mail servers that can send messages on behalf of your domain, it doesn’t offer a mechanism to verify whether the message headers or body have been altered or forged while in transit.

DKIM works like this:

  • A domain administrator publishes a cryptographic public key in the domain’s overall DNS records.
  • An outbound email server generates and attaches a unique DKIM signature header to each message it sends. The header includes two cryptographic hashes – one of the specified headers and one of the message body (or part of it) – as well as information about how the signature was generated.
  • When an inbound mail server receives an email, it looks up the sender’s DKIM key in DNS and uses it to decrypt the signature and compare it against a freshly computed version. If the two match, the message can be assumed to be authentic and unaltered in transit.

A DKIM signature is a little more complicated to create than an SPF record, but it adds another layer of security that helps keep bad actors from impersonating your business. It looks like this:

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=sendemail;

Here’s how to read those tags:

  • “v=1” should always be there, since it indicates the signature specification version
  • “a=” is the algorithm used to generate the signature; it should be “rhsa-sha256” unless there’s a reason to use something else
  • “c=” is an optional tag that defines what kinds of minor modifications may be present in the email, such as extra white space, after it was sent, which can happen with some kinds of mail servers; this helps keep the receiving mail server from rejecting a legitimate email
  • “d=” is the sending domain; that tag is used with “s=,” which is the selector record name used to locate the public key in DNS
  • “h=” is a list of headers used by the signing algorithm to create the hash in the “b=” tag
  • “bh=” is the message body hash

You can learn more about the specifics of implementing DKIM in an explainer we created.

Implementing SPF and DKIM help keep bad actors from sending emails that look like they’re coming from your business, but you should keep reading to learn how to add DMARC for a complete email authentication solution.

Step 3: Add DMARC to the Foundation Created by SPF and DKIM

DMARC (Domain-based Message Authentication, Reporting, and Conformance) is a technical standard that allows a company to publish a policy that defines its email authentication practices and provides instructions to inbound mail servers for enforcing them. It wraps around the SPF and DKIM authentication standards to enable a complete email sending solution.

This is important because neither SPF or DKIM alert you to malicious messages that managed to bypass both safeguards. That’s where DMARC comes into play.

Like SPF and DKIM, DMARC supplements SMTP and piggybacks on DNS. It works like this:

  • A domain administrator creates a policy defining its organization’s email authentication practices and how receiving email servers should handle messages that violate it. The policy is included in the company’s DNS overall DNS records.
  • When an inbound mail server receives a message, it uses DNS to look up the DMARC policy for the domain contained in the “From” header. The server evaluates the message for three key factors:
    • Was the message’s DKIM signature validated?
    • Did the message come from IP addresses allowed by the sending domain’s SPF record?
    • Do the message headers show proper domain alignment? (For SPF, the message’s From domain and Return-Path domain must match. For DKIM, the message’s From domain and its DKIM “d=” domain must match.)
  • After answering the questions in the previous step, the inbound mail server uses the sending domain’s DMARC policy to decide whether to accept, reject, or otherwise flag the message.
  • After making the decision in the previous step, the inbound mail server reports the outcome to the sending domain owner.

Like an SPF record, a DMARC record is a specially-formatted version of a standard DNS TXT file. It looks like this: IN TXT "v=DMARC1\; p=none\; rua=mailto:dmarc-aggregate@\; ruf=mailto:dmarc-afrf@\; pct=100"

Reading left to right, it says:

  • “v=DMARC1” is the DMARC version
  • “p=” is the policy that should be applied when a message fails the DMARC check:
    • “none” means you want no action to be taken, which can be useful when you first implement DMARC and want to spend some time receiving and analyzing reports
    • “quarantine” means to quarantine the email, which typically means that it ends up in the recipient’s junk mail folder
    • “reject” means the email should be rejected
  • “rua=” is the address where aggregate reports should be sent; these daily reports include information about message sources, domains used to send messages, sending IP addresses, and the number of messages sent on a specific date
  • “ruf=” is the address where forensic reports should be sent; this report includes a copy of an email that failed DMARC validation as well as any SPF and DKIM failures, minus any personally identifiable information
  • “pct=” is the percentage of messages that the policy should be applied to

Aggregate reports are XML documents designed to be machine-readable, so accumulated data can be easily analyzed over time. Forensic reports use a special format called AFRF and are useful for troubleshooting a domain’s authentication issues as well as identifying malicious domains and websites.

When you first implement DMARC, it can be useful to apply no policy to all messages for at least the first few days. You can use the aggregate reports to monitor the situation. Over time, you can start quarantining failed emails, first at a low percentage (5% or 10%) and then ramping that up over time.

After you spend some time quarantining 100% of emails that fail DMARC, you can switch to the reject policy and start at a low percentage again. Increase that percentage over time until you reach 100%. Use forensic reports in addition to aggregate ones to decide how quickly you should reach 100%.

The State of DMARC Implementation

Recent research shows that just half of Fortune 500 companies have deployed DMARC policies, and a whopping 99% of domains worldwide are unprotected by it. While it’s possible to use SPF and DKIM without adding on DMARC, those standards don’t help you take action against bad actors, since inbound mail servers don’t give you reports without a DMARC policy in place.

If your company hasn’t implemented SPF, DKIM, and DMARC yet, you should do so as soon as possible to not only protect your employees but also preserve brand trust among consumers.

~ Casey

The post 3 Free Email Security Standards That Can Help You Preserve Brand Trust appeared first on SparkPost.

Building an Email Archiving System: Storing the Email Body – Part 2 Mon, 04 Mar 2019 14:00:02 +0000 email bodyOur Senior Messaging Engineer describes the process he went through to store the email body onto S3 and ancillary data into a MySQL table.

The post Building an Email Archiving System: Storing the Email Body – Part 2 appeared first on SparkPost.


* This blog is addressing the process(s) in green

In this blog, I will describe the process I went through to store the body of the email onto S3 (Amazon’s Simple Store Service) and ancillary data into a MySQL table for easy cross-referencing. Ultimately, this is the starting point for the code base that will include an application that will allow for easy searching of archived emails, and then displaying those emails along with the event (log) data. The code for this project can be found in the following GitHub repository:

While I will leverage S3 and MySQL in this project, by no means are these the only technologies that can be used to build an archiving platform, but given their ubiquity, I thought they were a good choice for this project. In a full-scale high volume system I would use a higher performance database than MySQL, but for this sample project, MySQL is perfect.

I have detailed below, the steps I took in this first phase of the project:

  1. Creating the duplicate email for archiving
  2. Use SparkPost’s Archiving and Inbound Relay features to send a copy of the original email back to SparkPost for processing into a JSON structure, then sent to a webhook collector (application)
  3. Dismantle the JSON structure to obtain the components necessary
  4. Send the body of the email to S3 for storage
  5. Log an entry into MySQL for each email for cross-referencing

Creating a Duplicate of the Email

In SparkPost the best way to archive an email is to create an identical copy of the email specifically designed for archival purposes. This is done by using SparkPost’s Archive feature. SparkPost’s Archive feature gives the sender the ability to send a duplicate of the email to one or more email address. ?This duplicate uses the same tracking and open links as the original. The SparkPost documentation defines the Archive feature in the following way:

Recipients in the archive list will receive an exact replica of the message that was sent to the RCPT TO address. In particular, any encoded links intended for the RCPT TO recipient will be identical in the archive messages

The only difference between this archive copy and the original RCPT TO email is that some of the headers will be different since the target address for the archiving email is different, but the body of the email will be an exact replica!

If you want a deeper explanation, here is a link to the SparkPost documentation on creating duplicate (or archive) copies of an email. Sample X-MSYS-API headers for this project are shown later in this blog.

There is one caveat to this approach; while all of the event information in the original email is tied together by both a transmission_id and a message_id, there is no information in the inbound relay event (the mechanism for obtaining and disseminating the archive email) for the duplicate email that ties back to one of those two id’s and thus the information for the original email. This means we need to place data in the email body and the header of the original email as a way to tie together all of the SparkPost data from the original and archive email.

In order to create the code that is placed into the email body, I used the following process in the email creation application.

  1. Somewhere in the email body, I placed the following input entry:
    <input name="ArchiveCode" type="hidden" value="<<UID>>">
  2. Then I created a unique code and replaced the <<UID>> field:
    $uid = md5(uniqid(rand(), true));
    $emailBody = str_replace(“<<UID>>,$uid,$emailBody);

    Here is an example output:
    <input name="ArchiveCode" type="hidden" value="00006365263145">
  3. Next, I made sure I added the $UID to the meta_data block of the X-MSYS-API header. This step makes sure that the UID is embedded into each event output for the original email:


Now we have a way to tie all of the data from the original email to the email body of the archive.

Obtaining the Archive version

In order to obtain a copy of an email for archive, you need to take the following steps:

  1. Create a subdomain that you will send all archive (duplicate) email(s) to
  2. Set the appropriate DNS records to have all emails sent to that subdomain to SparkPost
  3. Create an inbound domain in SparkPost
  4. Create an inbound webhook in SparkPost
  5. Create an application (collector) to receive the SparkPost webhook data stream

The following two links can be used to help guide you through this process:

  1. SparkPost technical doc: Enabling Inbound Email Relaying & Relay Webhooks
  2. Also, the blog I wrote last year, Archiving Emails: A How-To Guide for Tracking Sent Mail will walk you through the creation of the inbound relay within SparkPost

* Note: as of Oct 2018, the Archive feature only works when sending emails using an SMTP connection to SparkPost, the RESTful API does not support this feature. ?That probably isn’t an issue because most emails that need this level of audit control tend to be personalized emails that are fully built out by a backend application before email delivery is needed.

Obtaining the duplicate email in a JSON structure

In the first phase of this project, all I’m storing is the rfc822 email format in S3 and some high-level description fields into a SQL table for searching. ?Since SparkPost will send the email data in a JSON structure to my archiving platform via webhook data streams, I built an application (often referred to as a collector) that accepts the Relay_Webhook data stream.

Each package from the SparkPost Relay_Webhook will contain the information of one duplicate email at a time, so breaking the JSON structure down into the targeted components for this project is rather straightforward. ?In my PHP code, getting the rfc822 formatted email was as easy as the following few lines of code:

if ($verb == "POST") {
    $body = file_get_contents("php://input");
    $fields = json_decode($body, true);
    $rfc822body = 
    $htmlbody = 
    $headers = 

Some of the information that I want to store into my SQL table resides in an array of header fields. ?So I wrote a small function that accepted the header array and looped through the array in order to obtain the data I was interested in storing:

function get_important_headers($headers, &$original_to, &$headerDate, &$subject, &$from)
???foreach ($headers as $key => $value) {
???????foreach ($value as $key_sub => $value_sub) {
???????????if ($key_sub == 'To') $original_to = $value_sub;
???????????if ($key_sub == 'Date') $headerDate = $value_sub;
???????????if ($key_sub == 'Subject') $subject = $value_sub;
???????????if ($key_sub == 'From') $from = $value_sub;

Now that I have the data, I am ready to store the body into S3.

Storing the duplicate email in S3

I’m sorry to disappoint you but I’m not going to give a step by step tutorial on creating an S3 bucket for storing the email nor am I going to describe how to create the necessary access key you will need in your application for uploading content to your bucket; there are better tutorials on this subject than I could ever write. ?Here a couple of articles that may help:

What I will do is to point out some of the settings that I chose that pertain to a project like this.

  1. Access Control. ?You not only need to set the security for the bucket, but you need to set the permissions for the items themselves. ?In my project, I use a very open policy of public-read because the sample data is not personal and I wanted easy access to the data. ?You will probably want a much stricter set of ACL policies. Here is a nice article on ACL settings:?
  2. Archiving the Archive.?In S3 there is something called Lifecycle Management. ?This allows you to move data from one type of S3 storage class to another. ?The different storage classes represent the amount of access you need to the stored data with lower costs associated with the storage you access the least. A good write up of the different classes and transitioning through them can be found in an AWS guide called, Transitioning Objects. In my case, I chose to create a lifecycle that moved each object from Standard to Glacier after one year. Glacier access is much cheaper than the standard S3 archive and will save me money in storage costs.

Once I have the S3 bucket created and my settings in place, S3 is ready for me to upload the rfc822 compliant email that I obtained from the SparkPost Relay Webhook data stream. But before uploading the rfc822 email payload to S3 I need to create a unique filename that I will use to store that email.

For the unique filename, I’m going to search the email body for the hidden id that the sending application placed into the email and use that id as the name of the file. There are more elegant ways to pull the connectorId from the html body, but for simplicity and clarity I’m going to use the following code:

???????$start = strpos($htmlbody, $inputField); ?
???????$start = strpos($htmlbody, "value=", $start) + 7;
???????$end = strpos($htmlbody, ">", $start) - 1;
???????$length = $end - $start;
???????$UID = substr($html, $start, $length);

* we are assuming that $inputField holds the value “ArchiveCode” and was found in my config.php file.

With the UID, we can then make the filename that will be used in S3:

$fileName = $ArchiveDirectory . '/' . $UID . '.eml';

Now I’m able to open up my connection to S3 and upload the file. If you look at the s3.php file in the GitHub repository you will see that it takes very little code to upload the file.

My last step is to log this entry into the MYSQL table.

Storing the Meta Data in MySQL

We grabbed all of the data necessary in a previous step, so the step of storage is easy. ?In this first phase I chose to build a table with the following fields:

  • An automated field entry for date/time
  • The target email address (RCPT_TO)
  • The timestamp from the email DATE header
  • The SUBJECT Header
  • The FROM email address header
  • The directory used in the S3 bucket
  • The S3 filename for the archived email

The function named, MySQLLog within the upload.php application file goes through the necessary steps to open the link to MySQL, inject the new row, test the results and close the link. I do add one other step for good measure and that is to log this data into a text file. Should I do a lot more logging for errors? Yes. But I do want to keep this code lite in order to allow it to run extremely fast. At times this code will be called hundreds of times per minute and needs to be as efficient as possible. In future updates, I will add ancillary code that will process failures and email those failures to an admin for monitoring.

Wrapping it up

So in a few fairly easy steps, we were able to walk through the first phase of building a robust email archiving system that holds the email duplicate in S3 and cross-referencing data in a MySQL table. ?This will give us a foundation for the rest of the project that will be tackled in several future posts.

In future revisions of this project I would expect to:

  1. Store all log events of the original email
  2. Send storage errors to an admin when a failure to upload or log happens
  3. Minimize the collector complexity.
  4. Add a UI for viewing all data
  5. Support the ability to resend the email

In the meantime, I hope this project has been interesting and helpful to you; happy sending.

~ Jeff

The post Building an Email Archiving System: Storing the Email Body – Part 2 appeared first on SparkPost.

Email Strategies Worth Investing In Fri, 01 Mar 2019 14:00:51 +0000 Email Strategies Worth InvestingOur new ebook, Email Strategies Worth Investing In, showcases examples of successful financial services emails from real financial services companies.

The post Email Strategies Worth Investing In appeared first on SparkPost.


Years ago the financial services industry relied more heavily on face-to-face interactions between customers and financial professionals like tellers and advisors. Nowadays, with the rise of technology, there is much less need for customers to enter a physical branch of a bank to have their requests addressed. Rather, customers rely on in-app and mobile OS notifications, SMS messages, and emails to keep track of deposits, withdrawals, payments sent and received, and more. Due to the sensitive nature of banking and personal finance, email is the backbone of communication between banks and customers as email messages are easier to save and refer back to than messaging through other communication channels. In fact, a 2018 study found email to be the top channel used by financial services companies to communicate with customers and prospects. More than that, a 2017 study indicated that the financial services industry leads all other verticals in email open rates (35.7%). With all of this in mind, how can financial services businesses effectively leverage email, a communication channel that is no doubt integral to the financial services industry?

Our new ebook, Email Strategies Worth Investing In, is designed to answer this question by showcasing examples of successful financial services emails from real financial institutions, banks, and fintech companies. We created this guide to help you craft a holistic email strategy that covers the entire customer lifestyle. The guide explores the most important use cases for sending email to your customers and guidelines on how to incorporate them into your strategy.

In this guide you will learn about:

  • The different types of financial services emails
  • Email best practices for financial services customer communications
  • How to build a relationship with your customers based on security and trust
  • Tons of examples of great triggered, transactional, and promotional financial services emails

Whether you’re a seasoned financial services email marketer or just learning the ropes, this guide will provide clear action items and steps you can take to improve your business’ email program. Download Email Strategies Worth Investing In now to dive into financial services email guidelines you can bank on.

~ Erica

The post Email Strategies Worth Investing In appeared first on SparkPost.

Email Marketing for Fiserv: How to be Compliant Without Breaking the Bank Wed, 27 Feb 2019 14:00:21 +0000 FiservDiscover how to design a Fiserv email campaign that is compliant with recent regulations and directives without exceeding your budget.

The post Email Marketing for Fiserv: How to be Compliant Without Breaking the Bank appeared first on SparkPost.


Financial services is without a doubt one of the world’s most regulated industries. It always has been. This traditional, thriving and ever-evolving sector is accustomed to complying with directives and regulations in almost every aspect of its operations, and customer-facing communication is no exception.

In email marketing, regulatory compliance is a requirement, and that applies to both B2B and retail banking. But, this doesn’t mean that the FCA is giving organizations a run for their money. The purpose is to protect markets, businesses and clients alike by establishing transparent rules of conduct. The Markets in Financial Instruments Directive is a case in point. The latest update to MiFID was introduced at the beginning of 2018 with the aim of improving transparency and trade reporting in European financial markets, but also to further protect businesses and consumers. MiFID II provides a framework for promotional and customer engagement activities run by Financial Services organizations including traditional banks and?FinTechs and requires a specific approach when it comes to the context and tone of communications.

When designing an email campaign for the financial?services industry, keep these guidelines in mind:

  • Marketing material and correspondence sent to existing or potential customers must comply with MiFID II. That includes promotions and disclosure of fees.
  • MiFID II demands language that is “fair, clear and not misleading.” This of course is good practice for marketing communications generally but has now become compulsory for financial?services organizations in Europe.
  • ?Marketing material should provide specific details about the anticipated performance of financial instruments and investments.
  • ?Warnings about risk must be prominent and clearly displayed in the same font type/size used for marketing content.
  • Marketing assets must be retained for at least five years.

Compliance can be expensive – the cost to the financial services industry as a whole is estimated to be over $2B – but it doesn’t have to “break the bank.” ?The market is evolving rapidly and with the strict regulations now in place, following best practices and leveraging email platform analytics will help banks and FinTechs to operate within the regulatory guidelines without having to invest in onerous compliance resources or compromising the outcome of their marketing campaigns.

~ Greg

The post Email Marketing for Fiserv: How to be Compliant Without Breaking the Bank appeared first on SparkPost.

Gmail’s Promotions Tab: Friend or Foe? Mon, 25 Feb 2019 14:00:44 +0000 Gmail's Promotions tabDiscover how Gmail's Promotions tab makes life easier for their users and can potentially help increase open rates on your marketing messages.

The post Gmail’s Promotions Tab: Friend or Foe? appeared first on SparkPost.


One of the most common requests I get from our customers is to help them get their marketing messages into Gmail’s Primary tab rather than Gmail’s Promotions tab.

Gmail introduced “tabs” and “new inbox” in May 2013. ?The new inbox routes incoming mail into categories which appear as different tabs: Primary, Social, Promotions, Updates, and Forums. This way you can simply choose which categories you want and organize your inbox in a way that lets you see what’s new at a glance.

This new inbox created a sudden panic amongst marketers as they feared that the?routing?of marketing emails to the Promotions tab would decrease the chances of their messages being seen and accordingly would cause a drop in open rates and revenue.

Some companies started getting creative and deployed scripts, while others encouraged their subscribers to create plugins to overwrite the tabs. Unsurprisingly, these “solutions” didn’t work for long.

There were two points marketers were missing:

1.? The Promotions tab is not the same as the Spam folder

All of the tabs from Primary to Updates are all considered to be “inbox”. The Spam folder, on the other hand, is a completely different story. If your messages are routed to the Spam folder, it means a high amount of people have marked your emails as such.

2. The Promotions tab is part of the inbox?

The Promotions tab is just a different category of messages in the inbox. It basically routes marketing messages to a unique tab so the end user can review marketing emails all in one place.

Now, almost 6 years after Gmail’s introduction of tabs to the email world, marketers have noticed that having marketing messages routed to the Promotions tab can potentially increase open rates. Given that most of us receive a very high number of emails per day, from our friends, e-commerce sites, social networking sites, and banking sites, it has become more and more challenging to prioritize which messages we need to focus on first. There is a higher chance of people reporting spam on marketing emails if they end up in the Primary tab.

The reality is that there is no golden rule to get marketing messages into the?Primary tab! So, please don’t fight the tabs. They are designed to make life easy for Gmail users and increase the chance that marketing emails are read. If you’re interested in learning more about deliverability best practices check out our eBook:?The New Rules of Email Deliverability.

~ Kate

The post Gmail’s Promotions Tab: Friend or Foe? appeared first on SparkPost.

3 Key Ways Financial Services Emails Have Changed Fri, 22 Feb 2019 14:00:44 +0000 financial services emailsRead about three important trends in financial services emails that institutions should pay attention to as they continue to engage consumers via email.

The post 3 Key Ways Financial Services Emails Have Changed appeared first on SparkPost.


Email may be the oldest direct-to-consumers digital channel still around, but it’s not going away any time soon. In fact, The Financial Brand found that 70% of all consumers (and 72.1% of older Millennials) think email will still be around in a decade, more than any communication channel they were asked about, including cable TV and social media.

Given email’s continued longevity, we’re highlighting three important trends in financial services emails that institutions should pay attention to as they continue to engage consumers through their inboxes.

Protecting users’ data privacy: then and now

Consumers have become increasingly vigilant about ensuring that all businesses protect their data, particularly in the financial services vertical. A Harris Poll survey conducted in seven countries found that 75% of adults will not buy a product from a company – no matter how great its products are – if they don’t trust that company to protect their data.

The European Union has long been strict about how companies handle its citizens’ private data. The Data Protection Directive (DPD) adopted in 1995 outlined seven principles that regulated the collection and processing of personal data, including names, addresses, government-issued ID numbers, credit card numbers, and bank statements. It affected all companies that handled data within the EU, including businesses physically located outside the EU that conduct transactions within its borders.

However, enforcement of the directive was difficult and expensive, due to the differing privacy laws in the EU member states, which led to the development of the General Data Protection Regulation (GDPR). The GDPR went into effect in May 2018 across the EU, ensuring that companies would no longer have to take different laws into account. Like the DPD, companies must comply with it when handling EU citizens’ data, even if those businesses are headquartered outside the EU.

Data privacy rights under today’s GDPR

The GDPR offers EU citizens several rights, including:

  • An explicit consent requirement for the collection of personal data
  • A 72-hour deadline for breach notifications
  • The ability to request a copy of personal data and know how it’s processed
  • A data erasure option (“right to be forgotten”)
  • Control over moving data from one company to another

In addition, the GDPR requires companies to include data privacy in the foundation of all systems designs and to appoint Data Protection Officers who have specific duties.

The GDPR doesn’t affect sending email, as long as the company has the consent of EU citizens. There’s no specific data retention requirement, including email storage, but the “right to be forgotten” may be superseded if the company needs to retain user data to comply with a legal obligation, such as financial regulations. There are other exceptions too.

Email as a vector for cyber attacks: then and now

Cybercrime in the financial services community is sharply rising. According to IntSights Cyber Intelligence, the average number of cyber attacks per US bank was 520 during the first half of 2018, more than double the 207 recorded in the first half of 2017. Many of those assaults happen through increasingly sophisticated phishing, spear phishing, and spoofing efforts that trick email recipients into clicking malicious links.

Part of the reason for email being a popular vehicle for cyber attacks is its use of SMTP (Simple Mail Transfer Protocol), which was developed in 1982 and has no authentication mechanisms. In the early 2000s, two standards were developed that layered authentication controls onto SMTP:

  • SPF (Sender Policy Framework): This standard defines a way to validate that an email was sent from an authorized email server.
  • DKIM (DomainKeys Identified Mail): This authentication method adds a digital signature to an email header. An inbound mail server validates it against a public cryptographic key in the sending organization’s public DNS records.

Wrapping SPF and DKIM into today’s DMARC security protocol

While SPF and DKIM are useful for reducing malicious email, neither of them allow domain owners to specify how unauthorized emails should be handled by inbound mail servers. DMARC (Domain-based Message Authentication, Reporting, and Conformance) does that by allowing companies to publish policies that define their email authentication practices and provide instructions for enforcing them.

With DMARC in place, an inbound mail server uses that policy to determine whether to accept, reject, or quarantine a message. Email senders can use DMARC to receive aggregate reports that show how many emails were rejected and quarantined, as well as forensic reports that help administrators troubleshoot authentication issues and identify malicious domains and websites.

SPF, DKIM, and DMARC are free to implement and aren’t difficult to use. While the five largest banks in the U.S. have deployed DMARC, only 11 of the top 50 banks in the U.S., and 9 of the 50 largest banks in Europe, are using it, according to the Global Cyber Alliance.

Email design: then and now

In 2011, mobile device users accounted for just 8% of email opens, according to Litmus. Back then, designers had a larger canvas to work with because they could assume that most people were opening emails on their computers.

However, Litmus saw email opens on mobile devices leap to 46% in June 2018, and the company believes that percentage could actually be 67% when accounting for the fact that Gmail counts email opens the same whether they happen in a web browser or in a mobile app. Litmus made the adjustment because Google says 75% of Gmail users access email on mobile devices.

3 characteristics of modern financial services emails

Given how many people open email on mobile devices today, it’s imperative that financial services companies adopt a “mobile first” mindset. There are three key ways they can do that:

  • Make emails mobile responsive: Like the way responsive websites automatically adapt to the user’s device, responsive emails adjust their layouts on mobile so recipients can read them without zooming in and scrolling around.
  • Use the highest resolution images possible: Many people own mobile devices with high-definition displays, so senders should ensure logos and photos don’t look pixelated when they open emails.
  • Take advantage of preheader text: Also known as preview text, this is a short snippet that appears below the subject line. It’s valuable for prompting people to open emails – if the preheader text isn’t specified, the mobile email client will default to something like, “Click here to view this email online with images.”

Get started

Financial services companies should consider those three trends when creating emails and sending them to consumers, so they help protect users’ privacy, fend off the bad guys, and keep engagement rates high.

~ Casey

The post 3 Key Ways Financial Services Emails Have Changed appeared first on SparkPost.

On-Premises and Cloud: Putting the Pieces Together Wed, 20 Feb 2019 14:00:01 +0000 on-premisesIn our upcoming webinar, hear directly from our team of on-premises experts about how to confidently use both on-prem and cloud email solutions.

The post On-Premises and Cloud: Putting the Pieces Together appeared first on SparkPost.


If you have an on-premises email solution today, you know how much work it is to maintain the database, spin up new servers, worry about bandwidth and capacity, and have recommendations ready for when your ISP goes down or power goes out.

Beyond the database portion and building up your own environment, the email metrics are nothing to write home about. There is no way to see open or click metrics and no way to really check to see if a campaign did well or look at historical performance of campaigns over time. And the truth is, many folks turn to outside consultants to help bridge the knowledge gap and the ongoing maintenance, which can be costly over time.

While moving your email infrastructure to the cloud may sound like a daunting hassle, what if I told you it’s really not all that hard. In fact, there are many options that you have at your fingertips today as an on-premises user that can get you real-time analytics and the email expertise at your fingertips, without having to hire a consultant or a dba.

In our upcoming webinar, “On-Premises and Cloud: Putting the Pieces Together,” you’ll have an opportunity to hear directly from our team of on-premises experts about how to confidently use both on-prem and cloud solutions as well as what it really means to migrate completely to the cloud. I think you’ll be pleasantly surprised to find out it’s not as painful as you think.

Register to hear our experts speak about:

  • The pros and cons of deploying Momentum or PowerMTA in cloud services
  • How to downsize physical data centers and cut costs·
  • SparkPost’s cloud offering and how it works
  • SparkPost’s new features including BYOIP and SparkPost Signals for on-prem
  • How you can leverage PowerMTA or Momentum with SparkPost
  • Implementation of hybrid on-prem/cloud solutions
  • BONUS: Upcoming networking events with our partners for our on-prem customers

Hope to see you there!

~ Tracy

The post On-Premises and Cloud: Putting the Pieces Together appeared first on SparkPost.

5 Valentine’s Day Cards for the Email Geeks in your Life Thu, 14 Feb 2019 14:00:49 +0000 Valentine's DayWe’ve put together 5 Valentine's Day cards with tasteful copy and graphic design so all you have to do is just download and send to your email geek.

The post 5 Valentine’s Day Cards for the Email Geeks in your Life appeared first on SparkPost.


Today is the day to make a grand gesture and let that special email geek in your life know how you really feel about them. Unfortunately, sometimes it can be hard to find the right words to let someone know exactly just how great you think they are. Luckily for you, we’ve put together 5 Valentine’s Day cards with extremely thoughtful copy and tasteful graphic design so all you have to do is just download and send to your email geek. These cards will have your valentine saying, “You shouldn’t have, no…really, you shouldn’t have.”

We are SO excited to provide you with these cards so you can focus less on thinking of something unique and meaningful to say to your special someone and more time on your one true love: email.

Happy Valentine’s Day!


The post 5 Valentine’s Day Cards for the Email Geeks in your Life appeared first on SparkPost.

How to Create a Seamless Omni-Channel Marketing Program with MessageBird and SparkPost Wed, 13 Feb 2019 14:00:35 +0000 Learn how our partnership with MessageBird provides enterprises with a solid path to enhance customer experience by employing the best technology available.

The post How to Create a Seamless Omni-Channel Marketing Program with MessageBird and SparkPost appeared first on SparkPost.


Here’s a fact: 15 years ago, the average consumer typically used two touch-points when buying an item and only 7% regularly used more than four. Today though, consumers use an average of almost six touch-points, with nearly 50% regularly using more than four. And they expect the same rich experience during all interactions with a brand.

Delivering that experience is not as easy as it sounds. Many companies are off message with their customer service; while consumers are well aware of a brand’s shortcomings. In fact, a Zendesk study showed that 87% believe that brands need to work harder to create a seamless customer experience. And while email remains the king of ROI, businesses across the globe are looking for ways to unify and enhance company-customer interactions and ensure a high level of service for consumers.

They need look no further. Yesterday, we announced a strategic partnership agreement with MessageBird to extend the communications channels available to businesses. MessageBird is the cloud communications platform that has been connecting companies to their customers on billions of devices since 2011. As part of the agreement, SparkPost will extend the MessageBird cloud communications platform to our customers, while MessageBird further extends its omnichannel capabilities by making SparkPost email available via its popular Programmable Conversations API.

This agreement provides enterprises with a solid path to enhance customer experience by employing the best technology available; both MessageBird and SparkPost are leaders in their respective markets, with proven experience at helping businesses reach their business objectives.

Through our partnership with MessageBird, we can offer businesses seamless access to an even broader range of communications solutions to enhance customer engagement. Our customers can now leverage the highly scalable MessageBird platform to send messages with unrivaled speed and reliability anywhere in the world. Conversely, MessageBird adds the ability to send email via its popular Programmable Conversations API, which unifies customer interactions across multiple channels into a single conversation thread. The partnership with SparkPost provides businesses with a complete omnichannel experience that includes the highest email deliverability possible by the world’s most popular email solution.

Why should companies consider this? Here’s three good reasons:

  • Customer retention: Companies with strong omnichannel engagement strategies retain 89% of their customers (Invesp).
  • Increased customer value: Omnichannel customers have a 30% higher lifetime value than those who shop using only one channel (IDC).
  • Increased revenue: People are willing to pay up to 15% more for a great consumer experience (PwC).

To find out more, visit


The post How to Create a Seamless Omni-Channel Marketing Program with MessageBird and SparkPost appeared first on SparkPost.

Dating Apps and Triggered Email: It’s a Match! Mon, 11 Feb 2019 14:00:33 +0000 dating appsCheck out how dating apps like Tinder, Hinge, and Coffee Meets Bagel use app-generated email to simplify and streamline their users’ love lives.

The post Dating Apps and Triggered Email: It’s a Match! appeared first on SparkPost.


Somewhere along the way Cupid stopped shooting arrows and started sending emails. It’s hard to say exactly when this shift happened but I’d guess it was sometime around 1995 when was first launched. For nearly a quarter of a century, people have turned to the internet to find love through websites and since 2009 through dating apps. While most users interact with brands like Tinder, Hinge, and Coffee Meets Bagel through their mobile apps, the user experience these dating apps provide would not be complete without their unique triggered email programs, respectively.

Check out how Tinder, Hinge, and Coffee Meets Bagel employ app-generated email to simplify and streamline their users’ love lives:

It’s a Match!

Tinder, which amongst other things is known for creating “double opt-in” technology in which two users must both mutually like each other (or “swipe right”) for the app to deem the interaction a “match”. Scoring a Tinder match can feel super exciting, particularly when you’re very interested in the person who swiped right on you. Maybe it was her totally original shot in front of an angel wings mural or the impressive fish he’s holding in every photo, but something caught your attention. But, what happens when you’re too busy to check Tinder or have your push notifications turned off? Do you completely miss out on these match opportunities?

Lucky for singles everywhere, Tinder sends out triggered email messages when users are matched. These minimalistic branded emails allow users to easily engage with the app as when the email is viewed on a mobile device the “Find Out Who” CTA button in the email opens up the Tinder app directly to the page that displays a user’s matches. More than that, when clicked on, the “turn on push notifications” hyperlink leads directly to the settings page of Tinder’s app. These app-generated emails lead users directly back to the app itself, creating a seamless full-circle customer experience.

We Think You Two Should Meet!

Hinge which originally launched in 2012, made use of the same “double opt-in” initially popularized by Tinder. However, in 2017 they relaunched with a new UI that completely disrupted Tinder’s (and nearly every other dating app’s) “Swipe Right – Swipe Left” paradigm. Hinge’s new design requires users to read others’ profiles and like a specific part of a profile rather than swiping quickly and making snap judgments about other users. In addition to the new design, Hinge also recommends users to one another based on their algorithm and user data. Just in the same way Hinge’s design requires users to spend more time looking at each profile, Hinge also spends time “hand-selecting” recommendations for a more curated experience. Accordingly, when one of these recommendations is created Hinge sends an app-generated email notification:

Hinge’s transactional emails not only highlight their unique recommendation feature but also cleverly invite users to engage with the app even though they don’t necessarily have a new match. Similar to the button in Tinder’s transactional Match emails, the light green “View” CTA button in Hinge’s email when viewed on a mobile device leads directly to the user’s profile the app has recommended. Almost instantaneously, users are able to look at a curated potential match, and even if the recommendation isn’t spot-on Hinge has brought users back on to their app where they can continue scouting for potential matches that are more to their liking.

Check your Bagels!

Coffee Meets Bagel creates a curated experience by offering a finite amount of potential matches (which they call Bagels) for users to consider once a day. Each day at noon, Coffee Meets Bagel sends out a push notification paired with a triggered email to remind users to check their Bagels. Because Bagels “expire” after 24 hours it’s imperative that users check their batch of Bagels everyday in order to see the most amount of profiles and conversely, have their profile shown to people they’re interested in.Each of Coffee Meets Bagel’s app-generated email’s subject lines contain the daily push notification. The body of each email, however, is identical and reminds users about the necessary urgency of checking their Bagels each day. Following the same convention as Tinder and Hinge, the “Check Now” button opens up Coffee Meets Bagel’s app so users can check out their batch of piping hot Bagels. The gamified nature of the app and corresponding frequency of their app-generated emails encourages users to build a daily ritual around checking the app– something I might add that can be hard to do discreetly at work…??

While Tinder, Hinge, and Coffee Meets Bagel are certainly not the only dating apps out there communicating with customers via triggered emails, their three different spins on the technology show the importance of app-generated email within the dating space. When it comes to a new match, a promising recommendation, or a potentially great first date, scouting singles deserve encouraging and timely notifications. We may be biased, but the key to finding love may just be checking your email!

Happy Valentine’s Day!


The post Dating Apps and Triggered Email: It’s a Match! appeared first on SparkPost.

Looking Closer at 4 of the Most Innovative Fintech Companies Fri, 08 Feb 2019 14:00:17 +0000 fintech companiesCheck out these four examples of fintech companies that have made their apps and websites pleasurable to use while adhering to the law.

The post Looking Closer at 4 of the Most Innovative Fintech Companies appeared first on SparkPost.


It’s not hard to find examples of financial services companies that struggle with updating the decades-old ways they do business for the modern world. Regulations hamper them to some degree, forcing them to, for example, make onboarding more tedious than signing up for a social network.

However, there are fintech companies out there that have figured out how to make their apps and websites pleasurable to use while adhering to the law. Here are four aspects of a fintech app or website that you should pay attention to during the development phase, along with examples of companies that do those things well.

Onboarding: Setting users up for success

Many financial services companies struggle to bolt modern sensibilities onto user interfaces that were first built during the early days of the web. As a result, their sign-up and onboarding flows can be difficult to navigate, with legacy UI elements competing with newer technologies.

Acorns, however, has figured out how to make onboarding enjoyable, or at least as enjoyable as an app that encourages people to save money can be. The company took an old idea – tossing spare change in a jar – and modernized it by rounding up users’ credit and debit card purchases to the nearest dollar and investing the spare change for them.

Acorns users also benefit when they make purchases from companies like Nike and Airbnb, and they can simply transfer money into their accounts on a one-time basis or according to a schedule. The service offers a “set it and forget it” way of saving money.

When users install and launch the Acorns app, they’re greeted with a clean onboarding process that employs just five screens to explain what the service does. Engaging animations and brief, straight-to-the-point text make a subject that could feel like drudgery into something light and enjoyable.

However, the rubber meets the road in any app when the time comes to sign up for the service. In the financial space, companies must figure out how to abide by regulations while keeping new users from getting bogged down in lots of legalese and clicking or tapping.

On the other hand, a breezy sign-up process cannot only possibly expose a company to legal liability but can also worry new users that the service isn’t as secure as it should be. If someone just has to enter an email address and a password to get started, does that mean the company will be on the ball when it comes to protecting their account?

Acorns does a good job of walking that line by making it as easy as possible to create an account while abiding by legal requirements with the link to the program agreement. Indicators show that the user has entered a valid email address and created a sufficient password, so there’s no “Oops, you need to go back and fix something” message when tapping Create Account.

Before the user links their bank account, Acorns takes a moment to insert a visual reminder of the benefit they offer, which helps reassure people who may have glossed over the earlier explanatory screens. And when the time comes to enter personal information, including a Social Security number, Acorns gets straight to the point and notes that this is a requirement for opening an investment account. Note that they’ve built in a handy auto-complete function for the Contact Information screen.

The final part of the onboarding process involves choosing an investment portfolio based on answers to a few questions about income and assets. (Acorns asks for income and asset ranges, rather than specific amounts.) Then it produces a handy screen that breaks down the user’s portfolio in a pie chart and leaves them with some words of wisdom from Warren Buffet.

Using the app: Ensuring users come back for more

Of course, getting a new user signed up is just half the battle (or less). They need a reason to stay engaged with an app or website, constantly finding new things to do or, at a minimum, needing to regularly check on their accounts.

The investing app Robinhood has racked up over 5 million users, many of them members of the millennial generation, by offering commission-free stock trading as well as commission-free cryptocurrency transactions in some states. Robinhood also makes buying and selling stocks as simple as a few taps and a swipe up to confirm – that last action helps keep users from accidentally making trades.

Confetti even showers the screen after the user buys stock. We’ll go out on a limb and assume that investing apps from decades-old companies don’t do that.

Robinhood brings the same slick UI to the rest of the app. The home screen displays the user’s total money in stocks, cryptocurrencies, and cash, with the percentage increase or decrease that day and a graph that can be viewed on various timelines. The user can press and hold on the graph to see their portfolio’s value on that date. More detailed portfolio information is found in the user’s Account screen.

Each stock and cryptocurrency offered in Robinhood has a scrollable screen with plenty of handy information, including news articles culled from the Internet and historical earnings data going back four quarters. The cryptocurrencies also have comment threads that add a social factor to an area of investing still in its infancy.

Account management: Eliminating the pain points

It’s crucial to keep users engaged, especially as new ones approach the time when you find them more susceptible to churning for various reasons. However, account management plays a role in minimizing churn too: difficulties with that area of your app or website could be a contributing factor in their decision to abandon it.

Wefunder, founded in 2011, describes itself as “Kickstarter for investing.” It allows anyone to invest as little as $100 in a start-up that interests them, with the understanding that start-ups can be very volatile and many of them fail.

Surprisingly, they don’t have a mobile app, but perhaps that’s because investing in start-ups is something best done with a cup of coffee while reading articles and financial data on a laptop or desktop. Small screens tend to lend themselves to quick browsing and high drop-off rates, which isn’t optimal when someone is trying to decide whether to invest some of their hard-earned money in a nascent business.

After someone creates their Wefunder account and answers some questions to create a profile that lets them interact with other investors, as well as start-ups, they use the Settings area of the website to manage their account. It’s set up in a simple, easy-to-use manner, with a handy red Deactivate Your Account button in the Account menu. That may not seem like much, but given how hard some companies make it to disengage from them, it’s nice to know that Wefunder doesn’t want to use obfuscation to buoy account metrics.

The rest of the Settings sub-menus are also pretty simple, although the Notifications area is a bit lengthy, with several options for getting emails about new fundraisers, companies the user is following, and social interactions, among other activities. However, it’s not too unwieldy to use on a desktop or laptop computer.

The rest of the settings cover things that are relevant to Wefunder users, such as Investor Limits, which has sliders for net worth and annual income. As the user adjusts the sliders, information dynamically changes in the “How much am I allowed to invest?” section below. Under each allowed investment amount, it says “Why?” – the user can hover over that to see a pop-up that explains more details.

It’s a well-done way of giving the user a big picture view of their investment limits since Wefunder has to abide by quite a few regulations.

At a certain level of income, a pre-checked box appears, with text that begins “I am an accredited investor” next to it. Accredited investors can invest an unlimited amount in Regulation D and Regulation A+ start-ups, so that’s an important distinction that Wefunder has to highlight “for boring SEC regulation reasons,” as they say.

Security: Keeping away the bad guys

Even after you’ve gotten users hooked on your service and turn them into steady customers, you have to keep an eye on security. Poor security can easily ruin months and even years of painstaking work.

PayPal rose to prominence alongside eBay, which later acquired the company and then spun it off as a separate entity, so it had a large head start on newer companies in the payments space. Its 20-year history has also given it plenty of time to bake security into its website and mobile app.

While other services like Venmo, which is now part of PayPal, have arisen in the “friends and family” segment of the digital money transfer space, PayPal still makes social financial transactions easy and secure through its mobile app. It offers an option to use a fingerprint to log in, with that requirement renewing if the app is open for longer than a few minutes, and it doesn’t store anything more than the last four digits of credit card, debit card, and bank account numbers.

PayPal employs industry-standard security and requires merchants that accept it as a payment method to do the same. It also has a bounty program that offers a financial reward to anyone who discovers and submits a valid vulnerability in its system. Many companies, including those outside the financial services space, do the same thing – it’s a good way to ensure that a company’s internal teams haven’t missed anything.

In PayPal’s mobile app, the Help section of its settings menu offers a handy way for mobile users to get assistance when they run into problems while on the go, rather than having to dig through the website. Each topic contains several useful articles that cover everything from the basics to how to identify phishing emails.

Using deep linking to drive user engagement in your app

When designing your website and mobile app, you’ll want to consider ways to drive users to specific areas of your service through notifications sent by email, desktop and mobile OS alerts, text messages, and other channels. While deep linking them to a specific place on your website is fairly straightforward, the same technique is a little trickier in an app.

You’ll want to use a URI (Uniform Resource Identifier) to link a specific location within your app, but that standard differs for each mobile platform, including the two most popular ones, Apple’s iOS and Google’s Android. To ensure none of your users encounter problems if their device’s OS doesn’t know where to redirect a link, you’ll want to use one of two types of advanced deep links: deferred or contextual.

How a deferred deep link works

When you create a deferred deep link, you can direct users who don’t have your app installed to a website link or to the appropriate app store to download it. The link is called deferred because, if the user installs the app and then opens it, they’re immediately sent to the desired content, as if the app was on their device when they first tapped the link.

How a contextual deep link works

A contextual deep link works the same as a deferred deep link, but it adds tracking data to your users’ activities, which is helpful for measuring the effectiveness of your marketing efforts. That information can include:

  • Who users are, where they were referred from, and who referred them
  • Whether they used a promo code
  • Which parts of your app they visited

A contextual deep link also allows you to personalize the user experience. For example, if the user followed a friend’s recommendation into your app, you can create a message for them that acknowledges the referral.

How to set up different kinds of deep links

Your app needs to be set up so that it can deal with incoming links and seamlessly send users to the right places so that the underlying redirects are invisible to them. iOS and Android currently support deep links that use the same HTTP (Hypertext Transfer Protocol) convention used by traditional web page URLs. iOS started that support with version 9.2, calling them Universal Links, and Android began with version 6.0, where they’re known as Android App Links.

When creating a deferred deep link, it’s best to implement it as a URL starting with HTTP and specify a fallback that uses a URI, in case a user has an earlier version of iOS or Android that doesn’t support HTTP links. Such a setup is also useful in case the user is directed to your app from another app that can only handle URIs.


The post Looking Closer at 4 of the Most Innovative Fintech Companies appeared first on SparkPost.

Align Your Marketing and Transactional Emails for a Great CX Wed, 06 Feb 2019 14:00:31 +0000 transactional emailsDiscover how to ensure that your business' transactional and marketing email messages are aligned to deliver a great customer experience.

The post Align Your Marketing and Transactional Emails for a Great CX appeared first on SparkPost.


Fintech and financial services, B2B SaaS platforms, e-commerce, and other industries have very diverse product requirements. Yet, product teams who succeed in driving adoption and growth for solutions in their particular markets also have something in common: a focus on delivering a great customer experience (CX).

That’s not news to you if you’re a product manager building an app or service. You already know how important CX is to the success of your product. And, like many successful product teams, you might already understand how important email notifications are to user engagement and retention.

But there is one aspect of product emails that sometimes gets short shrift in this equation: ensuring that all of a user’s email touchpoints deliver a great experience. And that means making sure transactional and marketing email messages are aligned to deliver a great CX.

Transactional Receipts, Password Resets, Product Announcements, and Legal Notices, Oh My!

Should be easy, right? After all, most companies are chock full of motivated teams building great products who want to do right by their customers. But the reality is that too many businesses are structured in a way that silos responsibility for different communications and makes it hard to deliver on the promise of a consistent customer experience.

And that’s reflected in how emails are designed, sent, and delivered. Some messages might be sent using a marketing-centric tool, while others are hard-coded into the app or a back-end system. Just consider two examples I recently received in my inbox:

To be sure, there are some practical reasons (including a very real concern for security!) why the bank chose this approach. But as a user, it’s jarring and interrupts my customer experience in a pretty significant way. Compare it with these examples:

Ahh, that feels like a much better experience! And just as importantly, they make it easy for the user to engage and accomplish the actions that deliver value for them and the institution alike.

Important Transactional and Marketing Email Differences

To be sure, marketing and transactional emails do have some important differences?that must be respected. First, quick definitions:

  • “Transactional emails”?are sent to a person as a result of a?specific?action taken?by the user. Think receipts, password resets, and other messages necessary to the basic operation of a product and business.
  • Marketing and other so-called “commercial emails” are promotional messages sent to a user in order to drive awareness, encourage engagement, or make a sale.

Among other things, they’re regulated differently in most markets. The U.S. “CAN-SPAM” law, Canada’s CASL regulation, and similar rules in the E.U. and elsewhere define whether an email is considered a necessary part of doing business; these transactional messages get certain exemptions from rules that govern opt-in/opt-out requirements and the like.

Those legal distinctions matter, of course, but they should not be an excuse to treat transactional messages as ugly ducklings. On the contrary, because transactional emails such as receipts, password resets, privacy and other legal notices are such common—and in fact, unavoidable—parts of the customer experience, it’s even more critical that they be designed from the perspective of a holistic, unified customer experience and not shunted off, inflexibly hard-coded into back-end systems.

Recipes for Success: Build a Great CX with Email

Aligning marketing and transactional emails is an important aspect of delivering a great experience for your customers, but it’s also just one part of the puzzle. Fortunately, SparkPost’s email pros have developed helpful guides that give teams a solid foundation using email to grow and support great products.

  • If you’re building a SaaS product, “The Product Manager’s Guide to Email” shows how email delivers an outsized impact on user engagement. The guide explains how to use notifications, alerts, transactional emails, and more to build a great app.
  • Meanwhile, “Email 101 for Financial Services” delivers a crash course for product teams in banking, insurance, and similar industries. It gives teams what they need to know to improve the ROI of email operations with recommendations specific to their market’s key concerns.
  • Finally, SparkPost’s “Transactional Email Benchmark Report” provides data-driven benchmarks that define the state of transactional email today, along with recommendations that will improve the effectiveness of your own messages.

Is your team approaching email from a CX perspective? I’d love to hear your experiences aligning marketing and transactional messages.


The post Align Your Marketing and Transactional Emails for a Great CX appeared first on SparkPost.

Building an Email Archiving System: The Challenges and of Course the Solution – Part 1 Mon, 04 Feb 2019 14:00:09 +0000 email archiving systemOur Senior Messaging Engineer describes the process he went through in order to store the email body onto S3 and all relevant log data in MySQL.

The post Building an Email Archiving System: The Challenges and of Course the Solution – Part 1 appeared first on SparkPost.


About a year ago I wrote a blog on how to retrieve copies of emails for archival and viewing but I did not broach the actual storing of the email or related data, and recently I wrote a blog on storing all of the event data (i.e. when the email was sent, opens, clicks bounces, unsubscribes, etc) on an email for the purpose of auditing, but chose not to create any supporting code.

With the increase of email usage in regulatory environments, I have decided it is time to start a new project that pulls all of this together with code samples on how to store the email body and all of its associated data. Over the next year, I will continue to build on this project with the aim to create a working storage and viewing application for archived emails and all log information produced by SparkPost. SparkPost does not have a system that archives the email body but it does make building an archival platform fairly easy.

In this blog series, I will describe the process I went through in order to store the email body onto S3 (Amazon’s Simple Store Service) and all relevant log data in MySQL for easy cross-referencing. ?Ultimately, this is the starting point for building an application that will allow for easy searching of archived emails, then displaying those emails along with the event (log) data. The code for this project can be found in the following GitHub repository:

This first entry of the blog series is going to describe the challenge and lay out an architecture for the solution. The rest of the blogs will detail out portions of the solution along with code samples.

The first step in my process was to figure out how I was going to obtain a copy of the email sent to the original recipient. In order to obtain a copy of the email body, you need to either:

  1. Capture the email body before sending the email
  2. Get the email server to store a copy
  3. Have the email server create a copy for you to store

If the email server is adding items like link tracking or open tracking, you can’t use #1 because it won’t reflect the open/click tracking changes.

That means that either the server has to store the email or somehow offer a copy of that email to you for storage. Since SparkPost does not have a storage mechanism for email bodies but does have a way to create a copy of the email, we will have SparkPost send us a duplicate of the email for us to store in S3.

This is done by using SparkPost’s Archive feature. SparkPost’s Archive feature gives the sender the ability to tell SparkPost to send a duplicate of the email to one or more email addresses?and use the same tracking and open links as the original. SparkPost documentation defines their Archive feature in the following manner:

Recipients in the archive list will receive an exact replica of the message that was sent to the RCPT TO address. In particular, any encoded links intended for the RCPT TO recipient will be identical in the archive messages

The only differences from the RCPT TO email are that some of the headers will be different since the target address for the archiving email is different, but the body of the email will be an exact replica!

If you want a deeper explanation here is a link to the SparkPost documentation on creating duplicate (or archive) copies of an email.

As a side note, SparkPost actually allows you to send emails to cc, bcc, and archive email addresses. For this solution, we are focused on the archive addresses.

* Notice * Archived emails can ONLY be created when injecting emails into SparkPost via SMTP!

Now that we know how to obtain a copy of the original email, we need to look at the log data that is produced and some of the subtle nuances within that data. SparkPost tracks everything that happens on its servers and offers that information up to you in the form of message-events. Those events are stored on SparkPost for 10 days and can be pulled from the server via a RESTful API called message-events, or you can have SparkPost push those events to any number of collecting applications that you wish. ?The push mechanism is done through webhooks and is done in real time.

Currently, there are 14 different events that may happen to an email. ?Here is a list of the current events:


Click Delay


Generation Failure

Generation Rejection

Initial Open

Injection Link Unsubscribe

List Unsubscribe


Out of Band

Policy Rejection Spam Complaint

* Follow this link for an up to date reference guide for a description of each event along with the data that is shared for each event.

Each event has numerous fields that match the event type. ?Some fields like the

?are found in every event, but other fields may be more event-specific; for example, only open and click events have geotag information.

One very important message event entry to this project is the

. ?All of the message event entries for the original email, archived email and any cc and bcc addresses will share the same

There is also a common entry called the

?that will have the same id for each entry of the original email and the archived email. Any cc or bcc addresses will have their own id for the

So far this sounds great and frankly fairly easy, but now is the challenging part. Remember, in order to get the archive email, we have SparkPost send a duplicate of the original email to another email address which corresponds to some inbox that you have access to. But in order to automate this solution and store the email body, I’m going to use another feature of SparkPost’s called Inbound Email Relaying. What that does, is take all emails sent to a specific domain and process them. By processing them, it rips the email apart and creates a JSON structure which is then delivered to an application via a webhook. See Appendix A for a sample JSON.

If you look real carefully, you will notice that the JSON structure from the

inbound relay
?is missing a very important field; the
. While all of the outbound emails have the
? with the same entry which binds all of the data from the original email, archive, cc, and bcc addresses; SparkPost has no way to know that the email captured by the inbound process is connected to any of the outbound emails. The inbound process simply knows that an email was sent to a specific domain and to parse the email. That’s it. It will treat any email sent to that domain the same way, be it a reply from a customer or the archive email send from SparkPost.

So the trick is; how do you glue the outbound data to the inbound process that just grabbed the archived version of the email? What I decided to do is to hide a unique id in the body of the email. How this is done is up to you, but I simply created an input field with the hidden tag turned on.

<input name="ArchiveCode" type="hidden" value="<<UID>>">

I also added that field into the metadata block of the X-MSYS-API header which is passed to SparkPost during injection. This hidden UID will end up being the glue to the whole process, and is a main component of the project and will be discussed in depth in the following blog posts.

Now that we have the UID that will glue this project together and understand why it’s necessary, I can start to build the vision of the overall project and corresponding blog posts.

  1. Capturing and storing the archive email along with a database entry for searching/indexing
  2. Capture all message event data
  3. Create an application to view the email and all corresponding data

Here is a simple diagram of the project:

The first drop of code will cover the archive process and storing the email onto S3, while the second code drop will cover storing all of the log data from message-events into MySQL. You can expect the first two code drops and blog entries sometime in early 2019. ?If you have any questions or suggestions, please feel free to pass them along.

Happy Sending.

– Jeff

Appendix A:

"msys": {
  "relay_message": {
    "rcpt_to": "",
    "friendly_from": "",
    "customer_id": "122",
    "content": {
      "subject": "test Tue, 04 Dec 2018 17:28:12 -0800",
      "html": <html_body>,
      "headers": [{
        "Return-Path": "<>"
      }, {
        "Authentication-Results": "…."
      }, {
        "Received": "from [] ([] helo=mta…."
      }, {
        "DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed\/relaxed; d=mail.geekwitha; …."
      }, {
        "X-MSFBL": "iGlF1akiy0VZT34sRlvFVNKusa4lkwzCcN…."
      }, {
        "Authentication-Results": " smtp.user=<hidden>; …."
      }, {
        "Received": "from [] ([] helo=jeff-...."
      }, {
        "Date": "Tue, 04 Dec 2018 17:28:12 -0800"
      }, {
        "To": ""
      }, {
        "From": ""
      }, {
        "Subject": "test Tue, 04 Dec 2018 17:28:12 -0800"
      }, {
        "Message-Id": "<20181204172812.046850@jeff-gs-macbook-pro.local>"
      }, {
        "X-Mailer": "swaks v20170101.0\/john\/code\/swaks\/"
      }, {
        "MIME-Version": "1.0"
      }, {
        "Content-Type": "text\/html"
      }, {
        "Cc": ""
      }, {
        "List-Unsubscribe": "<"
      }, {
        "List-Id": "<spc-122-0>"
      "email_rfc822": <rfc822 compliant email>,
      "email_rfc822_is_base64": false,
      "to": [""],
      "cc": [""]
    "msg_from": "",
    "webhook_id": "66600222946105557",
    "protocol": "smtp"

The post Building an Email Archiving System: The Challenges and of Course the Solution – Part 1 appeared first on SparkPost.

S/MIME Part 4: Collecting Recipient Public Keys the Easy Way – with SparkPost Inbound Relay Webhooks Fri, 01 Feb 2019 14:00:10 +0000 recipient public keysIn part 4 of his series, Senior Messaging Engineer, Steve Tuck explains how to collect recipient public keys with SparkPost Inbound Relay webhooks.

The post S/MIME Part 4: Collecting Recipient Public Keys the Easy Way – with SparkPost Inbound Relay Webhooks appeared first on SparkPost.


In part 1, we had a quick tour of S/MIME, looking at signing and encryption of our message streams across a range of mail clients. Part 2 took us through a simple command-line tool to sign and encrypt emails, then send them through SparkPost. Part 3 showed how to inject secure mail streams into on-premises platforms such as Port25 PowerMTA and Momentum.

In this series, we’ve seen how including an S/MIME signature is fairly straightforward. Sending S/MIME encrypted mail is more complex because you need to obtain recipient public keys. It’s one thing when you’re using a mail client for humans such as Thunderbird – but how can that work with app-generated email streams?

But wait – there is another way into Mordor to get those keys. Your service can invite your customers (via email, of course) to send you back a signed mail to a known customer-service address. Using the magical powers of SparkPost Inbound Relay webhooks, we’ll extract and store that public key for you to use.

We can summarise this in a simple use-case:

  • As a recipient of messages, I provide your service with my personal email signature via email, so that in future, emails can be sent to me in S/MIME encrypted form.

From this, let’s derive some more detailed requirements:

  • We need an always-on, reliable inbound email service to receive those signed emails.
  • There should be no special requirements on the mail format, other than it should carry an S/MIME signature.
  • Because anyone can try to send a mail to this service, it should be designed defensively, for example, to reject “spoof” messages from bad actors. There will need to be several layers of checking.
  • If everything checks out OK, the service will store the certificate in a file, using the well-known plain-text Privacy-Enhanced Mail (PEM) format.

There are some non-functional requirements:

  • Machine-to-machine webhook services can be hard to see just from responses to what’s happening inside. The service should provide extensive human-readable application-level logs. In particular, the certificate parsing and checking should be logged.
  • We add test cases for the app internals, using the nice Pytest framework, and run those tests automatically on check-in using Travis CI integration with GitHub.

OK – let’s get started!

1. Solution overview

Here’s what the overall solution will look like.

2. Installing, configuring and starting the web app

We’ll start with this part, so we have it fully tested before plumbing the inbound relay webhooks.

The web app is included in the same GitHub project as parts 1 – 3, so if you’ve followed those parts, you already have it. Here are the new bits:

  • Program – read an email and parse out intermediate and user certificates.
  • Program – simple Flask-compatible web application for use with SparkPost Inbound Relay Webhooks.
  • webapp.ini – configuration file for the above. A config file enables the same values to be passed in easily to both command-line and web applications.

You need to ensure your host has the correct TCP port number open to inbound requests from the outside world so that SparkPost can POST messages to your app. If you’re hosted on AWS EC2, for example, you’ll need to configure the Security Group of your instance.

Instructions for configuring and starting the web app are given here – it’s quite easy. To check your app is running and accessible from the outside world, you can send (blank) requests from another host using curl, for example:

curl -X POST

You should see a response such as:

{"message":"Unknown Content-Type in request headers"}

This is a good thing – your app is running!

In webapp.log on your host, you’ll see output similar to this:

2019-01-15 00:11:07,575,root,INFO,Request from,scheme=https,path=/
2019-01-15 00:11:07,575,root,INFO,| len(headers)=3,len(body)=None
2019-01-15 00:11:07,575,root,INFO,| Unknown Content-Type: None

To help you play with real data in your app straight away, you can import this specific Postman request from the project repo. This simulates what your SparkPost account will be doing, i.e. it sends an https POST containing an email with a specific, valid certificate (belonging to a test account of mine)?to your app.

You just need to change the target address in the request (in the gray box above) to match your installation. If you changed the token value in webapp.ini, adjust the header value in Postman to match.

If your app is working, you will see a “200 OK” response back in Postman. Your host webapp.log file will contain output like this:

2019-01-15 00:11:48,554,root,INFO,Request from,scheme=https,path=/
2019-01-15 00:11:48,554,root,INFO,| len(headers)=10,len(body)=14778
2019-01-15 00:11:48,555,root,INFO,|,,len(email_rfc822)=9223
2019-01-15 00:11:48,599,root,INFO,|,DKIM passed
2019-01-15 00:11:48,600,root,INFO,| content-type=multipart/signed; protocol="application/pkcs7-signature"; micalg=sha-256; boundary="------------ms010908020707040304020406",content-description=None
2019-01-15 00:11:48,600,root,INFO,| content-type=text/plain; charset=utf-8; format=flowed,content-description=None
2019-01-15 00:11:48,600,root,INFO,| content-type=application/pkcs7-signature; name="smime.p7s",content-description=S/MIME Cryptographic Signature
2019-01-15 00:11:48,600,root,INFO,| filename=smime.p7s,bytes=3998
2019-01-15 00:11:48,601,root,INFO,| Certificate: subject email_address=[''],not_valid_before=2018-10-03 00:00:00,not_valid_after=2019-10-03 23:59:59,hash_algorithm=sha256,key_size=2048 bytes, issuer={'countryName': 'GB', 'stateOrProvinceName': 'Greater Manchester', 'localityName': 'Salford', 'organizationName': 'COMODO CA Limited', 'commonName': 'COMODO RSA Client Authentication and Secure Email CA'}
2019-01-15 00:11:48,602,root,INFO,| Certificate: subject email_address=[],not_valid_before=2013-01-10 00:00:00,not_valid_after=2028-01-09 23:59:59,hash_algorithm=sha384,key_size=2048 bytes, issuer={'countryName': 'GB', 'stateOrProvinceName': 'Greater Manchester', 'localityName': 'Salford', 'organizationName': 'COMODO CA Limited', 'commonName': 'COMODO RSA Certification Authority'}
2019-01-15 00:11:48,616,root,INFO,| written file ./,bytes=1870,ok=True

For a quick sanity check, look for the last line – if it says “written file”, then you’re good. The rest of this is showing the DKIM check and certificate validation process.

3. SparkPost inbound relay webhooks setup

Firstly, we select a domain to use as our inbound message address – ?here, it will be Set your domain up following this guide. Here are the steps I used in detail:

3.1 Add MX Records

You’ll need access to your specific Internet Service Provider account. When done, you can check them with dig – here’s the command for my domain.

dig +short MX

You should see:


3.2 Create an Inbound Domain

Use the SparkPost Postman API collection, selecting the Inbound Domains / Create .. call. The body of the POST request contains your domain, for example:

???"domain": ""

3.3 Create a Relay Webhook

Create an inbound relay webhook using the relevant Postman call. The message body in my case contains:

	"name": "Certificate Collection Webhook",
	"target": "",
	"auth_token": "t0p s3cr3t t0k3n",
	"match": {
	          "protocol": "SMTP",
	          "domain": ""

As mentioned before, I recommend setting an auth_token to your own secret value, as set in the webapp.ini file on your host.

Your “target” value needs to match your host address and TCP port where you’ll be hosting the web app.

Your “domain” value needs to match your MX records set up in step 1.

That’s it! The plumbing is done. You should now be able to send certificates to your inbound address, they will be processed and show up on your web application host – in this case, a file named

Now you can send encrypted emails to Bob, using the tools described in parts 2 & 3 of this series.

You can examine the contents of a certificate using:

openssl x509 -inform PEM -in bob.lumreeker\ -text -noout

4. Internals: DKIM checking, certificate validation

The app checks received emails have valid DKIM and checks?that the certificates themselves are valid, as described here. There are implementation notes in there too, and ideas for further work.

Summing up…

We’ve seen how recipient public keys can be gathered easily using an email to an inbound relay webhooks address. Once done, those recipients can receive their messages in S/MIME encrypted form.

That’s it for now! Happy sending.


The post S/MIME Part 4: Collecting Recipient Public Keys the Easy Way – with SparkPost Inbound Relay Webhooks appeared first on SparkPost.

Life at SparkPost: Our Mentor Program Wed, 30 Jan 2019 14:00:55 +0000 mentor programLearn about our Mentor Program where employees can choose to be paired up to work towards professional or personal development goals.

The post Life at SparkPost: Our Mentor Program appeared first on SparkPost.


You may be interested to learn that January is National Mentoring Month. ?For the third year in a row, SparkPost is in the midst of running our annual Mentor Program. ?Employees may choose to participate as a mentor or mentee and are paired up to work towards professional or personal development goals. ?Everyone from tenured employees, “repeat offenders” (those who participated in prior years now acting in a different role), to new hires and VPs are on the list of participants.

If you’ve never had one, then you may not know the benefits of working with a mentor are pretty much endless. During our kickoff meeting last October, I shared just a few of the perks that working with a mentor deliver:

  • Helps provide professional development
  • Demonstrates recognition of his or her knowledge, skills and abilities
  • Helps advance his or her career more quickly
  • Increases confidence
  • Helps remote employees feel more in touch socially and professionally
  • Provides the fulfillment and satisfaction of helping others
  • Gives “payback” for the support received from others in the past
  • Increases employee morale
  • Supports an innovative work environment

Since taking over managing the program two years ago, I realized that it “takes a village” not only to raise children but to help one another in the working world as well. As we build relationships with one another in the workplace, you may find yourself connecting with people whose values and opinions matter to you. You may bounce ideas off of them and talk about future plans of transitioning to other roles within, or perhaps out of, your company. This more informal type of mentoring can be impactful for sure. But think of what you could do with that person if you actually set goals and made a promise to work towards bettering yourself.

Without our spectacular employees who are willing to give time outside of their busy schedules to be a mentor and support a fellow SparkPoster, the program wouldn’t exist. In that same vein, I applaud our mentees; those folks who can look inside themselves and recognize a desire to improve and are willing to ask for help. There is a wonderful sense of collaboration that comes out of interacting with coworkers on a vulnerable and sometimes intimate level. ?It really is a true testament to the types of folks who decide to come join our company.

If you are interested in working towards something bigger, something more, then I say go out and find a mentor. ?For a quick read and some insight into how to get started on your journey, I recommend picking up a copy of One Minute Mentoring by Kenneth Blanchard and Claire Diaz Ortiz. ?And if you’re in the market for a new opportunity and want to come work for a great company with awesome people, consider browsing our Open Positions.

Happy Mentoring!


The post Life at SparkPost: Our Mentor Program appeared first on SparkPost.

Knowing Your Social Media Privacy Settings Mon, 28 Jan 2019 14:00:58 +0000 privacy settingsHave you reviewed the privacy settings on any of your social media accounts recently? Our guide will help you pick the privacy settings that best suit you.

The post Knowing Your Social Media Privacy Settings appeared first on SparkPost.


When was the last time you reviewed the privacy settings for any of your social media apps? Social media has become the platform of choice for many Internet users but many are often left unsure of the visibility of their uploaded and posted content. The only way to combat this is by taking the time to better understand the nuances of their settings. Let’s take a look at some of these and see if have we an understanding of the privacy settings for them.

According to a 2018?Business Insider?article, the popularity or preference of a certain social media application fluctuates based on age group. The platform of choice for teens (born between 1997 and 2006) is Snapchat with 16.4 million users, while Instagram is in second place with 12.8 million users. Millennials (born between 1981 – 1996) use Facebook the most (at 58.8 million users) with Instagram also sitting in second place (at 43.4 million users). Gen X (born between 1965 and 1980) use Facebook the most at 45 million users. As a Millennial, I also follow the trends of the article and find myself using Facebook and Instagram the most.

Age Group Application & Users
Teens (born between 1997 – 2006) Snapchat – 16.4 million users

Instagram – 12.8 million user

Millennials (born between 1981 – 1996) Facebook – 58.8 million users

Instagram – 43.4 million users

Gen X (born between 1965 – 1980) Facebook – 45 million users

Privacy on Facebook

As you upload content, these well-known platforms allow you to decide on the visibility of your posts. But how do they highlight these controls? Let’s take Facebook for example. Do you understand what each icon next to the date means when making a post on your Timeline? Is it a globe, or a silhouette of 2 or 3 people? A globe will indicate that your post is public and anyone can view that post on your page. The silhouettes allow only your friends (2 silhouettes) or friends of friends (3 silhouettes) to view your post. These options can be controlled under your settings in the application. Here is a link to their support page if you want some step by step guidance.

Privacy on Instagram

Instagram also gives you options in your privacy settings, but they aren’t as flexible as Facebook. On Instagram, your profile is either 100% public or private without the ability to choose whether an individual photo can be shared?with?everyone or just your friends. You can get a better understanding of your settings by visiting their support page as well.

With all of the different settings, it can be overwhelming when trying to decide what content should be made public or private. At the end of the day, is a “private” post really private? Whether you’re uploading a video of yourself singing or tweeting about which Bachelor team you’re on, just take the time to know and understand your settings. It never hurts to have some peace of mind about it. Happy Data Privacy Day!


The post Knowing Your Social Media Privacy Settings appeared first on SparkPost.

New Events API: More Powerful, Flexible Events Searching Fri, 25 Jan 2019 14:00:09 +0000 Our new Events Search API's searching capabilities allow you to access the raw event data associated with the messages you send via SparkPost.

The post New Events API: More Powerful, Flexible Events Searching appeared first on SparkPost.


SparkPost’s New Events Search Is Here

We’ve just released a new and improved Events Search feature for all SparkPost customers. When you log into SparkPost, you’ll see it highlighted in the navigation menu, under “Reports.”

Events Search’s robust searching capabilities provide ready access to the raw event data associated with the messages you send via SparkPost. In addition to the Events Search capabilities in the SparkPost web app, the functionality also is available programmatically through a new Events API endpoint.

Why You’ll Want Events Search

The data provided by Events Search allows for the debugging of potential deliverability issues your mail streams may encounter, viewing the lifecycle of individual emails, and syncing your SparkPost data to external sources.

In fact, the Events API and Events Search feature have the most flexible filtering capabilities of any SparkPost feature to date, providing the ability to refine queries to events associated with individual emails, regardless of what starting piece of information is used.

Some common scenarios for Events Search include:

Digging into issues with a particular recipient domain. Imagine those times when you’re seeing decreased engagement or increased blocks to a particular domain. Events Search can filter message events to find all messages sent to a specific domain like to see details of what’s going on.

Drilling down on individual messages in an A/B test. If you’ve run a test using SparkPost’s A/B features, you might want to see what’s happened at the individual message level. With Events Search, it’s easy to filter or search events by the A/B test ID.

Searching by subject to examine details for a mailing. Let’s say you’re on the email team working with a number of clients or stakeholders and need to help them troubleshoot deliverability issues with a particular piece of content. Events Search can make that easy—even if the mailings cross several campaign IDs.

This kind of flexibility really helps when you’re working to solve email challenges every day. Penny-Merelle Gray, a product manager on the email deliverability team at Intercom, works with a lot of email. She saw the value of Events Search right away. “We’ve wanted this for ages. It’s so useful when you’re troubleshooting and trying to deep dive in an investigation.”

Events Search Replaces Message Events API

The improved Events Search extends our old Message Events feature to include new filtering and keyword search options. The Events Search API’s filtering capabilities are even more powerful and flexible than those provided by the old Message Events API.

By the way, if you’ve coded against the old Message Events API, we definitely encourage you to move to the new Events API. The increased power and flexibility is well worth it. Our engineering team has created a helpful guide for migrating and getting started with Events Search.

Below is a handy cross-section displaying what is filterable in each API, and as you can see, we’ve added many new ways to search for the exact events you need.


Filtering Capability Message Events Support Events Search Support
Event Types X X
Recipient Addresses X X
Friendly From Addresses X X
Bounce Classes X X
Bounce/Failure/Rejection Reasons* X X
Subaccounts X X
Transmission IDs X X
Message IDs X X
Campaign IDs* X X
Template IDs* X X
Recipient Domains* X
Subject* X
Sending Domains* X
Sending IPs X
IP Pools* X
AB Test IDs* X
AB Test Version X
Search by keyword X


* = supports keyword search in Events Search API and UI

Let’s Get Started: API or UI?

The Events API is a powerful way to search through SparkPost email events from your own code. The API endpoint is

. This endpoint supports adding search criteria through query parameters added to the URL. Please refer to the Events API documentation for additional information about the different filters you can add to Events API calls.

For day-to-day interactive use, the Events Search report is a new SparkPost application feature built on top of the Events API that provides a convenient way to perform the same types of queries you would with the Events API, but without having to write a line of code.

The new report lives under the “Reports” section of the SparkPost application. For those familiar with the SparkPost application, this report is very similar to the interface provided by the old Message Events report (and in fact, the Events Search report has replaced the Message Events report). The new report provides all the same searchability as the Events API, under the “More Filters” section. There, you can add multiple filters, and also provide word search filters where applicable.

Want to integrate your systems with the Events API?

As I mentioned earlier, our engineering team created a quick start and migration guide called?Getting Started with the Events Search API. It’s a great resource for developers integrating against the new Events API.


The post New Events API: More Powerful, Flexible Events Searching appeared first on SparkPost.

Financial Services: How to Implement DMARC Fri, 18 Jan 2019 14:00:16 +0000 DMARC financial servicesFollow our guide on DMARC to ensure your financial services company meets this vital security standard for email authentication.

The post Financial Services: How to Implement DMARC appeared first on SparkPost.

  • This blog post was originally published on 1/12/2014 and was updated on 1/18/2019

For companies that house and handle massive amounts of customer data, security is key, particularly when sending sensitive information via email. With the growing amount of cyberattacks in recent years, financial services companies must remain vigilant and take every measure possible to secure communications with their customers. Enter: Domain-based Message Authentication, Reporting & Conformance (DMARC), an email security protocol was developed about six years ago by major email providers, e-commerce companies, and social media networks to block fake emails or have them marked as spam. The top five US banks have all adopted DMARC, has your business? Follow the guide below to learn how to ensure your financial services company meets this vital standard for email authentication:

DNS entries that DMARC uses:

1 – The DMARC DNS text entry

The following is an example DMARC text entry for DNS :

v=DMARC1; p=none;;; adkim=r; aspf=r; rf=afrf; sp=none

The above example was generated with the following utility:

In order to get this in the real world use:

dig +short _dmarc.<domain> TXT
[root@mymachine ~]# dig +short txt
“v=DMARC1\; p=none\;\;”

2 – The SPF DNS text entry

The following is an example of an SPF DNS text entry: IN SPF “v=spf1 ip4: ip4: a -all”

You can find this for most domains by issuing a

dig +short <domain> TXT
. Here is an example:

[root@mymachine ~]# dig +short txt
“v=spf1 ~all”
[root@mymachine default]# dig +short txt
“v=spf1 ip4: ip4: ip4: ip4: ip4:
 ip4: ip4: ip4: ip4: ip4: 
ip4: ip4: ~all” <snip>

More information on creating an SPF DNS text entry available here:

For SPF validation you can use:

3 – The DKIM DNS text entry

The following is an example of a DKIM DNS text entry: 86400 IN TXT “v=DKIM1; k=rsa; h=sha1;

You generally can find this by doing a

dig +short _domainkey.<domain> TXT
. Here is an example:


[root@mymachine ~]# dig +short TXT

“v=DKIM1\; k=rsa\; 


You can find more details on validation of DKIM available here:

You can find a utility to create DKIM DNS entries here:

The DMARC Validation Process.

In order for DMARC to begin passing a message, either the DKIM must pass or the SPF must pass, if neither passes then the action requested, in p (Domain policy) or sp (Subdomain policy) in the above DMARC DNS text entry will be adhered to. The options on the policies are none, quarantine or reject.

Once either DKIM or SPF have passed, and it can be both, DMARC will then take action based on the requested behavior of adkim or aspf.

For strict adherence:

  1. In all cases, the RFC5321:Mailfrom and the RFC5322:From must match exactly.
  2. If the adkim is set to strict then the d= entry must match exactly the RFC5322:From domain.
  3. If spf is set to strict then spf domain must exactly match the RFC5322:From domain.

For relaxed adherence:

  1. In all cases both RFC5321:Mailfrom and RF5322:From must share an organizational domain.
  2. For dkim relaxed the d= domain must share an organizational domain with the RFC5322:From domain.
  3. For spf relaxed the domain must share an organizational domain with the RFC5322:From domain.

Here are some additional resources on DMARC that you may find useful:



The post Financial Services: How to Implement DMARC appeared first on SparkPost.

S/MIME Part 3: Plug and Play for On-Premises Secure Email Wed, 16 Jan 2019 14:00:30 +0000 on-premisesSenior Messaging Engineer, Steve Tuck, explains how S/MIME tools can be adapted to inject mail streams into on-premises platforms.

The post S/MIME Part 3: Plug and Play for On-Premises Secure Email appeared first on SparkPost.


In part 1, we had a quick tour of S/MIME, looking at signing and encryption of our message streams across a range of mail clients. Part 2 took us through a simple command-line tool to sign and encrypt emails, then send them through SparkPost.

In this part, we’ll look at how the tool can be adapted to inject mail streams into on-premises platforms such as Port25 PowerMTA and Momentum.

OK – let’s get started!

1. Getting Started

Installing the tool, getting your keys etc. is exactly the same as before. When you’re using an on-premises email system such as PowerMTA or Momentum, you’re already responsible for setting up sending domains, DKIM keys etc. What we need to do now, is to provide some way of injecting the fully-formed S/MIME messages into your servers.

2. SMTP injection towards Port25 PowerMTA

PowerMTA supports various means of message injection, including a file “pickup” directory, SMTP, and an API. SMTP is the method used here.

To illustrate the simplest possible setup, we’ll install the S/MIME tools on the same server as PowerMTA. We inject messages to the listener, which is open by default on TCP port 25, accepting local traffic only.

export SMTP_HOST=localhost

(If you forget that step, you’ll see:

“Environment var SMTP_HOST not set - stopping”
?when you try to run.)

We have the sender’s private key (
) and the recipient’s public key (
) already present. The first few lines of the message file are:

To: SteveT <>
From: Steve <>
Subject: This is a message created using HEML
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Language: en-GB
Content-Transfer-Encoding: 7bit

We send the message with:

./ tests/fancy-HTML-to-smt.eml --sign --encrypt --send_smtp

We see:

Opened SMTP connection (plain) to localhost, port 25, user="", password=""
Sending tests/fancy-HTML-to-smt.eml From: Steve <> To: SteveT <> 
OK - in 0.028 seconds

The message arrives quickly in the inbox and reports in Mac Mail as signed and encrypted.

Bonus feature: DKIM with PowerMTA

DKIM is quite easy to configure and coexists happily with S/MIME. The steps are:

  • Use the PowerMTA DKIM Wizard site to create sending domain private key (in my case,
    ) and public DNS TXT record contents.
  • Set up the DNS TXT record, with a chosen selector. For example, I used selector
    . Valid selector characters are defined here.
  • Put
    ?file on the server in directory
  • Add the following to my
    ?and restart the pmta service. (Here, these directives are written at global scope; on a production system, you might prefer to add them under a virtual-mta instead.)

domain-key pmta201811,*,/etc/pmta/

<domain *>
???dkim-sign yes

The DNS record checks out OK via MX Toolbox, and DKIM is now active.

3. SMTP Injection Towards Momentum

Momentum supports various means of message injection, including API and SMTP. SMTP is the method used here, towards a host already running Momentum. We’ll leave its configuration unchanged, as it already has a capability to accept incoming injections from other approved hosts.

This is a smaller version of a production setup, where “generation” nodes and MTA nodes are separate, yet closely coupled via a private VLAN and load-balancers, carrying internal SMTP injection traffic.

The S/MIME tools are installed as before, and we will inject messages to the address of the SMTP host (MTA):

export SMTP_HOST=xx.xx.xx.xx                               # set your own MTA / VIP address here

As before, we have the sender’s private key (
) and the recipient’s public key (
) already present on the “generation” node. The first few lines of the message file match these addresses.

We send the message from the “generation” node with exactly the same command as before, and the message shows up in the inbox.

./ tests/fancy-HTML-to-smt.eml --sign --encrypt --send_smtp

As you’d expect, S/MIME also happily coexists with Momentum’s DKIM signing.

4. SMTP injection towards SparkPost

In part 2 we used the SparkPost transmissions REST API to inject messages. Of course, it’s also possible to inject messages into SparkPost using SMTP. We set the environment variables like this:

export SMTP_USER=SMTP_Injection
export SMTP_PORT=587

If you’re using SparkPost EU-hosted service then set

(See here for more options – for example you can inject on port 2525 rather than 587.)

The output below shows STARTTLS is used, along with the username and password.

./ tests/fancy-HTML-to-smt.eml --sign --encrypt --send_smtp

You’ll see:

Opened SMTP connection (STARTTLS) to, port 587, user="SMTP_Injection", password="****************************************"
Sending tests/fancy-HTML-to-smt.eml From: Steve <> To: SteveT <> 
OK - in 0.057 seconds

The password is printed with substitute *** characters, so you’re not compromising the privacy of your key if someone’s looking over your shoulder.

Securing Your Credentials

Note that environment variables could be set up in a shell script file or similar, to save retyping. If you do, please look after your passwords/API keys by limiting access to that file to yourself only. For example, if your credentials setup file is named
, then run:

chmod 0700

SMTP-Related Warnings You May See

SparkPost’s SMTP injection is pretty strict, as you would expect from a public service. If you haven’t set the SMTP port number, you’ll see a warning:

{'': (550, b'5.7.1 relaying denied')}

If you haven’t set the SMTP username or haven’t set the password, you’ll see:

(530, b'5.7.1 Authorization required. Ref.', '')

These error messages are simply reported as-is from the Python SMTP library, hence the formatting.

Which one’s faster – SMTP or API?

Frankly, S/MIME is unlikely to be a high-volume use-case, but having the same tool with two output options was just asking for us to run a race!

The “Avocado” email test file used here is approx 19KB. Repeating the tests 10 times via a bash loop showed the average times to be similar for SMTP and API, around 60 milliseconds per message, which is pretty fast. In this case, we injected from a medium EC2 instance in the same hosting region as, which is a good way to keep network round-trip times low.

Repeating this with a larger test file (577KB), the API took roughly 200 milliseconds, while SMTP took 280 milliseconds per message – still impressive for a file size 30x larger. Of course, your mileage may vary depending on location, internet congestion etc, but performance is unlikely to be an issue.

If you really need maximum performance, a good starting point would be to launch a set number of concurrent injection processes/sessions as per our transmission best practices recommendations – e.g. from a supervisor task.

Summing up …

We’ve seen how the SparkPost API-based tool used in Part 2 is updated to support SMTP injection to support on-premises MTAs such as Port25 PowerMTA and Momentum in a variety of configurations, as well as with SparkPost.

That’s it for now! Happy sending.

– Steve

The post S/MIME Part 3: Plug and Play for On-Premises Secure Email appeared first on SparkPost.

Email 101 for Financial Services Mon, 14 Jan 2019 14:00:56 +0000 Email 101 for Financial ServicesOur new ebook, Email 101 for Financial Services, is designed to help financial services companies learn how to improve the ROI of their email operations.

The post Email 101 for Financial Services appeared first on SparkPost.


Email is so ubiquitous that most of us take for granted that every email we send will be received immediately. But, what’s really happening behind the scenes? Why do certain emails end up in spam? While these are certainly interesting questions to ponder when sending a one-off personal email to a friend, the answers to these questions can be a bit more daunting when applying them to your business. When email is mission-critical to your business, as it is for financial services companies, it’s important to build a strategy that addresses the challenges and nuances of email communication.

Our new ebook, Email 101 for Financial Services, is designed to help financial services companies learn how to improve the ROI of their email operations. In this ebook you’ll learn:

  • How to navigate newer sending regulations that affect data and privacy
  • Everything you need to know about email authentication
  • Key differences between sending customers’ transactional emails, like bank statements and account activity versus marketing emails
  • Guidelines for navigating customers’ preferences and permissions
  • Techniques for building and maintaining an excellent sending reputation
  • Metrics you should monitor to measure the success of communication efforts

Whether your focus is email marketing, onboarding and user engagement, retention or customer service, every undelivered message is a missed opportunity — and a hit to your bottom line. Don’t let mediocre deliverability rates erode the value of your email operations. The best practices discussed in this e-book will help you ensure the best possible inbox rates — and the best ROI for your financial services business.

Don’t let your questions about email go unanswered. Download Email 101 for Financial Services now to learn how to create and implement an email strategy that will work for your financial services business.


The post Email 101 for Financial Services appeared first on SparkPost.

An Email Performance Primer for Financial Services Companies Fri, 11 Jan 2019 14:00:06 +0000 financial servicesIf your financial services company depends on email to attract, up-sell, service, and retain customers, here are some things you should definitely know.

The post An Email Performance Primer for Financial Services Companies appeared first on SparkPost.


Despite all of the fancy customer portals and apps, email is still the unsung workhorse of financial services. It’s ubiquitous, alerting customers to everything from transactions and statements to password changes, updates to policies, and potential fraud. Email has been so broadly adopted and used by society at large that it’s often taken for granted. But if your financial services company depends on email to attract, cross-sell and up-sell, service, and retain customers, here are some things you should definitely know. Because email experiences vary — dramatically — based on what infrastructure and processes you’re using.

How to Win the Latency Game

Email latency is the relative time delay between when an email is sent and when it’s received. Often it takes just a few milliseconds before an email is sent and when it appears in the recipient’s inbox. But between point A and point B, many factors can contribute to increased latency.

First, processes within a company. Some organizations are used to creating batch lists of names and email messages and then uploading them via FTP to their service provider. This can take up to an hour. If it’s an important, time-sensitive alert, this process is unacceptable. Whether manual or automated, these upload processes involve several steps and are error-prone as well as slow. Check to make sure these processes are not being used for email in your company.

Second, technical latency can also seriously slow emails and degrade your customer’s experience. How quickly the customer receives your email is based on how fast your Internet Service Provider sends the email and the profile of that ISP created by other ISPs. Internet traffic is constantly changing. Sending too many emails too fast might trigger an alert by an ISP that delays the email speed or causes emails to bounce. New technologies can now solve these potential problems by monitoring traffic and alerts in real-time, so the fastest possible service can be achieved — instead of relying on chance and accident.

Ensuring Delivery

A welcome email to a new customer that bounces and shows up two days later in the customer’s inbox can cause the customer to question the institution’s service quality. Any email from a financial institution — but especially those confirming transactions or alerting customers to what might be questionable activity related to their accounts — must be received promptly.
Bounced email, due to overfull inboxes or other issues, is captured by older systems and placed into separate mailboxes that might be looked at once a day or even less frequently.

Newer solutions alert senders that a particular mailbox was full and didn’t accept your email within seconds. These newer email systems give you the option of sending the email to an alternate address or sending the original message through SMS. Make sure you’re using one of these newer solutions.

Understanding User Engagement

Once a customer email is received, what’s happening? Is it being opened and read? Opened and deleted? Not opened and deleted immediately? What hyperlinks within the message have been clicked? In what order? During what day and time and with what frequency?

Older email systems don’t provide this data. Newer ones do.

Knowing these and other characteristics of how customers interact with email can be extremely valuable. It can tell marketers what each customer is interested in. It can tell what times of day certain customers check their email so email systems can be programmed to send it to that customer at those times so it appears atop the inbox. This data also helps you build a customer profile that can be accessed throughout the financial institution — from corporate departments to branch offices — to better monetize and serve customers.

Email is ubiquitous in financial services, to both older institutions and new FinTechs. It isn’t going away any time soon. It’s time to look under the hood to make sure your customers are getting the quality email experience they deserve.


The post An Email Performance Primer for Financial Services Companies appeared first on SparkPost.

Looping Event Booth Videos – Part 1 of 2 Wed, 09 Jan 2019 14:00:21 +0000 Senior Messaging Engineer, Steve Tuck, outlines his best practices for being a booth gopher: managing and executing a successful event booth.

The post Looping Event Booth Videos – Part 1 of 2 appeared first on SparkPost.


Recently we needed to run a “kiosk” style video display at an event. No problem, everyone does that, I hear you say. That’s just table-stakes.

Those of you who do this for a living will know that events have nice onsite people, usually in black T-shirts, with screwdrivers, leatherman tools, a walkie-talkie radio, and pockets full of cables. They come along and set everything up for you. They either work for the event itself, or for the hotel/venue you’re at. Just hand them your USB stick with your video or presentation and they will “make it so”. Soon afterward, a biiiiig TV on a stand turns up, if it’s not there already.

The black T-shirt person loads your video up, switches it on, sets the inputs, and hey presto! There’s your beautiful show running, and your marketing manager looks happy. Their radio starts squawking, they grab a signature from your event person, and they’re off, handing you the remote control with a meaningful look. As a true event veteran, you lock it in the little cupboard so people can’t mess with it.

So before continuing, let us pause for a moment and offer thanks for those nice people in black T-shirts. They will still be coiling up cables and sorting out equipment long after you and everyone else is schmoozing at the event happy-hour. They are blessed with the gift of knowing how to do one thing well.

Be afraid…

What happens when your Marketing department just needs to showcase their latest sparkly video, at an event that has no onsite AV cover? Well…here there be dragons. Sales Engineers get to do all sorts of things, often acting as technical “gophers” for Marketing, Sales and other parts of the organization. That’s part of the thrill of the job. So it’s probably going to land in your lap, and you may as well reduce your stress by getting prepared and testing in advance. Here’s my little survival guide which might help you one day. But first, a warning.

“You said you’re an Engineer – how hard can it be”

Only do the tech gopher thing if you absolutely have to. Those black T-shirt people have the tools, supplies, and backup; you don’t. You are a plane-ride, or at least a train journey away from home, in an unfamiliar city, and all your stuff for on-the-fly problem-solving and MacGyvering is back home, or at the office. Amazon Prime won’t get anything to you fast enough to make a difference, and you probably don’t even have a venue address that would make any sense to a delivery person. Brick-and-mortar tech stores usually aren’t open 24 hours, and you know all they will stock are fluffy faux-fur-covered iPhone covers in various neon colors.

Make friends with the people setting up the next-door booths. They might need something that you have spare. You might need something from them, even if it’s just a pair of gaudy-looking promotional socks, a Cat5 network cable, or some duct tape. Always have these things, plus cable ties, some basic tools, a USB hub, a mini wifi router, a power extension reel, spare USB and HDMI leads, even if you think you don’t need them. They could be useful barter in the jungle environment you’re about to enter.

We demand… a shrubbery!

Well not exactly – but like the wise Knights of Ni, know in advance what you need from other people on your quest for the Holy Grail. The content that’s going to be shown – is it in 16:9 or 4:3 format?

If it’s a Powerpoint presentation, make sure you have all the right fonts loaded and externally linked content. The only way to be sure is to nuke it from orbit load it onto a separate clean machine and test it. Look carefully at the options for showing unattended (in “kiosk” mode). Check it loops back around as you are expecting. Check the transitions look OK. Check you have cables long enough to be able to lock the laptop away in that cupboard (next to the TV remote!).

If it’s Google Slides, your “show” options are more limited. Be sure to set the “available offline” flag on your presentation machine’s Google Drive. Wifi coverage may be patchy, and public hotspots at the venue will have thousands of people just like you, crammed into a small indoor space, all trying to download stuff. Even cellular coverage is going to be congested. Events spaces are often in hotel basements which have zilch mobile coverage anyway.

If it’s video, there a host of different formats, quality settings and so on. More on that later.

The golden rule is – check the content looks good on the screen it will be shown on, or at least something similar. TV screens may have overscan which means they won’t show all the pixels in your material. Unlike a computer monitor, bits will likely be missing from the top, bottom, and sides.

Beware the killer rabbit

Most folks can manage plugging in a laptop to show a presentation – but are you going to use your work laptop? You know, the one with all your email, Slack messages, documents, and files? NOT a good idea. Have you really figured out how to disable notifications/pop-ups from the screen, and tested it doesn’t ping them up on the big screen? That could be really awkward.

What happens during lunch – will your stand be manned? Is someone you know and trust watching your kit all the time? Nope.

If you have a security team or a CISO, and you leave your main work laptop unattended, even for a moment, you just found one of the quickest shortcuts to hunting for a new job.

So let’s be clear, we’re going to set this up so you can keep your job, even if all the kit goes walkabout or gets savaged by a pack of roaming hyenas.

How many MPEGs do you need, granddad?

This brings us nicely back to video. In some ways, video is the best booth medium – no missing fonts, no problems with externally linked content. You can show happy customers talking about how wonderful you are.

What we want, though, is a way you can show your Marketing team’s sparkling new video without needing a laptop.

If your venue provides a smart TV with USB ports, then you may be able to play video straight from a USB stick. Of course, you would always use a freshly formatted USB stick, with nothing else on it. Assume it will get savaged by hyenas, or left plugged in when everyone’s gone, or thrown into a packing crate and forgotten.

Always check this approach well in advance with the event AV folks, because there are a hundred ways that it might go wrong and only one way for it to work properly. For example:

  • Can the TV be set to loop the content forever, or is someone on your team going to have to press the “play” button on the remote every three minutes? That looks bad. It will always have a few seconds of “black screen” which looks terrible, and someone will press the wrong button.
  • What file formats will their TVs accept? If they say “.mp4” that’s not enough. Get them to confirm exactly what video encoding (usually H.264), audio encoding (usually AAC 2-channel stereo), bit-rates (say up to 20Mbps) and so on. VLC is useful here, but MediaInfo is better for reporting on video file format internals and only costs a couple of dollars. If possible, check your content plays back smoothly with no artifacts or glitches on the same TV (or close model).
  • Check what file format your production company will deliver your video. It’s not unusual for them to deliver huge broadcast-quality files in 40Mbps or more because higher quality is better, right? Not if your TV can’t play it, or your memory stick isn’t big enough, or the files exceed the FAT32 limit (which can be as low as 4GB or 2GB). Plus it will take ages to transfer down to your laptop, and ages to transfer to your USB stick, only to find that the TV crashes part-way through playing it. Here a free command-line tool, FFmpeg, is your get-out-of-jail-free card. If you don’t like command-line, you can try iMovie, VLC or whatever .. but I like the predictability, control, and batch capabilities of FFmpeg.
  • When will you get the video? Production is often going on up to the last minute if you have a new product announcement. If you can get an early copy of the material, you can test it.

More pixels than you can shake a stick at

If you are playing video, consider getting an all-in-one player with built-in storage well before the event, and testing it. These are no longer expensive.

I’ve had recent good experiences with an “Amazon Fire TV Stick with Alexa Remote” costing around $30 – $40. You can use this as your plug-and-play video solution. You can read how to do that in Part 2.

That’s it for now! Happy eventing.



The post Looping Event Booth Videos – Part 1 of 2 appeared first on SparkPost.

A 20 Step Plan to Being Viscerally Horrified of Public Speaking and Giving a Talk Anyway Mon, 07 Jan 2019 14:00:38 +0000 public speakingSite Reliability Engineer and seasoned public speaker, Dave Josephsen, outlines his workflow for writing, practicing, and presenting tech-talks.

The post A 20 Step Plan to Being Viscerally Horrified of Public Speaking and Giving a Talk Anyway appeared first on SparkPost.


It’s fine, we’ll get you through this, provided you have:

  • 3 weeks to prep
  • Software with a “speaker notes” feature
  • An external faux-projector screen to practice with

This article is not a joke. It’s not intended as exaggeration or satire. I’m personally horrified of public speaking and I’ve given?50 some-odd tech-talks and it’s?never?gotten better. I’m not going to insult your intelligence with un-actionable tips about relaxing and pretending this or that about the audience. I’m going to give you my?workflow.

These are instructions. These are things you can?DO. Hope is not a strategy. Don’t skip steps, and commit yourself to this. Follow through, and your talk will be great, and you will do great.

Step 1. Daydream about the talk until 3 weeks?prior

Seriously. Don’t open your slide software; just fantasize every once in a while about you giving a talk. You’ll find that related “things” will present themselves, like good opening jokes, clever one-liners, occurrences in the news, anecdotes, tweets, or cat gifs that relate to your point. Remain open to these and jot them down or save them for later.

Step 2. Write an?essay

3 weeks before the talk, write your talk out in essay form. If you despise essays, call it a monologue, or a report. Use punctuation and sentence structure. Treat it like a report on your topic that’s due in a week. Target 3000 words for a 45-minute talk, or 2000 words for a 30-minute talk.

Step 3. Paste your essay into speaker?notes

Once you’re happy with your essay, but before the end of week 1, chop your essay into speaker-notes sized pieces and paste them into speaker notes. Leave the slides themselves blank for now (use your preferred slide background color or whatever, but no content). The rule is, with your laptop in display mode connected to the external display, and with speaker-notes enabled on the speaker-screen, you MAY NOT SCROLL THE SPEAKER NOTES WINDOW. Use only the amount of text that will naturally fit in the space of the speaker notes box with no scrolling. You’ll find you can fit a medium-sized paragraph in there.

Step 4. Backfill?Graphics

Use the speaker-notes as a guide to your slide transitions. Try to populate every slide you’ve created with a graphic or a small combination of words that illustrate the point you’re currently making in the speaker notes. It’s ok to use the same graphic for 3 slides (this will appear to the audience that you aren’t changing slides when in fact you are), but NO MORE THAN 3 slides. If you have to rework bits of your essay to make the graphics fit better that’s a good thing. Do that. Keep tweaking until the end of Week 2.

Step 5.?Practice

1 week before the talk, begin performing run-throughs to yourself. You need not be standing or projecting loudly. You can sit at your desk with your laptop and display, reading the speaker notes to yourself at a mumble (it must be out loud though). Move your lips. Practice inflection.

Jokes, bits, and gags may occur to you, rework your notes to include them (even if it breaks the 3 slides per graphic rule). Certain sections may seem difficult or awkward, delete them, they’re probably overly-detailed, and not necessary to your point.

Step 6. Repeat Step?5

Step 7. Repeat Step?5

Step 8. Repeat Step?5

Step 9. Repeat Step?5

Step 10. Repeat Step?5

Notice the timer in your slide software, and begin timing yourself. Your talk might be over time or exactly matching your time limit. In either of these cases, delete 8–10 slides. Pick the most boring ones. Be brutal and honest. If you’re coming in with 7–10 minutes to spare, you’re in the zone. (Yes. Your talk will take 10 minutes longer when you eventually give it at the podium. Yes, this is a hard law of physics. No, I have no idea why)

Step 11. Repeat Step?10

Step 12. Repeat Step?10

Step 13. Repeat Step?10

Step 14. Repeat Step?10

Step 15. Dress Rehearsal

At this point, you’ve performed 10 run-throughs of your talk. For a 45 minute talk, you’ve been reciting it verbally for 7 full hours. Your transitions and inflection should feel natural and practiced. You need to be done tweaking it now. It’s not going to get any better, but it might get worse. Now it’s time to stand up and project.

Don’t worry about posture or eye contact with the crowd. Forget the crowd, you aren’t going to be paying attention to them at all. You’re going to be at the podium reciting your speaking notes, not walking around waving your arms like a TED speaker. Yes, you’re going to be eyes-down, reading aloud to your audience. I know it doesn’t sound conventionally correct, but believe me, it works?really?well.

If you have someone you love and trust, have them sit in with you as you give your talk. Don’t listen to any of their physical advice about how you’re standing or the fact that you’re reading aloud, but?do?listen?for?anything they didn’t comprehend, or jokes they didn’t think were funny. Make minor adjustments to account for these if they feel correct to you.

Step 16. Repeat step?15

Step 17. Repeat step?15

Step 18. Repeat step?15

Step 19.?Chill

1 day (if possible) before your talk, put it down, and don’t look at it before you’re ready to go up to the podium. Take this time to reflect on the fact that you’ve already given this talk 15 times to assure yourself that it’s going to be fine. Allow yourself to believe it, because?it’s true.

Step 20. Give the?talk.

Stick to your notes. Bring water to the podium. Drink some when you feel unable to speak. Everybody wants you to succeed, which is exactly what you’re doing. When it’s over, drop the mic and run. Get outside and let the sun hit your face. Plant your feet and allow yourself to take a compliment. Respond with lies like “Thanks I really had a blast”. You nailed it. I knew you could.


The post A 20 Step Plan to Being Viscerally Horrified of Public Speaking and Giving a Talk Anyway appeared first on SparkPost.

Email Challenges and Strategies for 2019 [Infographic] Fri, 04 Jan 2019 14:00:38 +0000 email challengesWe hope that our infographic on how to best address email challenges enables you to have a happy and successful 2019! Happy new year!

The post Email Challenges and Strategies for 2019 [Infographic] appeared first on SparkPost.


The start of the new year is always a time to make resolutions and set intentions. For many, this is a time to get back on their gym routine or pick up that book they’ve been meaning to finish for months. While self-improvement is certainly commendable, here at SparkPost we’ve set our sights on…you guessed it, email!

Over the course of 2018, we polled over 500 hopeful Litmus Live attendees to learn about the types of email challenges that keep them up at night. We crunched the numbers and compiled our findings into the handy infographic that you can share with your email team and other key stakeholders at your company. As promised, we included resolutions we think you should set when it comes to your email operations and strategy. Based on our findings, creating resolutions around data, resources, design, deliverability, and engagement are a smart way to begin your new year.

We hope that even if you never make it to the gym or finish that book that our recommendations on how to best address email challenges enable you to have a happy and successful 2019! Happy new year!

– Erica

The post Email Challenges and Strategies for 2019 [Infographic] appeared first on SparkPost.

The Warm-Up Process: Level Setting – Part 3 of 3 Tue, 01 Jan 2019 14:00:26 +0000 warm-up processSenior Messaging Engineer, Jeff Goldstein, dives into more detail on the second implementation scenario outlined in part 2 of his blog series.

The post The Warm-Up Process: Level Setting – Part 3 of 3 appeared first on SparkPost.


In the final part of this blog series, I’ll dive into more detail on the second more realistic implementation scenario I outlined in part 2.

Connecting to the ESP – SMTP and RESTful API

Before getting too deep into the workflow described in part 2, let’s talk about a couple of different approaches to sending emails. First off there are typically two different ways to connect to a modern ESP, through SMTP, and through RESTful APIs. ?When connecting to an ESP through SMTP, the SMTP request will contain the full body of the email with each email request (this is often referred to as a fully qualified body). The second approach is to connect to the ESP via RESTful API. When taking that approach, you often have the option of either sending the email body as part of the API call or referencing a stored email template on the ESP server. ?Most modern ESP’s also allow you to send substitution data in the RESTful API request that will be merged with the template before sending the email off to the recipient. In both cases, this is simply how you are interfacing with the ESP, the email is always sent out via SMTP to the targeted email address. Also, this is out of the scope of the project. How the ‘connector’ sends the email is irrelevant to the overall solution but worthy of mentioning as part of our discussion.

Stored Templates

The optional Template Library is added into the diagram for completeness, but really has little to no effect on our discussion so I’ll assume for this blog that the email request is using the newer technique of connecting to the ESP via RESTful APIs and sending customer substitution data that will be merged into the template before sending the email. But remember, this really has no effect on best practices as it pertains to the warm-up process. ?With that said, sending an email with personal and relevant data into the email may have a huge effect on user interaction and thus your email reputation and inbox placement.

Build/Send Process Capability

Above, it is assumed that the Build/Send Email process(es) have the ability to not only send single email requests via SMTP or RESTful API, but also to make multiple email requests in a single email API call; so the supporting infrastructure needs to support email requests of any bundle size. Also, while it may not be clear, the controller process is actually a library that will be included in the Build/Send Email process. Taking this approach allows for fast processing and multiple Build/Send processes that can run in a cluster.

Process Flows

There are a few process flows that will run in parallel in order to make this a smooth, fast service.

Build/Send Emails flow


  1. Retrieve email body/content from Content Management System or stored template name
  2. Optional but highly recommended for almost all emails; get data to personalize email
    • Either merge personalized data into template yourself
    • Or Hold data for transmission to ESP for their merging process
  3. Call out to controller process to find out what SDIPC to use
  4. Call connector with all the information so it can send the email(s)


For the Build/Send Email process to start, something within the backend systems must trigger the need for an email (or many emails) to be sent. ?That can be anything from a cron job running at specific times, an event like an invoice being created, or any one of thousands of actions that may tell a program that an email(s) needs to be sent.

The Build/Send process(es) will then gather the content it needs. This may simply be a call to the Content Management system to get a fully built out email, or maybe the email body needs to be merged with personal information like it would be for a password reset link. Under that circumstance, the process will reach out into your data repositories to get the necessary personalization data and either change the template directly or save that data to send during the RESTful API call to the ESP for them to merge the data into the template.

Now that the Build/Send application has the content, it needs to find out which ESP and IP pool to use. The only input the Controller Process needs from the Build/Send process is the number of emails the Build/Send process wants to send and what kind (stream) of email is being sent. The Controller Process will then reply back to the Build/Send process with which ESP and IP Pool to use. Keep in mind that the Email Connector may need more than that information coming back. ?In my application, four pieces of information are passed from the Controller Process to the Build/Send Email Process:

  1. The name of the ESP (homegrown) system to use
  2. The name of the IP Pool to use.
  3. The number of emails you can send. ?What if a Build/Send Email process wanted to know where to send 500 emails but there are only 250 emails left in the warm-up process for that specific category? ?If this was the first couple of days in the warm-up process, sending 250 emails over the planned amount may adversely affect your reputation. So the Controller Process needs a way to say how many emails the requesting app can really send in order to stay within the warm-up plan.
  4. Random text. ?In order to future-proof your application against an Email Connector needing some specific information besides ESP and IP Pool, build in the ability to send undefined text from the controller to the Build/Send process that gets passed along to the Email Connector.

*Note* Notice that there is no mention of the Sending Domain being passed from one process to another. If you look closely, there may be a close correlation between Sending Domain and Stream, but then again there may not be. ?For example, if you have sending domains like, or, those subdomains may be closely tied to streams. ?But some companies have strict policies on sending domains that preclude a tight connection. For example, they may want all email to go out using the sending domain <company name>.com. ?With that approach, there is no direct correlation between a Stream and Sending Domain. For that reason, we are leaving sending domain name out of the process and use Stream instead. If you want an easy way to pass the sending domain to be used, you can add that information into the Random text field. ?Otherwise, the Build/Send or Controller has the task of obtaining the proper sending domain.

With the information from the Controller, the Build/Send process can call the connector with the information needed to send the email(s). On failure to connect to the ESP, the connector will update the ‘down’ file that is used as input into the controller process when determining which ESP to use.

We will discuss the Controller Process in a moment, but it’s important to note that the Controller process must check which ESPs are down so it doesn’t suggest using a pool that the connector can’t reach. ?In my system, there is a simple text file that denotes which ESP’s are down. This file is updated by the connectors after a failure to connect to the ESP is detected.

Controller Process Flow


  1. Get the list of downed ESPs (and corresponding IP Pools if supported)
  2. Pick a tracking file to check ESP/Pool allotments. In my application, I keep this current state information in 1 to N files which I call tracking files. Each file keeps track of what was sent while using that specific tracking file. There are multiple tracking files in order to protect against a file locking on LARGE fast email systems. More details below.
  3. Read the current state of what has been sent so far into a table; then lock the disk file from changes.
  4. Flag downed ESPs in the table so they won’t be used.
  5. Flag Streams that do not match requested stream in the table so they won’t be used.
  6. Search through the list for an available ESP/Pool combinations that hasn’t used its allotment. My approach was to look for the first pool with some allotment left, not for a pool that can service the whole request.
    • If the whole request can be serviced, update the allotted field by adding the requested amount to the amount already sent. Then let the Build/Send service know which ESP/Pool to use.
    • If only partial fulfillment can be made, update the allotment field to reflect that the full ESP/Pool allotment is used. Then tell the Build/Send process which ESP/Pool to use along with how many emails can be sent without going over the allotment. In reality, the allotment numbers are a guide, so if the Connector sent over that allotment there probably won’t be any damage to your reputation unless that overage was a significant amount over the allotment.
  7. If NO pool exists that can service this request, the request is sent off to another service that tracks long-term ESP/Pool combinations. ?In my project, I keep a file that has all long-term ESP/Pool combinations that are available for sending in a file named Balancer.csv. When no warm-up pools are available, the warmup controller moves to this long-term service. ?Each ESP/Pool is given a percentage of how much email should go through that ESP/Pool combination. The service will use that percentage as a guide to the Build/Send processes.
  8. Write the warmup pool usage results to disk, unlock the file.


Please keep in mind that while the Controller process and flow is being described separately from the Build/Send process, I decided to create the Controller process as a library to be ‘included’ into the Build/Send application/services. ?This allows each Build/Send process to obtain which ESP/Pool to use without worrying about any other Build/Send process.

As described above, the first step is to obtain a list of all downed ESPs. ?This will stop the connector from continually trying to send to a downed service.

This next step is a little convoluted. ?Since disk access is slower than memory and I must lock the file while going through the decision process so data won’t change underneath one Controller process by another Controller process (remember, Controller processes are libraries running within the Build/Send code), I decided to build out support for multiple files that track how many emails have been sent against any given pool. ?It’s an option that can be set via an input parameters file. When the Controller process starts, it looks up how many files are being used and randomly picks one of them. Each file can allot the total number of emails allotted that ESP/Pool divided by the number of files. For example, if we can send 10,000 emails through an ESP/Pool marked for password resets, and we are using 4 files for tracking allotment, each file can allot up to 2,500 emails. Once a tracking file is picked at random, the Controller process locks the file, parses it into memory, then continues through the evaluation process.

In my application, I decided to only look at one tracking file per request for an allotment. ?I randomly pick one of the files and if an allotment cannot be found then I move on to the long-term ESP/Pools. Taking this approach does have its drawbacks. One file might indicate that the allotment is used up while another tracking file still has some allotment shares available. If I randomly pick the wrong file, I may miss an opportunity to use up a warm-up pool allotment. This can be fixed by trying another tracking file, but I decided to simply pass that request to the long-term pools for fulfillment. In reality, each allotment will probably get used from following requests and any accidental leftover allotment during a given period due to this approach would probably be mouse nuts and not worth worrying about.

Once the tracking file is selected, it will be parsed into memory. Now we can merge the tracking information with the ‘downed’ ESP data. During this process, I go through the tracking file in memory and mark each row with the word ‘skip’ that match one or more of the following:

  1. The tracking ESP matches a downed ESP
  2. The pool stream does not match what stream of email is being sent
  3. The pool has been created in this system but has a start date greater than today’s date

Now that the tracking table is built, we simply need to read the table until we find a pool that still has some room. Remember, I took the approach of partial fulfillment being OK and letting the Build/Send process worry about re-sending a request for the unfulfilled amount. That simplifies the code for the controller process that needs to be as tight and fast as possible. I could have taken a couple of other approaches:

  1. Keep searching until I found a pool that could fulfill the whole request. ?I decided not to do that because continuing the search may not result in a hit and waste time getting back to the Build/Send process.
  2. I could grab allotment from multiple ESP/Pools to fulfill the request. This means that I would have to build an array of possible ESP/Pools. I decided to keep it simple so I’m only sending a simple set of fields back; not an array that needs to be parsed.

I’m not saying that I took the right approach, but I like it for its simplicity and speed.

If no pools are found, then the process is passed over to the long-term ESP/Pool process for fulfillment. The answer from that process is passed all the way back to the Build/Send process for fulfillment. We will dig deeper into the long-term process later.

Once the ESP pool is found and the information passed to the Build/Send process, the tracking file is written back down to disk and unlocked.

Warmup or Warmed IP addresses (Pools)?
Most of this blog series talks about warming up new IP or IP Pools, but the fact is the warm-up process is just a couple of weeks while your email sending over those IP addresses should be years. So this system also addresses a strategy for those long-term pools. Working with warmed up IP pools is a lot simpler than working through the warm-up process for new pools. There is no keeping track of allotments, just what percentage of your sending you want to use that ESP for that Pool or stream. Maybe for business continuity, you decided to use both SparkPost US and SparkPost EU for sending invoices and you decide to send 50% through each service. ?After the controller decides that there is no warm-up allotment for its request, it will check the warmed-up pools. ?I call this the Balancer process. The Balancer will use a random number generator to guide which warmed up ESP/Pool to use. ?Since there is no writing to files we don’t need to lock the input Balance file nor have multiple versions. As I said, life is much easier for the warm-up up IP addresses and the Balancer process.

But, the Balancer process does need to check against the ESP down file and get the right stream just like when checking against new IPs.

Note: After a lot of testing I found out that only very high volume senders with a lot of Build/Send processes will need multiple files. ?Each file lock only happens for a few milliseconds before the Build/Send process actually sends the email. The call to the MTA to send the email to take much longer than the typical Controller process takes to figure out which IP pool/ESP to use, so the overall process only sees slowdowns due to file locking when there are a lot of parallel Build/Send processes working at the same time. In my testing, I didn’t see any locking issues until I had 8 or 9 Build/Send processes all working at the same time. Given that each system is different, I highly recommend that you test against file locking issues and set the number of tracking files appropriately.

Check ESP Status Flow
This process is fairly easy so I’m not going to get too deep into this process. If you’re going to have a controller like we described throughout this blog, you need to know if your ESP’s are up and running so you don’t pick ESP/Pool combinations that are not able to service your request.

The approach this system takes is that the connector will write to a file called down when it fails to connect to an ESP. The Connector process will then know not to select that ESP for fulfillment. If you have multiple ESP’s it’s likely that one of those ESP’s will be up and used to fulfill your request. But something needs to remove the ESP’s names from the down file when the ESP is back up. That means another process needs to periodically read the list of ESP’s from the down file and check if those ESP’s are back up; and if they are, remove their name from the file. Easy Peasy.


We started out with a fairly easy task; warm up some IP addresses and found out that in reality, it isn’t as easy as it seems. It’s not like writing code that can extrapolate the inverse relationship between snails and the expanding universe, but there are some challenges that need to be thought through. My Hackathon project is a good swipe at a way to do just that. It’s a PHP project that includes most of the code necessary for implementing your own warmup and long-term IP strategies. While there is a sample application that calls the controller process and sends emails, that part of the code is up to you. You probably have that code already and just need a way to use the controller in order to help guide which ESP and IP Pools to use. As for tracking which ESP’s are up and down, again, I leave that to you. You probably already have most of the code for finding out which ESPs are down written somewhere in your current error code in your own connectors. All you have to do is write the ESP name into the file named down and another application then checks the status to update the down file when those ESPs are back up.?The full project is sitting in a Github repository at:

Feel free to download the project and make all the changes you need to fit your environment.


Jeff Goldstein

The post The Warm-Up Process: Level Setting – Part 3 of 3 appeared first on SparkPost.

S/MIME Part 2: Signed, Sealed, and Delivered through SparkPost Mon, 31 Dec 2018 14:00:49 +0000 S/MIMESenior Messaging Engineer, Steve Tuck, explains how to install some simple command-line tools for signing and encrypting email? in part 2 of his blog series.

The post S/MIME Part 2: Signed, Sealed, and Delivered through SparkPost appeared first on SparkPost.


In part 1, we had a quick tour of S/MIME, looking at signing and encryption of our message streams across a range of mail clients. S/MIME messages can be signed (giving proof of sender’s identity), encrypted (keeping the message body secret), or both.

In this installment, we’ll:

  • Install some simple command-line tools for signing and encrypting email
  • Get your sender key / certificate for signing
  • Send a signed message via SparkPost, and look at the received message
  • Optionally, get your recipient certificate for encryption
  • Send a signed and encrypted message via SparkPost, and look at the received message
  • Try a handy standalone tool “mimeshow” to look at email file internals.

OK – let’s get started!

1. Install the tools

The demonstration tools are in Github here, complete with installation instructions. You might notice the “build passing” logo – Travis and pytest automatically check the build status. Note these tools are not officially supported by SparkPost, but I’ve tried to make them robust and easy to use.

If you have some acquaintance with Python and

, installation should feel pretty familiar. The
?takes care of the external dependencies automatically for you. Once it’s done, you can check everything’s installed by running

./ -h

You should see the friendly help text. ?Next, we need to…

2. Get your sender key / certificate for signing

If you already have a key file for your sending identity, you can skip ahead. Otherwise here are two options to choose from:

a) Self-signed test key / certificate (not externally valid)?

If you’re just testing, you can make “self signed” certificates and keys for an email address using the command line tool openssl on Linux, ?following a procedure such as this one. At the end of that process, you’ll have a

? file. Rename this file to match your sending identity, including the @ sign, for example,


b) Externally valid keys / certificates?

If you want to get externally valid keys / certificates that enable you to sign, there’s a list of providers here. I found Comodo works well (free for non-commercial use), and it’s easier than the self-sign procedure above. Follow the sign-up process, receive your validation mail, and be sure to open the link in Firefox. Go to Firefox Preferences / Privacy and Security. Scroll to Certificates / View Certificates:

Select your certificate, and use the “Backup” option to save as a file in PKCS12 format (add the file extension .p12 to your filename) which carries the private key and the public certificate chain.

Provide a password to secure the .p12 file:

Generate separate public (.crt) and private (.pem) key files

Whether you used a) or b), you’ll now have a .p12 file for your sender identity. That’s a big step forward – grab a coffee now!

Now we need to generate separate public and private key files like this – substituting in your own email address for the example one. (Mac OSX and Linux):

openssl pkcs12 -in alice\ -clcerts -nokeys -out alice\
openssl pkcs12 -in alice\ -nocerts -nodes -out alice\

You’ll need to enter the password you provided earlier. Note those backslashes \ are used to escape the @ sign – not separating the names of a directory path (that’s a forward-slash / on Mac OSX and Linux).

If you’re using Windows, there are openssl implementations available such as the MINGW64 one built into the Git command-line tools, but I found it tended to just lock up. You’ll probably find it easier and quicker to do this on Linux and then copy your files over. Those same Git tools for Windows come with a nice ssh client you can use to login to a Linux box, such as an Amazon EC2 instance.

2.1 Signing a message

There’s already a dummy key/cert and email source file in the tests directory for, so you can get some output even before you have your own keys. Just type the following:

cd tests
../ example_email1.eml --sign

And you’ll get:

To: Bob <>
From: Alice <>
Subject: A message
MIME-Version: 1.0
Content-Type: application/x-pkcs7-mime; smime-type=signed-data; name="smime.p7m"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7m"


You can’t actually send emails from
?via SparkPost unless you own that domain, so the next step is to use your own key and send a signed message from your own domain.

3. Send a signed message via SparkPost

Now let’s use a real sending domain, set up as per the SparkPost New User Guide. We have the sender certificate and key files in the current directory:

The file

?is included in the project. It’s just a text file, so you can customize the From: address to suit your own sending domain and the To: address to suit your test recipient. The beginning of the file looks like this:

To: Bob <>
From: Steve <>
Subject: Here is our declaration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB

When in the Course of human events it becomes necessary …

Set your API key:

export SPARKPOST_API_KEY=<<Put your API key here>>

Send the email:

./ tests/declaration.eml --sign --send_api

You will see:

Opened connection to
Sending tests/declaration.eml From: Steve <> To: Bob ?<>
OK - in 1.15 seconds

A second or so later, the email arrives in Bob’s inbox. Thunderbird displays it with a red dot on the envelope, indicating a valid sender signature.

Success! Finish that coffee, you’ve earned it. If you are having trouble, check your From: address in the email file matches the name of your .crt and .pem files.

4. Encrypting messages

To encrypt a message, you need your recipient’s public key in certificate form. This is a text file which looks like this:

Bag Attributes
??friendlyName: s COMODO CA Limited ID #2
??localKeyID: 32 84 AB 9C 56 5C 80 C6 89 4D 40 46 DD D4 7C 71 E8 CD ED C1
issuer=/C=GB/ST=Greater Manchester/L=Salford/O=COMODO CA Limited/CN=COMODO RSA Client Authentication and Secure Email CA

looks like random characters in here


There’s a dummy recipient certificate for in the tests directory, so you can practice with it before you have a real certificate:

cd tests
../ example_email1.eml --sign --encrypt

You’ll see:

To: Bob <>
From: Alice <>
Subject: A message
MIME-Version: 1.0
Content-Type: application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename=smime.p7m


You’ll notice the length of output is quite a bit longer than with an encrypted message because it carries a lot of extra information as well as the scrambled message itself.

4.1 Sending an encrypted, signed message through SparkPost

Let’s send an encrypted message to a real email address. You can follow the same process as before (self-signed or a provider such as Comodo) to get a public key / certificate for your own recipient addresses. You only need the .crt file – the recipient does not ever need to give you their private key (.p12 and .pem files).

I have the file
?for my intended recipient – matching the From: address in my file.

Here’s the command to send:

./ tests/declaration.eml --sign --encrypt --send_api

I see:

Opened connection to
Sending tests/declaration.eml From: Steve <> To: Bob <> 
OK - in 1.168 seconds

The mail shows up in Thunderbird with the “red dot” signature icon and the “padlock” encrypted icon.

You can send complex HTML-based email with links and images just as easily, such as the one shown in Part 1. Some clients such as Thunderbird ask for permission to display external links and images within encrypted S/MIME messages, but signed-only messages display well in clients including Thunderbird and Gmail:

Note the drop-down shows “Verified email address”.

Further thoughts & things to be aware of

This tool takes a super-simple approach to pulling in the necessary keys – it just looks for named files in the current directory. More complex arrangements, such as holding all keys in a database could easily be added, but I wanted the code to be as simple as possible.

You can include other recipients with Cc: and Bcc: and they will be delivered; this could be useful for archival purposes. Signed messages are received and can be displayed by other recipients complete with the signature. The tool strips the Bcc: header from the delivered message (like a desktop mail client would do).

To ensure that messages pass through SparkPost unchanged (which could break signing), the tool sets API options for “transactional” mailing, with open and click tracking disabled.

If you use encryption, bear in mind that the tool picks up the single To: address for that. The other recipients can decode the message body only if they have the To: recipient private key. If you’re just using secondary recipients as a record of deliveries made, for example, that may be OK anyway.

Signed, sealed delivered…I’m yours

That’s our quick overview of how to sign, seal and deliver S/MIME messages through SparkPost. Quick reminder: the demo project is in Github here, I’ve tried to make it easy to install and use.

Bonus feature: displaying MIME parts with “mimeshow”

RFC822 MIME multipart file internals are quite complex to read for humans. The project includes a standalone tool to make this easier, called mimeshow.

This takes any email files you have (not just S/MIME ones) and shows the internal structure. Here’s an example:

./ testcases/img_and_attachment.eml

You’ll see:

?To Bob <>?
From Steve <>
?Subject Testing attachments etc
?MIME-Version 1.0?
Content-Type multipart/mixed; boundary="------------7D48652042860D0098C65210"?
Content-Language en-GB??
 ?Content-Type multipart/alternative; boundary="------------58C0BF87598336550D70EB95"

?? ???Content-Type text/plain; charset=utf-8; format=flowed?
 ???Content-Transfer-Encoding 7bit??

 ???Content-Transfer-Encoding quoted-printable
? ???Content-Type text/html; charset="utf-8"??

 ?Content-Type application/pdf; name="sparkpost-datasheet-tam-technical-account-management.pdf"
? ?Content-Transfer-Encoding base64?
 ?Content-Disposition attachment; filename="sparkpost-datasheet-tam-technical-account-management.pdf"

You can also use as a filter to give a human-readable summary of

? output:

./ tests/declaration.eml --sign --encrypt | ./

You’ll see:

To Bob <>
?From Steve <>?
Subject Here is our declaration
?Content-Language en-GB?
MIME-Version 1.0?
Content-Type application/pkcs7-mime; smime-type=enveloped-data; name=smime.p7m?
Content-Transfer-Encoding base64?
Content-Disposition attachment; filename=smime.p7m


To recap – we’ve installed some simple command-line tools for signing and encrypting email (the Github repo is here, complete with installation instructions).

We got our sender key / certificate for signing, and sent a signed message via SparkPost. We got a recipient certificate for encryption, then sent a signed and encrypted message via SparkPost.

Lastly, we tried the handy standalone tool “mimeshow” to look at email file internals.
That’s it for now! See you soon for Part 3.


The post S/MIME Part 2: Signed, Sealed, and Delivered through SparkPost appeared first on SparkPost.

The Warm-Up Process: Implementation Scenarios – Part 2 of 3 Fri, 28 Dec 2018 14:00:03 +0000 warm-up processIn part 2 of this blog series, you'll learn about the different situations that can arise when trying to implement the IP warm-up process.

The post The Warm-Up Process: Implementation Scenarios – Part 2 of 3 appeared first on SparkPost.


In part 1 of this blog series, I went over the challenge of the IP warm-up process. In this section, you’ll learn about the different situations that can arise when trying to implement the warm-up process.

Implementation Scenarios – The Easy

Let’s start with the easiest scenario. You have one application that sends one type of email and you are moving from one ESP to another. We will assume you have been using the old ESP for a while and those IP addresses are warmed up.

How is the application that is going to build and send the email know which ESP vendor to use? In the simplest of environments, you could have an input file which contains the number of emails that should be sent that day using this new?sending domain/IP combination (SDIPC). Since you may have multiple email categories, each line needs to represent a different email stream. Then someone would update that file on a daily basis with the new count. Depending on the ESP, the information the email sending application needs may be different. For SparkPost, you need to know both the sending domain and what is called the IP_Pool name (Some ESP’s allow you to have your own IP addresses and bundle them together in order to meet sending demand for a specific sending stream, like Newsletters, Daily Job Updates, Passwords, etc. These bundles will be referenced as IP Pools throughout the blog. An IP Pool can consist of 1:1 or 1:many IP addresses). The file might be a simple CSV file like:

<stream>,<sending domain name>,<IP address/pool>,<daily number of emails>


The application will read the file and keep track of how many emails it sent within each stream. Once the application has run out of its daily pool, it will start using the older warmed up SDIPCs already available.

Coding for that simple approach isn’t very difficult for even a new developer,?let alone an experienced one. But reality usually doesn’t take the simple path. What if you have more than one application that sends emails; maybe you have a full cluster of applications that send millions of emails an hour. Which one of those applications (services) uses that new SDIPC? What if that service goes down? What if one of the ESP’s are not responding? What if a Demogorgon is on a rampage through Hawkins, Indiana? How will you keep track of how many emails have been sent for each of those SDIPCs? What do you do if that SDIPC isn’t available?

Implementation Scenarios – Reality

Tackling this best practice isn’t as easy as it seems so I decided to start building a solution during a hackathon project in order to help customers and prospects through this process. It is important that this code supports large vendors that may have multiple high volume sending applications across a large number of SDIPCs. I also have to assume that the user is already using a previous ESP, so the system needs to support multiple ESPs at the same time. From a business continuity perspective, I think supporting multiple ESPs (or one ESP that can send from multiple unique locations) should be paramount to any email sending strategy. The rest of this blog post (and part 3 of this blog series) will describe the final product that blossomed out of that hackathon project.

In designing the SDIPC warm-up platform I used the following assumptions and philosophies:

  • Support multiple ESP’s (or sending endpoints)
  • Future proof if possible
  • Support both the warm-up process and long-term sending through multiple endpoints
  • Support for high volume (millions of emails/minute)
  • Need support for when and SDIPC is unavailable
  • Automate as much as possible
  • Easy installation
  • Support for SMTP and RESTful API (by staying away from the actual sending)
  • UI to simplify
  • Support the ability for an email application sending 1 to ‘n’ emails at a time

To support the above items, I ended up architecting a five-component system. Let’s go over the components:

  1. An adapter that can send email to a specific ESP
  2. One or many email generator(s)
  3. Something that keeps track of how many emails have been sent through a specific ESP, IP or pools of IPs (SDIPC)
  4. A controller process that updates how many emails can be sent through a specific SDIPC during a given time period
  5. Process to test if ESP is up

*Note* The controller process in my example was built as a library that will be ‘included’ into each Build/Send process. This allows the build/send processes to manage which SDIPC to use in parallel instead of waiting on a service.

In the final part of this blog series, I’ll go into more detail on this second more realistic implementation scenario.



The post The Warm-Up Process: Implementation Scenarios – Part 2 of 3 appeared first on SparkPost.

Wellness at SparkPost Wed, 26 Dec 2018 14:00:58 +0000 wellnessRead up on how our HR team made wellness a top-priority in 2018 by creating an immersive program that included CPR training, local produce, and flu shots!

The post Wellness at SparkPost appeared first on SparkPost.


During 2018, the HR team here at SparkPost made wellness in the workplace a priority! Even though we had a limited budget we were able to create a wellness program that we were proud of and got employees moving! We’re of the mindset that you can still be productive at work (maybe a little more so) while adding some fun and educational wellness initiatives to the mix.

Safety in the Office

One very important aspect of any wellness initiative is safety in the office. We added new first aid kits and AED machines to both our San Francisco, CA and Columbia, MD offices. Additionally, our Maryland employees and some of our remote employees had the opportunity to go through CPR & AED training offered by Howard County, MD?this past summer.

Krav Maga

Another activity that we hosted at our Columbia, MD office was a Krav Maga self-defense class. ?We felt this was a great educational and exercise opportunity for our employees. We had over 20 employees join in this rigorous program! Mike Erdely, Director of Infrastructure, was super excited for this class. ?He mentioned “After taking about a year off from Krav Maga, it was nice to have Jeremy [one of my favorite instructors] come to our office and remind me about what I’d been missing. It was great to see some of my SparkPost teammates learning about something that has been so important to me over the last 5 years. I would love to see more Krav Maga sessions in the future.”

Fresh and Local Produce

To improve our health, we offered Community-supported Agriculture (CSA) from Wheeler Farm this past summer. We figured this was an easy and convenient way for our employees to add fresh produce to their diets!? With delivery directly to the office, it was definitely a win for employees. Angie Parise, HR Specialist, raved about the program, saying “[My] family really enjoyed the CSA! It was great to have a farm fresh delivery every week. We loved their homemade Old Bay pickles!” Many other employees shared Angie’s sentiment, so in 2019 we plan to purchase an office plan so that employees can continue to have access to fresh and local produce.

Stretching Sessions

This summer we began offering afternoon stretching sessions twice a week in our Columbia, MD office. These quick 15 minute breaks in the afternoon were a hit with the SparkPost team!? We figured everyone needs a brain break, and what better way to do that than with some physical activity! Isaac Kim, Technical Product Manager (and Certified Trainer!) led most of our sessions over?the last several months. He focused on exercises and stretches that were best for those who sit for most of the day.

October Fitness Challenge

To get the whole company up and moving we ran a two-week fitness challenge in October. ?The goal was to help employees make wellness a priority by encouraging them to be more active throughout the day, drink more water, and eat healthier. Additionally, we also gave them access to flu shots in the office!? We ran the challenge across the company – so whether you were in the UK, San Francisco, Maryland or at home working remotely, you could join in the fun. We had 53 employees participate. Many of our Maryland employees took walks around our office block and opted for healthier snacks from our fully-stocked kitchen. Managers got creative and made their 1:1s more active by walking! Brent Sleeper, Senior Product Marketing Manager and one of the fitness challenge’s winners said, “I thought the social part of our wellness challenge was fun, and motivating as well. In part, I was able to see all the things I was already doing to be active and healthy, but it also helped me set some goals to be consistent about sticking to healthy habits and activity.” Additionally, he said, “It was neat to see the range of activities the SparkPost team participate in to be active outside of work. It definitely gave me some insight and connection to my colleagues that was different than the usual Slacks and emails.” Winners of the challenge won awesome health-related prizes including a Fitbit and a Hydrate Spark 2.0 Smart Water Bottle!

Employees were able to get their flu shots in the office again this year. ?We were happy about this year’s participation with over 50 employees getting their shots in our offices! We also encouraged clean workstations in the office. We nicknamed it ‘Wipe Down Wednesdays”. We’ll round out the year with massages in the Columbia, MD office and our San Francisco team will kick-off another year of wellness by attending a SoulCycle class in January 2019!

As you can see, we packed a lot in this year. We decided to try different things and this month we surveyed our employees to see what they liked and what we can we add and change in 2019! We are looking forward to a fun, active 2019!

Looking for new and exciting opportunities?! Come join our Team – and see what’s so great about #SparkPostLife!


The post Wellness at SparkPost appeared first on SparkPost.

How B2B SaaS Companies are Using Email to Engage with Customers Mon, 24 Dec 2018 14:00:18 +0000 B2B SaaS companiesIf deliverability, security and customer engagement keep you up at night, then check out our latest ebook on how B2B SaaS companies use email.

The post How B2B SaaS Companies are Using Email to Engage with Customers appeared first on SparkPost.


The Importance of Application or Product-Generated Emails

Application or product-generated emails are essential to SaaS apps and services. For consumers that use these products to schedule appointments, purchase items, or even reset their passwords, an email is expected instantaneously to legitimize these transactions.

When important receipts, confirmations, and notifications fail to reach customer inboxes in a timely manner, trust with that SaaS provider is lost. This can result in users taking their business to other vendors. That said, application and product-generated emails are vital to the customer lifecycle.

How are SaaS providers Using Application or Product-Generated Emails

For SaaS providers, application or product-generated emails help drive and nurture customer relationships. When these messages end up in the spam or promotions folder, recipients are less likely to open and interact with them—resulting in missed opportunities for SaaS vendors to engage and retain consumers.

With application and product-generated emails being core to SaaS business goals, we surveyed 124 executives in software and eCommerce companies in the United States to find out how they use these types of communications to reach their customers. The survey questions included: What platforms do you use? What difficulties do you face in achieving high inbox placement? How can you improve your email performance?

Key Survey Results

The key survey results show that one-third of respondents use in-house systems to send application and product-generated emails. Many of these SaaS vendors are constantly working to improve their systems. For example, 50% want to improve engagement, 16% want to implement new features to improve sales, and 19% want to implement a whole new system.

Maintaining and improving email performance is no easy feat, therefore these SaaS vendors are working harder than they have to to activate, engage and retain customers through with application and product-generated emails. Further, considering the volume of emails these companies send on a yearly basis, even an incremental discrepancy can result in a significant loss in revenue or other opportunities.

If email deliverability, security and customer engagement are keeping you up at night, then check out our ebook that includes our survey data, as well as information on how to provide the best user experience to your customers. We offer simple steps for improving application and product-generated emails to help you work smarter (not harder) to deliver the high demand brand experience your customers have come to expect.


The post How B2B SaaS Companies are Using Email to Engage with Customers appeared first on SparkPost.

The Legend of SaaSta Claus: Kris Kringle, Product Manager Fri, 21 Dec 2018 14:00:06 +0000 SaaSta ClausDiscover why Kris Kringle or "SaaSta Claus" is a great role model for SaaS product managers working anywhere south of the North Pole.

The post The Legend of SaaSta Claus: Kris Kringle, Product Manager appeared first on SparkPost.


How great products start with milk and cookies

It’s that time of year when the Internet is rife with lists of inspiring heroes, up-and-coming entrepreneurs, and, crucially, classic Christmas cookies. And certainly, tech titans are a perennial favorite of the form, but there’s someone conspicuously missing from most shortlists of technology leaders.

I’m talking about Saint Nick. He’s got a gift for entrepreneurship and logistics nobody else can touch.

Every year, his team answers countless customer requests from every corner of the globe by manufacturing and delivering millions, maybe billions of items. Exactly how many is hard to say, since his enterprise’s financials are a closely guarded secret.

What do we know about his operation? Santa Claus never does interviews, yet the media obsesses over tracking his every movement. He never has to answer to investors or regulators, has global reach and distribution, and enjoys almost universal acclaim and goodwill. Even though nobody has ever seen his P&L, it’s clear he’s banking several million (at least!) free servings of milk and cookies per year. ?This describes a unicorn-class enterprise if ever there was one.

Let’s face it: Larry and Sergey may have their own private company airport, Elon has rockets and a bunch of tunnel contraptions, but nobody else has a red-nosed flying reindeer on call as chief pilot.

So what’s the secret of his success? It’s actually obvious. Santa Claus is, first and foremost, the world’s greatest product visionary.

By following each and every best practice of great SaaS product management to the letter, he’s built a business empire. But if you’ve got difficulty believing in the customer engagement magic of “SaaSta” Claus (ahem), here’s the proof.

He’s focused on superior user experience

Does Santa harness his corporate sleigh to any single product? Or suite of products? Absolutely not. He knows that being too locked into the success of specific products or features is an unsteady foundation for building your business.

What is he actually providing? It’s holiday cheer, joyousness, and happiness. Or, as a?marketing psychologist might describe it, Santa supplies memorable and engaging user experiences that satisfy an authentic human need state. That experience is delivered every time one of his end users finds a hand-carved hobby horse, an Xbox Elite, or a pair of Prada pumps under the tree.

Each of these gifts can be safely compared to a SaaS feature: It may be innovative and engaging, but it’s also got to reinforce the customer’s feeling that they’re receiving real value in the form of solutions to real needs.

Santa avoids feature fixation

As Andrew Chen of Andreessen Horowitz observed a few years ago, app makers fall into the trap of the Feature Fallacy, where they invest all hopes (and budget) in trying to launch the Next Great Feature that will solve their drop-off in user engagement.

That loss of engagement, though, is usually due to the fact they’re so enamored of product, product, product! that they failed to understand their audience and didn’t build enduring usefulness into their app in the first place. So adding a new feature won’t solve the problem, as that’s coming from the same product-centric, rather than user-centric, way of thinking.

The result? Apps are doomed from the start to end up discarded and forgotten, inhabitants of a SaaS version of the Island of Misfit Toys.

Santa plans for the very long term

In my?last post, I talked about the advice of Ken Norton of GV, who points out how technologies and feature evolve with such speed and frequency that a Product Manager needs to step back and take a long-view look at the market. What forces will shape it? How can you stay in front of those changes by forecasting and responding to future trends, without getting immersed in feature-think? Where do you want your enterprise to be in 10, 20, or 30 years?

Others make the case that making annual plans can hamper growth in a variety of ways, and a three-year plan should be a Product Manager’s real planning window.

Santa, as explained above, long ago began his strategic product planning by identifying a basic need state – the desire for joy and reward. It’s practically wired into our human DNA, and won’t vanish as time goes by. The trappings around it may change, as will the products needed to gratify the user.

But his team’s fundamental mission? That’ll endure, though the product mix will be fine-tuned to stay relevant. That’s possible because Santa, like any great Product Manager, has built his entire enterprise on superb customer feedback and analytics architecture.

Santa really does his research

Great product design and development invariably starts out based on the first tenet of design thinking and growth hacking: Gaining empathy for the audience.

Santa, obviously, has a sophisticated behavioral research apparatus in place whose exact operations are extremely hush-hush. How else would he be able to generate the oft-rumored “naughty or nice” list(s)? ?Yet to grow true empathy for his target customers, he has even better tools on hand:

  • First, he’s aided by a global panel of end users who provide him with countless yearly reports about their behaviors and desires. By crunching the data provided by the deluge of “letters to Santa” he receives, he can track customer sentiment, discern the vital trends and demands of the marketplace, yet also target individual customers with an uncanny degree of personalization.
  • Second, there’s his field research staff, acting as user community advocates, who are able to gather firsthand feedback from prospective customers. Here, though, it’s important to recruit individuals with proper interpersonal skills, or things can get off on the wrong foot.

He nurtures customer evangelism

All that goodwill I mentioned earlier? By maintaining consistent engagement and responsiveness to customer needs over the years, Product Manager Kringle grows each user’s lifetime value.

Even better? Owing to their positive experiences, his user base conducts intergenerational brand evangelism on behalf of Claus, Inc., constantly bringing new customers into the fold.

For a SaaS Product Manager working anywhere south of the North Pole, then, these are all solid reasons why Santa Claus is a perfect example of great product management in action.

And if you still don’t believe? Go watch Miracle on 34th Street, you Grinch.

– Brent


The post The Legend of SaaSta Claus: Kris Kringle, Product Manager appeared first on SparkPost.

S/MIME: What is it, why should I care, and how does it relate to SparkPost? Wed, 19 Dec 2018 14:00:07 +0000 S/MIMEDiscover how S/MIME, is a long-established method of sending encrypted, signed email, based on public Internet standards, relates to SparkPost.

The post S/MIME: What is it, why should I care, and how does it relate to SparkPost? appeared first on SparkPost.


What is S/MIME?

S/MIME is a long-established method of sending encrypted, signed email, based on public Internet standards. We regularly come across requirements for S/MIME, particularly from regulated industries such as banking, health, and finance. S/MIME often is required when communicating between businesses and government agencies, for example.

Another secure mail standard, PGP (amusingly named as “Pretty Good Privacy”), is used more for secure person-to-person communications. It’s less popular now because the consumer versions of popular web-based email clients such as Gmail and Outlook/Hotmail aren’t able to display encrypted mail. That’s one reason much person-to-person communication that requires privacy has moved to platforms such as WhatsApp (and many others) that offer native, end-to-end encryption.

Both PGP and S/MIME require a mail client that can use keys and certificates. Many desktop and mobile clients, including Apple Mail, Microsoft Outlook, and Mozilla Thunderbird fit the bill, as do business versions of some web clients such as Microsoft Office 365. Setting up the keys takes work, but many organizations still consider it worthwhile, despite recent vulnerability disclosures requiring remedies to block loading of remote content.

S/MIME has been around since 1995 and gone through several revisions; the current version is covered by RFC 5751. It requires exchange of public keys, a non-trivial task that often requires the support of an IT team or similar resource. This is where commercial solutions from companies such as SparkPost partners Virtru and Echoworkx come in, making security easier for person-to-person business mailing (see our SparkPost/Echoworkx how-to for more information).

That said, let’s dig into plain old S/MIME a bit deeper and see what we can do with it.

Why should I care?

The short version:

  • Encryption gives you message privacy.
  • Signing gives you authentication (of the sender), non-repudiation of origin, and message integrity checks.
  • S/MIME works differently than DKIM and DMARC and can coexist with them.

If your messages contain nothing personal, private, or legally important, then you probably won’t need to think about S/MIME. Modern email delivery systems such as SparkPost already use “opportunistic TLS” to secure the message transport from sending server to recipient server.

The “opportunistic” part does mean however that if the sending server can’t negotiate a secure connection, we’ll send the mail in plain text. This isn’t suitable if you want to force the message to be secure all the way. You can take a peek at which mailbox providers claim TLS support and which actually do. Assuming the recipient’s server does support TLS, your message is secured like this:

TLS secures the conversations between mail servers (which it’s why it’s called Transport Layer Security). MIME (including S/MIME) is concerned with message content and its treatment, and can be thought of as being part of the “Presentation layer”.

S/MIME secures the message content all the way (“end to end”) from the message origin to the recipient mail client, encapsulating the message body.

S/MIME encrypts the message body with the recipient’s public key. The body cannot be decoded without the recipient’s private key—not by any “person in the middle” such as your ISP, SparkPost, or the recipient’s mail server.

The private key is never disclosed; it’s kept in sole possession of the recipient. The encrypted message travels over the Internet to the receiving mail server. When it lands in the recipient’s inbox, it is (usually automatically) decrypted with their private key and becomes readable.

A few S/MIME gotchas to be aware of:

S/MIME encryption has a side-effect of preventing server-based incoming message scanning for malware because the message payload is in encrypted form and therefore unidentifiable.

Note that the message headers (From:, To:, Subject: etc) are not encrypted, so the subject-line content needs to be created with that in mind.


Signing – authentication
S/MIME also provides the recipient the ability to check that the identity of the message sender is who they say they are.

The sender’s email has a certificate attached, which, rather like the certificate on a secure website, can be traced back to an issuing authority. There’s a full description of the signing process here.

We’ll take the approach of signing the mail first, and then encrypting it, so the process looks like this.

Another useful benefit of signing to the recipient is non-repudiation of origin. Consider a situation where an email message is used to approve a contract. The recipient gets the contract in a message from the sender. If the sender later tries to say, “Nope, I never sent that message to you”, then the received message shows that the sender’s certificate was in fact used.

Message integrity
The signing process creates a fingerprint of the plain source message (known as a message digest), encrypts the digest using the sender’s private key, and includes it in the delivered message. The recipient’s mail client can tell if the message body is tampered with.

Perhaps you might say, “I thought DKIM gives me message integrity checks!” Well yes, DKIM provides message body and message header integrity checks – anti-tampering guarantees. However, DKIM failure (or absence) will not usually cause the incoming message to be marked as completely invalid, …unless a DMARC policy of p=reject is in play (more on DMARC here). DKIM is one factor of many used by the ISP for reliable assignment of reputation to a domain and is, of course, an essential part of your messaging stack.

Your mail client will show you prominently if an S/MIME message fails signature checks:

Summary: end-to-end (S/MIME) vs server-to-server (DKIM, DMARC, TLS)
S/MIME is a presentation-layer capability that can work between two email end-users (with valid certificates/keys) without any action by the email admin. S/MIME provides encryption and signing and is personal to each user.

S/MIME is tied to the full sending address (local part and domain part), so, for example, and would need to have different certificates. In contrast, DKIM validates the email is coming from the signing domain. DKIM is a whole subject in itself; this article is a good place to start.

DKIM and DMARC setup is done by your email admin (working on the mail server and DNS records). Once set up, they are active for domains, rather than individual users.

How does this relate to SparkPost?

Mail systems for person-to-person messaging, such as Microsoft Exchange Server, have long supported S/MIME.

If you are using SparkPost to send to specific recipients with mail-clients that can read S/MIME, then it could make sense to S/MIME sign your messages. S/MIME signing adds further assurance that the message is actually coming from you (or your system), and has not been tampered with, which may be valuable in some use-cases. All you need for that is your own key and some free software that we’ll demonstrate in part 2 of this article.

Using S/MIME encryption is a separate choice to make. You’ll need the public key for each of your recipients. Obtaining this could be as easy as having them send you (or your app) a signed email. We’ll explore a practical tool for sending S/MIME signed and encrypted mail through SparkPost in a follow-up post.

Which clients support S/MIME?

Consumer Gmail
The ordinary Gmail web client displays incoming mail signatures (see below), but it’s not set up to hold your private key to read encrypted messages. Even if that were possible via third-party plugins, uploading your private key is not a great idea from a security standpoint.

I couldn’t get Yahoo! Mail to decode signatures in messages at all.

The consumer version of Microsoft Outlook/Hotmail accounts alert you to the presence of an S/MIME signature, but don’t give you full access to view or check the certificate.

Hosted business mail
For organizations with hosted mail, Microsoft Office 365 and G Suite Enterprise have S/MIME support.

Outlook mail clients
Client-based Microsoft Outlook (e.g. 2010 for Windows) works:

Clicking on the icons gives you more information:

On Outlook 2010 / Windows, the certificate store is accessed via File / Options / Trust Center / Trust Center Settings / Email Security / Import / Export.

Thunderbird – cross-platform and free
If you’re looking for a free client, Mozilla Thunderbird fits the bill. It’s available on PC, Mac, and Linux, and supports S/MIME across all of these. Here’s how a message looks on Mac. The “sealed envelope” icon indicates the message is signed, and the padlock indicates it was encrypted.

Clicking on the envelope/padlock displays info about the message:

Thunderbird has its own key store, accessed in similar ways on each platform:
Mac via Preferences / Advanced / Certificates / Manage Certificates
PC: menu (“hamburger” top right), Advanced / Certificates / Manage Certificates
Linux: menu (“hamburger” top right), Preferences / Advanced / Manage Certificates

Mac Mail
Mac Mail also supports S/MIME. It relies on your Mac keychain to hold your keys.

iOS Mail
Firstly, import your email account’s certificate like this, then you can view S/MIME signed and encrypted emails. They don’t really look any different on the viewing screen.

Some devices and apps support S/MIME; there’s a lot of variety out there. Samsung has a guide.


That’s our quick overview of the practical uses of S/MIME. If you want to get your own mail certificates, there’s a list of providers here. I found Comodo works well (free for non-commercial use – open this in Firefox, not Chrome).

In part 2, we’ll explore how to apply S/MIME signing and encryption to messages that you deliver via SparkPost.

Further reading
Microsoft has a good introductory article on S/MIME here.

For more info on the EFAIL vulnerability and how it’s been addressed, this is the definitive site. Other easy-to-follow explanations are here and here.

That’s it for now! See you in Part 2 for some actual S/MIME sending via SparkPost.

– Steve

The post S/MIME: What is it, why should I care, and how does it relate to SparkPost? appeared first on SparkPost.

Chris McFadden talks about SparkPost Signals on theCUBE at AWS re:Invent 2018 Mon, 17 Dec 2018 14:00:38 +0000 SparkPost Signals AWS re:Invent 2018SparkPost's VP of Engineering & Cloud Operations, Chris McFadden, talked email and SparkPost Signals on theCUBE at AWS re:Invent 2018.

The post Chris McFadden talks about SparkPost Signals on theCUBE at AWS re:Invent 2018 appeared first on SparkPost.


Chris McFadden, VP, Engineering & Cloud Operations, SparkPost, sits down with John Walls & Rebecca Knight of theCUBE at AWS re:Invent 2018 in Las Vegas, NV to talk email and SparkPost Signals

I really enjoy going to AWS re:Invent in Las Vegas each year. It is a good time to catch up on the latest AWS features, attend deep dive sessions, and help staff our SparkPost booth where I get to meet current and prospective customers.

This year’s AWS announcements included one simple but powerful thing: true autoscaling of Dynamodb on-demand. Our engineers are happy about that. I was also interested in all the new features and improvements around data lakes, analytics, and machine learning which will help us deliver data products to our own customers. During Andy Jassy’s keynote, I was also glad to see how well Guardians has succeeded in their cloud migration. They did it in part by leveraging a number of SaaS providers, which includes SparkPost.

As an added bonus, this year I got the opportunity to speak with John Walls and Rebecca Knight, co-hosts of theCUBE, SiliconANGLE Media’s mobile live streaming show. During the interview, I was happy to share details about our upcoming product SparkPost Signals.

SparkPost Signals

We all know how mission-critical email is to business. Email continues to be the most performant communication channel with consistently high ROI, the real workhorse of product and marketing teams. And unfortunately, an unexpected drop in email performance can have a corresponding negative impact on business. This can be caused by perhaps accidental poor sending practices that result in lower delivery, inboxing and engagement rates. That’s why we are releasing SparkPost Signals, a suite of dashboards and tools to provide data-driven, actionable, and predictive insights to simplify email expertise and to boost performance. With nearly two decades of email experience and a data footprint of over 1 trillion events in our data lake, growing at over a billion a day, we can deliver truly valuable analytics insights.

SparkPost Signals includes a Health Score and spam trap reporting capabilities to help you understand the quality of your mail sending practices. ?For example, if you or perhaps some other group in the company purchase email lists you will likely see an increase in spam trap hits and spam complaints and see a drop in your overall Health Score. By detecting issues in advance, you can swiftly react to critical events before they impact or interrupt your business. We go one step further and provide cohort reporting for engaged recipients. With email, it is often the case that less is more. ?By only sending to customers that are engaged and at the frequency they desire you can boost overall engagement and revenue significantly.

It was great to meet theCUBE crew and I certainly hope to get invited back next year. ?SparkPost Signals is coming early next year – for those of you interested in learning more about it and getting early access please let us know!

Chris McFadden
VP, Engineering

The post Chris McFadden talks about SparkPost Signals on theCUBE at AWS re:Invent 2018 appeared first on SparkPost.

AWS re:Invent 2018 Newbie Report Fri, 14 Dec 2018 14:00:14 +0000 AWS re:Invent 2018Principal Software Engineer, Dave Gray, dishes about his experience attending AWS re:Invent 2018 and offers advice to future attendees.

The post AWS re:Invent 2018 Newbie Report appeared first on SparkPost.


AWS re:Invent is the annual “all things AWS” conference, with everything from sessions to learn more about existing services, the announcement of new features or entirely new services, to the formation of a new league for racing remote control cars powered by machine learning. It’s held in the desert, by which I, of course, mean Las Vegas. This year is the first time I’ve personally attended, so this is my newbie trip report along with plenty of free advice that I may or may not have actually followed. It bears repeating that if you happen to get sucked in by craps tables or the various other vices that Vegas incessantly pushes on you, don’t go to this conference, because it’s inescapable. Public service announcement over.

It’s easy to underestimate everything that’s involved in planning a feasible schedule for yourself over the course of a week in Vegas. Several aspects of the planning process are more challenging than they appear at first, especially once the scale of the event became apparent to this newbie here. First of all, there are at least 5 different venues hosting sessions all up and down the strip for 50 thousand attendees. There are several different types of sessions, from the traditional “sit and listen to a lecture”, to a longer and more involved workshop-style training where you’re building something. Other types of sessions are mostly Q&A after a short intro, so people can talk through questions with experts in a particular area.

Pre-registration for sessions opens up about 6 weeks before conference time, and reserved spots for popular sessions fill up fast. It’s a good idea to read through the session catalog before pre-registration and mark the ones you’re interested in so you’re not starting from scratch while others are racing to reserve a spot in their favorite talks. There are some talks that aren’t available for pre-registration because they’re about new services or features that are announced during the conference in the keynotes, so keep an ear out. They’ll get added to the catalog as they’re announced, so if a new service pops up that piques your interest, fire up that conference app on your phone and go for it!

Logistics come into play already when considering what you’re interested in, for example, an hour is recommended to get from one hotel to another, so you can’t realistically schedule talks right after each other. And you have to eat too. There are “to go” boxed lunches available, or you can sit down in the dining area for better-tasting hot food. The first day, it was a happy accident that I ate lunch right as the dining hall opened because it got crowded quickly. I did my best to eat early, schedule permitting, for the rest of the week too. The desserts were surprisingly good, my favorite was the mochi. Oh, and find the closest Walgreens to where you’re staying, it’s a life-saver whether you need a toothbrush, a snack because you skipped lunch to go to a session, or you just don’t feel like paying quite as much for a beer.

With regard to reserved capacity, anecdotally at least, this year was handled better than last year. I heard stories of people at last year’s re:Invent who reserved seats and didn’t get into the talk because it had already filled up. 2018 was apparently much better, in that the number of reserved slots was lower than the total number of seats available, so all the reserved people got in, plus people from the “walk up” line. Lines start forming for both reserved and “walk up” an hour ahead of session start time, so with the number of venues and all the waiting in line, it’s entirely possible to spend more time transitioning between sessions than in the actual sessions if you’re not careful. And oh, the lines. Lines everywhere. Lines at registration, to pick up swag, for lunch, for shuttles, for sessions, to leave sessions, for games at re:Play, and for a dozen other things.

With all that said, I read a lot of advice, and still managed to end up with a schedule that had me in 4 different casinos on the first day, chasing interesting topics up and down the strip. Here’s how that went! We stayed in the Venetian (that’s 1). My first session was a mile South in the Aria (now we’re at 2) at 10 AM. I walked. It wasn’t that bad. Lunch is served in each venue starting at 11 AM. My next session was in the MGM Grand (up to 3) at 1:45 PM “just across the street”, but it’s farther than it looks. My last session of the day was in the Mirage, which would have been 4 (nope) but I was tired of walking by that point. We also had a booth to staff, and the first night was the welcome party in the expo with food, beer, and all sorts of free stuff covered in logos. I had less travel in my schedule the rest of the week, mostly staying in one location all day, but wow, that first day I was all over the place.

So with all that bouncing around, what did I learn? Well, I learned that the battery in my old laptop can’t go all day anymore, so half my notes ended up on my phone. All (well ok most) joking aside, I went to several very good talks. I’ll summarize a few here, with the tiebreaker being the order I saw them in.

First place was kind of not fair. All sorts of new features, services, and, um, cars were announced at the various keynotes. Some of the re:Invent advice I read recommended attending at least one keynote in person, so I went to Werner Vogels’ on Thursday. Watching the DJ do his thing up on stage in a dark room full of thousands of people at 8 o’clock in the morning was pretty entertaining too.

Next was the first talk I went to, CON310 “Breaking Containers: Chaos Engineering for Modern Applications on AWS”. I picked this talk because here at SparkPost, more of our services are running in containers every quarter, so it seemed relevant to start thinking about how to inject certain types of failure. For those of you familiar with the phrase “error budgeting“, this kind of poking and prodding is a great way to spend that budget and end up with useful information about your system in exchange. I enjoyed this talk because there were references to other sources (books, videos, etc) to get more in-depth information, and also because it raised questions to ask about your infrastructure and talked about ways of thinking more than just the details of one way to solve a specific problem. Well worth a watch.

Another good one was SRV373 “Building Massively Parallel Event-Driven Architectures”. This talk was a good overview of the various “serverless” services offered by AWS. A MapBox engineer also described a neat tool to help with “Lambda-backed custom CloudFormation resources”. I picked this talk because more and more parts of our system are using serverless technology, in a variety of ways, and I enjoyed hearing about gotchas and use cases from people who build and use the underlying systems every day.

There were lots of other good ones, and I had a great time not just learning, but interacting with people in sessions, at lunch, and at our booth: customers, people with questions, and the rest of the crowd that wante