Clarity session data freshness: missing processing status for newly recorded sessions

Direct answer

The Clarity Export API does not expose a per‑session processing timestamp or status field, and there is no documented project setting that changes the aggregation cycle or reduces latency on the free tier. The only reliable way to know when a specific session has become queryable is to poll the dashboard (or the Export API for aggregated data) until the session appears.

Likely explanation vs. confirmed facts

• Confirmed fact: Sessions are recorded client‑side, uploaded asynchronously, and become visible only after server‑side ingestion and aggregation finish. This delay is expected behavior, not a bug.
• Likely explanation: Because the dashboard and Export API read from pre‑aggregated column stores, a session that has finished ingestion may still be invisible until the next aggregation cycle runs, creating the observed latency.

Steps to determine when a session is queryable

1. Record a test session and note the exact client‑side timestamp (or add a custom tag).
2. After a short wait (e.g., 5 minutes), open the Clarity dashboard → Recordings list and filter by the recorded time range or the custom tag.
3. If the session does not appear, wait another interval and repeat the check.
4. Continue polling until the session shows up; the elapsed time gives you the current end‑to‑end latency for your project.

If you need sub‑hour latency and are on a paid tier, you may want to verify whether your plan offers faster processing; otherwise, the polling approach is the only documented method.

Missing diagnostic detail

Are you using the free tier or a paid Clarity plan? This influences whether reduced‑latency options might be available and could change the recommendation.