The Federal Trade Commission on October 19, 2026 accepted a proposed consent order that lets Publicis Groupe S.A. buy LiveRamp Holdings, Inc. on condition that LiveRamp keeps serving the clients of rival agencies on neutral terms, that Publicis is walled off from LiveRamp customer data, and that an outside auditor checks compliance every six months for the first two years after closing. The Commission vote was 2-0, and a 30-day public comment period now runs before the order can be made final.

In Short

Publicis, one of the biggest ad agency groups, wants to buy LiveRamp, a company that many advertisers, agencies and publishers use to match their data safely, and the US competition regulator has agreed to let the deal go ahead only with rules attached. The worry is that Publicis could use LiveRamp to squeeze clients of rival agencies or peek at their confidential campaign data to win their business. For five years, Publicis would have to treat every LiveRamp customer the same, keep its hands off their data, pay for regular outside audits and tell every customer about the rules in writing.

What the FTC decided

According to the FTC, the proposed order "would address the FTC's concerns that Publicis's acquisition of LiveRamp, which provides data connectivity services that help facilitate the secure and confidential movement of data used for digital advertising, would harm competition in the markets for media agency services and audience data services."

The press release is dated October 19, 2026. It carries the headline "FTC Order Preserves Competition in Digital Advertising Ecosystem as Part of Publicis's Acquisition of LiveRamp" and the subheading "Order addresses concerns that proposed deal would harm competition in markets for media agency services and audience data services." The accompanying Decision and Order runs to 14 numbered pages, plus a six-page contract addendum, in a 20-page PDF.

The deal is not blocked. Nor does it involve a sale of any business. The remedy is entirely behavioral: a set of conduct rules that bind both companies, written into an FTC order and copied into every LiveRamp customer contract.

"By requiring LiveRamp to continue operating as it does today as a neutral platform, this order will ensure that Publicis does not gain an unfair advantage over its competitors in the digital advertising marketplace," said David Shaw, Principal Deputy Director of the FTC's Bureau of Competition, according to the press release. "The FTC's action today ensures that the digital advertising marketplace can continue to grow and evolve without risking harm to competition."

Only two commissioners are named on the order: Chairman Andrew N. Ferguson and Mark R. Meador. According to the FTC, "The Commission vote to issue the complaint and accept the consent agreement for public comment was 2-0."

The parties and the deal

The order identifies Publicis Groupe S.A. as a French corporation with its executive offices at 133, Avenue des Champs-Elysees in Paris, and LiveRamp Holdings, Inc. as a Delaware corporation based at 225 Bush Street, 17th Floor, San Francisco.

The transaction itself is defined by reference to an "Agreement and Plan of Merger by and among MMS USA Holdings, Inc., Covey Merger Sub, Inc., LiveRamp Holdings, Inc., and solely for the purposes of Section 10.14, Publicis Groupe S.A., dated as of May 16, 2026." MMS USA Holdings reappears in the access provisions of the order, which give FTC staff the right to inspect the records of "MMS USA Holdings Inc. and its U.S. subsidiaries" on five days' notice.

The FTC describes the transaction as "the $2.2 billion deal" under which Publicis "would acquire 100% of LiveRamp." That figure differs from the one most widely reported in May. PPC Land's coverage of the announcement put the equity value at $2.5 billion, or $38.50 per share in cash, with an enterprise value of $2.167 billion after deducting $379 million of acquired net cash. The FTC's $2.2 billion figure matches the enterprise value, rounded, rather than the equity value. Neither of the attached documents explains which measure the agency used.

Who are these companies to each other? According to the FTC, "LiveRamp is the leading data connectivity provider in the U.S. media marketing ecosystem and the only provider with a full spectrum of data connectivity services." Publicis, the agency said, "is the largest among the five major advertising agencies in the United States. It also provides audience data services through its Epsilon subsidiary that help companies target their advertising to particular audiences."

The combination therefore joins a large media agency and audience data business with a supplier that competing agencies and data providers rely on. That is a classic vertical integration concern: the buyer gains control of an input its rivals need.

The competitive concerns

The FTC press release sets out three theories of harm, each attributed to the agency's complaint. The complaint itself was not among the documents supplied for this article, though the press release links to it on ftc.gov.

