> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/reporting/overview.md).

# Reporting overview

Use reporting to understand how prospects move through routing and booking. Start with your routing type, then choose the report that answers your question.

## Choose your reporting area

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Inbound reports</strong></td><td>Track website form submissions, qualification, and meeting outcomes.</td><td><a href="/reporting/reporting.md">Inbound reports</a></td><td><a href="https://2442454418-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2FnSbsXJknntpsJ9G33c3u%2Freport-guide-inbound.png?alt=media">report-guide-inbound.png</a></td></tr><tr><td><strong>Campaign reports</strong></td><td>Follow routed visits from campaign links through booking and meeting outcomes.</td><td><a href="/reporting/reporting-1.md">Campaign reports</a></td><td><a href="https://2442454418-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2FIlXjKOHTZa2Le6Nco2q8%2Freport-guide-campaign.png?alt=media">report-guide-campaign.png</a></td></tr><tr><td><strong>Outbound reports</strong></td><td>Review sales handoffs, assignments, booking conversion, and delivery health.</td><td><a href="/reporting/outbound-reports.md">Outbound reports</a></td><td><a href="https://2442454418-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2FXAL9LEjacwGlD6j3lgBV%2Freport-guide-outbound.png?alt=media">report-guide-outbound.png</a></td></tr></tbody></table>

Open inbound reports from **Form routing**, campaign reports from **Click routing**, and outbound reports from **Outbound routing**. Outbound reports are available to workspace admins.

## Find the right report

| Report               | Use it to                                                                                                  |
| -------------------- | ---------------------------------------------------------------------------------------------------------- |
| **Routing Insights** | Follow the routing process from a form submission, routed visit, or sales handoff.                         |
| **Booking Insights** | Review meeting outcomes and owner workload, or outbound booking conversion, channels, and delivery health. |
| **Routing Logs**     | Inspect an individual submission, routed visit, or handoff and its routing context.                        |

## Compare date ranges

Each report uses a specific date field. Match the date range and filters before comparing results.

| Reporting area | Routing Insights | Booking Insights |
| -------------- | ---------------- | ---------------- |
| **Inbound**    | Submission date  | Meeting date     |
| **Campaign**   | Click date       | Meeting date     |
| **Outbound**   | Handoff date     | Handoff date     |

A form submission or campaign click this week can produce a meeting scheduled next month, so routing and booking totals can differ for the same date range. Both outbound insight reports use the date the handoff started.

For an individual prospect, follow [Routing Logs](/reporting/routing-logs.md). Personal and group booking-link CRM delivery is tracked in [CRM activity](/crm/activity.md), separately from routing reports.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.distro.so/reporting/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.