Skip to content

How to Track the Source of Leads and Bookings in Calendly

Website analytics can tell you how many visitors arrived from each channel, but a visit is not the same as a booked meeting. If you want to know which campaigns actually produce calls, demos or consultations, the source has to travel with the booking itself. This guide walks through wiring an embedded Calendly widget so that each booking carries the channel, campaign and keyword that brought the person in, and then shows what to do with that data once it lands. The capture and handoff described here rely on Attribution Analytics; confirm the product and its terms with the owner before publishing.

Why booking source data is worth the setup

Most analytics platforms are good at counting sessions and attributing traffic. They are much weaker at telling you how many leads or customers a channel produced, because the conversion happens inside a scheduling tool rather than on a page you control. That gap is what this setup closes.

A useful way to think about it: traffic reports answer "how many people came?" while booking source reports answer "who actually sat down with us, and why?" The second question is the one that justifies budget decisions.

The three-step setup at a glance

The workflow has three stages, and each one depends on the previous one being correct:

  1. Install the tracking script and rebuild your Calendly embed. The script must be on the page, and the embed must be the generated variant rather than the plain Calendly snippet.
  2. Let the script classify and store the visit. On each visit, technical details about the referral are read, sorted into a channel, and held in the browser.
  3. Pass the stored data into the booking. When the visitor completes the widget, the stored values are submitted alongside the booking and appear inside Calendly.

Before you start, confirm two things: you can edit the page template that hosts the widget, and you have a way to add hidden fields to the Calendly event you are embedding. If either is missing, fix that first — the rest of the setup will not hold.

Step 1: Install the script and configure the widget

Begin by creating an account with Attribution Analytics and adding the tracking snippet it provides to your site. If you use a common website builder, follow its documented installation path rather than assembling the script by hand; the important point is that the snippet loads on every page where a booking widget appears. Treat the trial length and any commercial terms as items to confirm with the account provider before you rely on them in a launch plan, and record the dates you are evaluating so the decision is not left to memory. The step that is most often overlooked is the embed itself. A standard Calendly embed has no mechanism for carrying attribution parameters, so bookings made through it will arrive without source data. Replace it with the code produced by the embed generator: paste your Calendly URL into the generator and use the returned snippet wherever the widget should appear. That output is still a Calendly embed, with a small set of additions that make the handoff possible. Before moving on, open the page in a private browsing window, launch the widget, and check that the booking form renders and submits normally. An embed that is broken at this stage will present later as a tracking problem, which is much harder to diagnose.

Step 2: How the visit gets classified and stored

Once the script is live, every visitor's arrival is examined using the same kind of technical signals an analytics platform would read — referrer, campaign parameters and similar markers. Those signals are reduced to a channel label such as Paid Search, Paid Social, Organic Search or Referral, and the result is saved in the visitor's browser rather than on your server.

That browser-side storage is what makes the next step possible. The visitor may browse several pages before booking, and the original classification needs to survive that journey. When the booking form is submitted, the stored values are attached to it.

Step 3: Where the data shows up and what you can do with it

After submission, the source values are visible on the event record inside your Calendly account. From there you have three practical routes:

  • Read it in Calendly. Fine for spot checks and small volumes, less so for trend analysis.
  • Forward it to a CRM such as Salesforce, Pipedrive or HubSpot, then use that system's native reporting to build dashboards covering bookings, leads and closed customers.
  • Export to a spreadsheet in Excel or Google Sheets to see everything in one table, optionally connecting it to a BI tool such as Looker Studio or Power BI for deeper reporting.

Whichever route you pick, decide it now rather than after the data accumulates — the field names you map in step 3 determine how easy step 4 will be.

What each captured field means

Four values are written into the booking. Understanding them prevents most reporting mistakes:

  • Channel is the broad bucket — Paid Search, Paid Social, Organic Search, Referral and so on.
  • Channel Drilldown 1 is the first level of detail, typically the platform or network (Google, for instance).
  • Channel Drilldown 2 is the next level, usually the campaign name or the referring domain.
  • Channel Drilldown 3 is the finest level, often the keyword or a descriptive term.

A worked example makes this concrete. Imagine a marketing team at a fictional agency, DigitalEdge Solutions, running ads for its social media management service. A prospect clicks the ad and later books a call through the embedded widget. The booking would carry Channel: Paid search; Channel Drilldown 1: Google; Channel Drilldown 2: Social media management campaign; Channel Drilldown 3: social media agency.

