Metric definitions and data behavior
Reference the exact analytics definitions, time windows, cache behavior, organization scope, and relationship to Usage.
Video placeholder
Add a localized screen recording here: demonstrate a range change, compare a detailed report with Usage, and show the difference between no data and pending data.
Metric definitions
| Metric | Definition in the current dashboard |
|---|---|
| Pageview | A public tenant-site $pageview event; marketing and dashboard traffic are excluded |
| Unique visitor | A distinct visitor identifier in the selected website range |
| Visitors now | Distinct people with public-site activity in the last five minutes |
| Views (30 min) | Public-site pageviews in the last thirty minutes |
| Session | A completed streaming session recorded for the organization |
| Streaming minutes | Sum of completed streaming-session durations |
| Peak listeners | Maximum peak-listener value among sessions in the selected range |
| Recording/restream minutes | Current billing-period usage values shown as translation context |
| DAU/WAU/MAU | Unique app users in rolling one-day, seven-day, and thirty-day windows |
| Returning app users | Current-range users also observed in the previous equal-length range |
| Donation revenue | Succeeded one-time and recurring donation amounts in the selected range |
| Active subscriptions | Recurring donations whose current status is active |
| MRR | Monthly equivalent of current active recurring subscriptions |
| Donation funnel | Analytics events for form viewed, checkout started, and completed |
Ranges and comparisons
The allowed range values are 7d, 30d, 90d, and 12m. An invalid or missing range falls back to 30d. Most selected-range queries use the last 7, 30, 90, or 365 days. The 12-month time series uses monthly buckets; shorter ranges use daily buckets.
Some values use fixed windows or current state instead:
- Website live cards use 5-minute and 30-minute windows.
- Overview cards use fixed 30-day, today, or seven-day windows.
- App DAU, WAU, and MAU use fixed rolling windows.
- Translation calendar covers one year.
- Translation recording and restream KPI values come from the current billing period.
- Donation goals describe active project state.
- Subscription movement always covers twelve months.
Where a KPI has a delta, the current selected window is compared with the immediately preceding window of equal length.
Latency and caching
Analytics data is cached per organization and query. The current cache tiers are:
- Live queries: up to 45 seconds.
- Daily queries: up to 5 minutes.
- Heavy queries: up to 15 minutes.
New activity can therefore take time to appear. The analytics provider may also process events asynchronously, especially for funnel, language-demand, listener, pipeline, and mobile-app engagement panels.
No data versus pending
The dashboard uses two different empty states:
- No data in this period means the selected source contains no recorded activity for the selected window, or the query returned no rows.
- Data arrives after the next update means the translation-agent instrumentation has not yet accrued data.
- Data arrives with the next app update means the richer mobile-app engagement events are not available until an instrumented app version is in use.
A no-data state is not a failure. First change the range, confirm the correct organization, and perform the source activity that should create the event.
Analytics and Usage are different views
Analytics answers “what activity was observed in this reporting window?” Usage answers “how much of the current billing period has been consumed?” The website pageview quota card reads the current pageview limit from Usage, while the website chart follows the selected analytics range. Translation recording and restream cards similarly show current billing-period usage even when the selected analytics range is 7, 30, or 90 days.
Use Analytics for behavior and trends. Use /usage for plan limits, current consumption, and billing-period decisions.