AdCP — Connected TV

CTV uses the standard video_hosted and video_vast canonicals. SSAI/CSAI mode, app environment, ad-pod position, measurement availability, and inventory guarantees belong on the product or placement.

{
  "publisher_domain": "tv.streamhaus.example",
  "format_option_id": "ctv_ssai_30s",
  "format_kind": "video_hosted",
  "params": {
    "width": 1920,
    "height": 1080,
    "duration_ms_exact": 30000,
    "containers": ["mp4"],
    "video_codecs": ["h264"],
    "audio_codecs": ["aac"],
    "slots": [
      { "asset_group_id": "video_main", "asset_type": "video", "required": true },
      { "asset_group_id": "companion_image", "asset_type": "image", "required": false }
    ]
  }
}

For CSAI or third-party delivery, use video_vast and a required vast_tag slot. A multi-output creative agent may advertise separate SSAI and VAST capability IDs; buyers select them with target_capability_ids[] and receive portable canonical manifests. Preview on the seller/publisher endpoint when device chrome, companion placement, ad-pod context, or remote-control interaction matters. The impression-time CTV renderer remains the seller runtime behind sync_creatives. Beyond linear video, the IAB CTV Ad Portfolio’s home-screen and on-glass experiences — Menu, Pause, Screensaver, Overlay, Squeezeback, and In-Scene — layer a ctv_ad_experience declaration onto native_in_feed, image, video_hosted, video_vast, and sponsored_placement. See CTV experience profiles for the experience-to-canonical matrix, per-experience duration and interactivity constraints, and the OpenRTB/AdCOM signaling bridge. See Video, Multi-agent orchestration, and Creative delivery.

Getting Started

Building with AdCP

Protocol

Using AAO

FAQ

Trust & Security

Reference

Certification

Connected TV