Rheo documentation
Core concepts

SDK environment

Test vs live environments, publishable keys, and how the SDK connects to Rheo.

Purpose

Every Rheo app has two fixed environments: test and live. They are created automatically. You do not add environments manually. Each environment has its own publishable API key and channels. The SDK authenticates with the key (which selects the environment) and names the channel (which selects what to serve).

Publishable keys

EnvironmentKey formatTypical use
TestStarts with ob_pk_test_Development, QA, internal builds
LiveStarts with ob_pk_live_App Store, Play, and production website builds

Copy keys from App settings → API keys. Keys are used when your app initializes the SDK—they are not dashboard login credentials. The same key works for the mobile SDKs and the web SDK. Browser calls also require the site origin under App settings → SDK. Never commit live keys to public source control.

Production API: Live (ob_pk_live_*) and test (ob_pk_test_*) keys both talk to Rheo's hosted API at https://api.getrheo.io. The key selects the environment (test vs live channel assignments); you do not need a separate API host unless you self-host.

App settings → API keys page showing separate test and live publishable keys with copy buttons

Channel routing

A channel belongs to exactly one environment. When you integrate the SDK, pass the channel's public ID (for example ch_test_… or ch_live_…) alongside the publishable key for that environment.

Rheo verifies the channel matches the app and environment implied by the key. The SDK never sends a flow or banner ID. The server returns the channel's content kind: a published flow, a published banner, a code key and parameters, or one experiment variant. An unassigned channel returns not found.

React Native example

Pass credentials on config. Mount the channel on <Flow />, <RheoBanner />, or useChannel — not on RheoProvider.

import { RheoProvider, Flow } from '@getrheo/react-native-expo';
import type { RheoConfig } from '@getrheo/react-native-expo';

const rheoConfig: RheoConfig = {
  publishableKey: 'ob_pk_test_…',
  userId: userId, // required on React Native
};

<RheoProvider config={rheoConfig}>
  <Flow channelId="ch_test_…" />
</RheoProvider>

See the React Native SDK guides for setup, caching behavior, and event APIs.

Logging: Omit logLevel on RheoProvider in production builds — the SDK defaults to silent (no console output). Use warn when debugging event transport; debug only in dev builds for manifest dumps and integration hints. See Diagnostics and logging.

Dashboard test vs live toggle

The main sidebar has a Show test data toggle just above App settings. It scopes analytics, channels, customers, and Engage to the test environment while it is on, and to production while it is off. The choice is stored in the page link, so it persists when you share the URL with teammates. The toggle affects dashboard views only. The SDK environment is determined by which publishable key you embed in the app build.

Dashboard environment toggle (test/live) visible on a Channels or Customers page

MAU and billing

Live environment monthly active users count toward plan limits and Indie caps. Test traffic is excluded from live MAU metering. Usage alerts appear in the dashboard as you approach limits on Indie plans.