Server-side tracking for Cal.com
Self-hosted Cal.com is close to the ideal case: your own database, your own webhooks, your own infrastructure. Hosted Cal.com is a normal webhook integration. Either way the booking event is clean and the cancellation event exists.
Free30 minutesNo obligation
Cal.com server-side · what breaks
What goes wrong on Cal.com — Cal.com server-side
- 01
Self-hosted and hosted differ
Establish which before designing anything.
- 02
Embed type decides click ID capture
Inline, popup or hosted page.
- 03
Cancellations rarely reversed
Paying for calls that never happen.
- 04
Booked is not attended
Two outcomes, usually one event.
Cal.com server-side · the fix
What changes — Cal.com server-side
Click ID inside the booking
Via prefill or link parameters.
Bookings from the webhook
Created, cancelled, rescheduled.
Direct database access if self-hosted
The cleanest reconciliation available.
Cal.com server-side · architecture
What Cal.com exposes to a server container
The most tractable scheduler here, especially self-hosted.
- 1
Booking webhook as the event source
Created, with cancellation for reversals.
- 2
Booking UID as the deduplication key
Stable and unique.
- 3
Click ID via prefill or booking questions
Captured on landing.
- 4
Direct database reconciliation if self-hosted
Authoritative and trivial.
- 5
Attendance from your own records
The scheduler doesn't know.
Cal.com server-side · diagnose
Where Cal.com tracking breaks, in diagnostic order — Cal.com server-side
Each check rules out a class of cause, so by the last one there is usually a single explanation standing.
- 01
Establish self-hosted or hosted
The first question.
- 02
Identify the embed type per page
Inline, popup or hosted.
- 03
Book a test slot from a tagged click
Check the booking for the click ID.
- 04
Confirm webhooks are configured
No tier gating if self-hosted.
- 05
Reconcile bookings against your records
For a closed month.
Cal.com server-side · prove
The QA evidence — Cal.com server-side
Run on Cal.com specifically, on a live conversion rather than in preview mode.
Source of truth
your Cal.com booking records
- Click ID confirmed present on a real booking.
- Hosting model and embed type documented.
- Bookings confirmed arriving as conversions from the webhook.
- Cancellations confirmed reversing.
- Bookings reconciled against Cal.com records for a closed month.
- Reconciled over a fully closed window, matched per record rather than on totals.
- Re-checked 30 days later, and after any platform update.
Cal.com server-side · free audit
What we check in the free audit
- Establish self-hosted or hosted
- Identify the embed type per page
- Book a test slot from a tagged click
- Confirm webhooks are configured
- Reconcile bookings against your records
Checked against
your Cal.com booking records
Free30 minutesNo obligation
Cal.com server-side · when not to buy
When you don't need this on Cal.com — Cal.com server-side
Worth reading before you buy anything, from us or anyone.
- If bookings already carry click IDs and reach your platforms, the work is done.
- Self-hosted Cal.com gives you database access, so reconciliation is a query rather than an export. Use that before buying anything.
- The webhook integration is well documented and open source. Your developer can read the code, which is not true of any hosted competitor.
- Check one real booking for the click ID before assuming anything is broken.
Cal.com server-side · what we deliver
What the server-side build gives you on Cal.com
Container on your own subdomain
Your domain, your certificate, hosting in an account you control.
Money events from Cal.com bookings
Cal.com's booking webhook, or direct database access where you self-host.
Deduplicated at every destination
On a shared event ID, verified before any existing path is removed.
Consent enforced before dispatch
A denied destination receives nothing, verified by capture rather than configuration.
Written guarantee
95%+ tracking accuracy
Measured against your Cal.com booking records. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
Cal.com server-side questions, answered
The booking webhook, or the database directly if you self-host.
The Cal.com booking UID.
Considerably. Database access makes reconciliation a query, and there's no tier gating on webhooks.
Yes, which means your developer can read exactly what the webhook sends rather than guessing.
Free · 30 min
Move Cal.com events off the browser
WhatsAppFree30 minutesNo obligation