The first is foreclosure in agency services. According to the FTC, the deal "would likely result in Publicis having the ability and incentive to foreclose customers of competing media agency service providers by using its control of LiveRamp to push customers to switch their media agency business to Publicis even if those customers otherwise prefer competing media agencies."

The second concerns the quality of service rivals would receive. "The FTC also alleged Publicis would deny or degrade access to LiveRamp services on which competitors rely, which would lead to higher costs and lower quality services for customers of competing digital advertising services," the press release states.

The third is about data. "In addition, the FTC alleged that under the deal Publicis would gain access to competitively sensitive data of non-Publicis clients serviced by LiveRamp, which Publicis would leverage to pressure those clients to switch to Publicis."

The legal basis, according to the FTC, is that "combining Publicis and LiveRamp would decrease competition in the relevant markets for media agency services and audience data services in violation of Section 7 of the Clayton Act." The Decision and Order adds Section 5 of the FTC Act to the charges in the draft complaint.

As is standard, the companies admit nothing beyond jurisdiction. The decision records that signing the consent agreement "is for settlement purposes only and does not constitute an admission by Respondents that the law has been violated as alleged in the Draft Complaint."

What Publicis and LiveRamp must do

Neutral operation and non-discrimination

Section II of the order carries the core conduct rules, lettered A through L. The opening paragraph sets the principle: the companies "shall not disfavor, disadvantage, or discriminate among LiveRamp's Customers, based on whether such entities have a competitive relationship with Publicis or with Publicis's customers, including operating the LiveRamp Business as a commercially neutral provider of identity, data collaboration, and interoperability services."

The definition of a LiveRamp Customer is broad. It covers "any current or future customer of the LiveRamp Business, including direct customers, publishers, advertisers, agencies, technology providers, or other users of the LiveRamp Business." The LiveRamp Business itself is defined as "all U.S. business activities conducted by Respondent LiveRamp, including identity, data collaboration, and interoperability services." The order, in other words, is limited to the United States.

Paragraph II.B runs in the other direction. Publicis may not "deny, degrade, delay, or otherwise impair continued access to media-related information or support provided by Publicis (including audience or measurement platform input) to any LiveRamp Customer that relies on such information or support," based on competitive relationships with LiveRamp, Publicis or Publicis's customers. This protects companies that depend on Publicis data, not just those that depend on LiveRamp.

Under II.C, the companies must "continue to offer to all LiveRamp Customers, on fair, reasonable, and non-discriminatory terms, equivalent access to LiveRamp standalone products, services, APIs, technical support, and commercial programs, at the time of the relevant offer or contract renewal, regardless of whether the customer is otherwise a Publicis customer."

Two carve-outs soften these rules. Different products may be offered to different customers "so long as the reasons for offering differing products and services are objective, specific, and related to the work being performed by LiveRamp for the particular customer, consistent with past practices of LiveRamp." And Paragraph II.D, which bars degrading access to standalone services, explicitly permits Publicis to develop "new products and services that integrate LiveRamp products and services with the products and services of Publicis," adding that "Publicis will be free to choose to which customers it will offer such new integrated products and services."

That second proviso matters. The order protects what LiveRamp sells as standalone products. It does not stop Publicis from building combined offerings that only its own clients can buy.

No tying, no lock-in

Paragraph II.E requires the companies to let customers "choose their preferred operating model and composable technology architecture, including the use of lawful third-party platforms, tools, and services, without restriction or any penalty being imposed by Publicis or LiveRamp."

Paragraph II.F bans tying outright: the companies "shall not condition a LiveRamp Customer's use of LiveRamp standalone products and services on the adoption, integration, or purchase of any technology, platform, or service offered (such as CDPs, data services, media activation, and creative services) by Publicis."

Paragraph II.J goes further, barring the companies from conditioning "access to pricing, product functionality, roadmap priorities, technical integration, or customer support" on a customer buying Publicis services or on "a LiveRamp Customer's decision to authorize the sharing of information with Publicis, or Publicis's customers." Paragraph II.K bars preferential treatment for Publicis customers on terms not "made available on substantially equivalent terms to similarly situated customers."

Clean rooms and ATS

