Core concepts
Customer
End users identified by the SDK who appear in Customers and analytics.
Purpose
A customer is an end user of your mobile app who interacts with Rheo onboarding. Rheo identifies them by a stable user ID your app provides when you integrate the SDK. The dashboard Customers section lists these users and shows per-user event timelines.
Customers are not synthetic dashboard personas. They appear from live SDK traffic in the selected environment (test or live).
Dashboard surfaces
| Area | What you see |
|---|---|
| Customers (app sidebar) | Searchable list with environment and date filters |
| Customer profile | Timeline, captured variables, permissions, and revenue signals |
Use customer profiles to debug individual journeys, verify experiment assignment, or support users who report onboarding issues.
How identity works
Your app provides identity when initializing the SDK:
- User ID (required) — Primary analytics key and experiment bucketing input. Use a stable ID that persists across sessions (for example your auth user ID or a generated anonymous ID).
- Custom user ID (optional) — Your CRM or backend user ID, set at runtime if it differs from the primary ID.
- Session ID (optional) — Per-launch session for funnel analysis.
Related
- Customers — List, profile, timeline, and variables.
- Customers & analytics — Flow-level funnels and cohort charts.
- SDK environment — Test vs live scope in the dashboard.