RKG Logo 434-978-4300

An open letter to Google on their recent changes to the Adwords API terms and conditions:

Subject: RKG: feedback on T&C changes

Hi Google Folks —

Several weeks ago xxx and xxx walked us through the upcoming changes to the Google API T&Cs and asked for feedback.

Given how we use the API today and how we plan to use it in the future, the most relevant T&C change to our company is the new API usage fee of the 25c per 1000 operations.

We agree the API shouldn’t be entirely free – zero cost leads to resource squandering, the “tragedy of the commons”.

Rather than charge for every unit, we favor the current system, where API users receive an appropriate included number of units based on ad spend, with the option to purchase more as needed.

An airline ticket comes bundled with permission to bring two standard pieces of luggage — travelers needing more bags or weight can pay for it. By this policy, the airline offers a strong suggestion to the appropriate amount of luggage to bring on a trip.

By granting API users an appropriate included quota, with an option to buy more, Google sends a strong message as to the recommended number of API calls per month per dollar of advertising. This implicit message is powerful and important guidance.

Charging for every unit could encourage less sophisticated advertisers to reduce their usage too severely, yielding reduced advertising efficiency, which in the long run hurts the advertiser and thus Google.

Regardless of the structure of the fee, we strongly suggest Google tunes the fee to cover its marginal costs of providing API calls, rather than treat the API fees as profit center. Google wins when advertisers buy more ads, and advertisers buy more ads when those ads work, and ads work when advertisers use the bidding platform intelligently and appropriately.

Our hunch is the 25c per 1000 rate turns the API into a profit center, rather than simply covering costs. Lower this rate — encourage advertisers to bid smarter — in turn, they’ll buy more advertising.

Finally, we suggest that Google adopt a fair and uniform API fee formula across all advertisers: agency or in-house, home-brew or commercial tool, partner or non-partner, large or small account. When a web company becomes a dominant market unto itself, it comes under public and regulatory scrutiny to provide a level playing field for market participants. (For example, to the best of our knowledge, all EBay sellers pay the same listing fees and commissions, regardless of their annual gross merchandise sales.)

To summarize:

  1. Agree: charge for API over-use
  2. Provide an included reasonable usage number of quota units based on spend
  3. Price the API to cover costs, not run as a profit center
  4. Uniform and public API pricing for all API users

Thanks for soliciting our opinion on these changes.

Technorati Tags: , ,

If you like this post, consider subscribing to our RSS feed. You can also have new posts sent to you via email.


Related Posts

    No related posts.

Comments

  1. David Rodecker, January 23, 2008:

    APIs are a designed to streamline and automate user interfaces. We are encouraged to implement APIs to reduce errors, provide dynamic system integration and reduce resource overhead. The Google API charges, though initially a modest cost, do add up.

    On the surface, the Google API cost can be justified. If you consider that their advertising marketplace is an organic, market driven machine; any overhead costs should probably be isolated so as to not disrupt that equilibrium.

    Being that the Adwords user interface is free to use; it is an unfair disposition for API users. The proposal of imposing limits and penalties for over-usage makes sense in principle; however, the devil is in the details. Creating a cost and quota structure that is defensible and long-term sustainable is challenging.

    Amazons Web API’s are a great model to follow. They have done a great effort to reducing everything down to a cost per CPU hour.

Your Comment

Tags

RKG Tags: , ,

Technorati Tags: , ,

Trackback

http://www.rimmkaufman.com/rkgblog/2006/04/18/google-api-usage-fees/trackback/

Email Updates

Categories

Recent Comments

  • Mark Ballard: Cory, I don’t see this as an SEO v. PPC issue. The core of my argument is that CTRs are lower primarily due to misleading...
  • Cory Grassell: What are your thoughts on stats that suggest consumers are more apt to click on organic search results than PPC results? As a...
  • George Michie: Kevin, Marc, thanks for your comments. Help is coming, but not the solution. There are a number of instances when the CTR on the...
  • Marc Adelman: George, You have been an advocate of “the advanced control option” for years now. Depressing right YEARS! Eh…listen...
  • Kevin Hill: Is what they really need is a fourth match type. Here’s google’s help documentation on broad match: This is the default...
  • Kevin Micalizzi, Dimdim Web Conferencing: Jim (& George)- We still offer a free version of Dimdim. Just click Sign Up Now at the top of the...
  • Tomas: indeed, i can’t talk about it either… :)
  • Philip Price: Thank you for the RegHack, it worked for me, tho at first when i made the reg file with the information i copied from above i also...
  • George Michie: Sorry Jim, this post was written in 2007. Apparently some of those products are gone.
  • Jim: Hey, I checked two products like dimdim and cutepdf but none is free. What are you talking about free and open source?
  • George Michie: If they keep hearing the same message, and seeing evidence in the data to back it up, something will have to give. There is hope on...
  • Tomas: I’ve been having the same argument with Google for months now and in the end there does seem to be a feature in the algorithm that...
  • George Michie: Doesn’t have to be, it can be intra-adgroup as well.
  • Josh: George – I take it you’re referencing a scenario where your exact-match keywords are not listed as negative exact match keywords...
  • George Michie: Melissa, you’re right, it’s always happened to varying degrees, particularly since the advent of extended broad match....

Blog Stats

  • Posts: 948
  • Words: 451,089
  • Comments: 2,877

Administration