Record when a visitor books a meeting in a Calendly widget embedded on your site, and see which channel, campaign and landing page brought them.
SourceTrack listens for the booking event that Calendly’s own embed sends to the page and records that a meeting was booked. It does not read the invitee’s name, answers or the meeting type. It can also add the invitee’s email to the visitor’s lead, if you turn that on (see below).
Why connect Calendly with SourceTrack
- No redirect page needed: The booking is picked up on the page where the widget sits, so you do not have to send people to a thank-you URL.
- Meetings by channel: Booked meetings are counted as conversions, so you can see which channels and campaigns lead to calls, not just visits.
- One journey: The booking sits on the same timeline as the visitor’s earlier visits, source and landing page.
What SourceTrack records
- A booking event: A conversion named
booking_scheduled, with Calendly as the provider. - Acquisition context: The visitor’s first-touch and last-touch source, referrer and landing page, as for any visit.
What SourceTrack does not do
- It does not read the invitee’s name or any answer from the booking form. It reads the email only when booking email capture is on (below).
- It does not record which event type was booked (for example a 30-minute call versus a demo).
- It only sees bookings made in a widget on your own pages. A visitor who books on calendly.com directly is not seen by the script.
Step-by-step setup
Step 1: Embed Calendly on your site
Use Calendly’s inline embed, popup widget or popup text. All three send the same booking event to the page.
Step 2: Make sure SourceTrack is on that page
The SourceTrack script must run on the same page as the widget.
Step 3: Book a test meeting
Open the page in a private window, book a slot, then find the visitor in SourceTrack. The booking shows on their journey.
Optional: add the booker’s email to the lead
With Form lead capture and Booking email capture both on in Settings and a Calendly personal access token connected, SourceTrack makes one read-only call to your Calendly account for the booking the visitor just made in your embed, and adds the invitee’s email to that visitor’s lead. It reads the email only, never the name, phone number or answers.
- It follows the same consent rules as form lead capture: only where the visitor’s region and consent allow it, and never under Do Not Track or Global Privacy Control.
- Paste the token under Booking email capture in Settings. The Calendly personal access token is stored encrypted and used for nothing else.
- Booking email capture is rolling out and may not appear in your Settings yet.
How it works under the hood
Calendly’s embed sends a calendly.event_scheduled message to the page when a booking is confirmed. The SourceTrack tracker checks that the message really comes from calendly.com, ignores every other Calendly message, and sends one booking_scheduled event with the provider name, the page address and the visitor and session ids it already uses. A repeat of the same booking event on the same page within a few seconds is dropped.
Common problems and fixes
- Do Not Track, Global Privacy Control or missing consent. The tracker sends nothing for that visitor. Test in a window without those signals.
- The script is not on the page with the widget. Check that page’s source for the SourceTrack snippet, not just your home page.
- The visitor booked on calendly.com. Only bookings made in a widget on your site are seen. Link to a page with the embed instead of your public Calendly link.
Related guides
Frequently Asked Questions
Does this work with inline embeds and popups?
Yes. The inline embed, the popup widget and the popup text all send the same booking event to the page.
Do I need a thank-you page?
No. The booking is recorded on the page with the widget. A thank-you page still works if you already use one.
Can a booked meeting be sent to Google Ads or Meta?
A booking is a conversion, so it can be sent server-side to an ad platform you connect in SourceTrack. Sending conversions to ad platforms is in beta.
