# Analytics

[**Analytics**](/360/analytics) turns your bookings into numbers — how many meetings got
created and confirmed, how many fell through, when people book, and who's taking them.
There are two tabs: **Event Analytics** (bookings) and **Routing Analytics**
([routing forms](/help/routing-forms/overview)).

## What it is — Event Analytics

Pick a **date range** (last 7 / 30 / 90 days, etc.) and, if you're an admin, a **user**
filter (or "all users"). Then you get:

- **Headline metrics** — **Created**, **Confirmed**, **Rescheduled**, **No-show**, and
  **Canceled**, each with the change vs. the previous period of the same length.
- **Completed Events Trend** — a bar chart of completed meetings over the range.
- **Popular Events** — which event types get booked most.
- **Duration Distribution** — how bookings split across meeting lengths (42 min, 30 min…).
- **Popular Times** — which days of the week get the most bookings.
- **Top Users** — who's hosting the most meetings (and **Users with No Events** — who
  isn't).
- **Export CSV** — download the underlying data for the current range/filter.

<Screenshot
  src="/help/screenshots/workspace/analytics.png"
  alt="The 42min Analytics page on the Event Analytics tab: a date-range and user filter, an 'Export CSV' button, metric cards for Created / Confirmed / Rescheduled / No-show / Canceled, a 'Completed Events Trend' chart, and 'Popular Events', 'Duration Distribution', 'Popular Times', 'Top Users', and 'Users with No Events' panels"
  caption="Event Analytics — the headline numbers up top, then breakdowns by event type, duration, day of week, and host. Change the date range or user filter to re-slice everything."
/>

## Routing Analytics

The second tab covers your [routing forms](/help/routing-forms/overview): how many people
**started** and **completed** each form, and where they ended up — which
[destination](/help/routing-forms/destinations) (event type, external URL, message,
chained form) each response was routed to. Use it to see whether a form is doing its job
or sending too many people to a dead end / the wrong place.

## When to use it

- Monthly / quarterly reporting — "how many demos did we book? how many no-showed?"
- Spotting problems — a rising **no-show** or **canceled** rate, or a routing form with a
  low completion rate.
- Capacity and fairness — **Top Users** and **Users with No Events** show how load is
  spread (especially for [round-robin](/help/event-types/round-robin) teams).
- Tuning — which event types and times actually get booked, so you can adjust hours and
  offerings.

## Common pitfalls

- **Comparing to the Dashboard's "Last 30 days".** The [Dashboard](/help/workspace/dashboard)
  uses a fixed 30-day window with no user filter; here you can change both, so totals
  won't always match.
- **"No-show is zero but people don't always show."** No-shows are only counted when
  someone **marks** the meeting as a no-show on the [Meetings](/help/workspace/meetings)
  page — keep that habit up or the number understates reality.
- **Empty charts.** A new account (or a narrow date range with little activity) just
  doesn't have data yet — widen the range.
- **Routing numbers look low.** "Completed" only counts people who finished the form *and*
  were routed — drop-offs mid-form count as started-but-not-completed, which is itself the
  signal that the form is too long or unclear.
