calendareventtrackingcleaned.txt Page 1 / 1 100%

Contents:

• Overview
• Use Cases
• Prerequisites
• What Gets Synced from the Calendar
• Buffer Events
• Viewing Calendar-Initiated Changes
• Reporting
• Considerations
• Troubleshooting
• Summary

 

Overview

When a meeting is booked through LeanData Scheduling, BookIt creates a calendar event on the host's Google or Microsoft calendar. Hosts and guests often act on that calendar event directly instead of using the cancel and reschedule links BookIt provides. Calendar Event Tracking keeps the Meeting Log in step with those calendar actions, so a meeting that was cancelled, moved, or updated on the calendar is reflected in BookIt with the correct status, times, and attribution.

A few terms used throughout this guide:

• Meeting event: the calendar event that represents the booked meeting and includes the hosts and guests.
• Buffer event: an optional calendar hold BookIt creates before or after a meeting for required hosts, configured on the Meeting Type.
• Meeting Log: the BookIt record that tracks the full lifecycle of a booked meeting and feeds reporting.
• Calendar-initiated change: any change made in the native Google or Microsoft calendar rather than through a BookIt cancel or reschedule link or the Meeting Logs page.

BookIt tracks changes only on events it created and can match back to a Meeting Log. Changes to any other event on the host's calendar are ignored.

Use Cases

• Accurate cancellation reporting. A rep deletes a meeting from their calendar after a no-show. The Meeting Log shows the meeting as cancelled instead of leaving it in a scheduled state, and the rep receives a meeting credit request for count-based pools.
• Accurate reschedule reporting. A host drags a meeting to a new time on the calendar. The Meeting Log start and end times update, reminders are recalculated for the new time, and the reschedule is counted in reporting.
• Pre-meeting preparation. A rep checks who has accepted, declined, or marked a meeting as maybe before joining the call.
• Cancellation and reschedule source analysis. An admin compares meetings changed on the calendar against those changed through BookIt links or the Meeting Logs page to understand how reps and prospects actually behave.

 

Prerequisites

• The host must have an authorized Google or Microsoft calendar connection in LeanData. Tracking depends on that connection staying valid.
• The meeting must have been booked through LeanData Scheduling so BookIt can match the calendar event to a Meeting Log.
• Tracking applies to calendar changes that occur after the connection is authorized. Changes made before that point are not backfilled.

 

What Gets Synced from the Calendar

Cancellations

When the meeting event is deleted or cancelled on the calendar, BookIt:

• Sets the Meeting Log status to Cancelled, with the cancellation source recorded as the calendar event.
• Applies the same cancellation handling used when a meeting is cancelled through BookIt, including submitting a meeting credit request for count-based pools.
• Updates the linked Salesforce event where applicable.
• Deletes any buffer events tied to the meeting.

Reschedules

When the meeting event is moved to a different start or end time on the calendar, BookIt:

• Updates the Meeting Log start and end times to the new time.
• Sets the Meeting Log status to Rescheduled, with the reschedule source recorded as the calendar event.
• Recalculates reminders so they are sent relative to the new meeting time.
• Keeps linked artifacts, such as the Salesforce event, aligned with the new time.
• Re-anchors buffer events around the new meeting time.

Attendee Responses

BookIt records the most recent response for each attendee it invited when the meeting was booked. Response values are:

• Accepted
• Declined
• Maybe
• No response

Response tracking is independent of meeting status. The last known response is retained even after a meeting is rescheduled or cancelled. Responses are informational, so no emails or workflows are triggered when a response changes, though reminders that already key off attendance status can use this data.

Event Detail Changes

Edits to the meeting event title, location, description, and conferencing details update the matching fields BookIt stores on the Meeting Log. Detail changes do not affect meeting status and do not trigger emails.

 

Buffer Events

Buffer events are enabled per Meeting Type through the Create Calendar Buffer Events setting. For configuration details, see the BookIt General Settings Guide.

Buffer events follow the meeting they support:

• When the meeting event is deleted on the calendar, its buffer events are deleted.
• When the meeting event is moved on the calendar, buffer events are re-anchored immediately before and after the new meeting time. Missing buffers are recreated, and buffers left behind at the old time are cleaned up.
• Deleting or moving only a buffer event, while the meeting itself stays on the calendar, is treated as intentional. The Meeting Log is unchanged and the buffer is not recreated. The full set of buffer events is reestablished the next time the meeting is rescheduled.

Buffer events never change Meeting Log status on their own, and attendee response tracking applies only to the meeting event.

 

Viewing Calendar-Initiated Changes

Calendar-initiated changes appear alongside changes made through BookIt links and the Meeting Logs page.

1. Navigate to BookIt > Meeting Logs.
2. Open the meeting you want to review.
3. Review the meeting status, start and end times, and attendee response values on the detail page.
4. Open the Meeting History modal to see the full change history for the meeting.

Each reschedule or cancellation entry in Meeting History identifies:

• Source, showing whether the change came from the calendar event, a reschedule or cancel link, or an action inside BookIt.
• Timestamp of the detected change.
• Organizer of the calendar event as the person who made the change.
• Before and after values, including the previous and new start and end times for a reschedule.

 

Reporting

Cancellation and reschedule attribution is available for reporting, so you can separate:

• Meetings changed directly on the calendar event.
• Meetings changed through a BookIt cancel or reschedule link.
• Meetings changed inside BookIt from the Meeting Logs page.

This breakdown gives you a complete cancellation and reschedule picture rather than only the portion that flows through BookIt links.

 

Considerations

• Attendee list changes are not synced. Adding or removing attendees directly on the calendar event is not reflected in the Meeting Log. BookIt tracks responses only for the attendees it invited when the meeting was booked, so the attendee list on the calendar and in BookIt can differ.
• Tracking starts when the calendar connection is authorized. Calendar changes made before that point are not applied retroactively.
• No BookIt emails are sent for calendar-initiated changes. The calendar provider handles attendee notification for those actions.
• Updates are eventually consistent. Calendar providers can send several notifications for one action, and BookIt processes them so the Meeting Log settles on the current calendar state without duplicating history entries or issuing duplicate credits.
• Events BookIt cannot match are ignored. A calendar event that cannot be tied back to a Meeting Log produces no change in BookIt.

 

Troubleshooting

• Calendar changes are not appearing in the Meeting Log. Check the host's calendar connection in LeanData. If the calendar authorization has been revoked or has expired, tracking stops for that user until the calendar is reconnected.
• A change appears late. Provider rate limits and transient errors can delay processing. Changes are retried rather than dropped, so recheck the Meeting Log before escalating.
• A meeting shows as cancelled that the rep expected to keep. Deleting the meeting event on the calendar is treated as a cancellation. Reps who want to keep the meeting should move it rather than delete it.

 

Summary

Calendar Event Tracking connects BookIt-created calendar events back to the Meeting Log so cancellations, reschedules, attendee responses, and event detail edits made on the calendar are captured with the correct status, timing, and attribution. Buffer events follow the meeting they support, buffer-only edits are left alone, and Meeting History shows where every change came from.

For questions or additional assistance, please contact LeanData Support.

Displaying calendareventtrackingcleaned.txt.