Confusion on /v2/conversations vs /v2/analytics/conversations for real-time state

Getting 404 Not Found when hitting /api/v2/analytics/conversations for active calls. The docs say this endpoint is for aggregates, but I need current state (active, queued) for a dashboard. The /api/v2/conversations endpoint works but feels heavy for just checking status. Which one should I use for real-time data without hitting rate limits?