Calendly
Booked is a signal. Attended is the conversion. You choose.
Calendly webhooks report the invitee lifecycle. Apointoo turns invitee.created into appointment_booked, tracks cancellations, and lets attended meetings, not raw bookings, feed the ad platforms if you want it that way.
Pages marked Planned are complete specifications written before the connector ships. They validate demand. Connectors with real delivery logs are marked Production or Beta.
Every booked meeting looks like a good one
Bidding on booked meetings pays for no-shows. The meeting that matters is the one where both people showed up, and Calendly alone cannot tell your ad account which was which.
The lifecycle becomes distinct events
Booking, cancellation, and attendance each carry their own event name. You decide which one becomes the advertising conversion, per destination, and changing your mind does not require rebuilding the flow.
What it sends to Google Ads
How the data flows
- Ad click lands on the scheduling page
- UTM and click ids captured at booking
- invitee.created webhook reaches Apointoo
- No-shows and cancellations update the record
- Completed appointments become the conversion
How the connection works
Subscribe the invitee.created and invitee.canceled webhooks.
Capture utm parameters and click ids at scheduling time.
Choose which lifecycle state becomes the conversion.
Cancellations follow your retraction rule automatically.
What it reads
Event mapping
| From | Apointoo |
|---|---|
| invitee.created | appointment_booked |
| Marked attended (via your workflow) | appointment_attended |
| invitee.canceled | appointment_cancelled (retracts booked signal) |
Frequently asked questions
Booked is a signal. Attended is the conversion. You choose.