Calendly conversion tracking: credit the ad behind each call
Track Calendly bookings as conversions: pass UTMs and a visitor ID to the scheduler, record bookings server-side, and send booked calls to Meta and Google.
By DATALYR · · 3 min read
Contents
How to track Calendly conversions
To track Calendly conversions, connect each booking to the visit that started it and record the booking as a conversion. Calendly offers three built-in options: its Google Analytics 4 integration, its Meta Pixel integration, and redirecting invitees to a page on your site after they book. UTM parameters on the scheduling link or embed carry the campaign.
Calendly says it does not integrate directly with Google Ads. Its suggested routes are importing GA4 booking conversions into Google Ads, or using Zapier.
The rest of this guide covers what each option records, how to pass campaign data into an embed, and how to record bookings from Calendly's side so a blocked script or closed tab does not lose them.
What Calendly's own options record
The GA4 integration sends scheduler activity to Google Analytics as events, including invitee_meeting_scheduled for a booked meeting. Calendly lists it on Professional, Standard and higher plans, and only account owners and admins can set it up. Inside an embed, Calendly's embed article lists events such as calendly.event_scheduled.
UTM parameters tell GA4 where the booking came from. Without them, Calendly notes, GA shows the source as direct. Calendly supports utm_source, utm_medium, utm_campaign, utm_content and utm_term, plus salesforce_uuid, and each value must be under 255 characters.
These options run in the invitee's browser. They are a good fit for on-site analytics; for ad-platform conversions you also want the booking recorded from Calendly's server.
Pass campaign data into the embed
An inline Calendly embed loads Calendly's page inside yours, so it does not see your page's URL on its own. Calendly's guide gives three ways to pass UTMs: put them in the embed's data-url, pass a utm object to the JavaScript embed, or read your page's query string with a script and forward it.
A visitor ID is more useful than UTMs alone, because it points to the whole visit, including ad click IDs. DATALYR reads a DATALYR visitor ID passed as salesforce_uuid on the booking URL; any other value in that field is ignored.
Put the tracking script on every page that embeds or links to your booking page, and load the embed below it so the visitor ID exists when the embed builds its URL.
Record bookings from Calendly's side
DATALYR connects to Calendly with a personal access token from an organization owner or admin on the Standard plan or above, then creates an organization webhook. Every booking arrives as call_booked; reschedules, cancellations, no-shows and routing-form leads with an email arrive as their own events.
Each booking is matched to an ad click in order: the visitor ID passed as salesforce_uuid, then the invitee email matched to an earlier visit, then the UTMs on the booking URL. No Calendly event carries a value.
The Calendly card's starter rules send call_booked to Meta as Schedule and to TikTok as SubmitForm. For Google Ads, create a rule in Conversions and pick your conversion action.
How a booking finds its ad click
1. Visitor ID
salesforce_uuid on the booking URL
Exact link to the visit and its click IDs.
2. Email
Invitee email
Matched to an earlier identified visit.
3. UTMs
Booking or embed URL
Campaign only, when nothing else matches.
Example: put a value on a booked call
A booked call has no price, so give the conversion a fixed value that reflects what a call is worth. This is a hypothetical example using last quarter's numbers.
Last quarter, 40 booked calls produced 10 closed deals at an average contract of $3,000, or $30,000 in total. Dividing by the calls gives $30,000 ÷ 40 = $750 of contract value per booked call. That $750 is a reasonable fixed value for the Schedule conversion.
Update it each quarter, and use contract value only as a bidding signal. Collected cash belongs to the payment source, such as Stripe or Commas.
Verify with one test booking
Open a page that embeds your booking page in a private window with ?utm_source=doctest. Book a slot with a test email. In DATALYR, confirm a call_booked row with source calendly, the invitee email and the doctest UTM.
Cancel the booking in Calendly and confirm a call_cancelled row arrives. If the visitor ID starts with calendly_, no visitor ID, known email or UTMs reached the booking, so check the embed URL first.
Related articles.
Tracking ·
UTM parameters: build a campaign taxonomy you can trust
Create consistent campaign tags, test the complete redirect path, and verify that source information survives the journey to a business outcome.
Conversion delivery ·
Offline conversion tracking: connect a lead to the sale that follows
Define the lead-to-sale record, preserve eligible matching data, and verify imported outcomes without confusing acceptance with advertising credit.
Conversion tracking ·
Meta Conversions API: setup, deduplication, and verification
Map a real conversion to the correct Meta destination, choose one delivery owner, and verify receipt separately from matching and attribution.
