UndrAds is this year's Diamond Sponsor at Mobidictum 2026, Istanbul 💎 - Check out the news

UndrAds
Adtech

Google’s Ad-Tech Antitrust Ruling: What It Means for Publishers and App Developers

Rashmita Behera
Rashmita Behera
Sep 19, 2026
Google’s Ad-Tech Antitrust Ruling: What It Means for Publishers and App Developers

Google will not be forced to sell its ad exchange or break up Google Ad Manager. But it will have to make important parts of its advertising system work more fairly with rival tools.

That is the simple version of the US court’s September 2026 decision in the Google ad-tech antitrust case.

For web publishers, the ruling could make it easier to use Google demand without committing the entire advertising stack to Google. It also promises better access to auction data and more room for independent ad servers and Prebid to compete.

For app developers, the immediate effect is much smaller. The case was about advertising on the open web. The court specifically treated mobile-app ads, instream video and social media ads as outside the market covered by the lawsuit. AdMob was not ordered to change, and developers do not need to replace an SDK or rebuild their mediation setup because of this ruling.

The case in brief

The US Department of Justice and a group of states sued Google in January 2023. Their argument was that Google controlled too many connected parts of the system used to sell display ads on websites.

Two products were at the center of the case:

  • DFP, Google’s publisher ad server, now part of Google Ad Manager. It decides which ad appears in a publisher’s available slot.
  • AdX, Google’s ad exchange. It brings advertiser bids into the auction.

Google also controls a large source of advertiser demand through Google Ads, called AdWords in the court documents. The government argued that Google used the connections between these products to favor its own exchange, make competing tools less attractive and lock publishers into the Google stack.

In April 2025, Judge Leonie Brinkema found that Google had illegally acquired and maintained monopoly power in two markets: publisher ad servers and ad exchanges for open-web display advertising. She also found that Google had unlawfully tied DFP and AdX together. The court’s September 2026 remedies opinion explains how Google must change its conduct.

The Department of Justice wanted a much tougher solution, including a forced sale of AdX and the possible separation of more of Google’s publisher technology. The judge rejected that breakup. She chose rules governing Google’s behavior instead.

Timeline of the Google ad-tech antitrust case from the January 2023 lawsuit to implementation of the September 2026 remedies.

The case moved from a proposed breakup to worldwide interoperability, data-sharing and non-discrimination rules.

What the judge ordered

The full opinion was entered under seal on September 2 and made public on September 16. The Justice Department’s official summary groups the main remedies into four areas.

1. Google must connect its tools to Prebid and rival ad servers

Google must build and support integrations between AdX, DFP and Prebid. AdX must also submit real-time bids to competing publisher ad servers on terms that are functionally equivalent to those offered to Google’s own ad server.

A publisher should be able to access valuable Google demand without being forced to let Google control every other part of the auction.

If you need a refresher on the how things work, UndrAds’ guides to Google Ad Manager, AdX, AdSense and Ad Manager 360 and how header bidding works explain what each layer does.

2. Publishers must get better access to their own data

Google will have to let publishers access and export covered data from DFP and AdX. It must also provide more technical information about how the DFP auction selects a winner, including pricing and bid adjustments.

This matters because switching an ad server is not like changing an email provider. A publisher needs historical auction data, configurations and reporting continuity to compare systems or migrate without flying blind.

The order does not make switching effortless. It should, however, reduce one of the largest barriers: not having enough usable information to evaluate an alternative.

3. Google Ads cannot secretly favor Google’s own route

The court prohibited AdWords from bidding directly into DFP and from giving preferential treatment to Google-owned ad-tech products simply because Google owns them.

Think of Google as owning a marketplace, a stall inside that marketplace and a major source of buyers. The ruling does not force Google to sell any of them. It says the buyers cannot be quietly directed to the Google-owned stall on better terms than everyone else receives.

4. A monitor will watch Google for six years

A court-appointed monitor and technical committee will oversee compliance. The requirements apply globally because the court found that these ad-tech markets and Google’s infrastructure operate worldwide.

The six-year period matters, but implementation will not happen overnight. The parties still need a final judgment, and the opinion allows time for Google to build new integrations and data systems. AdExchanger’s summary of the unsealed opinion notes that the final judgment had not yet been entered when the opinion became public.

What this means for web publishers

What improves and what stays limited for publishers after the Google ad-tech remedies ruling.

The ruling gives publishers more choice and data access, but Google keeps AdX and Google Ad Manager, and higher revenue is not guaranteed.

More choice without losing access to Google demand

This is the biggest potential benefit.

Many publishers use Google Ad Manager because AdX and Google Ads bring demand that is difficult to replace. Even if another ad server has useful features, leaving Google can feel commercially risky.

Required interoperability could separate those decisions. A publisher may eventually be able to choose a different ad server or run more of the final auction through Prebid while still receiving real-time AdX bids on fair terms.

That does not mean a wave of publishers will leave GAM immediately. Alternative ad servers still need to build strong products, integrations and support. The order creates an opening for competition; it does not create mature competitors by itself.

A stronger position for Prebid and independent demand

Prebid is the open-source framework behind much of header bidding. It was built so publishers could invite several exchanges to bid before the ad server made its final decision.

Google must now integrate more directly with that framework instead of keeping important demand and decision-making inside its own closed path. For publishers already running header bidding, this could reduce awkward workarounds and make auctions easier to compare.

The practical value will depend on the details: latency, documentation, data fields, bid timing and whether the integrations work as well in practice as they do on paper. Publishers should track those points through header-bidding analytics, not assume that technical compliance automatically produces better yield.

More transparency and lower switching risk