If the same prospect had instead found the agency through an ordinary Google search, the values would read Channel: Organic search; Channel Drilldown 1: Google; Channel Drilldown 2: www.google.com; Channel Drilldown 3: social media agency. Note that Drilldown 2 changes character between the two cases — a campaign name in one, a domain in the other. Build your reports to tolerate that, or split paid and organic into separate report views.

Three reports worth building first

Once the data reaches a CRM or spreadsheet, these three views cover most of the questions a marketing team asks.

Leads by channel. A month-by-month tally of bookings for each channel. Put it next to your spend by channel and the comparison becomes a budget conversation: which channels earn their keep, and which are being funded out of habit. When the two lists disagree sharply, the spend list is usually the one that should move.

Leads by Google Ads campaign. The same tally, but split by campaign rather than channel. This is the view that separates campaigns that fill a calendar from campaigns that only fill a click report. Keep funding the first kind; rewrite the offer or retire the second.

Leads by social network. When you advertise on more than one network, this ranks them by bookings instead of impressions or engagement. A network that looks quiet on reach metrics but steady on bookings deserves a closer look before you cut it.

Each report answers a different question, so build them in this order and stop when you have the decision you need.

Telling a missing source apart from a wrong source

Two failures look similar in a report but have different causes.

Missing source. The booking has no channel value at all. The usual culprits are a standard Calendly embed left in place, the script absent from the page hosting the widget, or a visitor whose browser blocked or cleared the stored data. Check the embed first — it is the most common cause.

Wrong source. The booking has a channel value, but it does not match how the visitor actually arrived. This usually traces back to malformed or missing UTM parameters on the ad, or to a link that drops its parameters during a redirect. Audit the destination URLs of your campaigns rather than the tracking script.

A quick diagnostic: submit a test booking yourself from a tagged link. If the channel appears, the pipeline works and any remaining problem is in your campaign tagging. If nothing appears, the problem is upstream in installation or embedding.

Getting started

A sensible rollout is to start with a single booking widget, submit a test booking from a tagged link, and verify that the channel and drilldown fields arrive as expected. Once that works, apply the same embed pattern to your remaining scheduling links. How long the full setup takes depends on your site, your template access and the number of widgets involved, so set your own target rather than assuming a fixed duration. Likewise, trial length, pricing and any plan terms should be checked directly with the provider before you commit; use the trial period to validate the pipeline end to end, including the route from Calendly into your CRM or spreadsheet, and only then decide whether to continue.

Captured booking fields and where each value comes from
FieldWhat it holdsPaid exampleOrganic exampleWatch out for
ChannelBroad marketing bucketPaid searchOrganic searchValues are assigned by the script, not typed by the visitor
Channel Drilldown 1Platform or networkGoogleGoogleUsually stable across paid and organic
Channel Drilldown 2Campaign name or referring domainSocial media management campaignwww.google.comField meaning shifts between paid and organic
Channel Drilldown 3Keyword or descriptive termsocial media agencysocial media agencyMay be blank when no keyword is available

Examples use a fictional agency and illustrative UTM values; actual captured values depend on how your own campaign links are tagged.

Which report answers which question
ReportQuestion it answersDecision it supportsData needed
Leads by channelWhich broad channels produce bookings?Where to shift overall budgetChannel field on each booking
Leads by Google Ads campaignWhich campaigns produce bookings?Which campaigns to fund, revise or stopChannel plus Drilldown 2 campaign name
Leads by social networkWhich social platform produces bookings?How to split spend across networksChannel plus Drilldown 1 platform

Report structures are illustrative; the exact charts depend on your CRM or spreadsheet configuration.

Frequently asked questions

Do I need to change my existing Calendly embed?

Yes. A standard Calendly embed does not carry the attribution parameters, so bookings made through it will arrive without source data. Replace it with the code produced by the embed generator, which is a Calendly embed with the necessary additions.

Where is the visitor's source information stored before they book?

In the visitor's browser. The script classifies the visit when the person first arrives and keeps that classification available across subsequent pages, then attaches it when the booking form is submitted.

Why does Drilldown 2 show a campaign name for paid traffic but a domain for organic traffic?

The field holds the most specific identifying detail available at that level. For a tagged ad that is the campaign name; for an untagged organic visit it is the referring domain. Reports that mix both should account for this difference.

Can I see the source data without a CRM?

Yes. The values appear on the event record inside Calendly, and you can also export bookings to a spreadsheet for a single-table view. A CRM becomes useful when you want recurring dashboards or want to connect bookings to closed revenue.

What is the most common reason a booking has no channel value?

The widget is still using the plain Calendly embed rather than the generated version. Check that first, then confirm the script is present on the page that hosts the widget.