Skip to main content

AI media

AI media inverts how advertising works. In traditional programmatic, the platform sends a bid request out — a thin signal containing a page URL, device type, and maybe a user ID — to a remote decision-maker that lacks the context to make a great ad. The decision-maker doesn’t have the context. The context-holder doesn’t make the decision. AI platforms reverse this. Instead of sending signals out, they receive everything in: product catalogs via sync_catalogs, conversion events via sync_event_sources, brand identity via brand.json, content standards via governance policies, and optimization goals on every media buy. The platform’s LLM then has full context — the user’s conversation, the brand’s catalog, suitability rules, and what success looks like — to generate the right ad in the right moment. The decision-maker is the context-holder. That is the fundamental shift.
New to AdCP? Start with the introduction for a protocol overview, or the seller integration guide for the general steps to expose inventory to AI buyer agents. This guide covers AI media-specific product modeling, workflows, and measurement.

For buyers and brands

For a non-technical guide to AI media buying — what it requires, what data you provide, and how to get started as a brand, agency, or small business — see the buyer’s guide to AI media. The rest of this page covers technical product modeling, workflows, and measurement for teams building or evaluating integrations. AdCP’s sponsored_intelligence channel is designed for this reversed data flow. Rather than defining bid request formats, it defines the data buyers push into platforms: catalogs, events, brand standards, and goals. The platform uses this to generate sponsored responses, AI search results, generative display, and brand experience handoffs via Sponsored Intelligence.

What buyers push in

The more data the platform has, the better the ad. Product catalogs feed creative generation. Offering catalogs enable commerce handoffs. Conversion events close the optimization loop. Brand identity ensures the output sounds right. Content standards ensure it stays safe. None of these are administrative setup — together, they are the ad. AI media sellers come in two shapes: first-party AI platforms (a single AI assistant or search engine selling its own inventory) and AI ad networks (aggregating inventory across multiple AI platforms and publishers). The account model and publisher properties differ accordingly — a first-party platform is a walled garden with explicit accounts, while an ad network may use implicit accounts and represent multiple publisher properties.

How AI media differs from programmatic

AdCP mapping

Each seller is a separate sales agent — whether that’s a first-party AI platform or an ad network aggregating across multiple platforms. Their ad offerings are modeled as products. The buyer pushes in the data the platform needs to make great ads: product catalogs, brand identity, conversion events, content standards, and optimization goals. Account relationships depend on the seller type: first-party platforms typically use explicit accounts (require_operator_auth: true), while ad networks may use implicit accounts where the agent is trusted to declare brands via sync_accounts.

Why an open standard?

If you’re building an AI platform’s ad infrastructure, you have three options for plugging in demand: The proprietary API gets the data flow right but doesn’t scale. The SSP scales but gets the data flow wrong. AdCP gets both right: data flows in through a standard interface that any buyer agent can use without a custom integration.

AdCP extends your platform, not replaces it

AdCP is not an aggregation layer that sits on top of your ad stack. It’s a standard interface to it. You implement AdCP tasks inside your platform — get_products queries your inventory system, sync_catalogs writes to your catalog store, create_media_buy creates campaigns in your ad server. The tasks are thin wrappers around capabilities you’re already building. The accounts protocol is where this becomes concrete. When a buyer calls sync_accounts, your platform creates a real advertiser account — the same kind of account a human would create through your dashboard. When they call list_accounts, they see the same accounts. sync_catalogs writes to the same catalog store your ad serving reads from. sync_event_sources registers the same conversion events your optimization engine uses. This means:
  • Your existing dashboard and API keep working — AdCP is an additional interface to the same backend, not a replacement
  • Accounts created via AdCP are real accounts — they show up in your admin tools, your billing system, your reporting
  • Catalog data synced via AdCP feeds the same serving pipeline — there’s no separate “AdCP inventory” and “direct inventory”
  • Buyer agents get the same capabilities humans get — same products, same pricing, same measurement
AdCP works over two transport protocols: MCP (direct integration with AI agents) and A2A (agent-to-agent workflows). The same task definitions work over both. See the protocol comparison for when to use which.

Ad networks

AI ad networks aggregate inventory across multiple AI platforms into a single seller interface. The protocol supports this topology natively — networks use account chains, catalog forwarding, and unified delivery reporting to sit between buyer agents and underlying platforms. For the full details on product modeling, governance, and Sponsored Intelligence routing through networks, see the AI ad networks guide.

The product spectrum

AI media sellers offer several distinct product types, each with different creative generation patterns, pricing models, and measurement capabilities. The flagship AI media product. When a user’s conversation is relevant to the brand, the platform generates a sponsored response using the brand’s catalog and identity. Pricing is typically CPC or cost-per-engagement.
Key characteristics:
  • CPC pricing with auction-based bidding on contextual relevance
  • templates_available: true — the platform generates creative from catalog and brand data
  • catalog_types declares which catalog types feed the generative creative — product feeds for e-commerce brands, offering feeds for services
  • metric_optimization with engagements and clicks — buyers can set cost-per-engagement targets

AI search sponsored results