Two LiveRamp products get named protections. For clean room services, Paragraph II.G lists four guarantees. Customers keep control over "access and roles within the clean room, including the designation of authorized users permitted to sign in, view audience data, and use features." They keep the right to set "content-level permissions governing permitted uses of data within the clean room" and to set "governance and privacy controls." LiveRamp must maintain "auditability sufficient for LiveRamp Customers to verify that no unauthorized users have accessed their clean room data," on a continuous basis, with supporting documentation for "the preceding one-year period available upon reasonable request."

The second is Authenticated Traffic Solutions, defined in the order as "permitting publishers to resolve consented user data with a RampID in real-time, enabling people-based advertising on authenticated, cookieless inventory across the open internet." RampID is LiveRamp's pseudonymous identifier. Paragraph II.H requires ATS to remain available "on non-discriminatory terms." The customer addendum adds a technical commitment absent from the order body: LiveRamp "will continue to maintain encrypted identity envelopes that contain no personally identifiable information or media cost or transactional data."

Interoperability

Paragraph II.I requires the companies to "support interoperability between LiveRamp standalone products and services and third-party advertising, marketing, measurement, retail media, and technology platforms without preferential treatment for Publicis's own products and services."

LiveRamp is not obliged to keep every integration alive, however. It may drop a third party that "declines to accept LiveRamp's standard commercial or data-protection terms," "fails to provide reciprocal technical cooperation," "presents a security or compliance risk," "ceases operations," or "is in material breach of its agreement with LiveRamp." The first two grounds give LiveRamp some discretion, since it sets its own standard terms.

No retaliation

Paragraph II.L bars retaliation against any customer "because the LiveRamp Customer is discussing or has discussed or may discuss any concerns about Respondents' compliance with the Orders with the Commission staff." The press release frames this as a requirement "that Publicis shall not retaliate"; the order text applies it to both respondents.

The data firewall

Section III is the firewall. Paragraph III.A states that "Respondent Publicis shall not access, or otherwise use LiveRamp Customer data held by LiveRamp, and such data shall not be transferred to, commingled with, or used to develop, train, or improve products and services offered by Publicis." The words "train, or improve" bring AI model development within the prohibition, which is notable given that Publicis framed the deal around agentic AI when it was announced.

The companies must maintain "technical access controls, logical separation, and access logging" to enforce that rule. When a customer leaves, LiveRamp "will promptly destroy all such customer's Confidential Business Information" and will provide written certification on request, subject to retention for legal or regulatory reasons or with the customer's authorization.

The exception is consent. Publicis may use LiveRamp customer data "when expressly authorized to do so by the LiveRamp Customer." Paragraph II.J, described above, prevents LiveRamp from making that authorization a condition of better pricing or support. The two provisions work together: the data can flow only with permission, and permission cannot be extracted through commercial pressure.

What counts as confidential is spelled out. The definition includes "bidding strategies, campaign performance data, pricing data, audience segment compositions, customer identity graphs, measurement data, end of month usage reports, contractual terms of Respondent LiveRamp's Customers and partners," and, notably, "aggregated, pseudonymized, and de-identified personal information processed or ingested by Respondent LiveRamp." The inclusion of identity graphs and de-identified data closes the route by which a buyer might argue that anonymized or derived data falls outside a firewall.

A limited group of Publicis staff, defined as "Management and Administrative Personnel," may see confidential customer information for "billing, financial reporting, tax, audit, legal compliance, corporate governance, and customary approvals." They may receive only "the minimum amount of Confidential Business Information necessary," must use it only for those functions, and may not pass it to other Publicis employees. Anyone receiving such information must be trained and must acknowledge the restrictions, and the companies must keep records of that training.

Audits, notices, mediation and reporting

Audits

Section IV sets the audit schedule. The companies "will conduct an audit, every six months for the first two years following the Acquisition Date (each audit covering the previous six month period), and then once a year for every year thereafter," covering compliance with Sections II and III. The audit must be carried out by "an independent industry-standard provider that routinely performs SOC-2 audits," and copies go to the Commission and, "upon reasonable request," to any LiveRamp customer.

