Analyze your Flow App
Flow App Studio tracks every user session and records usage data over time. Use the analytics views to understand how users interact with your flows and monitor against your plan’s limits.
Sessions
A session is a single user interaction from the first message to the End Node (or timeout). Every session is stored with:
| Field | Description |
|---|---|
| Session ID | The unique identifier passed by the provider (e.g. USSD session ID, Telegram chat ID) |
| Provider | Which channel the session came from |
| MSISDN / User ID | The user’s identifier (phone number, username, etc.) |
| Start time | When the session began |
| End time | When the session ended or timed out |
| State | The last node the user was on and any stored variables |
Sessions are visible in the project’s Analytics panel in the builder.
Usage Records
Flow App Studio tracks aggregate usage per organisation per month:
| Metric | Description |
|---|---|
active_apps | Number of projects that received at least one session this month |
session_count | Total sessions across all projects this month |
api_call_count | Total outbound API calls made from flows this month |
Usage records reset at the start of each billing month. You can view current usage in the Billing section of the web app — it shows consumption against your plan’s limits.
App Analytics
Each project has a dedicated Analytics view inside the builder. It shows:
- Session volume over time
- Drop-off by node — which nodes users exit from most
- Response distribution — how users split across branching options
- Session duration distribution
Use this view to identify friction points in your flow — nodes with high drop-off rates are candidates for redesign.
Plan Limits
Analytics data also powers the quota enforcement UI. When your organisation approaches its plan limits, the builder shows a warning:
| Limit | Enforced on |
|---|---|
max_apps | Number of projects you can create |
max_team_members | Number of users in your organisation |
max_sessions | Monthly session budget |
Pass current usage to the FlowStudio component via the quota prop so the UI can surface these warnings inline:
<FlowStudio
api_key="..."
quota={{
plan: 'Basic',
max_sessions: 10000,
current_sessions: 9200,
max_apps: 5,
current_apps: 4,
}}
/>The quota prop controls the builder UI warnings only. Actual session enforcement happens server-side in the Flow Engine.