<?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: The importance of using the correct tool id</title>
	<atom:link href="http://www.ebaypartnernetworkblog.com/en/news/the-importance-of-using-the-correct-tool-id/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ebaypartnernetworkblog.com/en/news/the-importance-of-using-the-correct-tool-id/</link>
	<description>The eBay Partner Network Blog Keeps You Up To Date With the eBay Affiliate Program</description>
	<lastBuildDate>Fri, 30 Jul 2010 10:08:23 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: AuctionCloud</title>
		<link>http://www.ebaypartnernetworkblog.com/en/news/the-importance-of-using-the-correct-tool-id/comment-page-1/#comment-2187</link>
		<dc:creator>AuctionCloud</dc:creator>
		<pubDate>Sat, 14 Nov 2009 04:41:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.ebaypartnernetworkblog.com/en/?p=1611#comment-2187</guid>
		<description>We&#039;re in the same boat and using 10001 as the tool ID for all our dynamically generated rover links. There is enough other IDs to keep track of (e.g. Campaign IDs, Category IDs, etc.).</description>
		<content:encoded><![CDATA[<p>We&#8217;re in the same boat and using 10001 as the tool ID for all our dynamically generated rover links. There is enough other IDs to keep track of (e.g. Campaign IDs, Category IDs, etc.).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tuan</title>
		<link>http://www.ebaypartnernetworkblog.com/en/news/the-importance-of-using-the-correct-tool-id/comment-page-1/#comment-2185</link>
		<dc:creator>Tuan</dc:creator>
		<pubDate>Fri, 13 Nov 2009 23:48:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.ebaypartnernetworkblog.com/en/?p=1611#comment-2185</guid>
		<description>I&#039;m ok with using different Tool ID for different calls and will code it in over the next week,

Just need an ID for GetItem on the trading services side.

Tuan</description>
		<content:encoded><![CDATA[<p>I&#8217;m ok with using different Tool ID for different calls and will code it in over the next week,</p>
<p>Just need an ID for GetItem on the trading services side.</p>
<p>Tuan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://www.ebaypartnernetworkblog.com/en/news/the-importance-of-using-the-correct-tool-id/comment-page-1/#comment-2171</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Fri, 13 Nov 2009 10:20:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.ebaypartnernetworkblog.com/en/?p=1611#comment-2171</guid>
		<description>Agree with all of the above, currently using 10001 for the tool Id, due to previous issues with API</description>
		<content:encoded><![CDATA[<p>Agree with all of the above, currently using 10001 for the tool Id, due to previous issues with API</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julia</title>
		<link>http://www.ebaypartnernetworkblog.com/en/news/the-importance-of-using-the-correct-tool-id/comment-page-1/#comment-2170</link>
		<dc:creator>Julia</dc:creator>
		<pubDate>Fri, 13 Nov 2009 09:11:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.ebaypartnernetworkblog.com/en/?p=1611#comment-2170</guid>
		<description>Hi all,

Thanks for all the comments so far - they&#039;re really going to help us,  Keep them coming!

Julia</description>
		<content:encoded><![CDATA[<p>Hi all,</p>
<p>Thanks for all the comments so far &#8211; they&#8217;re really going to help us,  Keep them coming!</p>
<p>Julia</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Binary Factory</title>
		<link>http://www.ebaypartnernetworkblog.com/en/news/the-importance-of-using-the-correct-tool-id/comment-page-1/#comment-2167</link>
		<dc:creator>Binary Factory</dc:creator>
		<pubDate>Fri, 13 Nov 2009 04:04:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.ebaypartnernetworkblog.com/en/?p=1611#comment-2167</guid>
		<description>I agree with Michelle. We also use the 10001 for the tool ID because of past known issues where the API was not returning the proper rover link (typically missing all together).</description>
		<content:encoded><![CDATA[<p>I agree with Michelle. We also use the 10001 for the tool ID because of past known issues where the API was not returning the proper rover link (typically missing all together).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ty</title>
		<link>http://www.ebaypartnernetworkblog.com/en/news/the-importance-of-using-the-correct-tool-id/comment-page-1/#comment-2165</link>
		<dc:creator>Ty</dc:creator>
		<pubDate>Fri, 13 Nov 2009 01:45:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.ebaypartnernetworkblog.com/en/?p=1611#comment-2165</guid>
		<description>I third the above suggestion. Otherwise, I need the ID for GetItem from the Trading API. 

Ty</description>
		<content:encoded><![CDATA[<p>I third the above suggestion. Otherwise, I need the ID for GetItem from the Trading API. </p>
<p>Ty</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: helios825</title>
		<link>http://www.ebaypartnernetworkblog.com/en/news/the-importance-of-using-the-correct-tool-id/comment-page-1/#comment-2164</link>
		<dc:creator>helios825</dc:creator>
		<pubDate>Thu, 12 Nov 2009 19:55:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.ebaypartnernetworkblog.com/en/?p=1611#comment-2164</guid>
		<description>Yes, I&#039;m in the same boat as the situation in the ~last paragraph, where I dynamically create links using scripts and the API (on the ePN forums we usually call this practice &quot;rolling your own&quot; links :) , and usually I&#039;ve chosen ToolID=10001 for said links since it seemed the &quot;closest&quot; ID for my situation. I agree that having a separate Custom Tool ID, as you suggest, would fit that use case well.

-h</description>
		<content:encoded><![CDATA[<p>Yes, I&#8217;m in the same boat as the situation in the ~last paragraph, where I dynamically create links using scripts and the API (on the ePN forums we usually call this practice &#8220;rolling your own&#8221; links <img src='http://www.ebaypartnernetworkblog.com/en/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  , and usually I&#8217;ve chosen ToolID=10001 for said links since it seemed the &#8220;closest&#8221; ID for my situation. I agree that having a separate Custom Tool ID, as you suggest, would fit that use case well.</p>
<p>-h</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michelle</title>
		<link>http://www.ebaypartnernetworkblog.com/en/news/the-importance-of-using-the-correct-tool-id/comment-page-1/#comment-2163</link>
		<dc:creator>Michelle</dc:creator>
		<pubDate>Thu, 12 Nov 2009 19:07:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.ebaypartnernetworkblog.com/en/?p=1611#comment-2163</guid>
		<description>I&#039;d like to have a generic custom ID for the API.  

I use 6-7 API calls and currently use 10001 in all of my rover links because that&#039;s what I picked up from the creatives page.

We build our own rover links instead of using the rover links in the API response to reduce errors.  There have been many document instances of missing rover info in the API response.  

Also, one generic custom tool ID is better than many IDs because it reduces the chance of error.  We already have enough complexity with geo targeting, setting the right campaign ID and setting the custom ID.   

Thanks, 

Michelle</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to have a generic custom ID for the API.  </p>
<p>I use 6-7 API calls and currently use 10001 in all of my rover links because that&#8217;s what I picked up from the creatives page.</p>
<p>We build our own rover links instead of using the rover links in the API response to reduce errors.  There have been many document instances of missing rover info in the API response.  </p>
<p>Also, one generic custom tool ID is better than many IDs because it reduces the chance of error.  We already have enough complexity with geo targeting, setting the right campaign ID and setting the custom ID.   </p>
<p>Thanks, </p>
<p>Michelle</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe R</title>
		<link>http://www.ebaypartnernetworkblog.com/en/news/the-importance-of-using-the-correct-tool-id/comment-page-1/#comment-2162</link>
		<dc:creator>Joe R</dc:creator>
		<pubDate>Thu, 12 Nov 2009 18:00:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.ebaypartnernetworkblog.com/en/?p=1611#comment-2162</guid>
		<description>I have used the Impression Pixel generator for my BANS site and have added the code to the footer. I have selected RSS because BANS shows RSS feeds.  The pages in this site also use and Editor Kit and some custom banners. Therefore, three different tools on one page.

Will the image pixel mess up the stats and reports?  Should I keep it, remove it?
</description>
		<content:encoded><![CDATA[<p>I have used the Impression Pixel generator for my BANS site and have added the code to the footer. I have selected RSS because BANS shows RSS feeds.  The pages in this site also use and Editor Kit and some custom banners. Therefore, three different tools on one page.</p>
<p>Will the image pixel mess up the stats and reports?  Should I keep it, remove it?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
