Ascend Documentation

Appearance

Analytics ​

Sidebar → Booking → View analytics (or visit /booking/analytics). Per-event-type and team-level metrics for diagnosing what's working.

What's on the Page ​

Three sections, top to bottom.

Headline numbers ​

A row of cards covering the selected period:

MetricWhat it counts
Confirmed bookingsDistinct bookings with status = confirmed or completed.
Cancellation rateCancelled / (Confirmed + Cancelled). Lower is better.
No-show rateNo-show / Completed. Includes hosts manually marking no-show.
Reschedule rateReschedules / Confirmed. High rates often mean your slots are too tight.
RevenueSum of paid-booking amounts (paid event types only).

Per-event-type breakdown ​

A table — one row per event type — with the same columns plus:

ColumnWhat it shows
Conversion(Confirmed) / (Booking page views). The "view" denominator counts unique sessions hitting the public page, not raw page loads.
Avg lead timeMedian time between booking creation and meeting start. Short lead times often mean availability is too tight.
Top question answerThe most common answer to your first single-select question (if any). Useful for sales triage.

Click a row to filter the rest of the page to that event type.

Time series ​

A line chart of bookings per day across the period. Tooltip shows confirmed, cancelled, and no-show separately.

Filters ​

Top of the page:

  • Date range — Last 7 days, Last 30 days, Last 90 days, This year, Custom.
  • Event type — All, or pick specific ones.
  • Host — All, or pick specific teammates.
  • Source — Direct, embedded, routing form, paid ad (if you used UTM-tagged links).

Source Attribution ​

If you append ?utm_source=...&utm_medium=...&utm_campaign=... to your booking links, Ascend captures those values on every confirmed booking. The Source filter then segments analytics by them.

Useful for:

  • Comparing booking conversion from your website vs. your email signature.
  • Seeing which marketing campaign drove the most confirmed meetings.
  • Splitting "we shared this in a webinar" vs. "this is on our pricing page".

The captured values appear on the booking detail sheet under "Source" too.

Per-Host Load (Round-Robin) ​

For round-robin event types, the analytics page shows a per-host breakdown of the pool — total bookings each member ran in the period. Useful for confirming your selection strategy is actually balancing load (or intentionally not, if you picked priority order).

Exporting ​

Click Export CSV in the top-right. Exports the current filtered view as a flat CSV: one row per booking with columns for every metric and every custom-question answer. Useful for pivoting in Excel or feeding into a BI tool.

What's Not Tracked ​

By design:

  • Page-level events on the public booking page (e.g. "scrolled to the picker") — too noisy, no privacy story for bookers.
  • IP / location of bookers — we don't capture them.
  • Mouse heatmaps — out of scope.

If you need deeper funnel analytics (e.g. "where do people drop off in the picker?"), embed the booking page in a wrapper you control and run your own analytics on the wrapper.

Plan Gating ​

Analytics is included on every plan, including Free. Source attribution and the per-host load breakdown are Pro+ only. The page renders empty cards on Free with a "Upgrade to see" affordance under the gated metrics.