Podcast episode
I Have a Thesis
dsp measurement programmatic publisher-economics
TL;DR
Adam Heimlich and Gareth Glaser use this episode to articulate the founding theses behind their respective companies — Chalice (buy-side custom algorithm platform) and Gamera (neutral inventory-labeling data vendor) — arguing that programmatic's original promise of accurate, per-impression valuation was never delivered, and that the market is now paying the consequences. They close with a sharp read on Omnicom CEO John Wren's evasive answer about AI savings and on Meta vs. Microsoft capex market reception.
What was covered
- Adam Heimlich's "Two Architectures" thesis: Enterprise advertisers require bespoke, per-advertiser AI stacks built on their own data; pooling many advertisers under one algorithm (as most DSPs, demand-side platforms, do today) drives competitive bidding concentration, erodes brand equity, and slows growth. Chalice is the embodiment of the per-advertiser architecture.
- Gareth Glaser's "Trust in Programmatic" thesis: Publisher-defined fields in the bid stream — IAB categories, placement IDs (including GPIDs, global placement identifiers standardized by The Trade Desk), seller-defined audiences — have no enforcement mechanism, are routinely gamed, and cannot be trusted. Gamera's pitch is a neutral, zero-trust, on-page JavaScript signal layer that objectively labels inventory without publisher manipulation.
- Why publishers game fields: Adam and Gareth argue it is a rational prisoners'-dilemma response to pooled DSP algorithms that concentrate bids on a small slice of inventory, leaving most impressions unfilled. Publishers manipulate metadata to attract the bids that pooled systems prefer, not because inventory genuinely qualifies.
- Curation origins and mechanics: Gareth traces curation to AppNexus, where a trader discovered the SSP (supply-side platform) side of AppNexus's unified system could be used to run per-campaign inventory optimization — effectively beating the DSP's pooled algorithm with advertiser-specific selection. He argues curation works because it is per-advertiser, not because publisher data is inherently valuable.
- Data vs. measurement vs. optimization: Adam asserts Chalice uniquely scores empirical page metrics (network calls, refresh rates, add-to-content ratio) against per-advertiser outcome data to derive cost-per-value. He singles out attention vendors as a "half-baked" blend of measurement and optimization that would be stronger if each function were separated.
- Oracle/Moat brand safety vacuum: Gareth notes that when Oracle deprecated Moat, publishers — especially news publishers managing dozens of local sites — lost the only active brand-safety monitoring tool available to them. DoubleVerify (DV) and Integral Ad Science (IAS) exist but serve buyers, not publishers, leaving a gap Gamera is now filling with free publisher-side reporting.
- Omnicom earnings / John Wren punt: When an analyst asked whether AI efficiency gains at Omnicom flow to the agency or back to clients, CEO John Wren declined to answer directly. Adam and Gareth read this as a sign that multi-year internal AI build claims are likely hollow — agencies are probably just repackaging generic tools from Google and Microsoft.
- Meta vs. Microsoft capex framing (via Ian Whitaker): Microsoft's heavy compute investment is rewarded by the market because Microsoft sells compute; Meta's comparable investment is penalized because Meta sells advertising outcomes, and the market remains skeptical that more compute translates linearly into an unassailable advertising moat.
Notable claims & predictions
- Adam Heimlich: "The scaled software for an AI application for enterprise advertisers is different at the core from what we'd call pooled stack… you cannot build one tool that does both." He ties slowing brand growth and brand equity erosion since the traditional-media era directly to the industry's failure to separate these architectures.
- Gareth Glaser on seller-defined fields: "When the architecture says that anyone can make up whatever they want and put it in these fields, the notion that these fields will have any utility whatsoever is a troubled one." He frames the entire seller-defined-audiences spec as architecturally broken by design.
- Adam Heimlich on attention vendors: "I think that attention is really better than viewability as a goal… but the only way that it's valuable is if you can prove that it correlates to something — and if you're proving that, why not just correlate the things that created attention to the thing?" He argues attention metrics are an unnecessary proxy once you have outcome data.
- Adam Heimlich on agency AI claims: "I think at least some of them are not really building internally any tools… relying on Google, Microsoft and some others to give them something that looks unique but just won't be custom-built for the agency or its clients." He frames the six-year internal-build narrative as a multi-year can-kick with no disclosed milestones.
- Gareth Glaser on programmatic's failed promise: "The original promise of programmatic was we're going to atomize all of these things and apply algorithms to them to do bidding and valuation that's super accurate — that shit just didn't occur… and that's why we have this huge turn away from programmatic."
- Adam Heimlich on Claude/LLMs replacing custom ad-tech builds: Dismissing the agency exec view that "Claude's gonna be able to do the same thing next year," he says: "The number of parameters we're dealing with and the execution pieces are way beyond anything Claude does — it's a different family of problems."
Fact check
- Gareth Glaser on GPID origins: Gareth says GPID "was invented by The Trade Desk trying to standardize this in the open-sourcing pre-bid," and that the original use case was to deduplicate AdX traffic. The GPID spec was developed within the Prebid community with Trade Desk involvement, but attribution of full invention to The Trade Desk is contested; it was a collaborative Prebid initiative. Gareth himself then partially corrects his own framing, noting an earlier related object called
pbAdSlotoriginated on his own product team. The "invented by The Trade Desk" framing is simplified to the point of being misleading — Trade Desk was influential but GPID is a Prebid community standard, not a Trade Desk proprietary invention. - Gareth Glaser on Moat deprecation leaving publishers without brand safety tools: Gareth states that after Oracle deprecated Moat, "basically no tools" exist for publishers to actively monitor brand safety violations on their own pages. This is contested/incomplete — IAS and DV both offer publisher-side monitoring products, and several independent vendors (Confiant, Protected Media, others) provide publisher-focused safety tools. The gap Gareth describes is real but likely overstated; he may be narrowing the claim to free, proactive, placement-level monitoring specifically, which is a narrower and more defensible point.
- Adam Heimlich framing agencies as relying on Google/Microsoft tools: This is presented as a factual assertion but is unverified and frankly self-serving — Chalice is a direct competitor to agency in-house tools. No evidence is provided; the claim rests entirely on inference from Wren's non-answer on an earnings call. Readers should weight it accordingly.
- Ian Whitaker's Meta/Microsoft capex read (as relayed by Adam): The characterization that Meta stock went down and Microsoft's went up post-earnings on this specific capex dynamic is directionally consistent with market coverage from the relevant earnings cycle, but the episode does not provide dates or precise figures. The framing is plausible but unverified from the transcript alone.
Full analysis
Two founders spent an hour arguing that programmatic never delivered on its founding promise: accurate, per-impression valuation. Adam Heimlich (Chalice) says the fix is per-advertiser algorithms instead of pooled ones. Gareth Glaser (Gamera) says the fix is a neutral, on-page signal layer that publishers can't game. Both are pitching their own book, but the diagnosis underneath is worth taking seriously.
What's actually being decided for an operator: whether the "pooled DSP algorithm" and the "trust the bid-stream fields" era is genuinely ending, and whether you should reallocate budget, roadmap, or vendor spend toward custom bidding and independent inventory labeling. This is a Type 2 decision for most: you can run a pilot, measure, and walk away. Cheap to test, so the bar for deliberation is low and the bar for action is also low.
Timeline / forcing function: none hard. The John Wren non-answer and the Meta/Microsoft capex split are the timely hooks, but the theses themselves are slow-burn. No renewal clock forces your hand this quarter.
The Market Analyst Two vendors both backed by The Trade Desk are on a podcast explaining why the incumbent DSP model is broken. Read the incentives and it still holds up: Trade Desk is the one large buy-side platform whose pitch has always been "we're on your side, not the pool's," so custom algorithms and neutral labeling feed its narrative against Google and Amazon. For an operator, the plain-English version: the money is starting to bet that generic, one-size-fits-all bidding loses to advertiser-specific bidding. The Meta-versus-Microsoft point Ian Whitaker made is the tell for the whole space. Microsoft gets paid for compute because it resells it; Meta gets punished because nobody believes more GPUs automatically buy a bigger ad moat. That skepticism is coming for agency AI claims next.
The Skeptic Steelman the case against these two, because they're selling. Heimlich asserts agencies build nothing and just repackage Google and Microsoft tools. His evidence is one evasive earnings answer. That's inference dressed as fact, and Chalice competes directly with agency in-house stacks, so weight it accordingly. Glaser's claim that Moat's death left publishers with "basically no tools" is overstated. IAS and DV run publisher-side products, and Confiant and others exist. The defensible version is narrower: free, proactive, placement-level monitoring is thin. Fine, but "narrower and more defensible" is not the headline they sold. The theses are directionally interesting. The specifics are self-serving.
The Operator Strip the theory and ask what breaks Tuesday morning. The prisoners'-dilemma read on why publishers game fields is the most useful thing in the episode: pooled algorithms concentrate bids on a thin slice of inventory, so publishers manipulate metadata to look like that slice. If you run a supply business, you already know this. You do it because your fill depends on it. A neutral on-page signal layer only helps you if buyers actually bid off it, and today they don't. So a publisher adopting Gamera-style labeling is betting on a demand-side behavior change that hasn't happened yet. On the buy side, custom algorithms are real work: your own outcome data, your own page metrics, your own maintenance. Not a switch you flip.
The Customer / End User For the advertiser, the per-advertiser architecture argument lands. If your bidding is pooled with fifty other brands chasing the same "premium" impressions, you're bidding against yourself and eroding your own brand equity. Heimlich ties slowing brand growth to exactly this. In plain terms: shared algorithms make everyone chase the same inventory, which raises what you pay and narrows what you reach. But the advertiser has to supply clean outcome data to make a custom stack work, and most don't have it organized. The attention-vendor swipe is the honest bit here. If you can correlate what created attention directly to outcomes, you don't need attention as a middle metric at all.
The CFO Custom-per-advertiser sounds great until you price the labor. Pooled algorithms exist because they're cheap to run across many accounts. Bespoke stacks mean per-advertiser build and upkeep, which is why this stayed a niche for years. The payback only works for advertisers big enough to amortize that cost against real budget, which is the enterprise tier Heimlich names. For everyone else the math doesn't clear. On the publisher side, Gamera is free, so the cost question flips: what's the opportunity cost of exposing objective labels that might rate your inventory lower than the fields you currently set yourself? That's a revenue risk, not a line item.
The tensions:
Heimlich and Glaser agree programmatic's valuation promise failed, but they disagree on the cure. Heimlich says fix the buy side with custom algorithms. Glaser says fix the signal by making inventory labels un-gameable. Those are different bets. One says the demand side is broken, the other says the supply signal is.
The Operator and the Customer split on feasibility. The advertiser wants per-advertiser bidding; the operator points out it requires clean first-party outcome data most brands haven't organized. The thesis is right and unusable at the same time for most of the market.
The Skeptic and the Market Analyst split on how much to trust the messengers. The money is genuinely moving toward custom and neutral. The men describing that move happen to sell both, and both are funded by the same DSP.
What it hinges on: whether buyers actually change behavior. Both theses die if demand keeps rewarding gamed fields and pooled bidding. Custom algorithms only pay off for advertisers with organized outcome data and budget to amortize the build. Neutral labeling only pays off if buyers bid off it. The council leans toward the diagnosis being correct and the timeline being slower than either founder implies. Test it cheaply: if you're a large advertiser, run one custom-algorithm pilot against your pooled baseline on your own conversion data. If you're a publisher, sample the free labeling before you expose it programmatically, and see whether your metadata survives contact with an objective read.
Prediction: At Omnicom's next two quarterly earnings calls through Q1 2027, John Wren or his CFO will again decline to disclose a specific split of AI efficiency gains between agency margin and client savings.
Confidence: Medium. Agencies have every incentive to keep the AI margin question vague.
Why: Wren already punted once when an analyst asked directly, and the reason is structural: if Omnicom admits AI savings flow to margin, clients demand price cuts; if it admits savings flow to clients, investors question the growth story. There's no answer that helps both audiences, so the rational move is to keep repackaging generic capability as proprietary build without disclosing milestones. The opposite outcome, a clean numeric disclosure, only happens if a competitor forces it or a client contract makes it public, and neither pressure is visible yet. The pending Omnicom-IPG integration gives Wren even more reason to stay vague, not less.
Revisit by 2027-02-28: We're right if Omnicom's next two earnings calls contain no specific agency-versus-client AI savings split. We're wrong if leadership quantifies where the AI efficiency goes.
Comments