<?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 Google API kerfuffle, and what it means for startups</title>
	<atom:link href="http://venturebeat.com/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/feed/" rel="self" type="application/rss+xml" />
	<link>http://venturebeat.com/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/</link>
	<description>News About Tech, Money and Innovation</description>
	<lastBuildDate>Wed, 25 Nov 2009 02:43:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Google AdWords API - why charging is a bad idea &#124; Merjis Search Marketing Blog</title>
		<link>http://venturebeat.com/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/comment-page-1/#comment-111917</link>
		<dc:creator>Google AdWords API - why charging is a bad idea &#124; Merjis Search Marketing Blog</dc:creator>
		<pubDate>Sun, 06 May 2007 19:07:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.venturebeat.com/contributors/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/#comment-111917</guid>
		<description>[...] Minor tweaks, reflecting the VentureBeat article. [...]</description>
		<content:encoded><![CDATA[<p>[...] Minor tweaks, reflecting the VentureBeat article. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google, Disintermediation and Agencies &#124; Merjis Search Marketing Blog</title>
		<link>http://venturebeat.com/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/comment-page-1/#comment-111889</link>
		<dc:creator>Google, Disintermediation and Agencies &#124; Merjis Search Marketing Blog</dc:creator>
		<pubDate>Sun, 06 May 2007 18:58:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.venturebeat.com/contributors/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/#comment-111889</guid>
		<description>[...] showed up some slow burning questioning over the effect of AdWords API fees on VentureBeat&#8217;s blog that I&#8217;d not clocked - it was in the period when my ADSL was barely functioning at all. It [...]</description>
		<content:encoded><![CDATA[<p>[...] showed up some slow burning questioning over the effect of AdWords API fees on VentureBeat&#8217;s blog that I&#8217;d not clocked &#8211; it was in the period when my ADSL was barely functioning at all. It [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve&#8217;s Weblog &#187; Blog Archive &#187; Google as a developer platform</title>
		<link>http://venturebeat.com/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/comment-page-1/#comment-17159</link>
		<dc:creator>Steve&#8217;s Weblog &#187; Blog Archive &#187; Google as a developer platform</dc:creator>
		<pubDate>Thu, 11 Jan 2007 16:42:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.venturebeat.com/contributors/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/#comment-17159</guid>
		<description>[...] Venture beat, a VC blog, has a post on the riskyness of startups using Google as a platform. Google recently removed new access to their SOAP API which allowed developers to have an application which talked to the search engine. Canceling APIs will not breed any sort of loyalty and will make creating applications which use Google services more risky. [...]</description>
		<content:encoded><![CDATA[<p>[...] Venture beat, a VC blog, has a post on the riskyness of startups using Google as a platform. Google recently removed new access to their SOAP API which allowed developers to have an application which talked to the search engine. Canceling APIs will not breed any sort of loyalty and will make creating applications which use Google services more risky. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ProgrammableWeb.com &#187; Blog Archive &#187; The Google API Controversies</title>
		<link>http://venturebeat.com/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/comment-page-1/#comment-17154</link>
		<dc:creator>ProgrammableWeb.com &#187; Blog Archive &#187; The Google API Controversies</dc:creator>
		<pubDate>Wed, 10 Jan 2007 19:53:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.venturebeat.com/contributors/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/#comment-17154</guid>
		<description>[...] Ron Drabkin gives an excellent summary of the AdWords issue over in VentureBeat&#8217;s The Google API kerfuffle, and what it means for start-ups. The primary debate isn&#8217;t over whether charging for the API is warranted but more specifically what sort of pricing model meets the needs of the provider and third parties as well as what implications does this have for Google&#8217;s other APIs. Ron&#8217;s company, Adisem, is one of a number of startups building applications on Google&#8217;s APIs and one of things he highlights is some complex pricing model.   Going forward, however, the new API expense could prevent startups and established companies from offering many services based on the AdWords API. In addition, several ad agencies have also decided to scale back or eliminate API efforts, since they find it less costly for them to hire analysts, usually in India, to crunch numbers on large spreadsheets&#8230;The structure of the API fees will also significantly impact several areas of the software industry. Since API cost scales with frequency of access, there are very negative implications to companies who would like to use Google data in a real time web analytics platform. Given that Google offers a free low end analytics tool, could this be a hint that Google will be targeting higher end web analytics in the future? [...]</description>
		<content:encoded><![CDATA[<p>[...] Ron Drabkin gives an excellent summary of the AdWords issue over in VentureBeat&#8217;s The Google API kerfuffle, and what it means for start-ups. The primary debate isn&#8217;t over whether charging for the API is warranted but more specifically what sort of pricing model meets the needs of the provider and third parties as well as what implications does this have for Google&#8217;s other APIs. Ron&#8217;s company, Adisem, is one of a number of startups building applications on Google&#8217;s APIs and one of things he highlights is some complex pricing model.   Going forward, however, the new API expense could prevent startups and established companies from offering many services based on the AdWords API. In addition, several ad agencies have also decided to scale back or eliminate API efforts, since they find it less costly for them to hire analysts, usually in India, to crunch numbers on large spreadsheets&#8230;The structure of the API fees will also significantly impact several areas of the software industry. Since API cost scales with frequency of access, there are very negative implications to companies who would like to use Google data in a real time web analytics platform. Given that Google offers a free low end analytics tool, could this be a hint that Google will be targeting higher end web analytics in the future? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Search Engine Optimization &#187; Blog Archive &#187; Google now charging for Adwords API</title>
		<link>http://venturebeat.com/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/comment-page-1/#comment-17148</link>
		<dc:creator>Search Engine Optimization &#187; Blog Archive &#187; Google now charging for Adwords API</dc:creator>
		<pubDate>Tue, 09 Jan 2007 15:08:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.venturebeat.com/contributors/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/#comment-17148</guid>
		<description>[...] Here are the details of Google Adwords API charge. [...]</description>
		<content:encoded><![CDATA[<p>[...] Here are the details of Google Adwords API charge. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Goodman</title>
		<link>http://venturebeat.com/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/comment-page-1/#comment-17136</link>
		<dc:creator>Andrew Goodman</dc:creator>
		<pubDate>Sun, 07 Jan 2007 17:41:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.venturebeat.com/contributors/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/#comment-17136</guid>
		<description>Re: &quot;trusting Google&#039;s broad match&quot;.

Chris, you left out phrase match. There&#039;s not as much need for trust there as I would assume that it works as billed.</description>
		<content:encoded><![CDATA[<p>Re: &#8220;trusting Google&#8217;s broad match&#8221;.</p>
<p>Chris, you left out phrase match. There&#8217;s not as much need for trust there as I would assume that it works as billed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: webprofessor</title>
		<link>http://venturebeat.com/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/comment-page-1/#comment-17117</link>
		<dc:creator>webprofessor</dc:creator>
		<pubDate>Fri, 05 Jan 2007 17:04:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.venturebeat.com/contributors/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/#comment-17117</guid>
		<description>Basing part of your business off of free tools of obvious value and not expecting that somewhere down the line that the free part might get scribbled out is short sighted.

I personally welcome the change. When the API first came out I worried that every one and there brother would be able to generate long tail campaigns. Not that the API is no longer free the value of having internal tools has increased.</description>
		<content:encoded><![CDATA[<p>Basing part of your business off of free tools of obvious value and not expecting that somewhere down the line that the free part might get scribbled out is short sighted.</p>
<p>I personally welcome the change. When the API first came out I worried that every one and there brother would be able to generate long tail campaigns. Not that the API is no longer free the value of having internal tools has increased.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eWhisper</title>
		<link>http://venturebeat.com/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/comment-page-1/#comment-17076</link>
		<dc:creator>eWhisper</dc:creator>
		<pubDate>Fri, 29 Dec 2006 18:48:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.venturebeat.com/contributors/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/#comment-17076</guid>
		<description>Google seems to be dividing the API users into &#039;platforms&#039; and &#039;customers&#039;.

Customers who develop the API for their own spend may not incur all of the costs than an agency or platform does. 

Platforms and agencies are stuck with all of the costs regardless of their acting on behalf of a customer.

The effect on this is that small businesses who rely on more technical 3rd party tools or agencies are being hurt by this decision.

The SEM growth is small businesses - it&#039;s really unclear why Google is isolating them.</description>
		<content:encoded><![CDATA[<p>Google seems to be dividing the API users into &#8216;platforms&#8217; and &#8216;customers&#8217;.</p>
<p>Customers who develop the API for their own spend may not incur all of the costs than an agency or platform does. </p>
<p>Platforms and agencies are stuck with all of the costs regardless of their acting on behalf of a customer.</p>
<p>The effect on this is that small businesses who rely on more technical 3rd party tools or agencies are being hurt by this decision.</p>
<p>The SEM growth is small businesses &#8211; it&#8217;s really unclear why Google is isolating them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack</title>
		<link>http://venturebeat.com/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/comment-page-1/#comment-17074</link>
		<dc:creator>Jack</dc:creator>
		<pubDate>Sun, 24 Dec 2006 16:49:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.venturebeat.com/contributors/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/#comment-17074</guid>
		<description>It doesn&#039;t matter what&#039;s &quot;available&quot; or not available...if there&#039;s demand to use google&#039;s results (or anyone else&#039;s) somebody will figure it out...take http://www.srchr.com for example.</description>
		<content:encoded><![CDATA[<p>It doesn&#8217;t matter what&#8217;s &#8220;available&#8221; or not available&#8230;if there&#8217;s demand to use google&#8217;s results (or anyone else&#8217;s) somebody will figure it out&#8230;take <a href="http://www.srchr.com" rel="nofollow">http://www.srchr.com</a> for example.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D G</title>
		<link>http://venturebeat.com/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/comment-page-1/#comment-17073</link>
		<dc:creator>D G</dc:creator>
		<pubDate>Sat, 23 Dec 2006 18:48:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.venturebeat.com/contributors/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/#comment-17073</guid>
		<description>Parasite should be taxed at least if they live well off the host. API to internal addresses integration and interoperability; to external, it meant bait and potential revenue stream.</description>
		<content:encoded><![CDATA[<p>Parasite should be taxed at least if they live well off the host. API to internal addresses integration and interoperability; to external, it meant bait and potential revenue stream.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ::::renaissance chambara:::: &#187; Blog Archive &#187; Google&#8217;s APIron curtain</title>
		<link>http://venturebeat.com/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/comment-page-1/#comment-17072</link>
		<dc:creator>::::renaissance chambara:::: &#187; Blog Archive &#187; Google&#8217;s APIron curtain</dc:creator>
		<pubDate>Sat, 23 Dec 2006 17:13:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.venturebeat.com/contributors/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/#comment-17072</guid>
		<description>[...] VentureBeat have a good analysis piece: The Google API kerfuffle, and what it means for start-ups on what Google charging for its AdWord API is. [...]</description>
		<content:encoded><![CDATA[<p>[...] VentureBeat have a good analysis piece: The Google API kerfuffle, and what it means for start-ups on what Google charging for its AdWord API is. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Zaharias</title>
		<link>http://venturebeat.com/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/comment-page-1/#comment-17071</link>
		<dc:creator>Chris Zaharias</dc:creator>
		<pubDate>Sat, 23 Dec 2006 16:33:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.venturebeat.com/contributors/2006/12/22/the-google-api-kerfuffle-and-what-it-means-for-start-ups/#comment-17071</guid>
		<description>I&#039;m glad Google&#039;s charging for AdWords API access; that&#039;ll keep VC&#039;s from pumping even more dumb money into the search mgmt space than is there already.  You&#039;re right, though, in that Google is hurting their advertisers.  They would rather advertisers trust G&#039;s broad matching than let the advertiser do the targeting themselves via Exact Match.</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad Google&#8217;s charging for AdWords API access; that&#8217;ll keep VC&#8217;s from pumping even more dumb money into the search mgmt space than is there already.  You&#8217;re right, though, in that Google is hurting their advertisers.  They would rather advertisers trust G&#8217;s broad matching than let the advertiser do the targeting themselves via Exact Match.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
