CASE STUDY · CONVERSION TRACKING · OCTOBER 2026
Calendly booking conversion tracking
Real Estate Expert Witnesses
GA4, Google Tag Manager and Google Ads
Implementation by Waqas Mehboob
A tested signal for actual booked meetings. One completed test booking sent one GA4 event. Opening the calendar or leaving the form without booking sent none.
Tracking a booking that actually happened
REEW wanted to measure completed Calendly meetings after visitors reached its Lovable website. A booking button click alone could not confirm that someone had scheduled a call.
The requirement was to count confirmed meetings, maintain a usable advertising conversion signal and prevent repeated booking messages from creating extra events.
What I implemented
I worked with the client on its AI website setup and managed the tracking in Google Tag Manager. I corrected the base GA4 tag configuration and added a listener for Calendly’s confirmed scheduling message.
- Checked the message origin, iframe source and booking completion event.
- Used a booking identifier to suppress repeated messages in the same browser session.
- Triggered
calendly_booking_completedin GA4 only after a confirmed booking. - Reviewed the imported Google Ads action as Book appointments, Primary and Count One.
The tested changes were published in GTM Version 3.
Validation results
| Test or configuration | Observed result |
|---|---|
| Open the embedded calendar | No booking event |
| Leave the booking form without submitting | No booking event |
| Complete one real test booking | One booking event and one GA4 hit |
| Review the Google Ads action | Correct event name, Primary and Count One |
Measurement context: These results verify event delivery and conversion configuration. A booking attributed to a live Google Ads interaction was not observed during the test. Count One in Google Ads applies per ad interaction; the listener separately suppresses repeated booking messages within the browser session.
Testing evidence
Open either screenshot to view it at full size.
The completed booking event
Tag Assistant shows the booking event and a successful GA4 tag after the test appointment was scheduled.
The Google Ads conversion settings
The imported action uses calendly_booking_completed. Its configuration was reviewed as Primary with Count One.
A verified booking signal
The client has a tested completed-booking event and a Google Ads conversion configured to use that signal. The documented scope is the embedded Calendly flow on real-estate-expert-witnesses.com, including its /book page. Bookings made directly on calendly.com are outside this implementation.
This case study reports implementation and test outcomes. It does not claim a measured increase in leads, revenue or advertising return.