Analytics answer one business question at a time: where do people drop out, which event types get attended, how far ahead do people book. Reporting is documented on the analytics page. The conversion guide shows the funnel to measure.
Before you start
- The question you want answered.
- The date range, event type, and time zone in scope.
- A baseline period to compare against.
How to complete this task
- Define the business question before choosing a report.
- Segment page views, slot views, booking starts, confirmations, and outcomes.
- Check date range, event type, team, source, and time zone.
- Act on one bottleneck and compare a complete period after the change.
Finish by opening the public link in a signed-out browser: a saved setting is not proof that the guest path works.
Troubleshooting
The problems people report most often with this task, and the cause behind each one.
Booking numbers disagree with the calendar.
Check the date range, time zone, and whether cancelled meetings are included. Those three account for most discrepancies.
Traffic is high but bookings are low.
The gap is usually between viewing the page and starting a booking. Look at duration, notice, and how few times are actually offered.
Which metric matters most?
Attended meetings. Confirmations that end in no-shows measure the booking page, not the outcome.
Related Meetin.gs help
Return to the Meetin.gs Help Center for the adjacent configuration guide, or send the exact event code and expected result when the documented checks do not explain the behavior.
