> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://contentful.com/developers/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://contentful.com/developers/docs/_mcp/server.

# Channels and destinations overview

> What channels and destinations are, how they relate to each other, and how they fit into the Experience Orchestration ecosystem.

Channels, destinations, and destination nodes provide a structured delivery model for experiences. Use them to:

* Assign or replace an experience at a delivery location without changing application code.
* Track where each experience is delivered and retain contextual metadata about that location.
* Remove an experience from a delivery location without removing its integration from the application.

A channel defines a reusable delivery schema. A destination is an instance of that schema, and destination nodes define addressable locations within the destination.

## Core concepts

**Channel** — defines the schema for a type of delivery surface. Channels are a category of destinations representing a specific medium for content delivery. For example, a web channel can define properties and node properties for websites and web pages, while a mobile channel can define properties for mobile applications and screens.

**Destination** — represents a specific delivery surface, such as a website, mobile application, or kiosk. It is created from a channel and uses the properties defined by that channel. Destinations contain destination nodes and identify the client through which experiences are delivered.

**Destination node** — represents a specific page or screen within a destination, such as a home page, product detail page, or application screen. Each node provides a stable delivery address and contextual metadata that applications can use to resolve the experience assigned to that location.