Individual customers also get their own right. Under Paragraph IV.D, a customer may, "at that customer's expense, up to once a year," have an audit conducted of the companies' data protection, privacy and security obligations to that customer.

There is no monitor trustee appointed by the FTC. That contrasts with the order the FTC finalized against Omnicom's acquisition of IPG in September 2025, which required a five-year compliance monitor. In the Publicis case, the checking is done by a privately engaged SOC-2 auditor whose reports go to the agency.

Customer notices and contract amendments

Within 60 days of the order being issued, the companies must send every LiveRamp customer a letter in the form of Appendix B together with a copy of the order, by US mail with return receipt or electronically with a read receipt or proof of delivery. In the same 60 days, they must amend every existing customer contract with the addendum in Appendix A and include it in all new ones.

The draft letter describes the order as one "that we have voluntarily entered into with the Federal Trade Commission," and states: "If anything in this letter conflicts with the terms in the Order, the terms in the Order prevail." It also characterizes the obligations as an effort "to crystalize LiveRamp's longstanding commitments" and says that "As LiveRamp has always done, without explicit permission from you, LiveRamp will not allow others, including Publicis, to access or use the confidential business information you provide to LiveRamp."

Mediation

Section VI covers disputes. For "any contractual dispute with a LiveRamp Customer arising from or relating to noncompliance with this Order that has not been resolved within 30 days," the companies must notify FTC staff, identify the customer and submit the relevant contract. If the dispute remains unresolved 30 days after that notification, or 30 days after staff tell the companies that a third party has raised it, the companies must "engage in third-party mediation with an accredited mediator." Whether the dispute counts as unresolved is "in the LiveRamp Customer's discretion."

The addendum adds an earlier step not found in the order body: a customer may escalate a dispute to Publicis's Chief Compliance Officer, who must have it investigated "in no longer than a one month time period after notice," before mediation before "an independent mutually selected mediator."

Reports to the FTC

Section VII requires Publicis to email the FTC compliance team with the acquisition date "no later than 5 days after its occurrence." Within 60 days of closing, the companies must adopt written policies on the non-discrimination provisions and submit them, together with written procedures for the Section III firewall. Verified compliance reports are due 45 and 90 days after the order is issued, one year after issuance, and "annually for the next 4 years on the anniversary of that date." Each report must be verified by the chief executive or another authorized officer, and "conclusory statements that Respondents have complied with their obligations under this Order are insufficient."

Section VIII requires 30 days' notice before any dissolution, acquisition, merger or consolidation of Publicis Groupe S.A., or other changes that may affect compliance.

Duration: two different clocks

The press release says Publicis and LiveRamp are bound "for five years." Section XI of the order states that it "shall terminate 5 years from the date it is issued." The customer addendum, by contrast, provides commitments that "will remain available to you for a period of five (5) years from the Closing Date." The two clocks start at different events. If the deal closes after the order is issued, the contractual commitments would outlast the order itself by the gap between the two dates.

The audit schedule shows a similar wrinkle. The press release says audits run "every six months for the first two years after the date that the proposed transaction closes, and then once a year thereafter for the following three years." The order text says "once a year for every year thereafter" without a stated end, leaving the termination clause to cap it.

What the documents leave out

Several points that matter for the market are absent from the two documents.

The closing date is not given. The order defines the "Acquisition Date" as the date the companies "consummate the Acquisition," without saying when that will be. PPC Land reported in May that Publicis expected to close before the end of 2026, subject to regulatory approvals and a LiveRamp shareholder vote; LiveRamp shareholders were scheduled to vote on August 17, 2026. Neither FTC document mentions the shareholder vote or any other regulator.

The order is not final. The copy supplied leaves the docket number as "C-" and the "ISSUED" line blank, consistent with a proposed order awaiting public comment. The 60-day notice deadline and the five-year term both run from issuance, so neither has started.

The comment window has no fixed end date in the documents. According to the FTC, "The public will have 30 days to submit comments on the proposed consent agreement package," with instructions on the docket and comments posted on Regulations.gov once processed.

The Order to Maintain Assets, referenced several times in the Decision and Order, was not among the documents. Nor was the complaint, so the market definitions, market shares and any evidence behind the FTC's allegations cannot be assessed here.

