Analytics & Usage Tracking
The Analytics dashboard gives you visibility into how your organization uses Ocriva — document processing volume, template efficiency, member activity, and storage utilization. Use it to identify patterns, spot anomalies, and optimize your workflows.
Accessing Analytics
Navigate to Analytics from the main sidebar. The page is scoped to your currently selected project and organization:
- Project-level data — processing history, recent activity, and project statistics
- Organization-level data — aggregate usage statistics, daily processing charts, template rankings, and member activity
You must be a member of the organization to view analytics. All data reflects the organization's projects collectively.
Date Range Selection
The analytics page supports four time ranges that control the date window for charts and statistics:
| Range | Period |
|---|---|
| 7d | Last 7 days |
| 30d | Last 30 days (default) |
| 90d | Last 90 days |
| 1y | Last 365 days |
Changing the date range reloads the daily processing chart and organization statistics. Summary cards (total documents, storage, members) always show all-time or current figures.
Summary Metrics
The top of the Analytics page shows organization-wide summary cards:
Documents
| Metric | Description |
|---|---|
| Total | All documents ever processed across all projects |
| This Month | Documents processed since the start of the current calendar month |
| Last Month | Documents processed in the previous calendar month |
| Growth | Percentage change between this month and last month |
Templates
| Metric | Description |
|---|---|
| Total | All non-deleted templates across all projects |
| Active | Templates with isActive: true |
| Inactive | Templates that exist but are disabled |
Storage
| Metric | Description |
|---|---|
| Used | Sum of all non-deleted upload file sizes (in MB) |
| Limit | Reference storage figure used for the dashboard display |
| Percentage | Used / Limit as a percentage |
NOTE
Storage figures are calculated from live upload records. Files that have been soft-deleted are excluded from the used storage total.
WARNING
The storage Limit shown in the analytics dashboard is a display reference constant and may not match the actual storage quota allocated by your subscription plan. For your real storage quota, check your organization's Limits page or the billing page. The Free plan, for example, includes 1 GB of storage — not 10 GB.
Members
| Metric | Description |
|---|---|
| Total | All memberships in the organization |
| Active | Members with status: active |
| Pending | Invited members who have not yet accepted |
Processing Quality
| Metric | Description |
|---|---|
| Success Rate | Percentage of completed vs. failed processing jobs |
| Average Processing Time | Mean time from job start to completion (in seconds) |
| Total Processing Time | Cumulative processing time across all completed jobs |
Daily Processing Chart
The daily processing chart visualises document activity over the selected date range. Each day shows:
- Documents processed — total count for that day
- Successful — jobs that completed without error
- Failed — jobs that encountered processing errors
Days with no activity are filled with zeros so the chart always covers the full selected range without gaps.
This chart is useful for identifying:
- Traffic spikes that may correlate with scheduled batch jobs
- Days with elevated failure rates, which may indicate template issues or upstream provider problems
- Processing patterns across the week or month
Template Usage Rankings
The Template Usage table shows the top 10 most-used templates across the organization, ranked by total usage count. For each template you can see:
| Column | Description |
|---|---|
| Name | Template name |
| Usage | Total documents processed using this template |
| Success Rate | Percentage of successful processing jobs for this template |
A template with a low success rate relative to its peers may have schema issues, be configured with a model that does not suit the document type, or be used with inconsistent input formats.
Member Activity
The Member Activity table shows the top 10 most active members in the organization, ranked by total documents processed. For each member you can see:
| Column | Description |
|---|---|
| Name | Member's full name |
| Documents Processed | Total documents this member has submitted |
| Last Active | Timestamp of their most recent processing activity (falls back to join date if no activity yet) |
This helps team administrators understand workload distribution and identify members who may need training or access adjustments.
Recent Processing Activity
Below the charts, the page shows the 10 most recent processing history records for the currently selected project. Each record includes the file name, processing status, template used, and timestamp.
To view the full history with search and filtering, go to the dedicated Processing History page within your project.
Webhook Statistics
If your organization has webhooks configured, the analytics page also displays webhook delivery statistics — the number of successful and failed deliveries within the selected period. This provides a quick health check without navigating to the Webhooks settings page.
Real-time Updates
The Analytics dashboard listens for dashboard_updated WebSocket events. When the platform emits a dashboard update — for example, after a document finishes processing — the page automatically reloads its statistics in the background without showing a loading state.
This means you do not need to manually refresh the page to see newly processed documents reflected in the charts and summary cards.
Exporting Analytics Data
Use the Export button on the Analytics page to download the current analytics snapshot as a JSON file. The export includes:
- Project details (name, description, creation date)
- All visible statistics and chart data
The exported file is timestamped so you can track reports over time.
Best Practices
- Check analytics before and after deploying template changes. A drop in success rate following a template update is a strong signal that the schema change is causing extraction failures.
- Use the 7-day view for operational monitoring, 30-day for reporting. Short ranges reveal recent anomalies; monthly ranges are better for trend analysis and billing forecasts.
- Cross-reference template success rates with credit consumption. Retrying failed jobs still consumes credits. High failure rates on a heavily used template can significantly inflate your credit spend.
- Review member activity monthly. If most processing is concentrated in one or two members, consider whether automation (API tokens and programmatic upload) could reduce manual effort.