Functional equivalence is a compliance standard used in competition remedies. It requires that a connection a dominant company builds for its competitors work as well as the connection it operates for itself. The test is not whether an interface exists, nor whether it is documented, but whether a rival routed through it receives the same bids, the same signals and the same response times as the incumbent's internal path. A connection that technically exists and technically underperforms fails it.

The standard exists because access obligations kept producing access in name only. Courts ordering a platform to open a pipe found the pipe could be narrowed in ways no contract prohibited: added latency, a field withheld from the payload, a request cap applied selectively. Functional equivalence converts an obligation to connect into an obligation to perform, measured against the obligated party's own internal arrangement.

What the standard actually tests

The benchmark is internal, which is what separates this from ordinary fairness language. A company subject to a functional equivalence duty cannot satisfy it by treating all outsiders alike. It has to treat outsiders the way it treats the division sitting inside its own corporate boundary.

Four dimensions carry most of the weight in practice. The first is timing. In an auction resolved in tens of milliseconds, a bid that arrives after the timeout has not been refused; it has simply lost. Google Ad Manager processes roughly 8.2 million ad requests and 60 million bid requests per second at peak, according to testimony from engineering director Glenn Berntson recorded in the September 2026 remedies opinion, which works out at close to five trillion bid requests a day. At that scale a systematic delay of a few milliseconds on one route is invisible to any single publisher and decisive in aggregate.

The second is information parity. Bid requests carry payloads, and the value of a bid depends on what the bidder can see: user signals, floor prices, content category, device identifiers, the presence of consent strings. A route that omits two fields the internal route carries will price impressions worse without anyone declining to participate. The Virginia order addresses this directly by requiring that Google pass through the new integrations the same information AdX passes to Google's own buying tools.

The third is commercial terms. Revenue share, fee structure and request volume allowances sit outside the technical layer and reproduce the same disadvantage by other means. The remedies package bars Google from varying AdX's revenue share, adding latency, responding to fewer bid requests or transmitting less information depending on whether a publisher runs DFP, a rival ad server or Prebid.

The fourth is verification. Equivalence that cannot be measured by anyone other than the party providing it is an assertion. This is why functional equivalence provisions arrive attached to monitors, technical committees and data disclosure duties rather than standing alone.

Origin and evolution

The lineage runs through software antitrust. The final judgment entered against Microsoft on November 12, 2002 required disclosure of the application programming interfaces, or APIs, that Microsoft's own middleware used to interoperate with Windows, and required that the disclosure happen "in a Timely Manner", a defined term tied to beta release milestones rather than to Microsoft's convenience. Communications protocols had to be licensed on reasonable and non-discriminatory terms. The principle was already visible: outsiders should receive what insiders receive, when insiders receive it.

Ad tech acquired its own version on June 7, 2021, when the French Autorité de la concurrence fined Google 220 million euros in Decision 21-D-11 and made a set of commitments binding for three years. The authority had found that Google's publisher ad server applied less favourable technical and contractual conditions to rival ad servers than to Google's own products, and that publishers on a third-party server could not reach AdX demand in real time. The commitments required an interoperability route between DFP and third-party supply-side platforms permitting competition on the merits, fair access to auction information for exchanges bidding through header bidding, and an undertaking that AdX would stop using rivals' prices in ways competitors could not replicate. Google appointed and paid for an independent trustee to monitor the work.

Europe then wrote the idea into legislation. Article 6(7) of the Digital Markets Act obliges designated gatekeepers to provide free and effective interoperability with the same hardware and software features available to the gatekeeper's own services, a formulation that makes the internal benchmark explicit. The obligation became applicable on March 7, 2024, and the Commission has since run specification proceedings against Apple to determine what compliance means in engineering terms. Article 6(7) also permits integrity measures that are strictly necessary and proportionate, which is where most of the argument now sits.

The phrase itself entered United States ad tech law on September 2, 2026. Judge Leonie M. Brinkema of the Eastern District of Virginia rejected all three structural remedies the Department of Justice had sought against Google and imposed a behavioural package instead, following her April 2025 finding that the company had monopolised the publisher ad server and ad exchange markets. The 106-page memorandum opinion explaining that choice was sealed for fourteen days and became public on September 16. It requires that the new Prebid integrations operate "in a functionally equivalent manner and on materially identical terms" to the way DFP works with AdX today, without additional latency.

Why the standard matters for the marketing community

Everything publishers gained from the Virginia case depends on this phrase holding. No exchange changed hands, so the only route to competition is the quality of the connections Google builds for everyone else and then operates under a six-year monitor with source code access.

The numbers explain why a paper connection would not be enough. The liability ruling put Google at 91 percent of the publisher ad server market in 2022, with AdX taking 63 to 71 percent of open-web exchange transactions between 2018 and 2022 at a 20 percent take rate against roughly 10 percent charged by rivals. AdWords has integrated with about 50 third-party exchanges since 2015 and still placed only around 3 percent of its impressions outside AdX. Access without parity already exists, and it has not moved share.

Rajeev Goel, chief executive of PubMatic, made the same point on September 17 in the first detailed assessment from an independent supply-side platform. "But the existence of a connection does not, by itself, create meaningful choice," the company's blog states, setting four conditions: comparable terms, bids arriving in time, usable data, and the ability to switch providers without ending up worse off.

