StatusCake

Project Bernanke – Google’s Secret Ace

project Bernanke lawsuit

I know when you read Bernanke, you probably think of Ben Bernanke, the former chair of the Federal Reserve (aka the money maker), but this project has nothing to do with this famous Bernanke. Unfortunately, there is more bad news for big tech giant Google. It’s recently come to light that the state Attorney General of Texas has filed a complaint against Google and how Project Bernanke has given Google a massive competitive advantage over its rivals. 

What is Project Bernanke?

This project which Google has named “Project Bernanke” refers to the use of information that Google has access to from outside advertisers that use its bidding platform. Google is accused of using this data to create a competitive advantage over its rivals. Clanger. However, it seems that the main issue is that Google did not disclose this information and how it used the data it had access to – that reminds me of a certain social media tool beginning with F and ending in K.

It is suspected that this project has netted Google huge profits, in the millions even, and in 2013 in an internal memo, the company mentioned they could increase revenue by $320m that year alone. Yes, you read that right, 2013. This project has now been active for many years so the true value of Google’s financial gains could be much higher than this but it is too early in the investigation for there to be a close enough estimation. 

Why has this caused an issue for Google?

One of the reasons why the Texan Attorney General Ken Paxton proceeded with this lawsuit in December, in his own words is, “Google repeatedly used its monopolistic powers to control pricing” and “engage in market collusion to rig auctions”. The state of Texas has stated that their main problem is how Google used the information and how it manipulated the pricing of Google ads

Preliminary findings have shown that Google used this information by feeding it into its buying process to gain market insight into the top bids that their competitors were offering. This could then directly influence the price of Google ads to maximise profits. Now, you might not think this is a massive issue but if you are a rival ad tool provider then you would have undoubtedly seen this affect your performance and in turn, your clients’ performance. It is suspected that the main victims of Project Bernanke are the 3rd party ad exchange servers and publishers who have lost out. Why? Because Google could manipulate the bidding to favour its own ad exchange and thus make its own service look like a better performer. 

The issue now stretches even further; advertisers that would use Google’s DSP would have benefited from this system whilst those who used independent DSPs and SSPs would have lost access to the ad inventory as Google would change “the floor”. So in essence, Google secretly moved things around in the background to offer its own service at an unfair advantage over its competitors. 

How was Google able to do this?

It is estimated that over 90% of large digital ad publishers use Google to sell their ads giving Google access to an immense amount of data. This data would therefore give them the ability to predict pricing, target audiences and personal information of the users to better understand the markets. Not forgetting that Google’s also the biggest web search engine in the world which means it’s arguably more intelligent than any other online engine in targeting customers. Its business relies on returning customers’ expenditure on ads and this is why Google strives hard to maintain the top position in the services it offers and potentially, why they turned to Project Bernanke.

This all proved to be so successful for Google that it has recently come to light that they signed an agreement with Facebook which gave them a guaranteed preference over a set agreed percentage of ads that would win over competitors.The estimated amount exchanged is said to be over half a billion dollars so it would be impossible for small and medium-sized businesses to compete against these big players. It seems that the only good news here is the creative project names, and this one was no exception with project “Jedi Blue”. It seems Facebook can’t seem to get themselves out of the news recently..

What now for Google?

The tech giants have said they will of course contest the claims and it is only because of the court filing that the public has been made aware of the situation. Google’s lawyer said that the complaint “misrepresents many aspects of our ad tech business. We look forward to making our case in court”. Although an interesting argument, the question remains, how much will this hurt Google’s reputation? They managed to manipulate a service so well that other companies suffered for so long. Surely it won’t be long before governments across the globe start to get involved and regulate these platforms more harshly to stop things like this from happening again. It’s scary to think that the two biggest digital ad companies are based in the same State and the same city in the US. Coincidence? I think not…

Share this

More from StatusCake

Designing Alerts for Action

3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams

A Notification List Is Not a Team

3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years

Alert Noise Isn’t an Accident — It’s a Design Decision

3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.

The Incident Checklist: Reducing Cognitive Load When It Matters Most

4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already

When Things Go Wrong, Systems Should Help Humans — Not Fight Them

3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,

When AI Speeds Up Change, Knowing First Becomes the Constraint

5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things

Want to know how much website downtime costs, and the impact it can have on your business?

Find out everything you need to know in our new uptime monitoring whitepaper 2021

*By providing your email address, you agree to our privacy policy and to receive marketing communications from StatusCake.