Customers
Browse end users, inspect individual journeys, and debug support issues one person at a time.
What Customers is for
Customers are people associated with your app: SDK end users, product-analytics visitors who become customer records, and people created by Engage CSV import or email identify — including those who never completed a Convert flow.
The sidebar Customers group includes:
- Overview — app-level customer KPIs and charts (below)
- All customers — journey list and profiles (this page’s list section)
- Segments — audience filters for Engage broadcasts and automations
Dynamic segments use rules (attributes, consent, did / did not do an event). AI-assisted natural-language segments require Grow+ (same AI entitlement as Rheo Agent). Static segments are a fixed membership from a CSV of existing customers (Import segment).
Use Overview for trends across the app. Use All customers to answer support questions ("what did this user see?"), verify a single journey, inspect captured variables and permissions, or manage marketing consent. For charts across thousands of users in one flow, use Customers & analytics. For visitors and sessions across the app, use Analytics.
Customers Overview
Open Customers → Overview. The page uses the test / live environment selector and a date range. Each KPI tile shows a prior-period percent change for the same-length window immediately before your range.
KPI tiles
| Tile | Meaning |
|---|---|
| Customers | People created or updated in range, from any source, plus people with a flow start in range |
| New | First flow start in range (imports-only contacts excluded) |
| Returning | Flow start in range where the first flow start was before the range |
| With email | Subset of Customers with an email address (tile hint shows % of customers in range) |
| Marketing opt-in | Subset with marketing consent granted (same % hint) |
Charts
| Chart | What it shows |
|---|---|
| Customer growth | Running total through the end of the range, from each customer's first flow start |
| New and returning | First flow start versus a later one, by day (a person can return on more than one day) |
| Reachability | Marketing opt-in, email without opt-in, and no email for customers in range |
| Languages | Language on the latest flow start in range |
Use All customers in the header to open the journey list for the same environment.

Customer list
Open Customers → All customers.
Filters
- Environment — test or live (same selector used elsewhere in analytics)
- Search — user id or email
Table columns
| Column | Meaning |
|---|---|
| Customer ID | Masked identifier with a link to the profile |
| Status | Completed if they finished a flow in range; otherwise In progress |
| Language | Latest locale from their events |
| First / last seen | Activity timestamps |
| Flow starts / completions | How many times they started or finished flows |
| Revenue | On the profile, not this list. Net webhook gross in the selected range, including the first charge, renewals, and refunds. |
Summary tiles above the table show totals for customers in range, identified users (when your app sends a custom user id), flow starts, and completions.
Customer profile
Click a customer to open their profile. The heading is their first and last name when a name is stored. Either name alone is enough. Otherwise the heading is the same masked customer id as All customers. The breadcrumb stays that masked id.

Activity summary
Cards for flows started, completions, user since, and last active when start events exist in your date range. If the profile looks empty, try another environment or a wider range.
Customer history (timeline)
A chronological list of what this person did in the selected date range: Convert flow events, product analytics (sessions, pages, screens, and custom events from logEvent), and Engage messages. Older profiles can still show a row labeled Track. New custom events appear as product analytics. Each row is labeled with its kind. Flow names appear in plain language. Load more continues through the window.
Experiment variant labels can appear on Convert rows when validating which arm someone was in.
Sidebar panels
| Panel | Content |
|---|---|
| User IDs | Customer id, optional custom id from your backend, session context |
| Customer attributes | First name, last name, phone, locale, country, and timezone, then any other stored customer attributes. Empty fields stay off the card. |
| Revenues | Net webhook gross in the selected range, in USD. Includes the first charge, renewals, and refunds. Flow analytics revenue is originating charges only. |
| Recent context | Latest platform, locale, app version, channel, and flow |
| Variables | Values captured in flows or sent from the SDK. Separate from customer attributes. |
| Permissions | OS permission states Rheo recorded (for example notifications) |
Sensitive variable values may be masked in the UI depending on the key.
Identity fields
| Field | Role |
|---|---|
| Customer id | Required stable id from your app — primary key for analytics |
| Custom user id | Optional id from your CRM or backend |
| Session id | Optional per-launch session |
Customers are built from real SDK events, not synthetic personas. Your developers must send a stable customer id for sticky experiment assignment and accurate history.
Customers vs flow analytics
| Question | Where to look |
|---|---|
| How are customers trending for this app? | Customers → Overview |
| How is this one person doing? | Customers → All customers profile |
| How is the product used across web and mobile? | Analytics |
| How is the flow performing overall? | Customers & analytics on the flow page |
| Which variant won? | Experiments |
Limits
- The list shows up to 100 customers per page; use filters to narrow results.
- Aggregates may lag slightly after sudden traffic spikes.
- Viewers can browse customers if they have read access to the app.