Exportable data and clearer auction documentation should make it easier to answer basic questions that have historically been difficult:

  • Which bidder actually saw the impression?
  • Which bid won or lost, and why?
  • Did an adjustment change the apparent value of a bid?
  • Would a different auction path have produced a different result?
  • Can the publisher take its history and configuration to another provider?

Those answers give publishers more leverage when negotiating with vendors and make controlled tests more credible.

Potentially fairer auctions, but no guaranteed revenue increase

Stopping Google Ads from favoring Google-owned pipes should make competition fairer. In theory, fairer competition can produce better prices and encourage more investment by independent ad-tech companies.

But the ruling does not guarantee higher CPMs, fill rates or revenue. Results will still depend on audience, geography, consent signals, format mix, page performance, floors and demand quality.

The court also did not order Google to cut AdX’s fee, pay publishers compensation or sell AdX. Google still owns the ad server and exchange. Publishers are getting new rules and connections, not a new market structure.

No reason to rebuild the stack today

The sensible move is preparation, not a rushed migration.

Publishers should document their current Google dependency, clean up bidder and auction reporting, preserve historical data and identify where a rival server or a more independent Prebid auction could be tested once the required integrations exist.

If your present setup is underperforming, fix what is measurable now. Review common header-bidding mistakes, bidder timeouts, floors and demand concentration rather than waiting for a court order to lift revenue automatically.

What this means for app developers

The direct impact is limited

This is the most important point for mobile teams: the ruling is not an AdMob ruling.

The court defined the relevant markets around open-web display advertising—ads served on websites through third-party ad-tech infrastructure. In the remedies opinion, it explicitly said that instream video, mobile-app ads and social media ads were outside the case. It also rejected a broader data-sharing proposal partly because it would have covered in-app and video data that were not part of the proven violation.

So, for an app monetized only through AdMob, AppLovin MAX, Unity LevelPlay or another in-app mediation platform:

  • No immediate SDK change is required.
  • No new app-store release is required.
  • AdMob is not being separated from Google.
  • The ruling does not force Google to export all in-app auction data.
  • Prebid Mobile should not be assumed to receive the same court-ordered treatment as open-web Prebid integrations.

UndrAds’ AdMob guide and in-app bidding versus waterfall comparison cover the app-specific stack, which remains a different market from the one addressed here.

Some developers could see an indirect effect

The ruling may still matter indirectly.

First, developers that also operate websites can benefit on the web side of the business. A game studio with a news site, community portal or browser-based property should separate those open-web impressions from its in-app inventory when assessing impact.

Second, successful interoperability on the web could increase pressure for clearer data access and fairer auction connections elsewhere in ad tech. That is a reasonable possibility, not something the court ordered for apps.

Third, more competition among exchanges and publisher tools could influence advertiser budgets and technical standards over time. Again, that is a market effect to watch, not an immediate product change.

What app developers should do now

Do not switch mediation platforms because of this decision alone.

Instead:

  1. Measure how much revenue and fill come from Google demand by app, format and country.
  2. Check whether your mediation stack creates genuine competition or relies too heavily on one network.
  3. Keep SDKs current and test changes through staged releases.
  4. Preserve auction and revenue history so future platform changes can be measured against a clean baseline.
  5. Review your broader app monetization strategy on its own merits.

If AdMob concentration is already a business risk, compare AdMob alternatives because of your performance, control and resilience needs—not because this ruling requires a migration.

What the ruling does not do

The decision is meaningful, but it is narrower than a breakup. It does not:

  • Split Google Ad Manager from AdX.
  • Force Google to sell any ad-tech business.
  • Reduce AdX’s take rate by court order.
  • Award automatic payments to publishers.
  • Cover every kind of digital advertising.
  • Require an immediate AdMob or mediation change.
  • Guarantee higher publisher revenue.

That distinction matters. Headlines about “opening Google’s ad business” can easily sound broader than the actual order.

The bottom line

For web publishers, the ruling could loosen the strongest tie in the Google ad stack: the idea that access to Google demand requires Google to control the publisher’s auction too. Better interoperability, data portability and non-discrimination rules create a real opportunity for more choice.

The opportunity will take time to become useful. Publishers should watch the final judgment, technical specifications, implementation deadlines and any appeal. They should also demand evidence that new integrations are genuinely equivalent in speed, data and auction behavior.

For app developers, the message is simpler. Keep watching, but do not treat this as an AdMob mandate. The court drew a line around open-web display advertising, and the app economy sits mostly outside it.

The market did not get a breakup. It got a set of rules designed to make Google’s existing stack less closed. Whether that produces lasting competition will depend on how well those rules are implemented—and whether publishers use the new choices when they arrive.

FAQ

Did the court break up Google’s ad-tech business?

No. The judge rejected the proposed sale of AdX and other structural remedies. Google keeps DFP/Google Ad Manager and AdX, but must follow new interoperability, data-sharing and non-discrimination rules.

Does Google have to work with Prebid?

Yes, within the open-web display scope of the judgment. Google must build and support integrations connecting AdX and DFP with Prebid, as well as connect AdX to rival publisher ad servers.

Will publisher revenue go up?

Possibly, but it is not guaranteed. More competition and transparency can improve outcomes, but revenue still depends on inventory, users, demand, pricing, latency and execution.

Does this change AdMob?

Not directly. Mobile-app advertising was outside the market defined in the case. The ruling does not order an AdMob breakup or require developers to change the AdMob SDK.

When will the changes happen?

Not immediately. The court’s opinion called for a final judgment, a 60-day period before most obligations take effect and implementation time for technical work. Publishers should watch the final order and any appeal for the actual timetable.

Sources

Never Miss New Updates

Subscribe to our weekly newsletter and stay ahead with latest updates.