Rheo documentation
Core concepts

Glossary

Glossary-style reference for the nouns you will see throughout Rheo.

Purpose

Use this section when a label in the product is unfamiliar. Each page is intentionally short. Follow links into the User Guide when you need step-by-step workflows or permission details.

Core concepts

  • Workspace — Your team's Rheo account: members, billing, and shared settings.
  • App — A product container for Convert, Engage, customers, and SDK keys, including browser embeds.
  • Convert — Dashboard pillar: Overview, Channels, Flows, Banners, Experiments.
  • Web SDK — React package that runs a channel-resolved flow or banner in a host web app.
  • Stripe Payment Link — Integration Node URL the web SDK opens. A return advances the flow. The purchase is recorded when Stripe confirms checkout on the app webhook.
  • Flow — The multi-screen onboarding experience you design and publish.
  • Channel — The address an app resolves: unassigned, a flow pin, a banner pin, a code pin, or an experiment.
  • Banner — A single-frame, inline composable authored in the banner canvas, versioned like a flow, and assigned to a channel with assignmentKind: banner.
  • Experiment — A test on one channel. Flow variants serve published flows. Code variants serve a key and parameters. Banner variants serve a published banner manifest.
  • Customer — An end user of your app who appears in analytics and Engage audiences.
  • Analytics — Visitors, sessions, acquisition, and retention for the whole app and site.
  • SDK environment — Test vs live keys and how the SDK connects to Rheo.
  • Rheo Engage — Email, webhook, and push broadcasts, automations, templates, and content blocks. Email uses your provider. Push uses credentials you save. Webhooks POST to an endpoint on the message.
  • Engage template — Reusable email, webhook, or push starter copied into a broadcast or automation (not a live link).
  • Content block — Reusable Engage email fragment inserted in the composer.
  • CLI — Terminal client for apps, flows, channels, experiments, flow analytics, product analytics, rollouts, media, and Engage, using a personal workspace API key.
  • Layout axis mode — Hug, Fill, Fixed, and fractions on width and height in the flow builder.

Terminology: flow, funnel, and journey

Rheo uses these words in different contexts. They are related but not interchangeable.

TermMeaning
FlowThe versioned experience you author on the canvas, publish, and assign to a channel. This is the Rheo product object. See Flow.
AnalyticsApp-wide usage: visitors, sessions, pages and screens, acquisition, and retention. See Analytics.
Funnel (analytics)A step-through view of how users move through a flow: starts, drop-off between screens, and completion. Shown as the drop-off funnel on flow analytics and in experiment stats. See Customers & analytics.
JourneyThe broader business path across placements (install to trial to paid to cancel to win-back). One journey often spans multiple flows and channels.

Example: publish a win-back flow, then read its drop-off funnel to find the cliff.

A banner is a first-class artifact (not a flow flag) for inline UI: one root screen, optional fixed or responsive sizing in the manifest, and SDK render via RheoBanner / useChannel when resolve returns kind: 'banner'. Fixed-size banners declare width and height; responsive banners follow the host width and hug content height. Control arms in banner experiments resolve with control: true and render nothing while still logging experiment_exposed.

How concepts fit together

Your workspace owns one or more apps. Each app has a Convert pillar (flows, banners, channels, experiments) and Engage. The SDK resolves channels — unassigned, a flow pin, a banner pin, a code pin, or an experiment. Customers are people from the SDK, analytics, or Engage import — not only those who finished a flow — and you can reach them with Engage when they have granted marketing consent. Test and live environments keep QA traffic separate from production.