> 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/reporting-1/routing-insights.md).

# Routing insights

Track click-to-meeting conversions, compare routers, and spot drop-offs.

Open **Click routing → Routing Insights** to see how routed visits convert to meetings.

Choose **Click date** and use **Add filter** for the router or rule. A click here is a recorded routed visit, not a unique-person count or every click reported by your email platform.

![Click-date metrics and click-volume reporting.](https://2442454418-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2FPlmXuXFqbGNc8c0E6EvZ%2Fclick-insights.png?alt=media)

| Metric                   | Meaning                                                                                 |
| ------------------------ | --------------------------------------------------------------------------------------- |
| **Total clicks**         | Routed visits in the selected click-date scope.                                         |
| **Meetings booked**      | Routed visits with a booking, plus their share of total clicks.                         |
| **Not booked**           | Routed visits without a booking.                                                        |
| **Average time to book** | Average hours between the routed visit and booking creation for booked visits in scope. |

**Click volume over time** shows the combined active scope. Use **Compare previous** to compare the preceding period. **Router performance** separates traffic and conversion by router; **Bookings by owner** shows who received converted traffic.

Drilldowns retain the click-date, router, and rule filters. Use **Routing Logs** to inspect an individual visit. Use [Booking Insights](/reporting/reporting-1/booking-insights.md) for meeting-date outcomes; its totals can differ because it uses a different date field.


---

# 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/reporting-1/routing-insights.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.