Podcast episode
Episode 175: Tejas Manohar, co-CEO of Hightouch, on the Company's Giant Fundraise, Agentic Ads, and LiveRamp - Marketecture Podcast
Tejas Manohar, co-CEO of Hightouch, came on Marketecture to wave a fresh $2.75 billion valuation around, but the load-bearing claim wasn't the money — it was that his warehouse-native tool can now drop in and replace LiveRamp's identity onboarding with "equivalent or better performance." The timing is no accident: LiveRamp is being absorbed into Publicis, which hands every rival agency and independent publisher a reason to look for an exit, and Hightouch is sprinting through that opening. Manohar's pitch is that customer data already lives in Snowflake, so why copy it into yet another vendor silo just to push audiences to Meta, Google, and CTV. He stacks "300 integrations" and agentic campaigns that launch end to end on top, then argues AGI is basically here and the only gap is enterprise context. It's a tidy thesis, and conveniently the answer to "who owns the context layer" is him. The "equivalent graph assembled from best-of-breed partners," though, is marketing on a podcast, not a benchmark.
Here's the contradiction worth flagging: LiveRamp's moat was never the code — it was the offline-to-online graph and the reach of being everywhere. Assembling an "equivalent" version from third-party sources means renting the same match data everyone else can rent, which is a reseller agreement, not a moat. And the forward-deployed services team Manohar brags about is a tell — if the self-serve agentic product could actually run unattended, you wouldn't need consultants in the room, so you may be buying managed services dressed as software. For operators, the move is to treat the LiveRamp-replacement claim as credible negotiating leverage and an unproven product, not a rip-and-replace decision: demand a head-to-head match-rate test on your own data, and ask how much of that "equivalent graph" is licensed on terms available to literally everyone. The durable signal underneath the noise is that standalone onboarding is collapsing into a warehouse feature priced against the cloud bill you already pay, while the real prize migrates upstream to the governed context layer that feeds AI agents — and nobody on this episode wanted to dwell on the privacy and consent-propagation mess of letting agents act on all your customer data at once.
Full analysis
Decision Council — Briefing Mode
Step 1 — Frame
The load-bearing story here isn't the funding round — it's the claim that a warehouse-native data tool can now drop in and replace LiveRamp's identity onboarding, and that it's doing so precisely as LiveRamp gets absorbed into Publicis (an agency holding company). The episode's secondary thread — AI agents that run campaigns end to end — points at where the activation layer is heading. The AppLovin/Meta/X/ChatGPT-ads items are texture, not signal.
So the real question for an ad-tech operator: Is identity onboarding — translating a publisher's or advertiser's hashed emails and phone numbers into ad-platform IDs — becoming a commodity feature that sits on top of the cloud warehouse you already pay for, rather than a standalone product you buy from a specialist?
- Reversibility: Type 2 for any one buyer (you can switch onboarding vendors). Type 1 for the market structure — once onboarding collapses into the warehouse, the standalone-vendor business model doesn't come back.
- What's actually being decided: Where the "activation layer" — the thing that pushes audiences out to Meta, Google, Amazon, Trade Desk, CTV — lives. In a specialist vendor, or as a thin app on top of Snowflake/Databricks.
- Forcing function: The LiveRamp/Publicis deal. Every LiveRamp customer who is also a Publicis competitor now has a reason to look for an exit. That's the opening Hightouch is sprinting through.
Step 2 — The Council
The Skeptic The load-bearing claim is "equivalent or better performance than LiveRamp." That's marketing on a podcast, not a benchmark. LiveRamp's moat was never the code — it was the offline-to-online graph built from years of CRM data partnerships and the reach of being everywhere on the buy and sell side. Saying you "assembled an equivalent graph from best-of-breed partners" means you're renting match data from the same handful of identity sources everyone rents from. That's not a moat, that's a reseller agreement. Plainly: replacing the plumbing is easy; replacing the address book of who-matches-to-whom is the hard part, and that's mostly licensed, not built.
The Operator Tuesday morning, the appeal is real: if your customer data already lives in Snowflake, not copying it into yet another vendor silo saves a genuine integration headache and a data-governance fight with your security team. That's why warehouse-native tools win deals. But "300 integrations" and "agentic campaign launch" break at the edges — every ad platform's API has quirks, throttling, and audience-match minimums. The 90-day surprise: the forward-deployed services team Manohar brags about is there because the self-serve product can't actually run unattended. You're buying consulting dressed as software.
The CFO Watch the economics, not the valuation. $2.75B on roughly weeks-old revenue means the price assumes Hightouch eats a big chunk of the onboarding and CDP market — that's a bet, not a fact. For buyers, the math is what matters: onboarding as a feature on top of warehouse spend you already committed to is cheaper than a standalone six-figure LiveRamp contract. That's the squeeze. Plainly: the cost of moving customer data around is collapsing toward the cost of the cloud bill you already pay. Margin in standalone identity onboarding is heading down across the board.
The Long-Term Thinker Three years out, this episode looks like a marker for two convergences. First, the CDP, the identity onboarder, and the activation tool merge into one warehouse-resident layer — bad news for any vendor whose only job is one of those three. Second, the "agent needs structured context, not raw API access" argument is the durable insight. Whoever owns the context layer — the curated, governed, embedded version of a company's data that agents can safely act on — owns the next decade of ad activation. That's a more defensible position than onboarding ever was, and it's where the real fight will be.
Step 3 — Tensions
-
Skeptic vs. Operator on the moat. Is warehouse-native onboarding a real LiveRamp killer, or a thin layer over the same rented match data, propped up by a services team? If it's mostly rented graph + consulting, LiveRamp-inside-Publicis can compete on the same terms.
-
CFO vs. Long-Term Thinker on where value goes. The CFO sees onboarding margins compressing toward zero — a race to the bottom. The Long-Term Thinker says the money simply moves upstream to the "context layer" for AI agents. Both can be true: the old business commoditizes while a new one forms on top.
-
The "AGI is here, context is the problem" claim. If Manohar is right that the models are good enough and the only gap is enterprise context, then the winner is whoever controls the data plumbing — which conveniently is him. If he's wrong, agentic campaign management stays a demo that needs humans to babysit it, and the moat reverts to graph and reach.
Step 4 — Synthesis
What this hinges on:
- Whether identity onboarding is genuinely commoditizing (it is — warehouse-native delivery plus a decaying cookie-based RampID makes the standalone product less special) or whether LiveRamp's reach and partnerships still matter more than the tech (they do, for now, especially inside Publicis's media machine).
- Whether the value is migrating to the agent context layer — the answer the whole episode keeps circling back to.
Which way the council leans: Toward "the standalone onboarding business is structurally weakening, and the next prize is the governed data layer that feeds AI agents." The Publicis acquisition accelerates this by giving every rival agency and independent a reason to find a LiveRamp alternative.
What this means for the reader, by seat:
- Identity/measurement vendors (LiveRamp peers, the graph providers): your standalone onboarding line is under real pressure. Reposition around the context-and-governance layer or risk becoming a wholesale match-data supplier to the warehouse apps that own the customer.
- Publishers and advertisers: you have more leverage and more exit options than a year ago. If your data is already in a cloud warehouse, pressure-test whether you still need a standalone onboarder — but demand a head-to-head match-rate test before believing the "equivalent or better" pitch.
- Agencies (non-Publicis): the LiveRamp deal is a conflict-of-interest gift to Hightouch and anyone like it. Expect a wave of "neutral alternative to a competitor-owned vendor" pitches.
- DSPs/SSPs and CTV platforms: the activation layer consolidating into the warehouse means your integration partner list shrinks toward whoever owns that layer. Make sure you're a first-class integration, not an afterthought.
What to verify before acting:
- Get an actual match-rate and addressable-reach test against LiveRamp on your own data. The performance claim is unproven.
- Find out how much of the "equivalent graph" is rented from third parties — and whether those licenses are exclusive or available to everyone (they're probably available to everyone, which kills the moat).
- Separate the software from the forward-deployed services. If the agentic product only works with a vendor team in the room, you're buying a managed service, and you should price and staff accordingly.
My view: The funding round is noise; the signal is that onboarding is becoming a warehouse feature and the durable prize is the governed context layer for AI agents. Treat the LiveRamp-replacement claim as a credible threat to the incumbent but an unproven product — useful as negotiating leverage today, not as a rip-and-replace decision yet. Low individual-deal risk, high market-structure significance.
What did we miss? Is there a persona we should add for this specific decision? A General Counsel lens might be worth adding — warehouse-native activation and "embed all your customer data for agents to act on" raises real privacy, data-residency, and consent-propagation questions, especially under state privacy laws and for any data crossing into AI-agent workflows.