Meta Conversions API setup for Cal.com
Same mechanics as any scheduler. Booking UID as event_id, click ID in via prefill, cancellations reversed.
Free30 minutesNo obligation
Cal.com + Meta CAPI · what breaks
What goes wrong on Cal.com — Cal.com + Meta CAPI
- 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 + Meta CAPI · the fix
What changes — Cal.com + Meta CAPI
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 + Meta CAPI · architecture
How Meta tracking behaves on Cal.com
Standard scheduler mechanics with fewer gates.
- 1
fbclid via prefill or link
Captured on landing.
- 2
Schedule from the booking webhook
Server-side.
- 3
Booking UID as event_id
Stable and unique.
- 4
Customer data from the booking
Normalized before hashing.
- 5
Cancellations reversed
The event exists; use it.
Cal.com + Meta CAPI · diagnose
Where Cal.com tracking breaks, in diagnostic order — Cal.com + Meta CAPI
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 + Meta CAPI · prove
The QA evidence — Cal.com + Meta CAPI
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 + Meta CAPI · 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 + Meta CAPI · when not to buy
When you don't need this on Cal.com — Cal.com + Meta CAPI
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 + Meta CAPI · what we deliver
What gets built for Meta on Cal.com
A shared event ID on both paths
The Cal.com booking UID, present on the created and cancelled webhooks.
Standard event names, exactly cased
Meta matches on name and ID together, so a case difference alone produces two events.
Customer data normalized then hashed
Lowercase and trimmed email, phone in E.164. This is where nearly every low match quality score comes from.
fbc and fbp forwarded from the browser
fbc only exists if fbclid was captured on landing — a very common gap.
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 + Meta CAPI questions, answered
Schedule, from the webhook.
The Cal.com booking UID.
Prefill or a link parameter, captured on landing.
They should, and the webhook exists to do it.
Free · 30 min
Get Pixel and CAPI counting once on Cal.com
WhatsAppFree30 minutesNo obligation
