> Toden documentation. For the full index fetch /llms.txt. Every page is available as Markdown by appending .md to its URL. Identity verification uses /api/kyc, Risk Intelligence uses /api/v1; they are separate contracts with different error shapes. Never invent an endpoint, field or enum value: read the API reference page for the operation first. # Analytics dashboard > What the Toden console home dashboard shows, how each figure is calculated, the period and channel filters, exports and the permissions behind each section. The console home page is your analytics dashboard. It shows how much you are verifying, how those verifications end, what they cost and whether your integration is healthy. This page explains each section and exactly how its numbers are calculated, so that product, operations and compliance teams read them the same way. ## Where to find it Open **Home** in the console at [console.toden.co](https://console.toden.co). The figures follow the environment selector in the console header, so Sandbox and Production are always reported separately. ## Filters | Filter | Options | Notes | | ----------- | --------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Period | **7 days**, **30 days**, **90 days**, or **Custom** | The default is 30 days. A custom range is a pair of whole days in UTC, both included | | Channel | **SDK** or **Spot Checks** | Shown only when your organisation runs spot checks. SDK covers verifications started with an API key, Spot Checks covers one-off checks run from the console | | Granularity | **Daily**, **Weekly**, **Monthly** | Applies to the activity chart | Every comparison ("up 12% on the previous period") is against the window of equal length immediately before the one selected. With 30 days selected, the comparison is the 30 days before that. ## Sections The dashboard is made of sections that you can show, hide and reorder with **Customise**. | Section | What it shows | | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | **Verification performance** | Total verifications, approval rate, failed verifications, average processing time, average workflow cost and projected monthly spend | | **What needs your attention** | The items that currently need action, with the reason and the next step | | **Trends and outcomes** | Verification activity over time, and the outcome mix: approved, rejected, manual review, abandoned, in flight and errored | | **Workflow performance** | One row per workflow: volume, approval rate, manual review rate, abandonment, completion, median duration and cost | | **Risk & fraud** | Screenings run, sanctions, PEP and adverse media matches, events blocked by a rule and alerts still open | | **Integration health** | Webhook delivery success, failed deliveries, the retry queue and verification processing time | | **Failure reasons** | Why verifications failed, grouped by who can act on it | | **Verification breakdowns** | Performance by verification location (country) and by identity document | | **Recent verifications** | The latest verification outcomes | | **Team activity** | Recent changes made by your team | ## How the figures are calculated #### Volume and approval rate Total verifications counts every verification created in the period, in the selected environment and channel. The headline approval rate is verified verifications divided by all verifications in the period, rounded to a whole percentage. Verifications still processing count in the total, so the rate for a very recent period can rise as they finish. Deleted verifications are excluded everywhere, so the totals always match what your lists show. #### Outcome series In the activity chart, each period bucket splits verifications into verified, failed, not found and pending. Verifications that failed the check and verifications that ended in a system error share the "failed" series in this chart, because the chart answers whether volume is healthy. The **Failure reasons** section separates them. Buckets are in UTC. #### Workflow rates Workflow figures count workflow runs, not verifications. * **Approval rate** and **manual review rate** are shares of runs that reached a decision. Runs still in flight are left out of the denominator. * **Abandonment rate** is the share of all runs that are unfinished and past their deadline. A run with no deadline of its own counts as abandoned once it has been unfinished for 24 hours. This is a reporting rule only and never changes the run. * **Median duration** is the median time from start to completion. The median is used so that one run left waiting over a weekend does not distort the figure. * The table shows your 12 busiest workflows by run volume. #### Failure reasons Each failed verification carries a reason code (see [Errors](/get-started/errors)). The section groups them into four categories: the person being verified, your setup, Toden, and sandbox test outcomes. This tells you whether a rise in failures is something your users, your configuration or Toden needs to fix. Each reason shows its count, its share of all failures and the count in the previous period. #### Cost and spend Amounts come from your billing ledger, which is held in USD. If you have chosen another display currency, the console converts them for display only. * **Average cost** is spend in the period divided by the number of verifications that were charged. * **Projected monthly spend** is this calendar month's spend so far, extended at the same daily rate to the end of the month. It appears from the second day of the month, once there is spend to project from. * Spend figures are **not** split by environment. Sandbox verifications are free, so in practice spend is production spend. See [Billing](/get-started/billing) for how charges are made. #### Integration health Webhook delivery success is delivered events divided by delivered plus failed events in the period. The retry queue counts deliveries waiting to be sent or retried. Processing time is reported as the 50th, 95th and 99th percentile of the time Toden took to process a verification. > **Note** > > A figure with nothing to measure is shown as empty, not as zero. A workflow with no decided runs has no approval rate, and an endpoint that received no events has no delivery success rate. An empty value means "no data yet", never "0%". ## Who sees what The dashboard is assembled from several reads, each with its own permission. A section you are not permitted to read is simply not populated. | Data | Permission | | ------------------------------------------------------- | -------------------- | | Volume, outcomes, activity, breakdowns, processing time | `analytics:read` | | Workflow performance | `workflows:read` | | Failure reasons | `verifications:read` | | Spend and cost composition | `billing:read` | | Screening matches | `screening:read` | | Rule decisions and open alerts | `alerts:read` | | Webhook delivery figures | `webhooks:read` | All built-in roles hold these read permissions by default. See [Roles and permissions](/get-started/console/roles-permissions). ## Export Use **Export** on the home page to download the current view as a CSV file or a PDF report. The export uses the period and channel you have selected. ## Reporting from your own systems The dashboard figures are a console feature and are not part of the public API. To build your own reporting, use the data the API does expose: * [Webhooks](/integrate/webhooks/overview) deliver every verification outcome as it happens, which is the most reliable feed for a data warehouse. * The [API reference](/api-reference/overview) covers listing verifications with filters for status, date range, country, ID type and workflow. ## Related * [Billing](/get-started/billing) * [Errors](/get-started/errors) * [Workflows](/user-verification/workflows/workflows) * [Audit logs](/get-started/console/audit-logs)