> ## Documentation Index
> Fetch the complete documentation index at: https://docs.verbose.cx/llms.txt
> Use this file to discover all available pages before exploring further.

# Analytics & reporting

> Track delivery, engagement, and revenue — with prebuilt reports and a custom builder.

Analytics answers "how are we doing?" across two surfaces: **prebuilt reports**
behind your dashboards, and a **custom report** builder for ad-hoc questions.

## Prebuilt reports

Named reports (overview and more) over a **time range** — `today`, `7d`, `30d`,
`mtd`, and so on. These cover the headline funnel: messages **sent** and
**delivered**, **replies**, **clicks**, **opt-outs**, and **conversions/revenue**.
On large workspaces they read from maintained rollups, so they stay fast even
over millions of messages.

## Custom reports

Build one **metric** grouped by a **dimension** over a **range** — e.g. replies
by campaign, clicks by day, conversions by offer — without a prebuilt report.
Use it to slice the funnel the way a specific question needs.

<Steps>
  <Step title="Pick a metric">
    What you're measuring — sent, delivered, replies, clicks, opt-outs,
    conversions, revenue.
  </Step>

  <Step title="Pick a dimension">
    How to break it down — by campaign, by day, by offer, and so on.
  </Step>

  <Step title="Pick a range">
    The window to measure over.
  </Step>
</Steps>

## Over the API & MCP

Pull reports programmatically — [Get a report](/api-reference)
(`GET /v1/analytics/{report}`) and [Custom report](/api-reference)
(`GET /v1/analytics/build`) — or just ask in natural language via the
[MCP server](/mcp) (e.g. "how did yesterday's campaigns do?").