Skip to main content

Query Analytics

Before you start​

Use a token authorized for event reads (events.read or the applicable admin authority), the API base URL provided with your tenant, and a date/type where you have accepted data. Analytics event reads use verified Parquet selected from the segment ledger. There is no recent-event Postgres fallback.

Read a small range​

  1. Open Events (/events), select the intended date range and event type, and inspect returned rows.

  2. If using the API, send a bounded query like this JSON body:

    {"date":"2026-09-19","eventType":"page-view","limit":100,"source":"auto"}

    The route is POST /api/v1/analytics/query. Replace the date and event type with your actual data; send JSON content type and your bearer token.

  3. For multiple dates, use POST /api/v1/analytics/query-range with from, to, and the supported grouping/filter fields from the API reference.

  4. Check returned coverage and warnings alongside the rows. Follow a recent ingest receipt in Ready data if it is still processing.

Expected result: rows for the authorized tenant and chosen range, or an explicit empty/incomplete response. A limit bounds the response; it does not prove that only that many events exist. Use Reports for published aggregated results.

Recovery​

Missing rows can mean a wrong filter, processing input or missing verified coverage. Check the receipt and range before resending. Do not force a removed hot-store source. Correct a rejected query using its validation error and the API contract; keep request IDs when escalation is required.