Skip to main content

Media Channel Taxonomy

Status: Draft Specification Version: 1.0.0-draft Last Updated: 2026-01-23
本仕様は広告メディアチャンネルの標準タクソノミーを定義します。メディアプランニングツール、アドテクプラットフォーム、AI ベースの広告エージェント間での相互運用を目的としています。

背景

広告業界には標準化されたチャンネルタクソノミーがありません。IAB Tech Lab はコンテンツ・オーディエンス・広告商品向けのタクソノミーを提供していますが、メディアチャンネルに相当するものが存在しないため次の課題が生じます。
  • プラットフォーム間でチャンネル名称が不一致
  • クロスチャネルのキャンペーンデータ集約が困難
  • チャンネル/フォーマット/購入モデルの混同
  • 自動化されたメディアプランニングでの摩擦
本仕様は以下を定義することで課題を解消します。
  1. Media Channels - バイヤーが予算を配分する単位(計画上の抽象化)
  2. Property Types - 所有が検証可能なアドレス指定インベントリ面
  3. チャンネル・プロパティタイプ・フォーマットの明確な区別

設計思想

チャンネルは広告がどこで描画されるかではなく、バイヤーがどのように計画・予算配分するかを表します。 これは意図的な選択です。バイヤーは「web に 50 万ドル」ではなく「display に 50 万ドル」「OLV に 30 万ドル」と表現します。チャンネルタクソノミーはこの実態を反映しています。

