Skip to content
Rival Docs

Analytics

The Analytics dashboard at cortexone.rival.io/analytics is the operational view of how your organization’s tools are doing. Revenue, runs, ratings - all in one place.

Who can see it

Analytics is Owner and Admin only. Members and viewers don’t see this sensitive data.

Controls

Time range - sets the window for all metrics. 7 days is the default. You can also choose 24 hours, 30 days, 90 days, or a custom range. The cards, chart, and tables all respect the selected range.

Main chart

The main chart visualizes the selected metric across the time range. Hover any point to see the exact value for that day. The chart updates immediately when you change the metric or the range.

For revenue, you’d see daily revenue across the window. For runs, daily run counts. For error rate, the daily error percentage.

Tool Performance table

The Tool Performance table breaks the selected metric down by tool. Each row shows:

  • Tool name and current public version
  • The metric value for that tool over the time range
  • Runs, revenue, error rate, and average latency (regardless of which metric is selected)
  • A quick link to open the tool

This is the table to start with when you’re hunting for outliers - the one tool eating most of your revenue, or the one with the worst error rate.

Top Users

The Top Users panel shows the organizations or accounts running your tools most often during the selected period. For each one you see:

  • The customer’s name
  • Number of runs
  • Revenue contributed (for paid tools)
  • The tool they use most

Useful for spotting power users, prioritizing support, or understanding who’s driving the bulk of your usage.

Using analytics day to day

The most common workflows:

  • Pick the metric, set the range, scan the cards. Catches anything obviously off in seconds.
  • Open the Tool Performance table. Find which tools are driving the metric and which are underperforming.
  • Drill into a tool’s detail page from the table when something needs investigation.

For per-run debugging - the actual input and output of a single execution - look at the run history on a specific tool’s detail page.