Sponsored results within AI-powered search experiences. Similar to traditional search ads but rendered within an AI’s synthesized response. Keyword targeting is the primary relevance signal.
AI search products typically support keyword targeting. Sellers declare this in get_adcp_capabilities under media_buy.execution.targeting.keyword_targets, and buyers provide keywords on packages via targeting_overlay.

Generative display and video

Display and video ads generated from brand assets for placement within AI experiences — sidebars, interstitials between conversation turns, or visual responses. The platform uses build_creative to generate visual creative from the brand’s assets and guidelines.
Unlike sponsored responses, generative display uses standard format IDs from the creative agent. Buyers provide creative via build_creative or inline on the media buy — the platform doesn’t generate creative from catalog data.

Brand experience handoffs (Sponsored Intelligence)

When a user shows high purchase intent, the AI platform can hand off the conversation to the brand’s own AI agent via the Sponsored Intelligence protocol. This enables rich, multi-turn brand experiences — product recommendations, comparisons, configuration, and even transaction completion — without leaving the AI assistant. Brand experience handoffs are unique to AI media. The brand syncs offerings via sync_catalogs with type: "offering", and the platform triggers handoffs when user intent aligns with an offering. See the SI specification for the session lifecycle and capability model.

End-to-end workflow

Measurement

AI media measurement centers on engagement and intent signals rather than traditional impression-based metrics.

Key metrics

Conversion tracking

AI platforms that support conversion tracking declare it in get_adcp_capabilities under conversion_tracking. Buyers set up event sources via sync_event_sources and use kind: "event" optimization goals on packages — the same pattern as any other channel. See Optimization & Reporting for details.

Beyond ads: commerce in the conversation

AI surfaces are uniquely positioned for commerce. A user asking an AI assistant about running shoes is expressing intent in a context where the platform can recommend, compare, and — eventually — help the user buy. Today, AdCP handles the advertising layer: catalogs, media buys, and delivery. Offering catalogs via sync_catalogs already enable commerce handoffs through Sponsored Intelligence sessions, where the user can browse products and transition to checkout. As commerce protocols mature, the path from “interested” to “purchased” will happen entirely within the conversation.

Best practices

For buyers

With AI media, the quality of what you push in determines the quality of what comes out. Your catalogs, conversion events, brand identity, and content standards are not administrative setup — they are the inputs the platform uses to generate the right ad, match it to the right moment, and help the user transact.
  1. Push rich catalogs — products and offerings — sync via sync_catalogs with detailed descriptions, multiple images, structured attributes (size, color, category), and accurate pricing. Product catalogs feed creative generation. Offering catalogs enable promotions and commerce handoffs. The platform generates ads and matches intent from this data — thin feeds mean thin ads.
  2. Push conversion events — sync event sources via sync_event_sources so the platform can optimize toward your actual business outcomes. AI platforms can close the loop between conversational context and conversion — give them the data to do it.
  3. Push brand identitybrand.json provides voice, visual guidelines, and positioning. The platform uses this to generate creative that sounds and looks like your brand, not generic sponsored content.
  4. Push content standards — use governance policies to define suitability rules. Because the platform generates creative at serve time, these rules are enforced during generation, not applied as post-hoc filters.
  5. Set clear optimization goals — use optimization_goals on every package to tell the platform what success means. Combine with conversion events for outcome-based optimization.
  6. Set up accounts early — check get_adcp_capabilities for the account model. First-party platforms require OAuth; ad networks may accept sync_accounts directly.
  7. Use sandbox first — validate the full data sync pipeline (catalogs, events, brand identity, standards) before committing real spend.
  8. Use keyword targeting for AI search — specify relevant keywords on AI search packages to reach high-intent queries.

For sellers

The core value of AI media is that buyers push everything the platform needs to make great ad decisions. Your job as a seller is to accept that data and use it well.
  1. Accept catalogs — products and offerings — implement sync_catalogs for both product and offering types. Product catalogs feed creative generation. Offering catalogs enable promotions, services, and commerce handoffs. Declare catalog_types on products so buyers know what to sync. The more catalog data you ingest, the better you can match user intent to advertiser inventory.
  2. Accept conversion events — implement sync_event_sources so buyers can share what success looks like. This lets your platform optimize toward real business outcomes, not proxy metrics. The combination of conversational context + conversion data is what makes AI media optimization superior to remote bid optimization.
  3. Accept and enforce content standards — support governance policies so buyers can push suitability rules into your platform. Because you generate creative at serve time, you can enforce these rules at generation time rather than filtering after the fact.
  4. Honor optimization goals — buyers set optimization_goals on packages to tell you what “good” means. Use these alongside conversion events and catalog data to close the optimization loop.
  5. Implement accounts — first-party platforms should use require_operator_auth: true (each advertiser authenticates independently). Ad networks aggregating across publishers may use implicit accounts instead.
  6. Support sandbox — declare account.sandbox: true in capabilities. Buyers need to validate the full data sync pipeline (catalogs, events, standards) before committing real spend.
  7. Report engagement metrics — include clicks and engagement data in delivery reporting so buyers can evaluate AI media alongside other channels.
  8. Set channels: ["sponsored_intelligence"] on all products so buyers can filter by channel.
  9. Support keyword targeting for AI search products — declare keyword_targets in capabilities and honor targeting_overlay.keyword_targets on packages.