Rheo documentation

Get started in 15 minutes

Minimal path from an empty workspace to a Convert experience your users can see through a channel or the SDK.

Purpose

This guide walks you from an empty workspace to a Convert experience—usually a flow, optionally a banner—that users see through a channel or the SDK. Most teams finish the first pass in about fifteen minutes.

What you will have at the end

A flow (or banner) connected to an app in your workspace, ready to assign to a channel for staged delivery or to serve through the SDK in your product.

The model in one diagram

  1. Workspace — Your company's home in Rheo: members, billing, and settings.
  2. App — A product or surface you onboard users into (often one per mobile app or brand).
  3. Convert — Flows, banners, channels, and experiments for in-app conversion.
  4. Flow — The multi-screen storyboard: screens, branching, visuals, motion, and copy.
  5. Channel — How you roll a published flow or banner out (staging, QA, approvals).
  6. Customer — An end-user record with attributes and eligibility for experiments.

Continue in Core concepts for short definitions of each term.

First fifteen minutes

  1. Sign in to your workspace and finish any Setup prompts (profile and workspace basics).

Rheo dashboard after first sign-in, showing the Setup checklist or empty Apps list with a prominent option to create an app

  1. Create or open an app from Apps so you have a container for flows.

Apps list with the Create app button and at least one app row visible

  1. Under Convert → Flows, create a flow (blank, template, import, or paste manifest). You land in the flow builder canvas. (For a single-frame promo, use Banners instead.)

Flow builder canvas with a new or template flow open, showing the screen list and canvas area

  1. Add at least one screen and connect it meaningfully. Keep the flow valid—the editor warns when required fields are missing.
  2. Save frequently; autosave backs you up during longer sessions. Publish a version when you are ready to pin it.
  3. Choose delivery:
    • Channel path — create or pick a channel under Convert → Channels, pin the published flow (or banner), and optionally open a rollout request if your workspace uses approvals.
    • SDK path — integrate the Rheo SDK in your app and configure your environment keys. Start with the SDK overview, then pick Expo, bare React Native, or web.
  4. Optional integrations — enable RevenueCat, Superwall, or AppsFlyer under App settings → Integrations before using paywall nodes or attribution-driven decisions. Headless external surfaces need no toggle (register host UI in the SDK). See Integrations.
  5. Optional Engage — when you are ready to message customers who opted in, connect email or push under App settings → Engage settings and start with a Broadcast or Automation. Webhook messages store their own endpoint. See Rheo Engage.

Limits

Validation rules and rollout policies depend on your workspace plan and each member's role. Some features (experiments, approvals, integrations) require Grow or Scale. See Plans & entitlements.

  • Convert — Convert pillar overview.
  • Flow builder — Layers, timelines, animations, comments, external surfaces.
  • Banners — Single-frame Convert surfaces.
  • Channels & rollout — Assign, approve, archive.
  • Experiments — Compare variants safely.
  • Rheo Engage — Email, webhook, and push broadcasts and automations.
  • Integrations — RevenueCat / Superwall paywalls, headless host UI, and AppsFlyer attribution.
  • CLI — Automate apps, flows, experiments, and Engage from the terminal.