How do I read my Toden analytics?

Short answer

Start on the console Home page, confirm the environment and choose the reporting period and channel. Then read volume, outcomes, workflow performance, costs and integration health together. Different figures can use different populations and should not be compared as though they were the same measure.

Align the filters

Sandbox and Production are reported separately. The period and channel filters affect the current view and its export. Custom reporting dates use whole UTC days. A previous-period comparison uses an equally long window immediately before the selected one.

Check these filters first when two teammates report different numbers. An API-key-started verification and a console Spot Check can fall into different channels.

Read the denominator

Verification volume includes records created in the selected period, including work still processing. Very recent rates can change as those checks finish. Deleted verifications are excluded from the documented dashboard totals.

Workflow rates count workflow runs and can exclude in-flight runs from particular decision-rate denominators. A workflow approval percentage therefore need not equal the headline verification percentage. Median duration is also different from an arithmetic average.

Find the next action

Use Failure reasons to distinguish applicant capture problems, your configuration, Toden faults and Sandbox test outcomes. Integration health shows webhook delivery and retry issues. Risk and fraud panels describe a different set of screening and activity events from ordinary verification volume.

A missing section may reflect your permissions. Spend, screening, workflow and webhook panels each have their own access requirements.

For external reporting, retain your signed event feed or use documented listing APIs. The console analytics figures are not a separate public analytics API.

Related guides

• Analytics definitions and exports
• Billing