Statistics
Statistics
Technical metrics, payments, and subscribers
Statistics
Technical metrics, payments, and subscribers
Editor Statistics: how to read and use
The Statistics section shows actual bot behavior from runtime and audit data. Use it as an operational diagnostic tool: what really happened, where errors grow, and how payments/subscribers change.
Important
Important: statistics does not fix anything by itself. It helps you decide what to change in Canvas/System, where to add fallback, and which branches are error-prone.
Operational cycle
- 1) Choose the tab (
Technical,Payments,Subscribers) based on your current problem. - 2) Narrow period/filters to remove noise.
- 3) Find anomaly: error spike, empty activity, unexpected source.
- 4) Return to Canvas/System, apply a focused fix, run
Save -> Test. - 5) Re-open statistics and confirm metrics move in the expected direction.
1. Tab: Technical
Shows load, errors, and system events for the selected bot.
When to use: Use when bot behavior is unstable, responses are missing, or error rate grows.
Filters and ranges
Range:
Use short range (
1h / 24h / 7d.Refresh button for forced data reload.Use short range (
1h) for fresh incident debugging.KPI and key metrics
Total events — all events in selected range.Errors — number of error-level events.Error rate — error share across all events.Events / min — throughput intensity.Subscribers and Active in range — audience health in same window.Deep-dive checks
Event timeline reveals drops/spikes in activity.Top error sources shows where failures happen most often (runtime, telegram, editor, etc.).Recent audit events helps correlate with actions like settings.saved, test.started, test.stopped.If all metrics are zero, first verify test was actually running and Telegram updates were received.
2. Tab: Payments
Payment history with filters and summary metrics.
When to use: Use when validating conversion, pending buildup, or provider correctness.
Filters and ranges
Search by payer/id/username.
Period:
Method and status filters.
Period:
24h / 7d / 30d / all.Method and status filters.
KPI and key metrics
Total payments — number of transactions in period.Amount — aggregated payment amount (with currency limitations in UI).Successful — confirmed payments count.Pending / failed — unresolved and failed transactions in one KPI.Deep-dive checks
Table columns: payer, payment id, amount, method, status, time.
If pending grows and does not clear, check provider callback/webhook and auto-cancel timeout.
If failed rate spikes, verify provider secrets/keys and payment payload.
For disputed transaction, compare statistics row with runtime logs for the same timestamp.
If pending grows and does not clear, check provider callback/webhook and auto-cancel timeout.
If failed rate spikes, verify provider secrets/keys and payment payload.
For disputed transaction, compare statistics row with runtime logs for the same timestamp.
3. Tab: Subscribers
User base that interacted with the bot, plus source analytics.
When to use: Use when tracking audience growth, engagement, and traffic quality (message vs callback).
Filters and ranges
Search by name/username/user id.
Period:
Source:
Period:
24h / 7d / 30d / all.Source:
message / callback_query / unknown / all.KPI and key metrics
Total subscribers — total audience size.Active in period — users active in selected window.New in period — first-seen users in selected window.Last activity — latest recorded user interaction.Deep-dive checks
Source cards show distribution across
Language card shows top language_code values for localization prioritization.
Subscribers table: user, id, language, source, first/last seen.
If subscribers do not grow, verify subscriber collection mode is enabled in
message, callback_query, unknown.Language card shows top language_code values for localization prioritization.
Subscribers table: user, id, language, source, first/last seen.
If subscribers do not grow, verify subscriber collection mode is enabled in
System.Diagnostics
- Define problem class first: technical, payments, or audience.
- Use Dashboard -> Statistics for cross-bot analytics; editor Statistics is scoped to the current bot only.
- Avoid “all time” for incident response; start with narrow period.
- Correlate metrics with latest save/deploy/test cycle to avoid analyzing stale version.
- If numbers look wrong, click
Refreshand compare with test logs for same period. - For complex incidents, record period, filters, and KPI before/after each fix.
Documentation navigation
Move through pages step by step as a guided learning path.