Legal entity
Every one of those 1 sits in a single category, court-decisions. AdX is the most frequent co-covered peer, appearing in 1 of the 1 tracked story. We currently track 1 Legal story that mention Leonie Brinkema, all published on September 4, 2026.
Last mentioned: Sep 4, 2026
Entity pulse
Coverage balance Positive coverage leads. Positive coverage exceeds negative coverage by 100 percentage points.
Figures are computed live from our source-verified story record — see our methodology for how impact and sentiment are derived.
Every one of those 1 sits in a single category, court-decisions. AdX is the most frequent co-covered peer, appearing in 1 of the 1 tracked story. We currently track 1 Legal story that mention Leonie Brinkema, all published on September 4, 2026. Each carries 2 original sources on average.
Computed from the 1 stories linked to this entity, with beat comparisons drawn from all 10 Legal stories published in the same date window. Shares are omitted below five stories and comparisons below a twenty-story baseline.
Coverage cohort
Other entities that clear the same relevance threshold in stories also covering Leonie Brinkema. Shared-story counts are live from our verified record — not editorial picks.
Remedy order entered
Judge Brinkema declined to force a sale of AdX and DFP, instead accepting most proposed behavioral remedies with modifications.
Liability ruling in United States v. Google
Judge Brinkema found Google illegally monopolized key advertising technology markets, setting the stage for the remedy phase.
A federal judge in Virginia declined the DOJ's bid to force Google to divest AdX and DFP, instead imposing behavioral remedies. The sealed order, due for release in about two weeks, will clarify compliance obligations for Google's shrinking ad tech business.
Source: Daniel Sparks (us) · fool.com
Leonie Brinkema is linked from 1 story on this site, each scored at or above our 35% relevance threshold — see how these pages are built.
See something wrong on this page — a misattributed entity, a wrong stat, a broken source link? Report a data issue.
