A booking record does not establish attendance or qualification
Verify that a supported booking record represents the event you intend to count. A scheduling-page visit, confirmed meeting and canceled event are different stages.
Calendar bookings can provide useful inbound evidence, but creation, rescheduling, cancellation and attendance are different states. Define which records count and how repeated bookings by the same person are handled.
A worked example
A hypothetical prospect submits a form and books a meeting, then reschedules twice. That can represent one person and one continuing meeting journey, not four new leads. Attendance and qualification still need their own evidence.
How to apply it
- Capture the stable booking identity and relevant state where supported.
- Preserve source context and distinguish new bookings from updates.
- Review overlap with forms and other intake sources before counting unique inquiries.
What the result can establish
Use actual booking records rather than inferred button clicks. Keep missing attendance data unknown. A calendar count helps review intake and follow-up, not prove that every scheduled conversation produced pipeline.
Reference: Google Analytics: recommended events.
Supporting documentation
Google Analytics: recommended eventsW3C WAI: validating formsGoogle Analytics: measurement documentation