Epsilon is named in the press release but nowhere in the order. The definition of Publicis covers its "agencies, media, data, consulting, or advertising businesses," which would include Epsilon, but the order imposes no Epsilon-specific obligation.

One product commitment sits only in the addendum. Under the heading "Product Development," the addendum states that "Publicis is fully committed to the continuation of LiveRamp's existing product roadmap (including any roadmaps for existing clients) and to the development of the new products or services that are already in LiveRamp's development pipeline," subject to ordinary course adjustments. The order body contains no equivalent paragraph, although it requires the addendum to be added to every contract.

A smaller inconsistency appears in the customer letter, which lists an FTC contact as "Ben Lorigo" with the email address "slorigo@ftc.gov."

Why this matters for the market

The order addresses a question that has followed the deal since May: whether an agency holding company can own the data plumbing that its competitors use. LiveRamp's customer list made the question unavoidable. PPC Land's review of the SEC filings in June found 846 direct customers, including WPP, Omnicom-IPG, Dentsu, Havas and Stagwell - Publicis's main rivals. The same filings set out neutrality pledges, with Publicis stating that it, Epsilon or any other party could not access customer data without the owner's explicit permission. The FTC order converts those voluntary statements into enforceable obligations with reporting, audits and customer contract terms.

Not every rival waited for that outcome. PPC Land reported in May that Omnicom, which had planned to exit its LiveRamp contract in the first quarter of 2028, planned to leave sooner after the deal and is building its own identity product through Acxiom. Whether a five-year order changes that calculation is an open question; the order cannot compel any rival to stay.

For the large agency groups, this is the second time in 13 months that an FTC merger order has reshaped a holding company deal. The Omnicom-IPG order focused on ad placement decisions tied to political viewpoints. The Publicis order is about data access and commercial neutrality, a more traditional antitrust concern. Publicis was also one of three agency groups named in the FTC's April 2026 brand safety collusion case, which was resolved through a proposed consent order.

For advertisers, publishers and retail media networks that use LiveRamp, the practical effect is contractual. Every US customer contract is to be amended with a 14-section addendum covering neutral operation, non-discrimination, client choice, clean room and ATS protections, data protection, information safeguards, interoperability, governance, audits and dispute resolution. LiveRamp's clean room has become infrastructure for retail media measurement, commerce media platforms such as DoorDash and, from September 2026, out-of-home measurement with Clear Channel. Those relationships now carry written guarantees on access controls and auditability.

The order also has limits. It protects standalone products, not integrated products Publicis builds with LiveRamp, and Publicis "will be free to choose" who gets those. It lets LiveRamp drop integrations with parties that refuse its standard terms. It relies on auditors engaged by the companies themselves. And it lasts five years, after which the obligations fall away unless the FTC acts again.

The identity business LiveRamp operates is also under pressure from outside antitrust. Two LiveRamp domains appeared on the list of requests Apple's Safari began blocking in iOS 27, as PPC Land reported on September 30. The FTC order secures neutral access to LiveRamp; it says nothing about whether the browsers that carry its identifiers will allow them to function.

Timeline

Summary

Who: The Federal Trade Commission, with Chairman Andrew N. Ferguson and Commissioner Mark R. Meador voting; Publicis Groupe S.A., its acquisition vehicle MMS USA Holdings, and LiveRamp Holdings, Inc.

What: A proposed consent order allowing Publicis to acquire LiveRamp, in a deal the FTC values at $2.2 billion, on condition that LiveRamp operates as a neutral provider to all US customers, that Publicis is barred from accessing or using LiveRamp customer data, and that compliance is checked by independent SOC-2 audits, customer audit rights, mediation and compliance reports. No business is divested.

When: The FTC press release is dated October 19, 2026. A 30-day public comment period follows. The order lasts five years from issuance, while the customer contract addendum runs five years from closing. No closing date is given.

Where: The order covers LiveRamp's US business activities; Publicis is based in Paris and LiveRamp in San Francisco.

Why: The FTC alleged that the combination would let Publicis use LiveRamp to push rival agencies' clients to switch, degrade services competitors rely on and gain access to competitively sensitive data of non-Publicis clients, harming competition in media agency services and audience data services in violation of Section 7 of the Clayton Act.