FeedBlitz is an email and social media subscription automation service for blogs and social media, and the premium FeedBurner alternative.

Get free email updates:

Preview | By FeedBlitz

FeedBlitz News

Subscribe to the FeedBlitz Blog for news, customer service and feature updates by mail or RSS.


Coming Soon: The List Building for Bloggers E-book!

Thursday, April 28, 2011

List Building for Bloggers will soon be available as an eBook! I can't wait to have this see the light of day, as well as being just in time for my List Building for Bloggers session at Blog World Expo, New York.

The book contains additional new content, new illustrations and consolidated tips to help you rejuvenate your email list building activities with very little work.

When it comes out, I'll be thanking FeedBlitz clients with super-special customer-only pricing for the first couple of weeks, so watch out for that. FeedBlitz News subscribers will also get a good deal!

In addition, everyone will get the chance to pre-order at a simply insane price that will only be available for 48 hours once it's released. News next week on where to go and how to secure the "Phil is out of his freaking mind" launch discount.

Finally, we will be welcoming affiliate sales of the book. You'll be able to keep at least 50% of the sale price your sales make, so it's a standout opportunity. I'll have a full blog post to talk about affiliate pricing once the pre-ordering pages are ready to roll.

Labels: , ,


Subscriber Management Improvements for FeedBlitz Mailing Lists

Friday, April 22, 2011

As part of the changes that are going into the FeedBlitz v4 beta, we're not only changing overall navigation but also the way certain individual pages work as well. Some of these changes are sufficiently useful that they merit porting back to the current version.

The following changes should reduce a lot of the more common complaints we get about some of the things that FeedBlitz does!

Hope you like 'em :)

Easier resubscribes

Subscribers who used a site's subscription form to start subscribing after their subscription had lapsed used to have to log in to FeedBlitz to complete the task - a complex and confusing process for some subscribers. This is no longer true; a standard dual opt-in activation email is sent instead. One click there and they're back on the list.

Simpler dual opt-in activation emails

The default activation email (which list owners can change via Newsletters - Settings - Custom Confirmation Email) used to be verbose, and included the subscriber's email address in the activation link. This could create two problems:
  1. The chattiness of the text confused some would-be subscribers, and
  2. The email address confused some email apps, some of which erroneously converted the email address to a mailto: link.
If the subscriber had this second problem and clicked on the email address to activate their subscription, their app would instead fire up their email editor as if they were composing an email to themselves. Not a FeedBlitz bug, but something we can help change.

So, the text has now been dramatically reduced to improve clarity, and the email address in the copy moved outside the activation link, so users who are confirming their subscription won't be tempted to click that part of the text as they do so.

Direct subscriber change of address

List owners, when requested to change a subscriber's address, used the screens to create a request that was sent to the new subscriber to activate. A publisher-initiated dual opt-in, in effect. This was tedious and, since we know our publishers are made of the right stuff, largely unnecessary.

As of now, changing a subscriber's address via Newsletters - Subscribers - Change Subscriber Email Address will usually change the relevant email address immediately, sending a notification email that the change has been made to both the current and new addresses. No need for any activation clicks any more.

Rarely, the old "opt-in" method will still be used, depending on the status of the new address in the FeedBlitz database. This happens if something's up with the desired new address only.

Subscriber screens clarified

Some of the icons on the subscriber screens could be confusing to list managers; these have been replaced with labeled buttons instead. Much clearer.

Subscription audit data visible

A subscriber or a list manager can now access a subscription's audit data - creating IP address and referring page - in case the subscription was maliciously created. Drill down from the subscriptions page or the subscriber pages to view the data.

Clearer account merging

Finally, instructions on how to merge two accounts have been clarified. Sometimes users would feel stuck in a loop because they weren't logged in to the correct account as they tried to complete the merge.

Labels: , ,


Your Email Marketing: DIY or Outsource, Free or Paid?

Friday, April 15, 2011

My goal with this final post in the current List Building for Bloggers series is to help you frame the questions you need to answer to find the best fit for you, in terms of going DIY (Do It Yourself) or using a third party email marketing service; and paying or using a free option. In this article I will discuss:
  • Back to Basics
  • Planning
    • Minimizing list management technology changes
    • Understanding the true cost of "free"
    • DIY server restrictions
    • Understanding free service volume limits
    • Features
    • Support
  • When to DIY
  • When to FREE
  • When to PAY
  • Three Real World Examples
  • Your Mileage May Vary
  • And, Finally...
