<?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/"
		>
<channel>
	<title>Comments on: How to Word Disclosures &amp; Agreements to Meet FTC Rules</title>
	<atom:link href="http://www.amnavigator.com/blog/2009/10/09/how-to-word-disclosures-agreements-to-meet-ftc-rules/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.amnavigator.com/blog/2009/10/09/how-to-word-disclosures-agreements-to-meet-ftc-rules/</link>
	<description>Geno talks about affiliate marketing, leadership, etc</description>
	<lastBuildDate>Wed, 17 Mar 2010 00:52:08 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Geno</title>
		<link>http://www.amnavigator.com/blog/2009/10/09/how-to-word-disclosures-agreements-to-meet-ftc-rules/comment-page-1/#comment-4929</link>
		<dc:creator>Geno</dc:creator>
		<pubDate>Thu, 10 Dec 2009 13:38:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3735#comment-4929</guid>
		<description>Thanks, R.J.</description>
		<content:encoded><![CDATA[<p>Thanks, R.J.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: R.J.</title>
		<link>http://www.amnavigator.com/blog/2009/10/09/how-to-word-disclosures-agreements-to-meet-ftc-rules/comment-page-1/#comment-4924</link>
		<dc:creator>R.J.</dc:creator>
		<pubDate>Thu, 10 Dec 2009 06:40:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3735#comment-4924</guid>
		<description>As Geno said, an industry-wide disclosure/privacy policing should be written by the merchants for the affiliates (a one size fits all approach) with a spider to monitor compliance. Some affiliate networks already require this for each publisher(so it&#039;s nothing new just more clarified).</description>
		<content:encoded><![CDATA[<p>As Geno said, an industry-wide disclosure/privacy policing should be written by the merchants for the affiliates (a one size fits all approach) with a spider to monitor compliance. Some affiliate networks already require this for each publisher(so it&#8217;s nothing new just more clarified).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The FTC, Affiliate Disclosure and You &#124; Affiliate Tomorrow</title>
		<link>http://www.amnavigator.com/blog/2009/10/09/how-to-word-disclosures-agreements-to-meet-ftc-rules/comment-page-1/#comment-4898</link>
		<dc:creator>The FTC, Affiliate Disclosure and You &#124; Affiliate Tomorrow</dc:creator>
		<pubDate>Mon, 07 Dec 2009 23:16:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3735#comment-4898</guid>
		<description>[...] According to the FTC, &#8220;The disclosure should be clear, conspicuous and aiming to “alert the reader” that there is a “connection between the endorser and the seller.”  I also found great disclosure advice on Geno Prussakov&#8217;s affiliate marketing blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] According to the FTC, &#8220;The disclosure should be clear, conspicuous and aiming to “alert the reader” that there is a “connection between the endorser and the seller.”  I also found great disclosure advice on Geno Prussakov&#8217;s affiliate marketing blog. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geno</title>
		<link>http://www.amnavigator.com/blog/2009/10/09/how-to-word-disclosures-agreements-to-meet-ftc-rules/comment-page-1/#comment-4463</link>
		<dc:creator>Geno</dc:creator>
		<pubDate>Tue, 13 Oct 2009 20:31:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3735#comment-4463</guid>
		<description>I think the only way the policing/monitoring could work effectively is if there is an industry-wide standard/wording for the affiliate disclosure. Then content websites that have a merchant&#039;s name/link(s) could be spidered to verify if the standard-worded disclosure is in place.</description>
		<content:encoded><![CDATA[<p>I think the only way the policing/monitoring could work effectively is if there is an industry-wide standard/wording for the affiliate disclosure. Then content websites that have a merchant&#8217;s name/link(s) could be spidered to verify if the standard-worded disclosure is in place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cory Howell</title>
		<link>http://www.amnavigator.com/blog/2009/10/09/how-to-word-disclosures-agreements-to-meet-ftc-rules/comment-page-1/#comment-4459</link>
		<dc:creator>Cory Howell</dc:creator>
		<pubDate>Tue, 13 Oct 2009 18:21:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3735#comment-4459</guid>
		<description>Geno, as you &amp; one of your merchant&#039;s said, &quot;We support compliance although this is going to be near impossible to monitor.&quot;

I do not see how a company can be expected to: 
a) Find 
b) Follow 
c) Moderate 
d) Control 
a 3rd party to ensure proper disclosure - both time &amp; monetarily (budgets don&#039;t allow for a &quot;brand hunter&quot; position at most  companies).  

What if a webmaster can&#039;t be contacted or there is no other way to severe an affiliate partner?  Just way too many risks and opportunities to get into trouble.</description>
		<content:encoded><![CDATA[<p>Geno, as you &amp; one of your merchant&#8217;s said, &#8220;We support compliance although this is going to be near impossible to monitor.&#8221;</p>
<p>I do not see how a company can be expected to:<br />
a) Find<br />
b) Follow<br />
c) Moderate<br />
d) Control<br />
a 3rd party to ensure proper disclosure &#8211; both time &amp; monetarily (budgets don&#8217;t allow for a &#8220;brand hunter&#8221; position at most  companies).  </p>
<p>What if a webmaster can&#8217;t be contacted or there is no other way to severe an affiliate partner?  Just way too many risks and opportunities to get into trouble.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geno</title>
		<link>http://www.amnavigator.com/blog/2009/10/09/how-to-word-disclosures-agreements-to-meet-ftc-rules/comment-page-1/#comment-4398</link>
		<dc:creator>Geno</dc:creator>
		<pubDate>Sat, 10 Oct 2009 18:48:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3735#comment-4398</guid>
		<description>No, it definitely is not rocket science. I believe that as long as the affiliate is sincere and clear, he/she should be okay in the FTC&#039;s eyes.</description>
		<content:encoded><![CDATA[<p>No, it definitely is not rocket science. I believe that as long as the affiliate is sincere and clear, he/she should be okay in the FTC&#8217;s eyes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Katie @ Kitchen Stewardship</title>
		<link>http://www.amnavigator.com/blog/2009/10/09/how-to-word-disclosures-agreements-to-meet-ftc-rules/comment-page-1/#comment-4396</link>
		<dc:creator>Katie @ Kitchen Stewardship</dc:creator>
		<pubDate>Sat, 10 Oct 2009 05:38:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3735#comment-4396</guid>
		<description>I&#039;m amazed that my disclosure is a good example - it was just written with common sense and by the seat of my pants (after the disclosure.org part, that is).  Good to know it&#039;s not rocket science!</description>
		<content:encoded><![CDATA[<p>I&#8217;m amazed that my disclosure is a good example &#8211; it was just written with common sense and by the seat of my pants (after the disclosure.org part, that is).  Good to know it&#8217;s not rocket science!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geno</title>
		<link>http://www.amnavigator.com/blog/2009/10/09/how-to-word-disclosures-agreements-to-meet-ftc-rules/comment-page-1/#comment-4382</link>
		<dc:creator>Geno</dc:creator>
		<pubDate>Fri, 09 Oct 2009 22:12:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3735#comment-4382</guid>
		<description>&lt;b&gt;Cory&lt;/b&gt;, thank you for your comment.

Yes, both the affiliate/publisher and the merchant/advertiser want to (or is &lt;i&gt;must&lt;/i&gt; really a better verb?) have the disclosures/disclaimers. The affiliate - for the end users, while the merchant - for the affiliates.

While there &lt;i&gt;is&lt;/i&gt; some vagueness regarding the acceptable form to put it in (much is left by the FTC to the marketers&#039; discretion), I think the bigger problem is not this, but the monitoring/policing part. The burden of monitoring whether all affiliates who post reviews/testimonials have a proper disclosure on their site(s) has been put on the advertisers&#039; shoulders. One of the merchant&#039;s wrote to me today: &quot;We support compliance although this is going to be near impossible to monitor.&quot; I have a few ideas of how this may be implemented, but none are comprehensive enough; and I believe she is right -- it will be between difficult to impossible to monitor this effectively. Still thinking.</description>
		<content:encoded><![CDATA[<p><b>Cory</b>, thank you for your comment.</p>
<p>Yes, both the affiliate/publisher and the merchant/advertiser want to (or is <i>must</i> really a better verb?) have the disclosures/disclaimers. The affiliate &#8211; for the end users, while the merchant &#8211; for the affiliates.</p>
<p>While there <i>is</i> some vagueness regarding the acceptable form to put it in (much is left by the FTC to the marketers&#8217; discretion), I think the bigger problem is not this, but the monitoring/policing part. The burden of monitoring whether all affiliates who post reviews/testimonials have a proper disclosure on their site(s) has been put on the advertisers&#8217; shoulders. One of the merchant&#8217;s wrote to me today: &#8220;We support compliance although this is going to be near impossible to monitor.&#8221; I have a few ideas of how this may be implemented, but none are comprehensive enough; and I believe she is right &#8212; it will be between difficult to impossible to monitor this effectively. Still thinking.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cory Howell</title>
		<link>http://www.amnavigator.com/blog/2009/10/09/how-to-word-disclosures-agreements-to-meet-ftc-rules/comment-page-1/#comment-4381</link>
		<dc:creator>Cory Howell</dc:creator>
		<pubDate>Fri, 09 Oct 2009 21:53:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3735#comment-4381</guid>
		<description>This is a great breakdown for not only the affiliate, but also the advertiser and/or original merchants.

The need for a disclosure statement on an affiliate site is really a no-brainer - yes, you need to have one.  

The eye opening part, is that as a merchant or advertiser, you should have a disclaimer in your Terms of Service to prevent possible liability from your affiliates or partners (in case they mess up).

All of this is still pretty new, so hopefully the FTC will actually come out and specify what each party is required to show as proper disclosure.  At this time, it seems to be more of a guessing game.</description>
		<content:encoded><![CDATA[<p>This is a great breakdown for not only the affiliate, but also the advertiser and/or original merchants.</p>
<p>The need for a disclosure statement on an affiliate site is really a no-brainer &#8211; yes, you need to have one.  </p>
<p>The eye opening part, is that as a merchant or advertiser, you should have a disclaimer in your Terms of Service to prevent possible liability from your affiliates or partners (in case they mess up).</p>
<p>All of this is still pretty new, so hopefully the FTC will actually come out and specify what each party is required to show as proper disclosure.  At this time, it seems to be more of a guessing game.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
