How to Capture the GCLID in Calendly
A Google Ads click tells you someone arrived. A completed Calendly booking tells you someone raised a hand. The gap between those two events is where most paid-search reporting goes soft, because the click identifier from the ad — the GCLID — is easy to lose before the booking is saved. This guide walks through tagging the ad URL so the GCLID arrives, keeping it available while the visitor moves around your site, writing it into the booking, and then returning it to Google Ads as an offline conversion so bidding can learn from real outcomes.
What you are actually trying to connect
Google Analytics can count ad clicks and sessions, but it does not tell you which of those sessions turned into a booked meeting or a paying client. Closing that loop requires one identifier to travel the whole path: ad click, landing page, browsing, booking widget, CRM record, and finally a conversion upload back to Google Ads.
The GCLID is that identifier. It is generated by Google Ads and appended to your landing page URL when a tagged ad is clicked. Everything in this guide is about making sure it survives the journey intact, because a GCLID that is dropped at any step cannot be reconstructed later.
Step 1: Put the GCLID into your ad URL
Calendly can read UTM parameters natively, but it offers no way to add hidden fields for arbitrary custom values such as the GCLID. The workaround is to carry the GCLID inside a UTM parameter, which Calendly already knows how to receive.
Use the {gclid} ValueTrack parameter in your ad's final URL. ValueTrack placeholders are substituted at click time, so the visitor never sees the literal placeholder — they arrive with a real identifier in the query string.
A tagged URL looks like this: https://example.com?utm_term={gclid}
After a click, the visitor's address bar shows something like: https://example.com?utm_term=9876543210
That substitution is the whole trick. You are not asking Calendly to understand Google Ads; you are handing it a value in a format it already accepts.
Step 2: Keep the value available until the booking happens
If capture only works when the booking widget sits on the exact landing page, most real journeys will fail. A visitor may land on your homepage from an ad, read a service page, then book from a contact page — and by then the query string is long gone.
Attribution Analytics stores the GCLID in the visitor's browser as soon as they arrive. That persistence is what makes the rest of the chain work: the value survives page changes, and it survives the visitor leaving and coming back later. When the visitor completes a Calendly widget embedded on your site, the stored value is written into the hidden UTM fields at that moment.
Two practical checks follow from this. First, the booking widget needs to be embedded on your own site rather than only linked out to a standalone Calendly page, otherwise there is no page context for the hidden fields to be filled from. Second, if you change widget placement or rebuild a landing page, re-test the booking to confirm the value still arrives.
Step 3: Confirm the GCLID is on the booking record
Once the booking is submitted, Calendly stores the GCLID next to the invitee details it normally collects — name, email, phone number and so on. You can inspect it in the Scheduled Events area of your Calendly dashboard, and it will appear in any booking notification emails you have configured.
From there the value can move onward through Calendly's native integrations, or through an automation tool such as Zapier or Make, into your CRM or any other system that needs it. The important habit is to verify at this stage rather than later: open a test booking and confirm the GCLID field is populated before you start relying on downstream reports.
Returning the GCLID to Google Ads as an offline conversion
Sending the booking back to Google Ads closes the loop. Start by creating a conversion action: in Google Ads, open Goals in the left sidebar, go to Conversions, create a new conversion, choose Imported, then select CRMs, files, or other data sources. On the final screen, where a data source is requested, choose the option to add the data source later.
With the conversion action live, decide which sales stage should fire the upload. Then build the automation: create a Zap whose trigger matches that stage (for example, a new deal created in your CRM), set Google Ads as the action, choose Send Offline Conversion as the event, and map the GCLID from wherever you store it into the matching field.
Before increasing spend, test that conversions are actually arriving. A conversion action that exists but never receives data looks identical to a working setup from inside the Google Ads interface, so verify with a real or test record.
Choosing the trigger stage: a decision worth getting right
It is tempting to send the conversion only when a deal closes, because that is the outcome you care about. The problem is volume. Google's smart bidding strategies — Maximise Conversions, Maximise Conversion Value, Target CPA — generally need roughly 50 conversions per month to operate properly.
If you are not closing 50 deals a month, waiting for closed-won starves the bidding system of signal. Firing earlier, for example when a new deal is created in your CRM, still sends a meaningful event (a lead your sales team has qualified) while giving smart bidding enough volume to work with.
Use this as a starting test rather than a rule: count your typical monthly volume at each candidate stage, and pick the latest stage that still clears the threshold. If your volume is comfortably above it at closed-won, that stage gives the cleanest signal.
What a completed record looks like
Beyond the GCLID, the same mechanism can carry campaign context into the booking. Take a hypothetical architecture firm running paid search. A visitor clicking a Google Ad and booking a consultation would have values written into the hidden fields alongside the GCLID:
- Channel = Paid Search
- Channel Drilldown 1 = Google
- Channel Drilldown 2 = Residential Architecture Campaign
- Channel Drilldown 3 = Home Architect Sydney
- Channel Drilldown 4 = Free Consultation Ad
A visitor who instead arrives through a normal Google search and books the same consultation would produce a different set:
- Channel = Organic Search
- Channel Drilldown 1 = Google
- Channel Drilldown 2 = www.google.com (or whichever search engine domain they came from)
- Channel Drilldown 3 = Residential Architect Sydney (or whatever keyword they searched for, if it's available)
Having both sets means paid and organic bookings can be compared on the same fields, and the paid ones still carry the GCLID needed for conversion upload.
Two different failures, two different fixes
When GCLID reporting breaks, the cause is usually one of two things, and they need different remedies.
Capture failure: the booking record has no GCLID at all. Typical causes are an untagged ad URL, a placeholder that never got substituted, a booking made on a page outside your site, or a widget change that broke the hidden field mapping. Diagnose by opening a recent booking and looking at the field itself.
Delivery failure: the booking record has a GCLID, but Google Ads shows no corresponding conversion. Here the capture worked and the hand-off did not — a wrong trigger stage, a mapping pointed at the wrong CRM field, or a conversion action still waiting for its data source. Diagnose by tracing one known record from CRM to the automation run log.
Separating the two saves time, because a capture problem will never be fixed by adjusting your Zap, and a delivery problem will never be fixed by re-tagging ads.
Pre-flight checklist
Run through these before trusting the numbers:
- Ad final URLs use the {gclid} ValueTrack parameter inside a UTM parameter.
- A test click shows a real identifier in the address bar, not the literal placeholder.
- The Calendly widget is embedded on your own site, not only linked out.
- A booking made after navigating across several pages still shows the GCLID.
- A booking made after leaving the site and returning still shows the GCLID.
- The GCLID appears in the Scheduled Events view and in booking notification emails.
- The CRM record created from the booking contains the GCLID in the expected field.
- A Google Ads conversion action of the imported type exists and has a data source attached.
- The automation trigger matches the stage you deliberately chose.
- One end-to-end test record reaches Google Ads as a conversion.
Where this fits in a measurement stack
Capturing the GCLID is one link in a chain, not a complete attribution system. It answers a narrow but valuable question: which ad click produced this booking? Pair it with the campaign-level fields above and you can compare cost per booked consultation across campaigns, then compare cost per qualified opportunity once your CRM stage data is in place. Attribution Analytics handles the capture step described above; the reporting layers built on top of it are yours to configure.
Keep the two layers distinct in reporting. Click-level identifiers support conversion uploads and bid optimisation; campaign and channel fields support the human-readable reporting your team will actually read. Both come from the same capture step, so getting that step right pays off twice.
| Trigger stage | Signal quality | Volume risk | When it fits |
|---|---|---|---|
| Deal closed / won | Strongest — reflects real revenue | Highest — few events per month | You reliably exceed roughly 50 closed deals monthly |
| New deal created in CRM | Moderate — a lead sales has qualified | Lower — more events per month | You close fewer than about 50 deals monthly and need bidding volume |
| Booking completed in Calendly | Weakest — interest, not qualification | Lowest — most events | Early testing, or very low-volume accounts where any signal helps |
The 50-conversions-per-month figure is the guidance captured in the original article and applies to Google's smart bidding strategies generally; treat it as a planning heuristic and confirm current thresholds in Google Ads documentation before restructuring your conversion actions.
| Symptom | Likely layer | First thing to check |
|---|---|---|
| Booking record has no GCLID | Capture | Ad final URL tagging and whether the placeholder was substituted |
| Booking has GCLID, CRM record does not | Hand-off | Field mapping between Calendly and the CRM record |
| CRM record has GCLID, Google Ads shows nothing | Delivery | Conversion action status, data source attachment and automation run log |
| Some bookings carry GCLID, others do not | Capture (partial) | Whether the bookings without it came from pages outside your site or from direct traffic |
These are diagnostic starting points based on the capture chain described above, not a guarantee that the listed cause is the only possible one; platform interfaces change and should be checked against current product documentation.
Frequently asked questions
Can Calendly capture a GCLID without any extra tooling?
Not as a custom field. Calendly can receive UTM parameters natively, but it cannot add hidden fields for arbitrary values like the GCLID. The practical route is to pass the GCLID inside a UTM parameter using the {gclid} ValueTrack placeholder, then have Attribution Analytics write that value into the booking's hidden UTM fields.
What happens if a visitor books from a different page than the one they landed on?
With URL-only capture, the GCLID is lost as soon as the visitor navigates away, so a booking made on a contact page after landing on the homepage would carry nothing. Storing the value in the browser on arrival avoids this, because the stored value is still available when the booking widget is completed on any page of your site.
Should the offline conversion fire when the deal closes or when the lead is created?
It depends on volume. Closed-won is the most meaningful signal, but Google's smart bidding strategies generally need around 50 conversions per month to perform well. If you close fewer deals than that, firing at an earlier qualified stage — such as a new deal created in your CRM — keeps the signal meaningful while supplying enough events.
How do I know whether the problem is capture or delivery?
Look at the booking record first. If the GCLID field is empty, the problem is upstream: ad tagging, widget placement or hidden field mapping. If the GCLID is present on the booking and in the CRM but Google Ads shows no conversion, the capture worked and the issue sits in the conversion action, the automation trigger or the field mapping in your automation.
Does this only work for paid search bookings?
No. The same fields can carry attribution for visitors arriving through organic search, organic social, referral or direct traffic, which lets you compare paid and organic bookings side by side. Only paid clicks will have a GCLID, so conversion uploads apply to those records specifically.