Analytics troubleshooting

Resolve empty reports, stale cards, missing app data, and differences between analytics and billing usage.

Video placeholder

Add a localized troubleshooting recording here: change the range, verify the organization, wait through cache latency, and distinguish missing instrumentation from an empty period.

The page shows no data

Confirm that the correct organization is active.
Check the selected range; 30d is the default, but an organization may have activity outside a short range.
Open the relevant public site, complete a test stream, use the app, or complete a test donation according to the view being checked.
Allow time for event delivery and cache refresh.
Refresh the page and compare the detailed view with the overview.

Do not treat the absence of a chart line as proof that the feature is broken. Many cards intentionally render the no-data state when their query returns an empty series.

Completed session totals come from the streaming-session database. Language demand, listener activity, audience curves, and pipeline health come from separate translation or viewer events. Those panels can show a pending state until the related instrumentation is deployed and the first instrumented sessions run.

App engagement is pending

The app KPI cards can populate from lifecycle and screen-view events while the engagement counters remain pending. The engagement panel requires the app version that emits the prayer-times, news, event, Qibla, stream-join, and notification-open events.

The quota does not match the chart

This is expected when comparing different time bases. The website chart uses the selected analytics range. The quota card uses the current billing period from Usage. Translation recording and restream context also use current billing-period usage.

A number looks stale

Check the metric’s cache tier in metric definitions. Live cards can be cached for up to 45 seconds, daily queries for up to 5 minutes, and heavy queries for up to 15 minutes. Event-based reports can take additional processing time.

A report fails while other cards render

Website, translation, app, and donation views use separate bundles and query groups. A provider or query failure can leave one detailed view empty while other organization data still loads. Record the organization, route, range, timestamp, and affected card before contacting support.