Full disclosure: Obviously, I run a service and I’m skewed to thinking that’s a good idea. Don't say you weren't warned...

[This is the latest article in the List Building for Bloggers series – Click here to read all the recent #LBB posts]

Back To Basics

Throughout the List Building for Bloggers (LBB) series I’ve been emphasizing permission and relevance above all for success with your email marketing and subscriber growth efforts. The reason for this is that with permission and relevance you get better deliverability – your email is much more likely to make it to the inbox, and much less likely to be flagged as spam.

I’m emphasizing this point – again – because in this post I’m going to offer some tips on choosing between running your mailing yourself, or whether / when you should use an outsourced service. Deliverability is key. If the mail can’t get through, you’ve failed.

For the purposes of this article, the DIY option includes any software or service that you run on your own servers, since that means that any email you send goes through your mail servers, and that’s a critical for deliverability (see this earlier LBB post).

The Difference is Planning

Minimize list management technology changes

One of the things that can really mess up a mailing list and your success with email marketing is changing how you run that mailing. Every time you transfer subscribers from one app or service to another, you risk losing some of them according to the provider’s import policies (see the section on importing in this LBB post); you may experience significant delays if your new technology requires subscribes to resubscribe (FeedBlitz doesn’t), or if your new provider requires your list ot be vetted before mailing can begin (again, FeedBlitz typically won’t make you wait). Changing email servers and technologies might also require white list changes by your subscribers, further complicating inbox deliverability.

So, in a perfect world, you need to minimize the number of times you change list management systems for the life of your blog. It’s much less hassle all around.

What this implies, then, is that you need to think about where your list is now, how large you expect it to become and how quickly, because list size is a significant limiting factor on DIY implementations; I’ll get to this later when I discuss mailing volume limitations.

Understanding the true cost of “free”

Free is a compelling price point, no doubt about that, especially if you’re just starting out and don’t have many subscribers (yet). But free usually comes with extensive limitations: No support, limited features and no subscriber import (FeedBurner). No phone support (some services). Volume limitations (fairly close to bait and switch, in other words). Deliverability nightmares. Who needs that?

For apps that are free and limit your feature choices, you need to think about how much you intend to use your list in the future.

For apps that are free but have no – or restricted – support, do you have the time to dig into issues with ISPs, blacklists and logs to resolve deliverability problems? Do you have the time to figure out why an email did or didn’t go out, or why it looked that way?

Because in the real world, time is money. Consider: How much do you / would you charge for your time? If you’re spending time self-supporting your mailing list app, what is that time being NOT spent on (the “opportunity cost” in accounting-speak). Is spending time self-supporting the best use of your time and resources?

Let's make it really clear how much free really costs you by attaching some dollar numbers to it.

For the sake of argument, and to keep the math simple, say your nominal hourly rate is $60. If you spend just 5 minutes a day managing your mailing list during the work week, that’s 110 minutes per month on average. So your not being able to have a service do it for you is costing you $110. Put another way, if  your ad revenues are such that every post you write makes you $100 ad revenue a month, and you can write two extra posts in that 110 minutes, you just missed out on $200 of real money. Total cost of "free"? $310. 

It gets worse if you’re constructing your newsletter by hand instead of using an email marketing automation solution like FeedBlitz. If you spend an hour a week on your weekly newsletter, in addition to anything else, that’s costing you $240 a month in your time alone at $60 / hour, and if that’s 4 blog posts that could have been written instead, a financial loss of $400 in terms of revenue you didn’t see. That service (free or otherwise) is costing you $640 a month even when it “only” takes an hour a week of your time.


This is why FeedBlitz exists: automating these tasks practically eliminates these chores, saving you time and, hence, money.

But I digress...

DIY server restrictions

For most bloggers, a DIY solution means sending emails via your ISP’s email servers. Most ISPs and hosting services will strictly limit the number of emails that can be sent per day, because they don’t want their systems to be tagged as spammers (remember from earlier posts that IP sender reputation is the #1 factor in good deliverability). That number is usually in the 250-1000 emails per day range.

If you think your list has a chance of growing to be in this range, you’re going to exceed your ISP’s limits quickly and you’ll need to outsource to a dedicated service anyway.

Again, if you do end up with deliverability problems, or a subscriber saying “I didn’t get your email” – then what? You need to access logs (if they exist), interpret them (if you can) and then figure out a solution. Which is part of the deal if your day job is email marketing, ISP relations and server management.

But wait, yours isn’t, is it?

More on free and volume limitations

It’s also worth noting that some “free” solutions are for list sizes under some number, which might seem pretty large and decent to you at first, and also limit you to the number of emails you can send per month for free. At which point of course, comes the switch, and you have to pay.

For the sake of argument, let’s say the limitation is your list must be under 500 subscribers and you can send 5,000 emails for month for free. To keep the math simple, let's further assume that your list size is 400 subscribers, as an enthusiastic / professional blogger / content marketer you post once a day during the week, and your automated mailings are sent on a daily schedule if there's new content.

In this scenario, you hit the volume limit, without any list growth, in the third week. Gotcha!  The larger the list, the sooner you hit that limit. And now you have to pay. It isn’t really going to be free after all...

Well, perhaps then you can scale back to a weekly mailing? Oh, wait, you can’t, because these services don’t have a weekly automated mailing option (unlike FeedBlitz, which does). Well, OK, so instead you go to a manual mailing – but now "free" is costing you $640 a month (see the calculation further up) in your time / opportunity costs, plus your relevance just cratered because mailings are reaching everyone days late.  Or you can just write less – only you’re a content marketer, and that’s a quick way to lose your audience to a competing site. Not an option.

Does that sound like a win to you? Well, not for you, no. For the service, yes, because you pretty much have to upgrade to keep going.

Feature Creature

Of course, every email service or app is different. Broadly, though, you can consider categories of capability that you can use or grow into as your subscriber base expands. I’ve discussed these in earlier posts on growing your lists here, here and here, and discussing things like autoresponders here.

At a high level, this is checkbox stuff – and remember, even if you’re just starting out in bogging, you want to minimize the number of times you change services. So these questions apply to both “now” and “in the next year or two.”
  • Do you / will you want to say “thank you” or run time-based drip marketing or email courses? Then you need autoresponders.
  • Do you / will you want to automate the email process completely from your blog, or spend time constructing additional editorial content (why? Seriously, why is this not on your blog anayway?) and manually building your mailings? If you want to spend your time in things you’re good at and creating compelling content, a service must have blog-powered automation.
  • Do you / will you want automated mailings from your blog (a la FeedBlitz) but want to offer different schedules for different audiences? Then you need a solution with automation AND schedule flexibility.
  • Do you / will you have the time and energy to manage and maintain an email app on your own systems, or do you have more valuable things to do with your time? If the latter, run with a service.
  • Do you / will you use video in your blogs? Then a solution that automatically handles embedded video is a requirement.
  • Do you / will you need segmentation, personalization and demographics? Then you’ll need custom fields.


Sooner or later, you’re going to need help.  Getting set up, changing a setting, or dealing with an issue. Can you fire off an email, pick up the phone? If not, what other resources are there – user forums? (yuck, see here what I think about companies that abandon their product support to user forums).

Now it may be that not having true support is OK with you, especially if you’re blogging casually for kicks and not for greenbacks. But the more important the blog becomes to you and your income stream then the more important your list and deliverability becomes. A snafu at the wrong time can kill a campaign, event or special offer. Who are you going to call if and when that happens? Access to knowledgeable support is invaluable when you need it.

The devil (or God, depending on your perspective) is in the details of course. But at least answering questions like these can help you make the best informed choice you can.

When to DIY

  • If your list size is going to remain below your ISP’s volume limits (250-1000) for the foreseeable future;
  • AND there are no better ways to spend your time (and money) than to install, manage maintain and self-support the app for the foreseeable future;
  • AND you can handle deliverability / IP reputation issues from your server(s).
Only go DIY if your needs match all these criteria.

When to FREE

  • If your list size is low enough to qualify for the free service for the foreseeable future;
  • AND the feature limitations are not important to you for the foreseeable future;
  • AND price is the most significant factor;
  • AND the lack of prompt available support is not an issue;
  • AND you can trust deliverability.

When to PAY

  • If your list will outgrow your ISPs of FREE service limits;
  • OR your content marketing will result in many email sends a month;
  • OR you want expert support when you need it;
  • OR  you want features like multiple lists, advanced scheduling, autoresponders, enhanced branding;
  • OR  you want to NOT worry about deliverability, subscriber management etc.
In other words, you should plan on paying if ANY of the above criteria match your needs or expectations.

Three Real-World Examples

Google’s FeedBurner is a free service for bloggers that does the basic email service well and there are no list size restrictions. So it’s not DIY, and it is FREE. But there is no support, limited branding, no schedule flexibility and no features like Facebook integration, autoresponders or manual mailings. There’s no subscriber import and no subscriber management API. So it's very limited from a feature set perspective, and so an increasingly poor choice as your blog becomes a larger part of your income, marketing and branding strategy.

On the other hand, FeedBlitz is a PAY service (fees start at only $1.49 for very small lists) for bloggers with all the bells and whistles. Read more about us here.

Of the more traditional services serving small business and personal markets, Constant Contact is probably the best known. They’re feature rich, lots of service and oodles of support. But the service comes with higher entry costs, and charges extra for features such as archiving that other services bundle. Crucially for bloggers, all mailings have to be built by hand – they automate delivery, but not production. So you need to understand the extra hidden costs to you in terms of time and money building the mailing (there's that $640 a month again), as well as their service fees. If you’re not a blogger or content marketer, they may well be a great fit for you because you can't automate it - but then why are you reading this? Hmm...

[I haven’t any installed software examples because, honestly, anyone with any list of any size should not, in my opinion, be taking on the time burden, deliverability risk and feature limitations of self-installed email list management software. But you should certainly do your own due diligence if your email marketing goals match the DY criteria above.]

Your Mileage May Vary

Obviously, what works for you depends on your current and expected needs in terms of email marketing, and how that fits into your overall content marketing / blogging / social media efforts.  My goal with this final post in the current List Building for Bloggers series is to help you frame the questions you need to answer to find the best fit for you.

Good luck!

And, Finally...

I'm wrapping up this series here - it's been both fun and challenging to write, and I hope that you've manage to get something out of it.

I'm not, however, done with the concept! There will be a full recap post (maybe more than one) to come, and I'm using this series as the basis for conference presentations at Blog World Expo in New York this Spring, and at the Savvy Blogging Summit in Colorado in July. If you're at these events, please stop by and say hello.

Not only that, though. I'll be making a special announcement May 1st about the series that I'm pretty excited about! So stay tuned for that too.

About List Building For Bloggers #LBB

Written by Phil Hollows, the FeedBlitz Founder and CEO, List Building for Bloggers (#LBB) is a series of posts to help you make the most of your blogging by harnessing the power and capabilities of email, the universal social network, with your bog and social media communications. No matter whether you're a novice or a more advanced blogger, there will be something for you to learn, apply and benefit from in this series. Click here to read more about #LBB

P.S. If you think your friends or followers would find this series valuable, please retweet on Twitter or "Like" on Facebook using the buttons below. Don't forget to use the #LBB hashtag when you do. Thank you! And if you have a comment, contribution or something else to say, please comment too. :-)

Labels: ,


HTML Email Design Tips

Wednesday, April 13, 2011

In this issue of List Building for Bloggers I'll give some hints and tips on making your HTML mails work well in most readers. It isn't a "how to design great looking email" post; it's "having designed your great looking email, here's what you do to get it to look right" post.

It isn't as simple as you might think. It certainly isn't as easy as you want.

[This is the latest article in the List Building for Bloggers series – Click here to read all the recent #LBB posts]

All HTML is not created equal

HTML is the "language" - the code - that web pages are written in. Every web page is HTML; in fact is has to be in order to be a "web page" in the first place. Now, some of that HTML may be just enough to host the Mother of All Flash Objects (e.g. game and movie sites), but they all start as HTML.

As you also probably know, despite one's best efforts, some sites look sightly different, or behave slightly differently, depending on the browser you're using. The more complex the site, the greater the risk that some browser incompatibility will cause something funky to happen.

And it gets worse with smart phones.  BlackBerry browsers, let's be honest, are simply awful. iPhones and Android devices are a whole lot better because they use the same core browser technology that powers Apple's Safari browser (amongst others). But phones have different size screens, and they're typically a lot smaller (not just physically, but in the number of pixels they have) than most computer screens. It all adds to the fun of web site design.


As well as HTML, graphic designers use a related technology called CSS which helps make sure that the HTML displays (or "renders") the way they want. Like HTML, there are multiple generations of CSS, and each browser supports CSS to varying degrees. CSS is really, really powerful - and can get really, really, complicated - but the tools that graphic designers have rely on CSS to turn the HTML they build for sites into something that, more or less, within a certain degree of acceptability, looks and works the same way no matter where the web page is viewed. CSS is great for web sites; it helps eliminate many browser compatibility problems and makes complex / interesting web sites much easier to build.

So the typical web designer has to deal with all of this in order to get your web site to look good on all the different platforms and browsers that are out there.

It's a lot of work. It's complicated. It's often infuriating, fiddly and tiresome to boot.

They have it easy.

Welcome Back to the Stone Age - HTML for Email

Because it's just worse here in email-land. There are many more email apps (aka "clients") than there are browsers out there. There are desktop clients (e.g. Outlook, Thunderbird, Notes); the email app on your mobile phone, and web apps (gmail, hotmail, Yahoo!, whatever your ISP or cable company gives you).

All of them have different HTML rendering engines. All of them make different decisions about how to render the HTML. And, especially for desktop email clients, people can keep using the same app around for years and years (I still use Outlook 2003 personally, for example). Many of the older ones only have basic support - or even none at all - for things such as CSS.

Oh, and there are some email clients (I'm looking at you, Gmail), where lack of support for these capabilities is a design decision. They could support this stuff (if Yahoo and Hotmail can do a better job at rendering than gmail, it isn't a case of it being impossible). They simply elect not to. Don't like it? Tough luck.

So all the tools, technologies, that your web designer uses to build your beautiful web site? HTML 4, CSS 3? No good for email. Forget it. They're really not going to like what one has to do to get good HTML email rendering across the broadest set of email apps.

Email CSS Compatibility - the Chart of Doom

Corporate email provider Campaign Monitor has an excellent resource they update from time to time on the CSS support each major email client delivers. If you're a graphic design maven, gird your loins and read the whole post there. The chart doesn't yet include Android mobile devices, but since Android uses Apple's WebKit (well, mine does), the iPhone column will do for now. For bloggers, I'd caution that the market shares listed at the foot of the table will probably not reflect your readers' email software use, since you're much more likely to be talking to consumers. As such, webmail services like gmail, yahoo and hotmail etc will have a much higher share of your readership than indicated on the chart.

As a blogger, though, graphic design is no more your job than it is being a full-time email marketer. What the heck are you supposed to do to get your emails looking right across the board, given this degree of complexity?


Keep it simple, silly. The whole chart at Campaign Monitor is useful for graphic designers, but for the rest of us there are two areas that merit picking out.

They are the Notes 6/7 and Gmail columns, and the background and colors sections. Here they are, excerpted (remember, the source post with the whole graphic is here). Just look at all that red:

What you need to internalize from this is really basic:
  1. Gmail and Lotus Notes 6/7 really stink at CSS (and Outlook 2007/2010 is pretty odiferous too);
  2. Doing anything other than simple foreground colors is asking for trouble.
And it gets worse from there. More advanced CSS used for positioning and what's called the "box model" is inconsistently implemented, if at all. Use these CSS features at your peril.

The Blogger's Advantage

Ok, so this whole HTML email thing is one giant screaming nightmare, right? What are we to do?

Well, it isn't quite as bad as it seems as long as you follow a few basic rules of the road.

Better yet, as bloggers and content marketers, we actually have a huge advantage compared to corporate email marketers building custom "blasts" (ugh) every time they run a mailing. We deliver our messages in consistent form - what most email services call a template - time after time after time. The basic layout is similar every time we mail; only the post content changes. So what you need to focus on is getting the template right; once done you ought not to have to worry about rendering much in the future, provided you're a teensy bit careful with how you build your posts (and more on that below).

HTML Email Rules of the Road

For best results and the most consistent rendering:
  1. Don't use CSS at all. Use standard HTML tags - yes, even the nominally deprecated ones - to format your posts and template. So use old-fashioned tags such as the font, b and em tags; and use HTML tag attributes such as color, bgcolor, border, align attributes etc. instead of CSS. Don't use the style attribute; as soon as you do you're going to have rendering problems.
  2. Never, ever use CSS positioning statements. Use HTML tables to lay out your page. Yes, tables. They work consistently in HTML email; positioned divs won't.
  3. If you do use CSS for style, specifiy as much as you can as style attributes of the relevant HTML tags. Gmail in particular will simply ignore style tags and the classes / selectors they define or modify. Just to add to the fun and games, CSS will not always cascade as it should in some webmail clients. So if you're getting really fancy (again, don't), you're going to have to specify the style attribute on each tag.  But, really, don't do this. Specify a font, color etc. in the template with the font tag and be done.
  4. Don't use background images. They're inconsistently implemented, and if the subscriber is viewing with image display off, not having a background can make your email unreadable. In fact, if you can, avoid background colors too. Same reason.
  5. Don't use external stylesheets or classes. Did you not see the chart? They won't work in gmail at all. They also won't work in any email client where the user has images disabled. Besides, you're not using stylesheets, right?
  6. Always specify width and height for images. It makes the page look heaps better if there are no images, smooths rendering when images are being downloaded, and for some email clients (Outlook 2007/2010) stops images being displayed as too large or too small if they are downloaded late.
THE BOTTOM LINE: If you build your HTML template and party like it's 1999, you're going to be just fine.

It's also safe to ignore these rules, as long as you're ok with the email not "looking right" in certain email clients. That should be a business decision, though; don't take it lightly. It is also true that you can specify styles and classes (in which case redundantly include them in the HEAD and BODY of the HTML), knowing that email rendering will be better in those email clients that support them. By all means specify that images shouldn't have a border via CSS. But again, you need to know what your baseline is without that support, because you simply can't rely on it.

Other best practice

  • Use meaningful alt tags with images. When an email app doesn't display an image, it will typically display the "alt" tag in the box the image would have occupied instead (and if there isn't an alt tag specified, it may display the images URL, which will be very ugly). Why meaningful? Because you still want to get your message to the subscriber. Don't have an alt tag of "logo" - make it "The Latest from " or something. If you have a lot of imagery, see if you can "read" it using alt tags with images disabled. By the way, your blind readership only has this way of "seeing" images. Make your mailing work for them too.
  • Use a few, small images. The less work your email app has to do, the faster your email will display. Fast is good. Your beautiful 1MB photo will simply stop your mail from displaying right - if at all - for your mobile customer or the rural subscriber without broadband access.
  • Think about the preview pane. If you only have 3 lines in the preview and the user is going to decide whether to open your mail based on that, get the details up front - e.g. view online, the latest from , new coupon from Target today only etc.


Once you have your template happy (see testing below), you shouldn't have to worry much when you post. There are a few things that can mess up in certain readers, beyond the CSS tips above:
  • Keep the HTML simple in your posts. No CSS! Try to avoid using classes within the post itself.
  • Always specify image sizes for all images.
  • Always use alt tags for images. 
  • If you have active content (e.g. script, embedded audio, flash, even forms), provide options in your post to access the content if it doesn't appear, because in email it probably won't (well, apart from video, which FeedBlitz fixes for you).
  • Don't use MS Word to create posts. It adds lots of CSS and styles and will mess things up royally.


So there are three main problem email apps. Gmail, older versions of Notes, and Outlook 2007/2010. Most bloggers are unlikely to have many Notes users, and since it's about as useless as gmail, for most of us gmail can be used as a proxy. Once your mail looks OK in gmail with and without images, you're 95% of the way there everywhere else, especially when you follow the other rules.

To quick and dirty testing, then. Send yourself test mails from your system, and view in gmail. View with images on, and then view with images off. Don't like it? Edit, rinse and repeat.

Be Realistic

Finally, understand that 100% perfection across all email apps is very, very hard to achieve. Know your audience; if you have extensive readership on old Notes platforms you should verify your changes on Notes once you have gmail working acceptably. If your audience is using mobile devices more - and who isn't these days? - then consider how your template should change to accommodate the different form factor: Perhaps you can go from a fixed width to a flowing layout? Understand what compromises you are - and are not - prepared to make.

For FeedBlitz Users and Prospects

If you have a template you like from another vendor or service, please contact technical support. We'll be more than happy to help you convert it to our templating tags to simplify transitions.

Next Up

DIY or outsource: some help on deciding.

About List Building For Bloggers #LBB

Written by Phil Hollows, the FeedBlitz Founder and CEO, List Building for Bloggers (#LBB) is a series of posts to help you make the most of your blogging by harnessing the power and capabilities of email, the universal social network, with your bog and social media communications. No matter whether you're a novice or a more advanced blogger, there will be something for you to learn, apply and benefit from in this series. Click here to read more about #LBB

P.S. If you think your friends or followers would find this series valuable, please retweet on Twitter or "Like" on Facebook using the buttons below. Don't forget to use the #LBB hashtag when you do. Thank you! And if you have a comment, contribution or something else to say, please comment too. :-)

Labels: , ,


© FeedBlitz - Blog and RSS Email Solutions | www.feedblitz.com | info@feedblitz.com | Privacy | Terms of Service

Related Posts with Thumbnails Quantcast