Analysis
What the dashboard and the analytics API can answer
Everything below runs on the same analytics API the dashboard uses, so a script with a project key and secret gets the same numbers.
| Question | Where | Endpoint |
|---|---|---|
| How much traffic did we get? | Overview cards | GET /v1/analytics/overview, /metrics |
| How does it move over time? | Time series chart | GET /v1/analytics/timeseries |
| Which events happen most? | Top events | GET /v1/analytics/top-events |
| What exactly happened, and to whom? | Events explorer | POST /v1/analytics/events |
| Who are our users? | Users explorer | GET /v1/analytics/users |
| Where do people drop off? | Funnels | POST /v1/analytics/funnel |
| Do they come back? | Retention | POST /v1/analytics/retention |
| How does one event split by a property? | Segments | POST /v1/analytics/segments |
| Give me the raw data | Export | GET /v1/analytics/export/events, /export/users |
Date ranges
Every query takes start and end (ISO 8601). The dashboard defaults to the last 7 days; exports and lists page with limit (1 to 1000, default 100) and offset.
Live updates
The dashboard subscribes to GET /v1/analytics/init/stream, a server-sent events feed that pushes fresh panels while the page is open.
Programmatic access
Send X-Project-Key and X-Project-Secret instead of a session to read one project's analytics from a script running on your servers (never from an app or a browser; see Authentication). The pair is read-only and pinned to that project.