<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: How to annoy your affiliates</title>
	<atom:link href="http://www.affiliateblog.co.uk/how-to-annoy-your-affiliates.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.affiliateblog.co.uk/how-to-annoy-your-affiliates.html</link>
	<description>UK affiliate marketing news, views and podcast interviews.</description>
	<lastBuildDate>Wed, 21 Dec 2011 11:08:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Clarke</title>
		<link>http://www.affiliateblog.co.uk/how-to-annoy-your-affiliates.html/comment-page-1#comment-228</link>
		<dc:creator>Clarke</dc:creator>
		<pubDate>Thu, 17 Aug 2006 11:47:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.affiliateblog.co.uk/how-to-annoy-your-affiliates.html#comment-228</guid>
		<description>The problem for a lot of Merchants is the Network system won&#039;t allow them to do a simple replace. I say simple in that the idea is a simple one, the actually getting the system to do it is a bit more complex to put in when you need to have a simple to use system for the Merchant to use. So because of this and a number of other things Merchants do so wrong with banners Paid On Results has always done this task for the Merchants but this has lead to us having to dedicate a huge resource :-( ... However this week should see the launch of the New Merchant Control Area and for the 1st time Merchants will be able to update banners very easily using the Interface but what is magic about this system is they can&#039;t stick 120x600 banners in to 468x60 spaces, they can&#039;t simply delete a banner and make a big nasty space appear on the Affiliates website, the system guides them in to doing the “right” thing. Merchants will have to select a base banner for every size they want to provide so should they ever want to get rid of a creative they can default it to the generic banner for the Merchant and so solving the problem of a blank space. Believe me this system to make it super simple for Merchants and to ensure nothing daft happens to Affiliates sites took a while to make but I think we fully cracked this issue.</description>
		<content:encoded><![CDATA[<p>The problem for a lot of Merchants is the Network system won&#8217;t allow them to do a simple replace. I say simple in that the idea is a simple one, the actually getting the system to do it is a bit more complex to put in when you need to have a simple to use system for the Merchant to use. So because of this and a number of other things Merchants do so wrong with banners Paid On Results has always done this task for the Merchants but this has lead to us having to dedicate a huge resource <img src='http://www.affiliateblog.co.uk/wp-includes/images/smilies/icon_sad.gif' alt=':-(' class='wp-smiley' />  &#8230; However this week should see the launch of the New Merchant Control Area and for the 1st time Merchants will be able to update banners very easily using the Interface but what is magic about this system is they can&#8217;t stick 120&#215;600 banners in to 468&#215;60 spaces, they can&#8217;t simply delete a banner and make a big nasty space appear on the Affiliates website, the system guides them in to doing the “right” thing. Merchants will have to select a base banner for every size they want to provide so should they ever want to get rid of a creative they can default it to the generic banner for the Merchant and so solving the problem of a blank space. Believe me this system to make it super simple for Merchants and to ensure nothing daft happens to Affiliates sites took a while to make but I think we fully cracked this issue.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

