So you want to know ‘How to add a ‘Facebook Like Button’ to your email template‘. Ever since MailChimp promised to add the functionality to their system we have seen a buzz with people wondering how they do it. This article is a quick and dirty guide to DIY Facebook Like Buttons embedded in email templates. So no matter who your ESP is you can embed a Like Button within your email design.
Well to be perfectly honest it really is not that hard, however contrary to what you may have hoped it is not quite seamless and there is no way for it to be. It involves a 2 click process.
The simplest way and the one most likely to work for most users is to use the following code.
<a href="http://www.facebook.com/plugins/like.php?href=http://www.facebook.com/pages/Email-Expert/130177676994892?ref%3Dts&layout=standard&show_faces=true&width=450&action=like&colorscheme=light&height=80 target=">
<img title="Facebook Like Button" alt="" src="http://emailexpert.org/dontexist/likebutton.jpg" />
1. Change the URL to the page you want ‘liked’
2. Change the img location and upload your likebutton image.
The Mailchimp implementation is a little different. When you click the ‘Like’ button you are taken to the hosted version of the newsletter and the “Like Box” as above is overlayed as a div. You could also take this route by adding the code to your hosted version of the newsletter.
With a little tweaking of the code you can do one better than the new window that is launched using this method. What is not going to be possible is a single click with you landing on your facebook fanpage or your website homepage. There will need to be two clicks.You can have the like button delivered as overlay on the html version of your newsletter as one example.
What Mailchimp do
As MailChimp said in their recent release:
Qudos for MailChimp implementing this so quickly, but with a little tweaking you should all be able to do something similar relatively painlessly while you await your own ESP or software vendor adding similar social sharing to their email newsletters.
Anyone else have idea’s on improving on this basic implementation?
Credit to @iamelliott for inspiring this blog post with his question on LinkedIn