Meta Conversions API setup for Calendly
Same mechanics. fbclid in via prefill or link, out on the webhook, with the invitee UUID as event_id.
Free30 minutesNo obligation
Calendly + Meta CAPI · what breaks
What goes wrong on Calendly
- 01
Three embed types, different behaviour
Inline, popup and hosted each need a different approach.
- 02
Hosted pages have no parent context
The click ID must be in the link you built.
- 03
Cancellations rarely reversed
So you pay for calls that never happen.
- 04
Booked is not attended
Two different outcomes, usually counted as one.
Calendly + Meta CAPI · the fix
What changes — Calendly + Meta CAPI
Click ID inside the booking record
Via prefill or link parameters.
Bookings from the webhook
Created, cancelled, rescheduled.
Attendance tracked separately
Where the outcome is recorded.
Calendly + Meta CAPI · architecture
How Meta tracking behaves on Calendly
Same mechanics, different destination.
- 1
fbclid via prefill or link
The only route into a hosted calendar.
- 2
Schedule or Lead from the webhook
Server-side.
- 3
Invitee UUID as event_id
Stable and unique.
- 4
Customer data from the booking
Normalized before hashing.
- 5
Cancellations reversed
So you stop paying for no-shows.
Calendly + Meta CAPI · diagnose
Where Calendly tracking breaks, in diagnostic order
Each check rules out a class of cause, so by the last one there is usually a single explanation standing.
- 01
Establish the embed type per page
Inline, popup or hosted.
- 02
Book a real test slot from a tagged click
Check the booking for the click ID.
- 03
Confirm which parameters Calendly received
Question responses and UTMs.
- 04
Check whether webhooks are configured
They need a paid tier.
- 05
Match a month on invitee UUID
Against platform conversions.
Calendly + Meta CAPI · prove
The QA evidence — Calendly + Meta CAPI
Run on Calendly specifically, on a live conversion rather than in preview mode.
Source of truth
your Calendly booking records
- Click ID confirmed present on a real booking record.
- Embed type documented per page.
- Bookings confirmed arriving as conversions from the webhook.
- Cancellations confirmed reversing.
- Bookings reconciled against platform conversions 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.
Calendly + Meta CAPI · free audit
What we check in the free audit
- Establish the embed type per page
- Book a real test slot from a tagged click
- Confirm which parameters Calendly received
- Check whether webhooks are configured
- Match a month on invitee UUID
Checked against
your Calendly booking records
Free30 minutesNo obligation
Calendly + Meta CAPI · when not to buy
When you don't need this on Calendly
Worth reading before you buy anything, from us or anyone.
- If your bookings already carry click IDs and reach your ad platforms, the work is done.
- Webhooks need a paid Calendly tier. If you're on the free plan, that's a real constraint — attribution is possible, server-side conversions aren't.
- If you use only the inline embed on your own domain, the click ID may already be arriving. Check a real booking before assuming.
Calendly + Meta CAPI · what we deliver
What gets built for Meta on Calendly
A shared event ID on both paths
The Calendly invitee UUID, present on both the created and canceled 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 Calendly 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
Calendly + Meta CAPI questions, answered
Schedule, or Lead if that fits your funnel better. Fired from the webhook.
The Calendly invitee UUID.
Prefill or link parameter. A hosted calendar has no other route.
Yes, and Calendly gives you the event to do it with.
Free · 30 min
Get Pixel and CAPI counting once on Calendly
WhatsAppFree30 minutesNo obligation
