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 flows, channels, and SDK keys, including browser embeds.
- Web SDK — React package that runs a channel-resolved flow 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 onboarding experience you design and publish.
- Channel — A routing surface that connects SDK traffic to a flow or experiment.
- Experiment — An A/B test comparing flow variants on a channel.
- Customer — An end user of your app who appears in analytics and Engage audiences.
- SDK environment — Test vs live keys and how the SDK connects to Rheo.
- Rheo Engage — Lifecycle email broadcasts and automations sent through your own provider.
- CLI — Terminal client for apps, flows, channels, experiments, 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.
| Term | Meaning |
|---|---|
| Flow | The versioned experience you author on the canvas, publish, and assign to a channel. This is the Rheo product object. See Flow. |
| 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. |
| Journey | The 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.
How concepts fit together
Your workspace owns one or more apps. Each app contains flows you author and channels that decide which published flow users see. Experiments split traffic across flow variants on a single channel. Customers are the people who use those flows—identified by your app when you integrate the SDK—and the same people you can reach with Engage email when they have granted marketing consent. Test and live environments keep QA traffic separate from production.