Skip to main content

Google's Business Model

Mark Cuban appeared on CNBC the other day and succinctly described how Google makes money. He also pointed out a gaping technical hole in their business model that may jeopardize Google's earnings going forward.

According to Cuban, the vast majority of Google's revenue comes from Google AdWords. Google describes AdWords as follows:
"With Google AdWords you create your own ads, choose keywords to help us match your ads to your audience and pay only when someone clicks on them."
Owners and administrators of web sites can allocate space on their pages for Google to place the ads that advertisers create. They receive a portion of the revenue generated when someone clicks the advertising links. Google receives the rest of the "click revenue".

Cuban drew attention to the fact that competitors can game this system. I.e., a competitor to an advertiser can write an automated script that repeatedly "clicks" the link, thereby causing the advertiser to pay huge sums of money to Google for worthless clicks (clicks by a machine that will never purchase anything). If this problem becomes pervasive, companies will no longer want to advertise with Google, and Google's primary source of revenue will dry up.


Doojie said…
This really isn't a new idea by Cuban as Google as known about this for years. I'm not a big Google supporter, but I've read about how they are continually modifying their software to detect and prevent ghost clicks, so I doubt this will have a dramatic effect on them. Also, anything Cuban says on SqawkBox is most likely stated for a gain of his own.

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware