The FTC's LiveRamp Order Keeps the Old Products Neutral. New Publicis Integrations Sit Outside It.

The FTC cleared Publicis Groupe’s purchase of LiveRamp on the theory that LiveRamp can stay neutral under a new owner. Two of Publicis’s biggest rivals, according to Marketing Dive, aren’t waiting to find out. WPP is winding down its agencies’ use of LiveRamp, and Omnicom moved up an exit it was already planning [4].

That’s the tension in this one. The order is written for the customers who stay.

What the FTC signed off on

On October 19 the Commission voted 2-0 to issue a complaint and accept a proposed consent agreement for public comment [3]. The proposed order lists two commissioners, Chairman Andrew Ferguson and Mark Meador [2]. The analysis ran in the Federal Register on October 23 [1].

The deal: Publicis agreed on May 16, 2026 to buy LiveRamp in an all-cash transaction valued at about $2.2 billion [1]. Publicis is one of the five big advertising holding companies, with WPP, Omnicom, Dentsu and Havas, and it also sells third-party audience data through its subsidiary Epsilon [1]. LiveRamp is the plumbing between them. The FTC calls it “the leading data connectivity provider in the U.S. media marketing ecosystem,” with more integrations than any other provider, covering onboarding, identity graphs, identity resolution and clean rooms [1].

The complaint alleges harm in two U.S. markets, media agency services and audience data services, under Section 7 of the Clayton Act and Section 5 of the FTC Act [1]. The worry is simple. If Epsilon’s competitors move their data through LiveRamp, Publicis could see their pricing and campaign data, or degrade their access and raise their costs [1]. Agency clients of rival holding companies could feel pressure to switch to Publicis to avoid having their data appropriated [1].

There’s no divestiture. The fix is a set of conduct rules that run for five years [1, 2].

“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 [4]. Publicis called it “a mutually acceptable agreement” built on “commitments proactively proposed by the Groupe,” and said it still expects to close before the end of the year [5].

What the order actually requires

I read the 11-page order and both appendices. The main duties [2]:

• No discrimination. LiveRamp customers get “equivalent access to LiveRamp standalone products, services, APIs, technical support, and commercial programs” on fair, reasonable and non-discriminatory terms, whether or not they buy from Publicis (Paragraph II.C).
• No tying. Publicis can’t make LiveRamp access depend on buying its customer data platforms, data services, media activation or creative work (II.F), and can’t condition pricing, roadmap priorities or support on a customer agreeing to share information with Publicis (II.J).
• Clean rooms stay customer-controlled. Customers keep control over roles, content-level permissions and privacy settings, plus continuous audit logs with a year of supporting records on request (II.G).
• Data firewall. Publicis “shall not access, or otherwise use LiveRamp Customer data held by LiveRamp,” and that data can’t be “used to develop, train, or improve products and services offered by Publicis,” enforced by access controls, logical separation and access logging (III.A).
• No retaliation against a customer who talks to FTC staff about compliance (II.L).

Audits come every six months for two years after closing, then yearly, from a provider that routinely does SOC 2 audits, with copies to the FTC [2]. Within 60 days of the order issuing, Publicis has to send every LiveRamp customer a letter and amend every customer contract with a standard addendum [2].

Where are the gaps in the LiveRamp neutrality order?

This section is opinion.

The neutrality applies to what exists. The duties attach to LiveRamp’s “standalone” products. Then comes the proviso in II.D: nothing stops Publicis “from developing with LiveRamp new products and services that integrate LiveRamp products and services with the products and services of Publicis,” and Publicis “will be free to choose to which customers it will offer such new integrated products and services” [2]. Publicis sees the deal partly as a way to improve the AI agents it builds for clients, according to Marketing Dive [4]. If the valuable new features ship as integrated products, the order doesn’t reach them. The standalone catalog stays neutral while the roadmap that matters moves somewhere else. I could be wrong about how this plays out. The text allows it.

“Security or compliance risk” is doing a lot of work. LiveRamp has to support interoperability with third-party platforms, but it can drop an integration where the counterparty “presents a security or compliance risk,” declines LiveRamp’s standard data-protection terms, or “fails to provide reciprocal technical cooperation” (II.I) [2]. Those are reasonable reasons to cut off a partner. They’re also judgments LiveRamp makes first, and the order doesn’t say who reviews them.

The training ban is the part I’d copy. Most data-protection promises stop at “we won’t share it.” This one says the data can’t be used to train or improve the acquirer’s products, and it backs that with access logging that an outside auditor checks [2]. Read II.J next to it. A customer’s refusal to authorize sharing can’t cost it on price or support [2]. Consent that’s free to withhold is the only kind worth having.

Getting a dispute resolved takes a while. A dispute that goes unresolved for 30 days gets reported to FTC staff. If it’s still open 30 days after that, the customer can push it to mediation [2]. The contract addendum adds a route through Publicis’s chief compliance officer, who gets up to a month [2]. That’s two months or more before anyone neutral looks at it. For a startup whose integration got slower, two months is a long time.

Two clocks, two audit scopes. The order ends five years after it issues; the customer addendum runs five years from closing [2]. And the FTC’s published analysis says customers can request an audit of compliance “with the Order’s obligations for that customer” [1], while the order itself limits the customer-requested audit to data protection, privacy and security obligations, at the customer’s expense [2]. If you were counting on a customer audit of discrimination, the order’s text doesn’t give you one.

If you build on LiveRamp

If you’re an ad-tech vendor, a clean-room partner or a publisher using LiveRamp’s identity tools, the addendum is the document to read, since it becomes part of your contract [2]. Three things I’d do:

1. Write down what your integration does today, including latency, API access and support response times. “Deny, degrade, delay” is only enforceable against a baseline you can show.
2. Check what you’ve authorized LiveRamp to share. The data protections in Section III switch off when the customer “expressly” authorizes sharing [2].
3. Decide whether the comment period is worth your time. The FTC can still change the order before it’s final [1].

This is the second FTC ad-tech item I’ve written about this month, after the impersonation rule proposal aimed at ad tools.

What I’m watching

• November 23. Comments are due on File No. 261 0115 [1]. Whether rival agencies or data vendors file, and whether anyone asks the FTC to bring integrated products inside the order, will show how much the industry trusts a behavioral remedy.
• Closing. Publicis expects to close before year-end [5]. The first audit window, the customer letters and the contract addendum all start from closing or from the order’s issue date [2].
• The exits. WPP and Omnicom leaving would shrink the rival-agency customer base the order is meant to protect [4]. What I don’t know yet is whether other customers follow or stay for the contract terms.