Channel
The address an app resolves. A channel is unassigned, pinned to one experience, or serving an experiment.
Purpose
A channel is a named address in either the test or live environment. Your app tells the SDK which channel to resolve. Rheo serves whatever is assigned there. Changing the assignment updates the next resolve. You do not ship a new app build.
A channel is in one of three states:
| State | What the app receives |
|---|---|
| Unassigned | Resolve returns not found (channel_unassigned). |
| Pin | One fixed experience. A flow pin is one published flow version. A banner pin is one published banner version. A code pin is one variant key and its parameters. |
| Experiment | A running or pending-decision test on that channel (flow, banner, or code content kind). Each person stays on the same variant. |
The app switches on the content kind. flow is a multi-screen no-code experience. banner is a single-frame Convert surface. code is a key and parameters the host reads with get.
How routing works
The SDK needs two pieces of configuration:
- Publishable key. Selects the app and environment (test or live). You copy this from App settings → API keys.
- Channel ID. Selects which channel within that environment.
The SDK does not send a flow ID, banner ID, or a variant key. Rheo decides from the channel's current assignment.
When the assignment changes, clients pick it up on their next resolve. Unchanged assignments can reuse a cached response.
How to manage channels
Open Convert → Channels inside your app to create channels, pin a flow, banner, or code parameters, attach a running experiment, and review history. On a gated environment, a change to what the channel serves is a rollout request until someone approves it.

Related
- Channels & rollout: Pins, experiments, and approvals.
- SDK environment: Test vs live keys.
- Experiment: A test on one channel.