<?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: Twitter Hashtags for Affiliate Tweets</title>
	<atom:link href="http://www.amnavigator.com/blog/2009/10/07/twitter-hashtags-for-affiliate-tweets/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.amnavigator.com/blog/2009/10/07/twitter-hashtags-for-affiliate-tweets/</link>
	<description>Geno talks about affiliate marketing, leadership, etc</description>
	<lastBuildDate>Wed, 08 Feb 2012 00:14:20 +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/07/twitter-hashtags-for-affiliate-tweets/comment-page-1/#comment-4452</link>
		<dc:creator>Geno</dc:creator>
		<pubDate>Tue, 13 Oct 2009 13:31:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3675#comment-4452</guid>
		<description>&lt;a href=&quot;http://twitter.com/rictownsend&quot; rel=&quot;nofollow&quot;&gt;Ric Townsend&lt;/a&gt; has just tweeted about the &lt;a href=&quot;http://www.twittad.com/index.php?task=disclosure-policy&quot; rel=&quot;nofollow&quot;&gt;Twittad&#039;s disclosure policy&lt;/a&gt;. It does look like a good example of an overall campaign&#039;s/company&#039;s disclosure policy. Will it suffice for the FTC though (unless each tweet also has a link to the policy)? FTC is advising to either have it &quot;in proximity to blog&quot;/tweet, or to &quot;incorporate it into the blog discussion itself&quot; [&lt;a href=&quot;http://www.fastcompany.com/blog/jennifer-vilaga/slipstream/ftc-bloggers-its-not-medium-its-message-0&quot; rel=&quot;nofollow&quot;&gt;source&lt;/a&gt;]. Would going through the Spon.in url-shortening service meet one of these requirements (because spon.in does have the disclosure on their homepage)? It depends on how you look at it. Since the end user is never going to be clicking through to the homepage of Spon.in, but to the advertiser&#039;s landing page &quot;from Twittad.com&quot; at the end of each such tweet may not cut it (unless it starts with a &quot;www&quot; and links to Twittad&#039;s site).</description>
		<content:encoded><![CDATA[<p><a href="http://twitter.com/rictownsend" rel="nofollow">Ric Townsend</a> has just tweeted about the <a href="http://www.twittad.com/index.php?task=disclosure-policy" rel="nofollow">Twittad&#8217;s disclosure policy</a>. It does look like a good example of an overall campaign&#8217;s/company&#8217;s disclosure policy. Will it suffice for the FTC though (unless each tweet also has a link to the policy)? FTC is advising to either have it &#8220;in proximity to blog&#8221;/tweet, or to &#8220;incorporate it into the blog discussion itself&#8221; [<a href="http://www.fastcompany.com/blog/jennifer-vilaga/slipstream/ftc-bloggers-its-not-medium-its-message-0" rel="nofollow">source</a>]. Would going through the Spon.in url-shortening service meet one of these requirements (because spon.in does have the disclosure on their homepage)? It depends on how you look at it. Since the end user is never going to be clicking through to the homepage of Spon.in, but to the advertiser&#8217;s landing page &#8220;from Twittad.com&#8221; at the end of each such tweet may not cut it (unless it starts with a &#8220;www&#8221; and links to Twittad&#8217;s site).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geno</title>
		<link>http://www.amnavigator.com/blog/2009/10/07/twitter-hashtags-for-affiliate-tweets/comment-page-1/#comment-4311</link>
		<dc:creator>Geno</dc:creator>
		<pubDate>Wed, 07 Oct 2009 20:10:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3675#comment-4311</guid>
		<description>Any time, &lt;b&gt;Bryan&lt;/b&gt;. Glad to be of help.</description>
		<content:encoded><![CDATA[<p>Any time, <b>Bryan</b>. Glad to be of help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan</title>
		<link>http://www.amnavigator.com/blog/2009/10/07/twitter-hashtags-for-affiliate-tweets/comment-page-1/#comment-4310</link>
		<dc:creator>Bryan</dc:creator>
		<pubDate>Wed, 07 Oct 2009 20:07:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3675#comment-4310</guid>
		<description>Great examples. I particularly like Tim Carter&#039;s and will prob model off that. Thanks for the info!</description>
		<content:encoded><![CDATA[<p>Great examples. I particularly like Tim Carter&#8217;s and will prob model off that. Thanks for the info!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geno</title>
		<link>http://www.amnavigator.com/blog/2009/10/07/twitter-hashtags-for-affiliate-tweets/comment-page-1/#comment-4308</link>
		<dc:creator>Geno</dc:creator>
		<pubDate>Wed, 07 Oct 2009 19:59:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3675#comment-4308</guid>
		<description>I do not believe that at present time there is a clear understanding of how exactly this is to be handled on Twitter. Today&#039;s &lt;a href=&quot;http://www.msnbc.msn.com/id/33208950/ns/business-businessweekcom/&quot; rel=&quot;nofollow&quot;&gt;Business Week article&lt;/a&gt; references TwittAd&#039;s, Ad.ly&#039;s and IZEA&#039;s approaches.

&lt;blockquote&gt;These services meet the basic requirement of the new FTC guidelines: They ask users to include disclosures inside their &quot;tweets,&quot; such as &quot;Ad by Ad.ly.&quot; Twittad use several types of disclosure: Each Twitter publisher must post a badge on his or her page that says Twittad, links include the text &quot;spon.in&quot; -- meaning &quot;sponsorship in update&quot; -- and each time someone clicks on an ad they are shown a dropdown bar indicating they&#039;ve clicked on an advertisement.&lt;/blockquote&gt;

As far as blogs go, I believe one main disclosure per affiliate blog/website should be enough. &lt;a href=&quot;http://www.jangro.com/disclosure/&quot; rel=&quot;nofollow&quot;&gt;Scott Jangro&#039;s&lt;/a&gt;, &lt;a href=&quot;http://www.askthebuilder.com/Disclosure_Policy.shtml&quot; rel=&quot;nofollow&quot;&gt;Tim Carter&#039;s&lt;/a&gt; and &lt;a href=&quot;http://www.likeawarmcupofcoffee.com/home/?p=1513&quot; rel=&quot;nofollow&quot;&gt;Sarah Mae&#039;s&lt;/a&gt; examples can be helpful in crafting your own.</description>
		<content:encoded><![CDATA[<p>I do not believe that at present time there is a clear understanding of how exactly this is to be handled on Twitter. Today&#8217;s <a href="http://www.msnbc.msn.com/id/33208950/ns/business-businessweekcom/" rel="nofollow">Business Week article</a> references TwittAd&#8217;s, Ad.ly&#8217;s and IZEA&#8217;s approaches.</p>
<blockquote><p>These services meet the basic requirement of the new FTC guidelines: They ask users to include disclosures inside their &#8220;tweets,&#8221; such as &#8220;Ad by Ad.ly.&#8221; Twittad use several types of disclosure: Each Twitter publisher must post a badge on his or her page that says Twittad, links include the text &#8220;spon.in&#8221; &#8212; meaning &#8220;sponsorship in update&#8221; &#8212; and each time someone clicks on an ad they are shown a dropdown bar indicating they&#8217;ve clicked on an advertisement.</p></blockquote>
<p>As far as blogs go, I believe one main disclosure per affiliate blog/website should be enough. <a href="http://www.jangro.com/disclosure/" rel="nofollow">Scott Jangro&#8217;s</a>, <a href="http://www.askthebuilder.com/Disclosure_Policy.shtml" rel="nofollow">Tim Carter&#8217;s</a> and <a href="http://www.likeawarmcupofcoffee.com/home/?p=1513" rel="nofollow">Sarah Mae&#8217;s</a> examples can be helpful in crafting your own.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bryan</title>
		<link>http://www.amnavigator.com/blog/2009/10/07/twitter-hashtags-for-affiliate-tweets/comment-page-1/#comment-4306</link>
		<dc:creator>Bryan</dc:creator>
		<pubDate>Wed, 07 Oct 2009 19:19:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3675#comment-4306</guid>
		<description>I just read about the new FTC guidelines yesterday. Interesting to see how it will be addressed on Twitter. Geno, in terms of its impact on blogs, do you think the disclosure has to on each post or can it just be embedded on one page of the site? I also used the disclosure policy generator, very helpful!</description>
		<content:encoded><![CDATA[<p>I just read about the new FTC guidelines yesterday. Interesting to see how it will be addressed on Twitter. Geno, in terms of its impact on blogs, do you think the disclosure has to on each post or can it just be embedded on one page of the site? I also used the disclosure policy generator, very helpful!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geno</title>
		<link>http://www.amnavigator.com/blog/2009/10/07/twitter-hashtags-for-affiliate-tweets/comment-page-1/#comment-4299</link>
		<dc:creator>Geno</dc:creator>
		<pubDate>Wed, 07 Oct 2009 16:41:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3675#comment-4299</guid>
		<description>&lt;b&gt;Joel&lt;/b&gt;, thanks for chiming in. I love that &lt;a href=&quot;http://disclosurepolicy.org/&quot; rel=&quot;nofollow&quot;&gt;Disclosure Policy Generator&lt;/a&gt; by IZEA. Thanks for the link.

Will posting a link to a disclosure page in the Twitter profile suffice? I don&#039;t know. It may be that the full disclosure must be linked to from the profile, but each tweet should still have some kind of indication that it is a sponsored one. I think they will deem each tweet a separate blog (or microblog) post.</description>
		<content:encoded><![CDATA[<p><b>Joel</b>, thanks for chiming in. I love that <a href="http://disclosurepolicy.org/" rel="nofollow">Disclosure Policy Generator</a> by IZEA. Thanks for the link.</p>
<p>Will posting a link to a disclosure page in the Twitter profile suffice? I don&#8217;t know. It may be that the full disclosure must be linked to from the profile, but each tweet should still have some kind of indication that it is a sponsored one. I think they will deem each tweet a separate blog (or microblog) post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel Garcia</title>
		<link>http://www.amnavigator.com/blog/2009/10/07/twitter-hashtags-for-affiliate-tweets/comment-page-1/#comment-4298</link>
		<dc:creator>Joel Garcia</dc:creator>
		<pubDate>Wed, 07 Oct 2009 16:26:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3675#comment-4298</guid>
		<description>Is this something that can be handled by adding disclosure language to an existing policy page of a website or making use of a service like &lt;a href=&quot;http://disclosurepolicy.org&quot; rel=&quot;nofollow&quot;&gt;DisclosurePolicy.org&lt;/a&gt; to create a page of disclosure? If so, why not post a link in your Twitter profile to a disclosure page?

I appreciate the PCWorld.com suggestion that it is good policy to state you&#039;ve received a reviewed item for free, but a separate disclosure page would be a great addition and possibly cover other marketing efforts.</description>
		<content:encoded><![CDATA[<p>Is this something that can be handled by adding disclosure language to an existing policy page of a website or making use of a service like <a href="http://disclosurepolicy.org" rel="nofollow">DisclosurePolicy.org</a> to create a page of disclosure? If so, why not post a link in your Twitter profile to a disclosure page?</p>
<p>I appreciate the PCWorld.com suggestion that it is good policy to state you&#8217;ve received a reviewed item for free, but a separate disclosure page would be a great addition and possibly cover other marketing efforts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Geno</title>
		<link>http://www.amnavigator.com/blog/2009/10/07/twitter-hashtags-for-affiliate-tweets/comment-page-1/#comment-4297</link>
		<dc:creator>Geno</dc:creator>
		<pubDate>Wed, 07 Oct 2009 15:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3675#comment-4297</guid>
		<description>It does, but I wonder if it will be sufficient in the FTC&#039;s eyes.</description>
		<content:encoded><![CDATA[<p>It does, but I wonder if it will be sufficient in the FTC&#8217;s eyes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn Collins</title>
		<link>http://www.amnavigator.com/blog/2009/10/07/twitter-hashtags-for-affiliate-tweets/comment-page-1/#comment-4295</link>
		<dc:creator>Shawn Collins</dc:creator>
		<pubDate>Wed, 07 Oct 2009 15:46:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.amnavigator.com/blog/?p=3675#comment-4295</guid>
		<description>I&#039;ve seen #ad used - if it&#039;s necessary to use one, I think that would be ideal, since it communicates it effectively and uses a minimal amount of characters.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve seen #ad used &#8211; if it&#8217;s necessary to use one, I think that would be ideal, since it communicates it effectively and uses a minimal amount of characters.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