主要原則

  1. プランニング指向: エージェンシーのプラン構成に沿う
  2. 軽量タグ: 正確な分類を強制するのではなく意図を表明するためのもの
  3. マルチチャネル対応: 1 つのプロパティが複数チャンネルにまたがる場合がある(例: YouTube = olv, social, ctv
  4. パブリッシャー宣言: 在庫が対応するチャンネルをパブリッシャーが示します
  5. エージェント調整: 営業エージェントがバイヤー意図とパブリッシャー主張を突き合わせる

チャンネル vs 技術的な基盤

チャンネルは「web」「モバイルアプリ」のような基盤レベルの概念を意図的に避けています。
  • バイヤーはその粒度で計画しません
  • 多くのデジタル在庫が両方に該当してしまいます
  • 同じプレースメントを異なる方法で購入できます
代わりに、display/OLV/social/search/CTV など 購入コンテキスト を表します。

用語

本文中の “MUST” などの語は RFC 2119 に従って解釈します。

定義

Media Channel

メディアチャンネル はバイヤーが予算をどう配分するかを表す計画上の抽象化です。オーディエンス・環境・購入方法に関する前提を内包します。 チャンネルは 購入コンテキスト で定義され、以下では定義されません。
  • 技術基盤(web vs app)
  • 広告の見た目(それは フォーマット
  • 配信技術の詳細

Property Type

プロパティタイプ は次を満たすアドレス指定インベントリ面を指します。
  • 所有権が検証できる(例: adagents.json
  • プログラマティックに配信できます
  • ドメインやアプリ ID、デバイス ID などの識別子が存在します
プロパティタイプは技術的な分類でありチャンネルとは別です。同じプロパティが複数チャンネルにまたがる場合があります。

Format Category

フォーマットカテゴリ は広告のレンダリング方法(クリエイティブユニット種別)を表します。例: video, audio, display, native。フォーマットはチャンネルとは直交します。

チャンネルとプロパティタイプの理解

Concept回答する問い判断基準
Channelバイヤーはどう予算を配分するかプランニングコンテキストretail_media
Property Type広告が技術的にどこで配信されるかアドレス指定インベントリ面website

重要性

リテールメディアを考えると、バイヤーが「retail media」に予算を割くとき、以下を購入しています。
  1. 小売サイト上のスポンサード商品
  2. 小売アプリ内のディスプレイ広告
  3. 小売データを使ったオフサイト広告
  4. 店舗内デジタルサイネージ
すべて retail_media チャンネルですが、プロパティタイプは website / mobile_app / dooh など異なります。

マルチチャネルなプロパティ

1 つのプロパティが複数チャンネルに属する場合があります。
PropertyChannelsReasoning
YouTubeolv, social, ctv同一プラットフォームで異なる購入コンテキスト
ESPN Appolv, display動画とディスプレイ在庫を保有
Amazonretail_media, search, display複数の広告商品を提供

使い分け

channel を使う場面:
  • 予算配分カテゴリでプロダクトを絞るとき
  • メディアミックスをレポートするとき
  • プロダクト探索でバイヤー意図を表すとき
property_type を使う場面:
  • adagents.json で在庫所有を検証するとき
  • 配信の技術的判断を行うとき
  • プラットフォーム固有のターゲティングを行うとき

Media Channels

Channel Enum

The following 19 channels MUST be supported. Implementations MAY extend with additional channels using the ext field.
ChannelDescription
displayデジタルディスプレイ広告(バナー、ネイティブ、リッチメディア)
olvCTV 以外のオンライン動画(プリロール、アウトストリーム、インアプリ動画)
socialソーシャルメディアプラットフォーム
search検索エンジン広告
ctvテレビ画面での接続型/ストリーミング TV
linear_tv従来の地上波/ケーブルテレビ
radio従来の AM/FM ラジオ放送
streaming_audioデジタルオーディオストリーミングサービス
podcastポッドキャスト広告
doohデジタル屋外スクリーン
ooh伝統的な屋外(ビルボード、トランジット)
print新聞・雑誌などの紙媒体
cinema映画館広告
emailメール広告・ニュースレター
gamingインゲーム広告
retail_mediaリテールメディアネットワークやコマースマーケットプレイス
influencerクリエイター/インフルエンサーとの提携
affiliateアフィリエイトネットワーク、成果報酬型提携
product_placementプロダクトプレースメントやブランドコンテンツ

Channel Definitions

display

Digital display advertising including banners, native units, and rich media across web and app environments. Includes:
  • Display banners on websites
  • Display ads in mobile apps
  • Native content units
  • Rich media ads
  • Interstitials (non-video)
Excludes:
  • Video ads (use olv or ctv)
  • Social platform ads (use social)
  • Search results (use search)
  • Retail media placements (use retail_media)
Typical Formats: display, native, rich_media

olv

Online video advertising delivered outside of CTV/television environments. Includes:
  • Pre-roll, mid-roll, post-roll on websites
  • In-app video ads
  • Outstream/in-feed video
  • YouTube video ads (when not on TV screens)
  • Video on news sites, sports sites, etc.
Excludes:
  • CTV/streaming on TV screens (use ctv)
  • Social platform video (use social)
  • Linear TV (use linear_tv)
  • Retail media video (use retail_media)
Typical Formats: video Note: OLV (Online Video) is a distinct planning bucket from CTV. Agencies commonly budget separately for “OLV” and “CTV” campaigns.

social

Social media platform advertising, regardless of technical delivery surface. Includes:
  • Meta platforms (Facebook, Instagram, Threads)
  • X (Twitter)
  • TikTok
  • LinkedIn
  • Snapchat
  • Pinterest
  • Reddit
  • YouTube (when bought through social-style targeting)
Excludes:
  • Influencer content on social platforms (use influencer)
  • Video ads bought for reach, not social engagement (consider olv)
Typical Formats: display, video, native Note: Social is defined by BUYING CONTEXT (social platform ad tools) and audience engagement model. Search engine results pages and search advertising networks. Includes:
  • Google Search ads
  • Microsoft Bing ads
  • DuckDuckGo ads
  • App store search ads
  • Shopping/product listing ads in search context
Excludes:
  • Display ads on search engine properties (use display)
  • Retail media search (use retail_media)
Typical Formats: text, display (shopping)

ctv

Connected TV advertising delivered through streaming applications on television screens. Includes:
  • Streaming service apps (Netflix, Hulu, Max, etc.)
  • Virtual MVPDs (YouTube TV, Sling, etc.)
  • Free ad-supported streaming TV (FAST)
  • Smart TV native apps
  • Gaming console streaming apps
Excludes:
  • Linear broadcast/cable (use linear_tv)
  • Video on phones/tablets/desktops (use olv)
  • YouTube on mobile (use olv or social)
Typical Formats: video

linear_tv

Traditional broadcast and cable television advertising. Includes:
  • National broadcast networks (ABC, CBS, NBC, Fox)
  • Cable networks (ESPN, CNN, HGTV)
  • Local broadcast stations
  • Addressable linear TV
Excludes:
  • Streaming on TV screens (use ctv)
  • TV Everywhere apps on mobile (use olv)
Typical Formats: video

radio

Traditional AM/FM radio broadcast advertising. Includes:
  • Terrestrial radio stations
  • Satellite radio (SiriusXM terrestrial simulcast)
  • HD Radio
Excludes:
  • Streaming audio services (use streaming_audio)
  • Podcasts (use podcast)
Typical Formats: audio

streaming_audio

Digital audio streaming services. Includes:
  • Music streaming (Spotify, Apple Music, Amazon Music, Pandora)
  • Audio content platforms
  • Digital radio streams (iHeartRadio digital, TuneIn)
Excludes:
  • Podcasts (use podcast)
  • Terrestrial radio simulcast (use radio)
Typical Formats: audio, display (companion)

podcast

Podcast advertising, including host-read and dynamically inserted ads. Includes:
  • Host-read sponsorships
  • Dynamically inserted audio ads
  • Podcast network advertising
Excludes:
  • Music streaming (use streaming_audio)
  • Video podcasts on YouTube (use olv or social)
Typical Formats: audio

dooh

Digital out-of-home advertising on electronic screens in public spaces. Includes:
  • Digital billboards
  • Transit screens (subway, bus shelters, airports)
  • Retail/mall digital displays
  • Gas station screens
  • Elevator screens
  • Stadium/venue digital signage
Excludes:
  • Static billboards (use ooh)
  • Cinema screens (use cinema)
Typical Formats: display, video

ooh

Classic out-of-home advertising on physical (non-digital) surfaces. Includes:
  • Static billboards
  • Transit posters
  • Street furniture
  • Wallscapes
  • Wild postings
Excludes:
  • Digital screens (use dooh)
Typical Formats: display (static)

print

Newspaper, magazine, and other print publication advertising. Includes:
  • Newspaper display ads
  • Magazine display ads
  • Newspaper/magazine inserts
  • Trade publication advertising
Excludes:
  • Digital versions of publications (use display)
  • Direct mail
Typical Formats: display (static)

cinema

Movie theater advertising. Includes:
  • Pre-show advertising
  • On-screen trailers and ads
  • Lobby displays
  • Concession advertising
Excludes:
  • Streaming movie services (use ctv)
Typical Formats: video, display

email

Email advertising and sponsored newsletter content. Includes:
  • Sponsored email newsletters
  • Email display advertising
  • Dedicated email sends
Excludes:
  • Transactional email
  • CRM/owned email marketing
Typical Formats: display, native

gaming

In-game advertising across gaming platforms. Includes:
  • In-game display ads
  • Rewarded video ads
  • Playable ads
  • Advergames
  • Esports sponsorships
  • Gaming influencer integrations
Excludes:
  • Ads in non-gaming apps (use display or olv)
  • Gaming content on streaming platforms (use ctv or olv)
Typical Formats: display, video, native

retail_media

Retail media networks and commerce marketplace advertising. Includes:
  • Retail media networks (Amazon Ads, Walmart Connect, Target Roundel)
  • Grocery and delivery platforms (Instacart, DoorDash, Uber)
  • Travel marketplaces (Expedia, Booking.com, Kayak)
  • Financial services marketplaces
  • Sponsored product listings
  • On-site display and video on commerce platforms
  • Off-site ads using retailer first-party data
Excludes:
  • General display ads (use display)
  • Social commerce (use social)
  • Search ads on non-commerce platforms (use search)
Typical Formats: native, display, video Note: Retail media is distinguished by its transactional context and closed-loop attribution capabilities.

influencer

Creator and influencer marketing partnerships. Includes:
  • Sponsored content creation
  • Brand ambassador programs
  • Affiliate creator partnerships
  • User-generated content campaigns
Excludes:
  • Ads placed on creator content by platforms (use social)
  • Podcast host reads (use podcast)
Typical Formats: video, native, display Note: influencer describes the BUYING MODEL (creator partnership) rather than where content appears.

affiliate

Affiliate networks, comparison sites, and performance-based publisher partnerships. Includes:
  • Affiliate networks (CJ, Rakuten, Impact, Awin, ShareASale)
  • Comparison shopping engines (NerdWallet, Bankrate, The Points Guy)
  • Review and recommendation sites
  • Coupon and deal sites (RetailMeNot, Honey)
  • Content commerce (editorial with affiliate links)
  • Lead generation sites
  • Cashback and loyalty programs
Excludes:
  • Standard display ads on affiliate sites (use display)
  • Influencer partnerships (use influencer)
  • Retail media sponsored products (use retail_media)
Typical Formats: native, display, text Note: affiliate describes the BUYING MODEL (performance-based, CPA/CPC/rev-share) rather than where content appears.

product_placement

Product placement, branded content, and sponsorship integrations. Includes:
  • Traditional product placement (film, TV)
  • Virtual product placement
  • Branded entertainment
  • Event sponsorships
  • Naming rights
  • Branded content series
Excludes:
  • Influencer partnerships (use influencer)
  • Standard ad placements at sponsored events (use appropriate channel)
Typical Formats: native, video

Property Types

Property types describe addressable inventory surfaces with verifiable ownership. They are used in adagents.json for authorization validation.

Property Type Enum

Property TypeDescriptionExample Channels
websiteWeb properties accessible via browserdisplay, olv
mobile_appNative mobile applicationsdisplay, olv, social, gaming
ctv_appConnected TV applicationsctv
desktop_appDesktop applications (Electron, native)streaming_audio, gaming
doohDigital out-of-home screen networksdooh
podcastPodcast feeds and episodespodcast
radioRadio station propertiesradio
streaming_audioDigital audio streaming propertiesstreaming_audio

Channels Without Property Types

The following channels do not have corresponding property types because they lack addressable, verifiable inventory surfaces in the traditional sense:
  • linear_tv - Broadcast/cable inventory is managed through different authorization mechanisms
  • ooh - Physical inventory lacks digital identifiers
  • print - Physical publication inventory
  • cinema - Theater inventory management systems
  • email - Email list ownership differs from property authorization
  • influencer - Creator relationships rather than property ownership
  • affiliate - Performance-based partnerships, placements appear on partner websites
  • product_placement - Content/event relationships rather than properties
  • retail_media - Platform-managed inventory within retail ecosystems
  • search - Platform-managed inventory
  • social - Platform-managed inventory

Relationship Between Concepts

┌─────────────────────────────────────────────────────────────────┐
│                        MEDIA CHANNEL                            │
│         How buyers allocate budget (planning abstraction)       │
│                                                                 │
│   display, olv, social, search, ctv, linear_tv, podcast,       │
│   streaming_audio, radio, dooh, ooh, print, cinema, email,     │
│   gaming, retail_media, influencer, affiliate, product_placement│
└─────────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────┐
│                      PROPERTY TYPE                              │
│   Addressable inventory with verifiable ownership (technical)   │
│                                                                 │
│   website, mobile_app, ctv_app, desktop_app, dooh,             │
│   podcast, radio, streaming_audio                               │
└─────────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────┐
│                      FORMAT CATEGORY                            │
│         How the ad renders (orthogonal to channel)              │
│                                                                 │
│     audio, video, display, native, rich_media, text            │
└─────────────────────────────────────────────────────────────────┘

Implementation

JSON Schema

Channels are defined in the AdCP schema at:
/schemas/v1/enums/channels.json
{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$id": "/schemas/enums/channels.json",
  "title": "Media Channel",
  "description": "Standardized advertising media channels describing how buyers allocate budget",
  "type": "string",
  "enum": [
    "display",
    "olv",
    "social",
    "search",
    "ctv",
    "linear_tv",
    "radio",
    "streaming_audio",
    "podcast",
    "dooh",
    "ooh",
    "print",
    "cinema",
    "email",
    "gaming",
    "retail_media",
    "influencer",
    "affiliate",
    "product_placement"
  ]
}

Usage in Product Discovery

When filtering products by channel:
{
  "filters": {
    "channels": ["ctv", "olv", "streaming_audio"]
  }
}

Usage in Property Definitions

Properties in adagents.json declare which channels they support:
{
  "properties": [
    {
      "property_id": "youtube_app",
      "property_type": "ctv_app",
      "name": "YouTube CTV",
      "supported_channels": ["ctv", "olv", "social"],
      "identifiers": [
        {"type": "roku_store_id", "value": "12345"}
      ]
    }
  ]
}

Extensibility

Implementations MAY support additional channels beyond this specification using the ext field pattern:
{
  "channel": "display",
  "ext": {
    "sub_channel": "native_content"
  }
}

Versioning

This taxonomy follows Semantic Versioning:
  • MAJOR: Removing channels, changing channel semantics
  • MINOR: Adding new channels (append-only)
  • PATCH: Clarifying descriptions, fixing typos
Adding new channels is a MINOR version change and MUST NOT break existing implementations.

Migration from Legacy Channel Values

Prior to this taxonomy, AdCP used a different set of channel values. The following table maps legacy values to the new taxonomy:
Legacy ValueNew Channel(s)Notes
displaydisplayNo change, but now excludes video
videoolv, ctvSplit by viewing environment
audiostreaming_audio, podcast, radioSplit by audio type
nativedisplayNative is a format, not a channel
webdisplay, olvWeb is a substrate, not a planning bucket
mobile_appdisplay, olv, gamingApp is a substrate, not a planning bucket
doohdoohNo change
ctvctvNo change
podcastpodcastNo change
retailretail_mediaRenamed
commerce_mediaretail_mediaRenamed
socialsocialNo change
sponsorshipproduct_placementRenamed and refined

Migration Guidance

  1. Identify the planning context: Determine HOW the buyer allocates budget, not where ads technically render.
  2. Split video by environment: If video was a single category, split into olv (desktop/mobile) and ctv (TV screens).
  3. Remove substrate channels: If you had web or mobile_app as channels, map to planning-oriented channels (display, olv) based on buying context.
  4. Update filters: When filtering products, use the new channel values.

Edge Cases and Ambiguities

YouTube Classification

YouTube spans multiple channels depending on context:
ScenarioChannelReasoning
YouTube video ad on phone/desktopolv or socialDepends on buying approach
YouTube video ad on CTVctvTV screen environment
YouTube ShortssocialShort-form social context
YouTube Musicstreaming_audioAudio streaming context

Retail Media Complexity

Retail media may eventually warrant sub-channels:
ScenarioCurrentPotential Future
Sponsored products on Amazonretail_mediaretail_media_search
Display on retailer siteretail_mediaretail_media_display
Off-site using retailer dataretail_mediaretail_media_offsite
For now, use retail_media with format filters to distinguish.

Gaming vs Display/OLV

ScenarioChannelReasoning
Rewarded video in mobile game via Unity AdsgamingGaming-specific ad network
Banner in casual game via AdMob general pooldisplayStandard mobile programmatic
Esports tournament sponsorshipgamingGaming audience context

Influencer vs Social

ScenarioChannelReasoning
Buying promoted posts through Instagram AdssocialPlatform ad tools
Contracting an influencer directlyinfluencerCreator partnership
Platform-inserted ads around creator contentsocialPlatform ad tools

Future Considerations

The following channels may be added in future versions based on market evolution:
  • messaging - WhatsApp Business, Telegram ads
  • xr - VR/AR advertising
  • ai_agents - AI assistant and chatbot advertising

References

Changelog

1.0.0-draft (2026-01-23)

  • Initial draft specification
  • 19 channels defined (planning-oriented approach)
  • 8 property types defined
  • Clear distinction between channel (planning abstraction), property_type (technical surface), and format
  • Multi-channel support for properties
  • Migration guide from legacy values