Web X.0

Now that's not nice Google...

Google has apparently made a change to their ad placement formula. John Battelle has the details here:

"Under the new system, Google will change its eCPM calculation by using a CPC that is equal to, or less than, the advertiser’s max bid CPC. This change will result in increases to advertisers’ actual CPC paid when a CPC that is equal to or less than the advertiser’s max bid CPC generates an eCPM that exceeds the threshold eCPM required for north promotion...."

The language around this change is extremely washed out and even misleading, so the change sounds quite benign... But here's what's really going on...:

Google's auction system sorts ads by eCPM (or - effective cost per thousand ad impressions).  Yahoo's Panama and Quigo's AdSonar (disclosure: I'm founder of Quigo) do essentially the same.

These auction systems charge the advertiser 1c over the price needed to secure the highest possible placement (but of course, never over the advertiser's bid). This means that the advertiser can rest assured that the only thing affecting their actual cost-per-clicks are the real market forces - advertisers changing bids, other advertisers getting more clicks, etc.

What Google is now doing is sneaking secret reserve prices into their auction and artificially pushing advertiser bids up. Essentially this is rigging parts of the auction to Google's favor, without disclosing what the reserve prices are (I assume they are different per keyword).

This is a very slippery slope... there are a hundred hidden corners where artificial reserve prices can be snuck into the auction system and Google should be called out on shenanigans like this...

[UPDATE] - Google puts a great spin on this scheme, flipping it all into a wonderful improvement for the advertisers. Google advertisers, believe me - all this does is take more money from your pockets and puts it into Google's already overflowing pockets.

Graceful degradation

Seth Godin wrote about the recent tornado in Brooklyn:

"...Bottom line: the first thing to rehearse is your communication strategy. You can't predict weird events, but you can get really good at alerting people when they happen."

The web application parallel to this idea is - design for graceful degradation first.

Take it as an absolute given that your service is going to fail, and it will do so at the most unexpected times and places. No matter how great your code is, and how redundant your data center is, and how many thousands of man years QA spent bullet-proofing your system, and how your NOC guys are sitting in the cage and holding your server's hands 24/7 for good karma - take my word - your app will go down, guaranteed.

Once the software is written, it's very difficult to go back to existing code and find all the places where you might want to cover for possible outages. So the way to go is to get into the habit of designing wrapper codes that fail elegantly before *any* single piece of functionality is developed into those wrappers.

Gracefully degrading wrappers = a good night's sleep, which is priceless.

---

The author of this post loves the chocolate of these sponsors!:

Israel parade, Made in Japan

I have no idea what the context of this video is, but as an Israeli this is absolutely wild to see... As with cars and electronics, the Japanese make stuff that's superior to anyone else, and that seems to include parades now...

(thanks Ouriel!)