Limitations and disputes

The most serious objection is that the standard is measured using telemetry the obligated party generates. Latency, fill and bid density on Google's own path are observable to Google; a rival sees only its own outcomes. Digital Content Next argued on September 2 that the asset genuinely at stake was market-wide auction data rather than any single publisher's revenue, which is a claim about who can verify equivalence at all.

Second, the phrase is undefined at the margin. Materially identical terms admits of interpretation, and the Virginia opinion left the non-discrimination drafting, the deadline for opening AdX to rival ad servers and the format of Google's auction documentation to negotiation between the parties, with a joint proposed final judgment due on October 2, 2026.

Third, scope. Display & Video 360 emerged from the opinion untouched, the court finding an insufficient connection between that platform and the conduct at issue, so a demand-side platform competing against independent rivals sits outside an order otherwise built on equal access.

Fourth, the record on behavioural relief is contested. Index Exchange's Andrew Casale testified that conduct rules help but cannot guarantee certainty, since new preferencing features can be written at any time. The European Commission reached a harder conclusion in its own 2.95 billion euro ad tech decision of September 2025, keeping structural remedies on the table on the view that conduct had been repeatedly modified while its effects survived. The two tracks now diverge on the central question of ownership.

Not the same as

Non-discrimination bars a platform from treating comparable third parties differently. Functional equivalence goes further by fixing the comparator: the platform's own internal service. A company can be perfectly non-discriminatory towards every outsider and still fail an equivalence test.

FRAND, meaning fair, reasonable and non-discriminatory access, governs the terms on which access is licensed, principally price and conditions. It says nothing about whether the licensed route performs as well as the licensor's own.

Interoperability describes the capability: two systems exchange information and can use what was exchanged. Functional equivalence is a quality standard applied on top of it. Article 6(7) of the Digital Markets Act fuses the two.

Divestiture removes the conflict by changing ownership. Functional equivalence is what a court reaches for when it declines that route, which is why enforcement of the phrase carries more weight than its technical sound suggests.

Recent developments

The unsealed opinion reached the industry on September 16, 2026. PubMatic published its reading a day later, citing an engineering estimate of roughly a year to fifteen months for the ordered interoperability work. The obligations apply worldwide, take effect sixty days after judgment and run for six years, with a monitor and a three-member technical committee still to be appointed. Nothing in the open-web display auction changes this quarter. Whether the phrase means anything will be settled somewhere around late 2027, in telemetry most of the market cannot see.

Timeline

  • November 12, 2002: The final judgment in United States v. Microsoft requires disclosure of middleware APIs in a timely manner and licensing of communications protocols on reasonable and non-discriminatory terms
  • June 7, 2021: The French Autorité de la concurrence fines Google 220 million euros in Decision 21-D-11 and makes binding three years of ad tech interoperability commitments supervised by an independent trustee
  • November 1, 2022: Regulation (EU) 2022/1925, the Digital Markets Act, enters into force with an interoperability benchmark set against the gatekeeper's own services in Article 6(7)
  • January 24, 2023: The Department of Justice and state attorneys general file the ad tech complaint in the Eastern District of Virginia
  • March 7, 2024: Article 6(7) becomes applicable to the first designated gatekeepers
  • April 17, 2025: Judge Brinkema finds Google monopolised the publisher ad server and ad exchange markets for open-web display
  • September 22 to October 6, 2025: The remedies trial hears 26 witnesses over 11 days
  • September 2, 2026: All three structural remedies are rejected and behavioural remedies adopted as modified; the memorandum opinion is filed under seal
  • September 16, 2026: The 106-page opinion becomes public, carrying the functional equivalence requirement for the Prebid integrations
  • October 2, 2026: Deadline for the parties to file a jointly proposed final judgment

Summary

Who. Courts and regulators impose the standard: Judge Leonie M. Brinkema in the Eastern District of Virginia, the French Autorité de la concurrence, and the European Commission under the Digital Markets Act. Google is the party currently bound by it in advertising technology. Prebid, rival publisher ad servers and independent exchanges including PubMatic, Index Exchange, Magnite, Equativ and Kevel are the intended beneficiaries. A court-appointed monitor and technical committee will judge compliance.

What. A remedial standard requiring that access, integration or disclosure offered to competitors match what the obligated company provides to its own units, measured on timing, information passed, commercial terms and verifiability rather than on the existence of a connection.

When. The principle dates to the Microsoft final judgment of November 12, 2002, entered ad tech through the French commitments decision of June 7, 2021, became legislation in Article 6(7) of the Digital Markets Act applicable from March 7, 2024, and was applied to Google's ad stack in the memorandum opinion of September 2, 2026 made public on September 16.

Where. In publisher ad servers, exchanges and header bidding wrappers, at the API layer connecting them. The Virginia judgment applies globally rather than only in the United States, because both markets at issue were defined as worldwide.

Why. Ordering a monopolist to open a connection achieves nothing if the connection can be made slower, thinner or more expensive than the one the monopolist uses itself. The standard exists to close that gap, and its weakness is the same as its purpose: the company required to build the parity is the company best placed to measure whether parity exists.