Skip to main content
The partner analytics dashboard puts the evidence left by completed work beside the operational numbers that produced it. It is labeled Tessera Analytics in the partner portal and lives at:
Dashboard
Sign in with a user linked to your partner account. The page requests a 90-day snapshot and renders only that partner’s orders.

​
Evidence coverage first

Order throughput says work moved. Evidence coverage says what record remains. The dashboard places three counts together:
  • Completed orders assessed — orders in the 90-day creation cohort whose current status is Completed.
  • Sealed documents — attached document rows recorded as sealed or notarized for orders in the cohort.
  • Delivered with proof — attached shipment rows currently recorded as Delivered for orders in the cohort.
These are inventory counts, not a percentage or a unique-order coverage ratio. The document and shipment counters cover all orders in the cohort, not only completed orders, and one order can contribute multiple rows. They can therefore exceed the completed-order count. Read them as “evidence artifacts held,” not “percent of completed orders covered.” For the evidence vocabulary behind the records, see the evidence model.

​
What the dashboard shows

​
Volume

The monthly chart groups orders by their UTC creation month and shows:
  • all orders created in that month; and
  • how many of those same orders are currently Completed.
This is cohort reporting. “Completed” does not mean the completion happened during the displayed month. Months with no orders in the 90-day cohort are omitted.

​
Funnel

Every order in the cohort appears in exactly one current-state bucket: Created, Paid, In progress, Completed, or Problem. “Created” is the pre-payment bucket, not total created volume. The exact status-to-bucket contract is listed in the analytics API reference.

​
Turnaround

The headline reports median turnaround and shows the 90th percentile alongside it. Turnaround is measured only for completed cohort orders with a recorded payment.cleared event, from the earliest payment-clear time to the order’s current updatedAt completion stamp. When no order qualifies, the API returns zero hours. Treat that as no measurable sample; the dashboard does not show a separate sample size.

​
Service mix

Four counters show how many cohort orders include Sign, Notarize, Ship, and Fax. Services overlap: an order that includes signing, notarization, and shipping increments all three counters.

​
Revenue

Revenue is the sum of order totals, in USD cents before display formatting, for orders currently in the Paid, In progress, or Completed funnel buckets. Created and Problem orders are excluded. It is a current-order-total measure, not a payment-ledger balance.

​
Request-time figures

The dashboard does not replay a cached event stream. On each page request it reads your partner-scoped order cohort and derives the funnel, volume, service mix, evidence, turnaround, and revenue from the current transactional records. The page uses a no-store request and displays the response’s generation date. This has two practical consequences:
  • Current-state figures can change when an existing order advances, even if no new order entered the 90-day cohort.
  • An order ages out when its creation time falls outside the window, regardless of when it later completed, shipped, or acquired evidence.
For field-level definitions, a selectable 1..366-day window, authentication, and a complete response example, see GET /api/partner/analytics.