Thursday, 20 July 2006
Stocking up
A few months ago we launched Google Finance. Since then, we've listened carefully to your feedback and learned a lot about what you like and what you don't like about our product. And in response to these requests, we're pleased to announce a few small new features, including a stock-market module on the business section of Google News and support for multiple portfolios. We've also added an auto-suggest feature to the search box to help you find the companies and funds you're searching for more quickly, as well as an auto-refresh feature that keeps the data on your portfolio page current. In addition, rumor has it that a lot of users like to have the choice of reading message boards in reverse chronological order. So we've made sure our discussion groups have that feature, too. Lastly, it's earnings season, and we've been impressed by a small company called SeekingAlpha that offers free transcripts on many earnings calls, so we've added links to them.
These are small steps, and you can expect to see more features and ideas from us in the coming months. We appreciate your feedback and hope you'll continue to push us to make Google Finance better.
Friday, 14 July 2006
"Let click fraud happen"? Uh, no.
Posted by Shuman Ghosemajumder, Business Product Manager for Trust & Safety
You may have seen some of the media coverage generated by a blogger's quoting Eric Schmidt about click fraud. By using select excerpts and ignoring the context of the remarks, that blog post made for an interesting read, but was unfortunately misleading.
Eric spoke at a SIEPR economics event at Stanford in March. At the end of his remarks he took questions. (You can view the whole presentation and Q&A that followed here.)
Here's the relevant question Eric was asked about click fraud: "Recently there’s been some talk about click fraud being a potential threat to the entire advertising business model. I was just wondering what your thoughts on that were and if there’s an economic solution to it more than just technical solutions."
Eric made clear from the very beginning that he wasn't describing our approach to click fraud and was answering hypothetically. He introduced his answer by saying: "Let’s imagine for purposes of argument that click fraud were not policed by Google and it were rampant ..."
The "let it happen" excerpt followed, in which he discusses the economic forces that can retard click fraud: "Eventually the price that the advertiser is willing to pay for the conversion will decline because the advertiser will realize that these are bad clicks. In other words, the value of the ad declines. So, over some amount of time, the system is, in fact, self-correcting. In fact, there is a perfect economic solution, which is to let it happen."
But he made clear that we don't take that approach, by adding that click fraud is "a bad thing and because we don’t like it, and because it does, at least for the short-term, creates some problems before the advertiser sees it, we go ahead and try to detect it and eliminate it." He also said, "In Google's case, we worry about this a lot and we have a number of technical engineers who think that this is great fun to try to go ahead of this and get ahead of it."
The fact is that Google strives to detect every invalid click that passes through its system, and to prevent those clicks from ever reaching an advertiser's account. And Eric and many others at Google have discussed the problem of invalid clicks publicly many times -- on our quarterly earnings calls, at our Press Day, and in other places, such as blogs. Anyone who has followed Google knows that Eric, and others at Google, have stated several times that Google fights invalid clicks, that we've devoted significant resources to manage it, and that we take it very seriously.
Update: Added link to the original story.
You may have seen some of the media coverage generated by a blogger's quoting Eric Schmidt about click fraud. By using select excerpts and ignoring the context of the remarks, that blog post made for an interesting read, but was unfortunately misleading.
Eric spoke at a SIEPR economics event at Stanford in March. At the end of his remarks he took questions. (You can view the whole presentation and Q&A that followed here.)
Here's the relevant question Eric was asked about click fraud: "Recently there’s been some talk about click fraud being a potential threat to the entire advertising business model. I was just wondering what your thoughts on that were and if there’s an economic solution to it more than just technical solutions."
Eric made clear from the very beginning that he wasn't describing our approach to click fraud and was answering hypothetically. He introduced his answer by saying: "Let’s imagine for purposes of argument that click fraud were not policed by Google and it were rampant ..."
The "let it happen" excerpt followed, in which he discusses the economic forces that can retard click fraud: "Eventually the price that the advertiser is willing to pay for the conversion will decline because the advertiser will realize that these are bad clicks. In other words, the value of the ad declines. So, over some amount of time, the system is, in fact, self-correcting. In fact, there is a perfect economic solution, which is to let it happen."
But he made clear that we don't take that approach, by adding that click fraud is "a bad thing and because we don’t like it, and because it does, at least for the short-term, creates some problems before the advertiser sees it, we go ahead and try to detect it and eliminate it." He also said, "In Google's case, we worry about this a lot and we have a number of technical engineers who think that this is great fun to try to go ahead of this and get ahead of it."
The fact is that Google strives to detect every invalid click that passes through its system, and to prevent those clicks from ever reaching an advertiser's account. And Eric and many others at Google have discussed the problem of invalid clicks publicly many times -- on our quarterly earnings calls, at our Press Day, and in other places, such as blogs. Anyone who has followed Google knows that Eric, and others at Google, have stated several times that Google fights invalid clicks, that we've devoted significant resources to manage it, and that we take it very seriously.
Update: Added link to the original story.
Thursday, 6 July 2006
Code Jamming in Dublin
Posted by Jeanne Williams and Anne Driscoll, Staffing Programs Team
On June 29th, Google Dublin hosted the onsite finals for Code Jam Europe 2006. This is the third of four code competitions slated for this year, with China in January, India in April and a Global Code Jam this fall.
After nearly 10,000 registrants and three intense online rounds, the top 50 finalists persevered and flew to Dublin for the final challenge. ACM members also joined the coding community fun, traveling from countries as far afield as Kazakhstan, Russia, Sweden, Egypt, Spain, France, Poland and Bulgaria to celebrate the success of the finalists. Several of the ACMers had qualified for the Code Jam Finals in their own right, and having them in Dublin added a real buzz to the proceedings.
Over 15 countries were represented in the finals, and 31 of the top 50 are from Eastern Europe. We celebrate the success of the top finishers: Tomasz Czajka from Poland took home the €2500 grand prize; second- and third-prize winners were Petr Mitricheve and Roman Elizarov, both from Russia, who won €1000 each.
Watch the fun that defined Code Jam Europe in this short clip from the 3-day event -- and keep on coding to prepare for the next one!
On June 29th, Google Dublin hosted the onsite finals for Code Jam Europe 2006. This is the third of four code competitions slated for this year, with China in January, India in April and a Global Code Jam this fall.
After nearly 10,000 registrants and three intense online rounds, the top 50 finalists persevered and flew to Dublin for the final challenge. ACM members also joined the coding community fun, traveling from countries as far afield as Kazakhstan, Russia, Sweden, Egypt, Spain, France, Poland and Bulgaria to celebrate the success of the finalists. Several of the ACMers had qualified for the Code Jam Finals in their own right, and having them in Dublin added a real buzz to the proceedings.
Over 15 countries were represented in the finals, and 31 of the top 50 are from Eastern Europe. We celebrate the success of the top finishers: Tomasz Czajka from Poland took home the €2500 grand prize; second- and third-prize winners were Petr Mitricheve and Roman Elizarov, both from Russia, who won €1000 each.
Watch the fun that defined Code Jam Europe in this short clip from the 3-day event -- and keep on coding to prepare for the next one!