Tips, Expertise, Articles and Advice from the Pro's for Your Website or Blog to Succeed
You're reading How to Code a Mobile-First Responsive Email Template [Tutorial], originally posted on Designmodo. If you've enjoyed this post, be sure to follow on Twitter, Facebook!
![How to Code a Mobile-First Responsive Email Template [Tutorial]](https://designmodo.com/wp-content/uploads/2019/06/responsive-email-template-747x420.jpg)
In this tutorial, I’m going to show you how simple and easy it can be to code a fully responsive and fluid email template. This isn’t complicated or intimidating at all. All it takes is understanding the designs for the …
This post is originally published on Designmodo: Transactional Email Design: Examples and Best Practices
Transactional emails and promotional emails lay a sound foundation for every email marketing campaign. While the first one is responsible for luring people in, promoting products, and keeping the readers up-to-date, the second one is used for numerous notifications. Even …
For more information please contact Designmodo
Postfix is a free and open-source mail transfer agent (MTA) that routes and delivers email. This is required in order to be able to send emails from a local machine (without using any vendor’s client).
Postfix has to be configured. The suggested way to do that is via: sudo dpkg-reconfigure postfix. You can also directly edit your /etc/postfix/main.cf file and make changes to the configuration. For most purposes, dpkg-reconfigure should suffice.
Let's say you're rocking a JAMstack-style site (no server-side languages in use), but you want to do something rather dynamic like send an email. Not a problem! That's the whole point of JAMstack. It's not just static hosting. It's that plus doing anything else you wanna do through JavaScript and APIs.
Here's the setup: You need a service to help you send the email. Let's just pick Sparkpost out of a hat. There are a number of them, and I'll leave comparing their features and pricing to you, as we're doing something extremely basic and low-volume here. To send an email with Sparkpost, you hit their API with your API key, provide information about the email you want to send, and Sparkpost sends it.
So, you'll need to run a little server-side code to protect your API key during the API request. Where can you run that code? A Lambda is perfect for that (aka a serverless function or cloud function). There are lots of services to help you run these, but none are easier than Netlify, where you might be hosting your site anyway.
I signed up for Sparkpost and made sure my account was all set up and verified. The dashboard there will give you an API key:
Part of protecting our API key is making sure it's only used in server-side code, but also that we keep it out of our Git repository. Netlify has environment variables that expose it to functions as needed, so we'll plop it there:
Netlify Dev is a magical little tool that does stuff like run our static site generator for us. For the site I'm working on, I use Eleventy and Netlify Dev auto-detects and auto-runs it, which is super neat. But more importantly, for us, it gives us a local URL that runs our functions for testing.
Once it's all installed, running it should look like this:
In the terminal screenshot above, it shows the website itself being spun up at localhost:8080, but it also says:
◈ Lambda server is listening on 59629That'll be very useful in a moment when we're writing and testing our new function — which, by the way, we can scaffold out if we'd like. For example:
netlify functions:create --name hello-worldFrom there, it will ask some questions and then make a function. Pretty useful to get started quickly. We'll cover writing that function in a moment, but first, let's use this...
Sparkpost has an API, of course, for sending these emails. We could look at those docs and learn how to hit their URL endpoints with the correct data.
But things get even easier with their Node.js bindings. Let's get this set up by creating all the folders and files we'll need:
/project
... your entire website or whatever ...
/functions/
/send-email/
package.json
send-email.jsAll we need the package.json file for is to yank in the Sparkpost library, so npm install sparkpost --save-dev will do the trick there.
Then the send-email.js imports that lib and uses it:
const SparkPost = require('sparkpost');
const client = new SparkPost(process.env.SPARKPOST);
exports.handler = function(event, context, callback) {
client.transmissions
.send({
content: {
from: 'chris@css-tricks.com',
subject: 'Hello, World!',
html:
"<html><body><p>My cool email.</p></body></html>"
},
recipients: [{ address: 'chriscoyier@gmail.com' }]
});
}You'll want to look at their docs for error handling and whatnot. Again, we've just chosen Sparkpost out of a hat here. Any email sending service will have an API and helper code for popular languages.
Notice line 2! That's where we need the API key, and we don't need to hard-code it because Netlify Dev is so darn fancy that it will connect to Netlify and let us use the environment variable from there.
When Netlify Dev is running, our Lamba functions have that special port they are running. We'll be able to have a URL like this to run the function:
http://localhost:34567/.netlify/functions/send-emailThis function is set up to run when it's hit, so we could simply visit that in a browser to run it.
Maybe you'll POST to this URL. Maybe you'll send the body of the email. Maybe you'll send the recipient's email address. It would be nice to have a testing environment for all of this.
Well, we can console.log() stuff and see it in the terminal, so that's always handy. Plus we can write our functions to return whatever, and we could look at those responses in some kind of API testing tool, like Postman or Insomnia.
It works!
I'll leave it to you to get fancy with it ;)
The post Netlify Functions for Sending Emails appeared first on CSS-Tricks.
This post is originally published on Designmodo: Emojis in Email Newsletters: What You Need to Know
Emojis have a long history. It began in the 1980s when Scott Fahlman, leader of Common Lisp, introduced to the world the first emoticons. We know them as happy and sad face. There was nothing fancy: just a combination of colon …
For more information please contact Designmodo
I like Gutenberg, the new WordPress editor. I'm not oblivious to all the conversation around accessibility, UX, and readiness, but I know how hard it is to ship software and I'm glad WordPress got it out the door. Now it can evolve for the better.
I see a lot of benefit to block-based editors. Some of my favorite editors that I use every day, Notion and Dropbox Paper, are block-based in their own ways and I find it effective. In the CMS context, even moreso. Add the fact that these aren't just souped-up text blocks, but can be anything! Every block is it's own little configurable world, outputting anything it needs to.
I'm using Gutenberg on a number of sites, including my personal site and my rambling email site, where the content is pretty basic. On a decade+ old website like CSS-Tricks though, we need to baby step it. One of our first steps was moving our newsletter authoring into a Gutenberg setup. Here's how we're doing that.
Gutenberg Ramp is a plugin with the purpose of turning Gutenberg on for some areas and not for others. In our case, I wanted to turn on Gutenberg just for newsletters, which is a Custom Post Type on our site. With the plugin installed and activated, I can do this now in our functions.php:
if (function_exists('gutenberg_ramp_load_gutenberg')) {
gutenberg_ramp_load_gutenberg(['post_types' => [ 'newsletters' ]]);
}Which works great:
We already have 100+ newsletters in there, so I was hoping to only flip on Gutenberg over a certain date or ID, but I haven't quite gotten there yet. I did open an issue.
We ultimately send out the email from MailChimp. So when we first started hand-crafting our email newsletter, we made a template in MailChimp and did our authoring right in MailChimp:
Nothing terrible about that, I just much prefer when we keep the clean, authored content in our own database. Even the old way, we ultimately did get it into our database, but we did it in a rather janky way. After sending out the email, we'd take the HTML output from MailChimp and copy-paste dump it into our Newsletter Custom Post Type.
That's good in a way: we have the content! But the content is so junked up we can basically never do anything with it other than display it in an <iframe> as the content is 100% bundled up in HTML email gibberish.
I'd argue that the writing experience here is similar (MailChimp is kind of a block editor too), but nicer than doing it directly in MailChimp. It's so fast to make headers, lists, blockquotes, separators, drag and drop images... blocks that are the staple of our newsletter.
I like having a permanent URL for each edition of the newsletter. I like that the delivery mechanism is email primarily, but ultimately these are written words that I'd like to be a part of the site. That means if people don't like email, they can still read it. There is SEO value. I can link to them as needed. It just feels right for a site like ours that is a publication.
Now that we're authoring right on the site, I can output <?php the_content() ?> in a WordPress loop just like any other post or page and get clean output.
But... we have that "old" vs. "new" problem in that old newsletters are HTML dumps, and new newsletters are Gutenberg. Fortunately this wasn't too big of a problem, as I know exactly when the switch happened, so I can display them in different ways according to the ID. In my `single-newsletters.php`:
<?php if (get_the_ID() > 283082) { ?>
<main class="single-newsletter on-light">
<article class="article-content">
<h1>CSS-Tricks Newsletter #<?php the_title(); ?></h1>
<?php the_content() ?>
</article>
</main>
<?php } else { // Classic Mailchimp HTML dump ?>
<div class="newsletter-iframe-wrap">
<iframe class="newsletter-iframe" srcdoc="<?php echo htmlspecialchars(get_the_content()); ?>"></iframe>
</div>
<?php } ?>At the moment, the primary way we display the newsletters is in a little faux phone UI on the newsletters page, and it handles both just fine:
Since we aren't creating the newsletters inside MailChimp anymore, did we have to find another way to send them out? Nope! MailChimp can send out a newsletter based on an RSS feed.
And WordPress is great at coughing up RSS feeds for Custom Post Yypes. You can do...
/feed/?post_type=your-custom-post-typeBut... for us, I wanted to make sure that any of those old HTML dump emails never ended up in this RSS feed, so that the new MailChimp RSS feed would never see them an accidentally send them. So I ended up making a special Page Template that outputs a custom RSS feed. I figured that would give us ultimate control over it if we ever need it for even more things.
<?php
/*
Template Name: RSS Newsletterss
*/
the_post();
$id = get_post_meta($post->ID, 'parent_page_feed_id', true);
$args = array(
'showposts' => 5,
'post_type' => 'newsletters',
'post_status' => 'publish',
'date_query' => array(
array(
'after' => 'February 19th, 2019'
)
)
);
$posts = query_posts($args);
header('Content-Type: '.feed_content_type('rss-http').'; charset='.get_option('blog_charset'), true);
echo '<?xml version="1.0" encoding="'.get_option('blog_charset').'"?'.'>';
?>
<rss version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
<?php do_action('rss2_ns'); ?>>
<channel>
<title>CSS-Tricks Newsletters RSS Feed</title>
<atom:link href="<?php self_link(); ?>" rel="self" type="application/rss+xml" />
<link><?php bloginfo_rss('url') ?></link>
<description><?php bloginfo_rss("description") ?></description>
<lastBuildDate><?php echo mysql2date('D, d M Y H:i:s +0000', get_lastpostmodified('GMT'), false); ?></lastBuildDate>
<language><?php echo get_option('rss_language'); ?></language>
<sy:updatePeriod><?php echo apply_filters( 'rss_update_period', 'hourly' ); ?></sy:updatePeriod>
<sy:updateFrequency><?php echo apply_filters( 'rss_update_frequency', '1' ); ?></sy:updateFrequency>
<?php do_action('rss2_head'); ?>
<?php while( have_posts()) : the_post(); ?>
<item>
<title><?php the_title_rss(); ?></title>
<link><?php the_permalink_rss(); ?></link>
<comments><?php comments_link(); ?></comments>
<pubDate><?php echo mysql2date('D, d M Y H:i:s +0000', get_post_time('Y-m-d H:i:s', true), false); ?></pubDate>
<dc:creator><?php the_author(); ?></dc:creator>
<?php the_category_rss(); ?>
<guid isPermaLink="false"><?php the_guid(); ?></guid>
<description><![CDATA[<?php the_excerpt_rss(); ?>]]></description>
<content:encoded><![CDATA[<?php the_content(); ?>]]></content:encoded>
<wfw:commentRss><?php echo get_post_comments_feed_link(); ?></wfw:commentRss>
<slash:comments><?php echo get_comments_number(); ?></slash:comments>
<?php rss_enclosure(); ?>
<?php do_action('rss2_item'); ?>
</item>
<?php endwhile; ?>
</channel>
</rss>With a MailChimp RSS campaign, you still have control over the outside template like any other campaign:
But then content from the feed just kinda gets dumped in there. Fortunately, their preview tool does go grab content for you so you can actually see what it will look like:
And then you can style that by injecting a <style> block into the editor area yourself.
That gives us all the design control we need over the email, and it's nicely independent of how we might choose to style it on the site itself.
The post A Gutenburg-Powered Newsletter appeared first on CSS-Tricks.
You can make a garden variety anchor link (<a>) open up a new email. Let's take a little journey into this feature. It's pretty easy to use, but as with anything web, there are lots of things to consider.
<a href="mailto:someone@yoursite.com">Email Us</a>It works!
But we immediately run into a handful of UX issues. One of them is that clicking that link surprises some people in a way they don't like. Sort of the same way clicking on a link to a PDF opens a file instead of a web page. Le sigh. We'll get to that in a bit.
If a user has their default mail client (e.g. Outlook, Apple Mail, etc.) set up to be a native app, it doesn't really matter. They click a mailto: link, that application opens up, a new email is created, and it behaves the same whether you've attempted to open that link in a new tab or not.
But if a user has a browser-based email client set up, it does matter. For example, you can allow Gmail to be your default email handler on Chrome. In that case, the link behaves like any other link, in that if you don't open in a new tab, the page will redirect to Gmail.
I'm a little on the fence about it. I've weighed in on opening links in new tabs before, but not specifically about opening emails. I'd say I lean a bit toward using target="_blank" on mail links, despite my feelings on using it in other scenarios.
<a href="mailto:someone@yoursite.com" target="_blank" rel="noopener noreferrer">Email Us</a>This is somewhat rare to see for some reason, but mailto: links can define the email subject and body content as well. They are just query parameters!
mailto:chriscoyier@gmail.com?subject=Important!&body=Hi.You can send to multiple email addresses, and even carbon copy (CC), and blind carbon copy (BCC) people on the email. The trick is more query parameters and comma-separating the email addresses.
mailto:someone@yoursite.com?cc=someoneelse@theirsite.com,another@thatsite.com,me@mysite.com&bcc=lastperson@theirsite.com
I'm not sure how useful this is, but it's an interesting curiosity that you can make a <form> do a GET, which is basically a redirect to a URL — and that URL can be in the mailto: format with query params populated by the inputs! It can even open in a new tab.
See the Pen
Use a <form> to make an email by Chris Coyier (@chriscoyier)
on CodePen.
Because mailto: links are valid anchor links like any other, they are typically styled exactly the same. But clicking them clearly produces very different results. It may be worthwhile to indicate mailto: links in a special way.
If you use an actual email address as the link, that's probably a good indication:
<a href="mailto:chriscoyier@gmail.com">chriscoyier@gmail.com</a>Or you could use CSS to help explain with a little emoji story:
a[href^="mailto:"]::after {
content: " (📨↗️)";
}I dig how it doesn't just block them, but copies the email address to your clipboard and tells you that's what it did.
The post All About mailto: Links appeared first on CSS-Tricks.
This post is originally published on Designmodo: Free HTML Email Template Builder, No-Code Editor – Postcards
Postcards is here and we want to show them to you! Using Postcards, you can create beautiful responsive emails/newsletters templates in minutes with drag and drop features and ready-made modules. Generated and exported emails are optimized for most popular email …
For more information please contact Designmodo
Sending an email to another person is not as secure as one would think. When you send an email, your email does not travel directly to the computer of the person that expects the email; it needs to hop through a bunch of other mail and proxy servers until it reaches its destination. During all this hopping from server to server, your email content is visible to everyone that knows a little bit about sniffing the network, but more importantly, Internet companies and mail providers can read the content. Think of it as sending a postcard where everyone with access to the postal system (of your postbox) can read the content of the postcard.
A lot of people claim that they have nothing to hide, which I sympathize with, after all, we haven’t done anything wrong, so why should we hide things? However, that is not the point. The point is that you are having a private conversation with another person and sometimes you don’t want anybody else outside that conversation to know what you talked about. And that is your right to have that sort of privacy. The same goes for email and other digital means of communication, where only you and the destination should be reading the content of your email, not a telecom company, not someone sniffing the network, and definitely not your email provider. For the same reason that you do not give up your favorite social media password to anyone, no one should be able to access and read what is yours.
In most of the applications that we use today, the use of email continues to be an important part of many of the main functionalities that these systems offer us. Whether it's to register as users, recover a password, receive reports, invoices, flight reservations, accommodations, or anything else, sending emails is something that is still closely linked to the core functionality of many systems.
On the other hand, email is something that has been around for a long time. This is why we often overlook tests where sending emails is involved, either because of the complexity of the task or because we assume that there will be no errors. However, there are certain scenarios where it is advisable to perform some minimal tests. For example, some elements that you should want to check might be:
You're reading Microsoft Outlook Update: Animated GIF and Other Features, originally posted on Designmodo. If you've enjoyed this post, be sure to follow on Twitter, Facebook, Google+!
Although Microsoft Outlook is most widely used for B2B customers, something like sending an email with the unique layout is practically impossible. The reason for this lies in the fact that the Outlook is not compatible with most HTML innovations. …
You're reading How to Import HTML Email Template from Postcards to Convertkit (YouTube Tutorial), originally posted on Designmodo. If you've enjoyed this post, be sure to follow on Twitter, Facebook, Google+!
Welcome to a new video tutorial where we’ll learn about how to upload a customized email newsletter to Convertkit. In this tutorial, we’ll use Postcards to build a customized email template and Convertkit to send an email to subscribers.
You're reading Postcards Introduces Transactional Email Modules, originally posted on Designmodo. If you've enjoyed this post, be sure to follow on Twitter, Facebook, Google+!
Today, we released newly designed transactional modules for Postcards. We designed and coded 26 absolutely new modules! You can start using them directly in the Postcards App now.
Postfix is a free, open source software application that works as a Mail Transfer Agent (MTA) for routing and delivering email.
Dovecot is an Open-source MDA (Mail Delivery Agent) and is responsible for delivering emails to local recipients' mailboxes on a server.
This post is originally published on Designmodo: Free HTML Email Newsletter Templates
Email marketing is everywhere. Even if you have a website that represents small local business, chances are that you have a list of your loyal subscribers to inform about happenings in your company. Create email newsletter templates is very simple …
For more information please contact Designmodo
You're reading How to Import Custom HTML Email Template from Postcards to Intercom (YouTube Tutorial), originally posted on Designmodo. If you've enjoyed this post, be sure to follow on Twitter, Facebook, Google+!
In this video, I will show you how to import a custom email template created in Postcards directly to Intercom. Open the Postcards App and let’s prepare our template for Intercom. First, insert all of the required tags into your …
You're reading How to Import a Custom HTML Email Template from Postcards to Salesforce [YouTube Tutorial], originally posted on Designmodo. If you've enjoyed this post, be sure to follow on Twitter, Facebook, Google+!
In this video, I will show you how to import a custom email created in Postcards directly to Salesforce. First, open the email template in the Postcards app and insert all the required tags by Salesforce.
One of the keys to success in digital marketing is to ensure that the right hand is always talking to the left. This means that if you’ve spent time building a beautiful WordPress site and regularly write high-quality content for it, you’ll want those efforts shared across other marketing platforms.
Social media is one of the more obvious choices as it’s (typically) free to use and doesn’t take much effort to write a 140-character message and hit “Send.”
But email is another one of those marketing arms that should stay closely connected to everything you do.
Of course, as a web developer, email marketing might not be something in your wheelhouse.
But just because it’s your job to create websites for your clients doesn’t mean you shouldn’t know how to enhance it through other marketing strategies.
The same goes for your own professional website.
As a WordPress developer or designer, your website is a reflection of the work you do and would greatly benefit from increased exposure through email.
In general, email marketing is a term used for communications shared between you and email subscribers with the main goal of converting them into paid customers.
These types of emails are the equivalent of a landing page on your website.
In other words, sell, sell, sell.
A newsletter, on the other hand, is a type of email marketing; however, it’s more reminiscent of a blog as the goal is to establish trust and develop a relationship with email subscribers by delivering added value.
In this article, I want to focus on the newsletter arm of email marketing.
Much of what you’d need to do to create a newsletter is similar to the work you do to build a website, so this is a logical choice for dipping your toes into email marketing (at least to start).
I’ll discuss the power of email, how it can be used to promote your site, and break out some of the best newsletter plugins you can use in WordPress to create and send newsletters.
There’s a lot that goes into executing an email marketing campaign and I don’t necessarily believe it’s something you need to be fluent in as a WordPress professional.
However, I do believe that every business owner (including yourself) should be using newsletters to stay connected to their audience through email.
In a report from Radicati, they predicted that there will be over 3 billion email users around the world by 2020 and that the number of emails sent every day will average about 257 billion.
While that statistic basically says that there’s a lot of noise generated by email, it also demonstrates the huge opportunity available to business owners to reach a new audience, stay connected to them, and, hopefully, make more money through a newsletter.
Don’t believe me?
According to HubSpot, 73% of millennials prefer communications from businesses to come via email.
As well as this, more than 50% of U.S. respondents check their personal email account over 10 times a day and prefer to receive updates from brands
On the other side of the table, marketers are claiming huge benefits from using email in their marketing efforts.
81% of retail marketers surveyed by WBR Digital said that email marketing improved customer acquisition rates while 80% said it helped improve customer retention.
Want some more reasons as to why your WordPress site and business need a newsletter?
Here you go:
At the end of the day, a newsletter is yet another means by which you can reach your audience, and I’d argue it’s a lot easier to do than social media and definitely much cheaper than paid search marketing.
If you’re not using newsletters to stay in touch with current clients, convert interested prospects, and improve your business’s reputation right now, think about those potential growth and revenue generating) opportunities you’re missing out on.
The work you do within WordPress to build quality websites is incredibly important.
However, visiting a website and digging around it requires work from your visitors—and that’s not always the ideal experience.
Once you’ve made that first contact, wouldn’t it be nice to give visitors a chance to sign up for a free newsletter where you take control of the relationship for a while?
Yes, this means there’s more work for you to do, though probably not as much as you’d expect.
WordPress, of course, has a number of plugins available to help users integrate newsletters into their website.
Usually, however, when people talk about these plugins, they’re referring to email subscription forms that connect the subscribers to you, and their data to your newsletter platform. But that’s not what we’re talking about here.
Popups and contact forms will take care of automating the subscription process.
What you need now is a tool that will streamline the process of actually creating and sending newsletters to your email subscribers.
While you could use a third-party platform to do so, there are cheaper WordPress plugin alternatives that allow you to do all the work within WordPress.
Here are 7 plugins to consider:
HubSpot’s WordPress plugin makes it super easy for you to create, personalize, and optimize your marketing emails. The drag-and-drop editor allows you to quickly draft email campaigns with a professional design and optimized for any screen size. And if you’re running low on inspiration, you can get easily get started with one of the many goal-based templates available.
HubSpot’s email marketing software comes bundled with a free, powerful CRM where you can store all of your contact’s information and use it to personalize your emails to look like it was tailor-made for each and every one of your recipients. The built-in A/B tests and analytics will allow you to measure and maximize the impact of your outreach.
This free WordPress plugin is actually quite comprehensive. Not only does it enable you to add subscription boxes to your site, but it also gives you two options for sending newsletters. The first is a simple automation of sending out notifications to subscribers when a new blog publishes. The second is a more customized approach to designing and sending newsletters from WordPress.
There is a free version of this plugin as well as a premium one available. While I normally would recommend the premium plugin, the free MailPoet seems like it would be more than enough for a small business owner or marketer to use when starting out. It comes with 70 themes, a drag-and-drop builder, built-in analytics, automated messages, and is responsive. The only difference I see between the two versions is the number of subscribers you can send to (either less than or more than 2,000) and the amount of analytics insights available.
This premium newsletter plugin is perfect whether you’re a developer trying to quickly get your own newsletter out the door or you want to give your clients a tool that’s easy enough to use on their own. With a drag-and-drop builder, live template editing, and full newsletter campaign management within WordPress, this one is worth every penny.
While this seems at first glance like your typical newsletter plugin, I think my favorite thing about this one is all the different ways it enables users to capture newsletter subscribers. Rather than rely on newsletter-specific subscription forms, it also adds a subscription checkbox to other contact forms (in case those leads missed the newsletter form or just don’t want to sign up twice). It also imports all previously registered users into your newsletter subscriber list.
What makes this plugin really stand out from the pack is the fact that there are no restrictions put on how many newsletters subscribers you can have (something that can become quite frustrating after a while—both within and outside of WordPress). Other than that, this is simply a reliable newsletter plugin you can use to build cleanly-designed newsletters and schedule out at the most optimal times for your subscribers.
Another full-featured WordPress plugin, this one from Tribulant will cover all your bases. Newsletter templates are provided. You can manage your various mailing lists and review the statistics on each within WordPress. You can create a variety of subscription forms both for your site as well as off-site. And much, much more. One thing to be aware of is that the limit for subscribers is pretty low (500) with the free plugin, so if you intend on having a much larger list of subscribers, you’ll want to invest in the premium one.
As a consumer, think about how many newsletters you receive from your favorite brands.
Unless you’re swamped at work and trying to keep your eyes off of the growing list of emails in your inbox, you likely get excited to see the latest newsletter from them, right?
Who knows what this next one contains?
Maybe it’s a list of their most popular blogs from the week. Maybe it’s a special deal on that computer monitor you wanted to buy.
Or maybe there are just silly pictures of puppies they sent to lighten the mood on your Monday morning.
As a receiver of newsletters, you know what sort of lure they have over you as a consumer.
As a sender of newsletters, however, think about what you’d be able to do with those extra touch points with your consumer base.
They obviously want to hear from you as they willingly subscribed to your newsletter, right?
So why not make the most of their entrusting you with their email address and start sending them a valuable newsletter every week or every month?