Cal.com
Open-source scheduling, attributed end to end.
Cal.com webhooks report the full booking lifecycle: created, rescheduled, cancelled, rejected. Apointoo turns those states into distinct events and lets you decide which one becomes the advertising conversion.
Pages marked Planned are complete specifications written before the connector ships. They validate demand. Connectors with real delivery logs are marked Production or Beta.
Bookings without history are just intent
A booked slot says someone intended to show up. Without cancellations and attendance in the same ledger, bidding treats every booking as equal and pays for the ones that never happened.
The lifecycle becomes distinct events
Each webhook state maps to its own canonical event. Reschedules keep identity attached. Cancellations retract by rule. You choose whether booked or attended feeds optimization, per destination.
What it sends to Google Ads
How the data flows
- Ad click lands on the booking page
- UTM and click ids captured at booking time
- Booking webhooks reach Apointoo
- Reschedules and cancellations update the record
- Attended meetings become the conversion you chose
How the connection works
Subscribe the booking webhooks from your Cal.com app.
Capture utm parameters and click ids at booking time.
Map lifecycle states to canonical events once.
Cancellations follow your retraction rule automatically.
What it reads
Event mapping
| From | Apointoo |
|---|---|
| BOOKING_CREATED | appointment_booked |
| Marked attended (via your workflow) | appointment_attended |
| BOOKING_CANCELLED | appointment_cancelled (retracts booked signal) |
Frequently asked questions
Open-source scheduling, attributed end to end.