00The week in one paragraph
This was the week the open web’s reckoning stopped being a forecast and became a balance sheet. In seven days: CNN became the first TV network to sue an AI answer engine, accusing Perplexity of scraping 17,000+ stories — and publishers flatly rejected Perplexity’s “trust” pitch; fresh Piano benchmark data put hard numbers on the damage (search traffic −36%, revenue −16%, click-through −61% on AI-Overview queries), pushing publishers to pay for traffic they once got free; IAB Tech Lab opened bot-management guidance for comment while Microsoft told publishers the opposite — don’t block the bots; AdExchanger argued the agentic stack (MCP + AdCP + IAB’s AAMP registry) is the first architecture in 20 years that could let the open market rival the giants; Omnicom confirmed live agent-to-agent buys to cut the ad-tech middle as PubMatic’s AgenticOS scaled; Amazon compressed its flywheel into June (Prime Day to June 23–26, Dynamic TV Creative, a ~90%-reach DSP); Netflix wired Amazon and Yahoo data into its CTV stack; Disney finished folding Hulu into Disney+; Google’s ad-tech remedies neared a decision on whether AdX/DFP gets broken up; and IAB stacked two more comment deadlines (Campaign Data Standards June 14, TCF v5.0-B June 29). One thread ties it together: AI answer engines are draining the open web’s traffic, an agentic ad stack is being rebuilt around publishers, and the courts and standards bodies are writing the rules right now — in public comment windows most publishers will ignore. The ones who show up this quarter keep a seat. The ones who don’t will find the rules, the toll, and the traffic all set without them.
01CNN sues Perplexity — and the “trust” pitch falls flat
On May 28, CNN sued Perplexity (S.D.N.Y.), alleging it scraped 17,000+ stories, photos, and videos — CNN’s first AI copyright action and reportedly the first by any TV network. Talks collapsed in 2025, CNN blocked Perplexity’s crawler, and the suit says access continued anyway. Perplexity’s retort: “You can’t copyright facts.” It joins suits from the NYT and Chicago Tribune. Days later, Perplexity’s “trust and transparency” pitch to publishers — clearer attribution, traffic-sharing — drew a cold reception (Digiday).
Publisher takeaway
This is the clearest test yet of whether copyright holds the line in the answer-engine era. Inventory what AI engines are citing and reproducing, decide your posture by content type (license/block/litigate), and don’t trade compensation for attribution. Litigation is what brings AI companies to the licensing table — negotiate from strength while the pressure works.
02The AI search reckoning is now in the numbers
Piano’s benchmark across hundreds of publisher sites: search traffic −36%, revenue −16%, total audience −9%, with organic CTR down ~61% where a Google AI Overview appears. Individual publishers report losses of 20–90% over the past year; some have shut down. Media leaders expect search to fall another ~43% within three years. The workaround: publishers are paying for traffic they used to get free — and the same AI reducing referrals is making paid acquisition cheaper. One exec: “It’s not super sustainable.”
Publisher takeaway
Re-baseline your plan around a structurally lower, permanent search number. Treat paid acquisition as a measured experiment with margin tracked per acquired reader, not a faucet. Shift the mix toward owned and direct — newsletters, registration, apps, loyalty — the only audiences AI search can’t intermediate. And use the traffic-loss data as evidence in AI licensing talks (see #1).
03“Block or don’t block?” — IAB Tech Lab’s bot guidance meets Microsoft’s pushback
On May 27, IAB Tech Lab released bot- and crawler-management guidance for public comment (through June 26), built to pair with the CoMP API — giving publishers granular, machine-readable, auditable control over AI-crawler access instead of a blunt robots.txt. Almost simultaneously, Microsoft told publishers not to block AI bots, arguing visibility inside AI answers is now a primary discovery channel.
Publisher takeaway
The binary is the trap — block and you vanish from AI discovery; allow and you feed the engines eating your traffic. The standards exist to create a third path: conditional, priced, auditable access. That’s what turns “you scraped us” into a documented violation (relevant to #1) and “let us crawl you” into a metered licensing conversation. File a comment before June 26, audit which agents access what today, and segment content by where visibility pays vs. where attention pays.
04From open internet to open agent — AAMP, AdCP, and the standards landscape
AdExchanger’s June 1 essay argued the agentic stack is the first architecture in 20 years that could let the open market rival the walled gardens: MCP underneath, AdCP on top, IAB Tech Lab’s AAMP-style governance and agent registry wrapping it. A brief enters via an AdCP-native agent — “a front door that is a protocol, not a platform” — negotiating deal terms agent-to-agent in hours, validating brand safety in-flight, and surfacing clearing prices transparently. AdCP is the coalition protocol (Yahoo, PubMatic, Magnite, Scope3, +20) built on Anthropic’s MCP; AAMP is IAB Tech Lab’s umbrella (execution, protocols, agent registry as the “trust layer”).
Publisher takeaway
Whoever owns the protocol owns the terms. Transparent clearing prices and agent-to-agent deals are, for once, a structural win for sellers — and the registry deciding which agents can transact is a gate you want a say in. Get literate on both stacks, ask your SSPs where they stand, and engage with the IAB process while the rules are being written.
05The disintermediation trade — holdcos go agent-to-agent, SSPs ship operating systems
On the buy side, Omnicom confirmed it has already executed live agent-to-agent media buys for several clients, with the explicit objective of diminishing DSPs’/SSPs’ role “and, with it, the cut they take”; WPP Open has crossed 75,000+ users. On the sell side, PubMatic’s AgenticOS is accelerating globally in Q2 (real AdCP-enabled CTV campaigns running with agencies like Butler/Till), and Magnite is riding the same protocol momentum.
Publisher takeaway
This decides who captures the value between a budget and an impression — and historically publishers lose margin to every new intermediary. Agentic A2A could thin the stack (upside) or just rename the toll (downside). The deciding factor is whether you’re legible and represented in the agentic stack. Ask agencies if your inventory already transacts A2A, press SSPs on agentic take rates, and make your inventory machine-legible.
06Amazon’s June power play — Prime Day moves up, Dynamic TV Creative scales, DSP at ~90% reach
Amazon compressed its flywheel into June: Prime Day moves to June 23–26 (June, not July, for the first time in years); Dynamic TV Creative — Prime Video ads auto-tailored to what a viewer is watching, geography, and Amazon’s shopping data — scales, expanding to live sports and more advertisers in Q3; and the Amazon DSP now claims ~90% U.S. household reach, with Prime Video and live sports run as “one business.” Prime Video ads also expand to Belgium, Denmark, Norway, and Turkey.
Publisher takeaway
The connective tissue is Amazon’s commerce data, and its pitch is closed-loop attribution. When Amazon ties an impression to a checkout, your inventory gets benchmarked against that — “we drove awareness” loses to “we drove a sale.” Pull your commerce calendar forward for June, sharpen an independently verifiable outcome story, and differentiate on the brand-safe, trusted context a retail-media giant can’t claim.
07Even Netflix opens up — Amazon and Yahoo data enter its CTV stack
To keep its ad tier (70M+ MAUs) growing, Netflix is wiring third-party data and demand into its stack: Amazon Audiences and buying via the Amazon DSP, plus Yahoo’s deterministic segments for U.S. targeting. Buyers can now reach Netflix’s ad-supported audience with tools they already use elsewhere.
Publisher takeaway
The most premium, most closed streamer concluding it must be open, buyable, and richly targetable is a loud signal — interoperability is the price of demand, and hard-to-buy inventory loses budget. Note the gravity toward Amazon: routing through the Amazon DSP makes Amazon connective infrastructure for premium CTV (ties to #6). Make your video inventory easy to buy through the DSPs your demand uses, keep multiple non-aligned identity graphs live, and lean into independent measurement as targeting data consolidates.
08Disney folds Hulu into Disney+ — one ad-supported giant
Disney is completing the merger of Hulu into Disney+, ending Hulu as a standalone U.S. app. The combination brings ~50M Hulu subscribers into a 150M+ Disney streaming base, spanning premium brands, general entertainment, kids, news, and live sports — with the combined ad-supported business pegged at $5B+ annually. New bundles and price increases accompany the consolidation.
Publisher takeaway
Read with #6 and #7, the theme is unmistakable — ad-supported streaming is consolidating into a handful of mega-scale, better-instrumented platforms, and premium video budgets are pooling around fewer, bigger destinations. Reassess your CTV competitive set (a merged Disney+/Hulu is one larger rival), differentiate on premium brand-safe context, and consider curation/PMP partnerships to aggregate scale if you’re mid-tier.
09Google’s ad-tech remedies near a decision
Judge Brinkema has already ruled Google illegally monopolized publisher ad servers and exchanges, tying AdX to DFP (Google Ad Manager). The remedies phase pits DOJ’s structural demand — sell AdX, open-source the auction logic, or phase out/divest Ad Manager — against Google’s behavioral counter: open AdX bids to rival servers, drop Unified Pricing Rules, First Look, and Last Look, share data files, and build a DFP–Prebid integration. Reporting framed it as Google’s “moment of truth,” with Brinkema pressing both sides past the “window dressing.” Realistic window: mid-2026, then years of appeals.
Publisher takeaway
This case is about publishers — AdX and DFP are the exchange and ad server most publishers run on. Model both outcomes (structural and behavioral), audit how much of your monetization flows through AdX/DFP, keep non-Google exchanges and header-bidding partners live for leverage, and pressure-test your auction setup for a world without UPR/First Look/Last Look.
10IAB’s June comment calendar — two more deadlines
Beyond #3’s bot-management window (June 26), two more close this month: Campaign Data Standards (comment by June 14), aimed at ending “the reconciliation nightmare” via standardized campaign-data fields (final version Q4 2026); and TCF Policy v5.0-B (comment by June 29), which removes a legacy workaround and tightens consent-UI requirements, alongside GPP and DDRF updates.
Publisher takeaway
Once finalized, these become your obligations whether or not you participated. Put ad-ops on Campaign Data Standards (test the fields against your real reporting), put privacy/legal on TCF v5.0-B (scope your CMP reconfiguration and budget the engineering), and treat all three June windows — campaign data, bot management, consent — as the standards backbone you’ll run on for years.