<?xml version="1.0" encoding="UTF-8"?>
<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/"
	>

<channel>
	<title>MailChimp Email Marketing Blog &#187; new feature</title>
	<atom:link href="http://www.mailchimp.com/blog/tag/new-feature/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mailchimp.com/blog</link>
	<description>MailChimp, email marketing, and monkeys!</description>
	<lastBuildDate>Fri, 13 Nov 2009 21:09:20 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Update Profile Link</title>
		<link>http://www.mailchimp.com/blog/update-profile-link/</link>
		<comments>http://www.mailchimp.com/blog/update-profile-link/#comments</comments>
		<pubDate>Tue, 11 Dec 2007 17:16:53 +0000</pubDate>
		<dc:creator>Ben</dc:creator>
				<category><![CDATA[MailChimp News]]></category>
		<category><![CDATA[MailChimp Upgrade]]></category>
		<category><![CDATA[Tips, Tricks, Best Practices]]></category>
		<category><![CDATA[new feature]]></category>
		<category><![CDATA[upgrade]]></category>

		<guid isPermaLink="false">http://www.mailchimp.com/blog/update-profile-link/</guid>
		<description><![CDATA[When you send your email newsletters, do you get customers asking you to change the email address you have on file, because they&#8217;ve changed jobs or something? In the past, you had to log in, find their profile, and then make the edit for them. That&#8217;s not so bad, but if you&#8217;re like me, after [...]]]></description>
			<content:encoded><![CDATA[<p>When you send your email newsletters, do you get customers asking you to change the email address you have on file, because they&#8217;ve changed jobs or something? In the past, you had to log in, find their profile, and then make the edit for them. That&#8217;s not so bad, but if you&#8217;re like me, after you&#8217;ve spent a couple hours writing your newsletter and sending it off, the last thing you want to do is track down a profile to change someone&#8217;s address.</p>
<p>Subscribers to your MailChimp lists can now edit their own profiles (email address, name, interest groups, company name, whatever) by just clicking a link in the email footer.</p>
<p>To add the link, use our<strong> *|UPDATE_PROFILE|*</strong> merge tag. Wherever we see that tag, we&#8217;ll replace it with each recipient&#8217;s unique link.</p>
<p><a href="http://www.mailchimp.com/blog/update-profile-link/update_profile-tag/" rel="attachment wp-att-550" title="Update_Profile tag"><img src="http://www.mailchimp.com/blog/wp-content/uploads/2007/12/mailchimp_update_profile.gif" rel="facebox" alt="Update_Profile tag" border="0" hspace="0" vspace="5" /></a></p>
<p><span id="more-549"></span></p>
<p>If you send regular newsletters to members who might be subscribed for long periods of time, you should assume a lot of members will be changing their email addresses (I hear average email address turnover is  <a href="http://www.destinationcrm.com/articles/default.asp?ArticleID=2578" title="email address turnover" target="_blank">about 30% per year</a>).  So you&#8217;ll want to make it as easy as possible for them to edit their records with you.</p>
<p>This is not something that ALL users will want. Some of you might have some fields you just don&#8217;t want subscribers to edit (or even see). Some of you might be syncing MailChimp with your in-house databases (using the <a href="http://www.mailchimp.com/api/" title="MailChimp API" target="_blank">MailChimp API</a>), so you&#8217;re already using your own &#8220;update profile&#8221; type of link.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mailchimp.com/blog/update-profile-link/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
	</channel>
</rss>
