Agentic Advertising Is Already Here. The Receipts.

1. Google shipped the first official ads MCP server on October 7, 2025

The announcement is on Google's own Ads Developer Blog, dated October 7, 2025: Open Source Google Ads API MCP Server. It is open source and strictly read-only. The current repository at github.com/googleads/google-ads-mcp exposes retrieval tools only: a GAQL search tool, resource metadata, and a list of accessible customers. No writes. It cannot pause a campaign or move a dollar.

One correction worth making explicit, because the wrong version is circulating: several 2026 roundups date Google's server to late April 2026. That date is wrong. The primary source above is from October 2025. If a page you are reading gives a spring 2026 date for Google's first official ads MCP server, its author did not check the blog they are citing.

2. Meta went live on April 29, 2026 with 29 tools, including writes

Meta announced Meta Ads AI Connectors on April 29, 2026: a hosted MCP server at mcp.facebook.com/ads plus a companion CLI, in open beta. Per Meta's developer documentation, the server exposes 29 tools across reporting, campaign management, catalog management, and signal diagnostics. Meta's own wording: advertisers can "create and edit ads, ad sets, and campaigns using natural language." This is the first official server from a major platform with write access on day one, authenticated through Meta Business OAuth rather than a developer app and App Review.

3. TikTok announced its Ads MCP Server on May 13, 2026

At TikTok World on May 13, 2026, TikTok announced the TikTok Ads MCP Server, in the company's words "a new interface that allows developers and advertisers to build AI agents and tools directly on top of the TikTok Ads ecosystem." Note the tier boundary inside this receipt: the announcement is verified, general availability is not. TikTok's newsroom post names no launch date, and public developer documentation had not shipped alongside the announcement. Announced and shipped are different claims, and only the first one has a primary source today.

4. ChatGPT ads are live, and self-serve since July 22, 2026

OpenAI began testing ads in ChatGPT in February 2026 on the Free and Go tiers, then introduced a beta self-serve Ads Manager in the spring with CPC bidding and conversion measurement, covered by Search Engine Journal in May alongside named partners including Dentsu, Omnicom Group, Publicis Groupe, and WPP. On July 22, 2026, OpenAI opened self-serve access publicly, citing Best Buy, Lowe's, and VistaPrint as early case studies. A conversational surface at ChatGPT's scale selling ads through its own ads manager is a new buying channel that did not exist a year ago.

5. Named brands are on record buying media with agents

Not vendors talking about brands. Brands talking, on the record, at the Digiday Programmatic Marketing Summit in May 2026. Duluth Trading Company's marketing director described delegating bidding to agents while keeping creative in human hands. Butler/Till's chief strategy officer described the agency's first agentic buys, including this: "It was really fun to see the negotiation and interaction between our instance of Claude and [PubMatic's] seller agent. We were quite impressed how quickly that worked." Omnicom's OMD said it plans to let agents make optimization decisions in the second half of 2026, with human sign-off, its data lead adding "it's garbage in, garbage out. So if you don't have really solid human inputs into the agent or the workflow, it's going to break down."

6. The protocol itself keeps shipping

The layer all of this runs on is maturing fast. The MCP 2026-07-28 specification shipped on July 28, 2026, and the project reports "close to half-a-billion downloads a month" across its Tier 1 SDKs. That is the difference between a trend and a substrate. Ad platforms are not betting on a research demo; they are building on a protocol with an enterprise-grade release cadence.

Perplexity as a live ad channel

Perplexity killed its advertising business. In February 2026 the company confirmed it had stopped the ad tests it began in 2024, with no plans to bring them back, arguing that sponsored placements risk the trust an answer engine depends on (Search Engine Land, February 18, 2026). Yet Perplexity still shows up in AI-advertising decks and channel lists in mid-2026 as if it were bookable inventory. It is not. Any strategy doc presenting Perplexity ads as live is at least six months stale.

Platform counts dressed up as customers

A recurring vendor move in this category, and one we watch for because we are a vendor too: an integrations count quietly becomes social proof. "Supports 14 platforms" drifts into "trusted across 14 platforms" and lands as "trusted by thousands of teams" with no customer number, no date, no named buyer. The check is one question: how many paying customers, as of when? If a page cannot answer that, the platform count is an engineering fact being marketed as a traction fact. They are not the same claim.

Revenue figures with no source attached

AI-ads press releases in 2026 are thick with revenue and ARR figures that trace to nothing: no filing, no audited number, no named customer, often no date. The wrong Google launch date from receipt one spreads the same way, each roundup citing the previous roundup until nobody remembers that the primary source says something else. The test for both is identical. Follow the citation chain one step. If it ends at another blog instead of a primary source, treat the number as marketing, not data.

Six agencies became paying customers in four days

In May 2026, six agencies converted to paid PaidSync accounts within four days. We anonymize client names as policy, which means you cannot independently verify this the way you can verify receipt one, and we will not pretend otherwise. What we can state plainly is the count, the window, and the month. Judge it with the same suspicion this page applies to everyone else's numbers.

Production agents spend their calls on measurement, not glamour

The demo version of agentic advertising is an agent writing ad copy. The production version is an agent fixing the measurement layer, because broken tracking quietly ruins every optimization decision downstream. That is the layer no official server touches: Google's covers Google Ads reporting, Meta's 29 tools cover Meta. Neither reaches Google Tag Manager, GA4, or Search Console. PaidSync exposes 37 GTM tools covering the full tag, trigger, and variable lifecycle including publish, 28 GA4 tools including conversion event creation, and 6 read-only Search Console tools. Real agent sessions lean on exactly these, wiring conversion events and auditing tags before they touch a single bid. The Meta bulk operations guide shows what that looks like at agency scale.

Gated writes were the adoption answer

The blocker for every agency we spoke to was never capability, it was blast radius. Nobody hands live budgets to an autonomous system on trust. What converted pilots into paid accounts was the gate design: every write is approval-gated, dry_run previews the exact change before anything executes, destructive operations require an explicit confirm_destructive flag, and any session can be revoked instantly. The worst case becomes a blocked action instead of a damaged account. OMD's plan for optimization decisions with human sign-off, from receipt five, is the same conclusion reached independently at holding-company scale.