Skip to content

Capture the GCLID in Cal.com and send it to your CRM

Connect Google Ads clicks to Cal.com bookings so you can see which campaigns produce leads, not just website visits. The workflow below stores the click identifier when a visitor arrives, writes it into a hidden booking field, and makes it available in Cal, notification emails, your CRM and offline-conversion tools.

Why click-to-booking attribution matters

Google Analytics can report ad clicks and landing-page visits, but it does not by itself show which of those visitors booked a meeting or became a paying customer. Without that link, budget decisions rely on traffic rather than downstream value.

The fix is to attach the Google click identifier to the booking record. Once it travels with the lead into your CRM, you can compare campaigns by booked and qualified outcomes and, where appropriate, send the result back to Google Ads as an offline conversion.

Three-step setup

  1. Install the attribution snippet

Add the small site snippet provided by your attribution tool. The exact placement depends on your website platform, usually through its settings or header area.

  1. Add a hidden field to the Cal booking form

Create a hidden field named "GCLID". This gives the tool a destination field that is submitted with the booking without changing what the visitor sees.

  1. Let the tool store and write the identifier

When a visitor arrives from a Google Ads click, the tool reads the GCLID from the URL and stores it in the browser. If the visitor browses other pages, leaves, or returns later, the stored value remains available. At booking, the tool writes it into the hidden field.

  1. Use the captured value downstream

Cal stores the value with the booking details, including name, email and phone where provided. It can appear in the Cal bookings view and notification emails, and can be forwarded through Cal integrations or tools such as Zapier or Make to a CRM, spreadsheet or other system.

Send the GCLID back as an offline conversion

Create the conversion action first:

  • In Google Ads, open Goals, then Conversions.
  • Start a new conversion and choose Imported, then CRMs, files, or other data sources.
  • When asked for a data source, choose "Add data source later".

Then choose the pipeline stage that should trigger the upload. Smart bidding strategies such as Maximise Conversions, Maximise Conversion Value and Target CPA generally need at least 50 conversions per month to work effectively. If closed deals are below that level, triggering on an earlier qualified stage, such as a newly created CRM deal, can provide a more usable signal.

Finally, build the automation:

  • In Zapier, create a Zap whose trigger matches the chosen stage.
  • Add Google Ads as the action and select "Send Offline Conversion".
  • Map the stored GCLID from the CRM or other storage location to the matching Zapier field.
  • Test the flow before increasing ad spend.

What else the hidden fields can carry

Landing-page-only capture fails when the booking happens elsewhere. For example, a visitor may land on the homepage from an ad, then navigate to a contact page to book. At that point the GCLID is no longer in the URL. Browser storage on first arrival solves that gap.

The same hidden-field approach can also carry UTM-derived attribution. In a paid-search example, the fields might include:

  • Channel = Paid Search
  • Channel Drilldown 1 = Google
  • Channel Drilldown 2 = Timber Fencing Campaign
  • Channel Drilldown 3 = Fence Installation Sydney
  • Channel Drilldown 4 = Free Quote Ad

For organic visits, comparable fields might show Channel = Organic Search, Channel Drilldown 1 = Google, the search-engine domain, and the searched keyword where available. Organic social, referral and direct traffic can be represented in the same framework.

Customer example and worked example

A useful way to evaluate this setup is to run a small, controlled comparison rather than relying on a single customer story. Pick two ads or campaigns that both send traffic to the same booking journey, tag each with its own UTM values, and let the hidden fields record the GCLID and channel details on every booking. After a few weeks, match each booking in your CRM back to the campaign and ad fields it carried in, then compare booked and qualified leads per campaign against the spend behind each one. The question to answer is simple: does one ad produce meetings and qualified opportunities while another produces only visits? If so, the CRM record makes that difference visible without depending on landing-page traffic alone. Treat any result as specific to your own traffic, offer and sales process, and confirm the current Google Ads conversion requirements before acting on it.

Pre-launch checklist

Before launch, check these items:

  • The site snippet is installed on every page where booking journeys can start.
  • The Cal form contains a hidden field named "GCLID".
  • A test booking from a GCLID-tagged URL shows the identifier in Cal and in the destination CRM.
  • A test booking after navigating to a different page still carries the identifier.
  • The offline-conversion trigger, mapping and test event are confirmed in Google Ads.

Before choosing a plan, confirm the current pricing, included usage, trial conditions, billing schedule and cancellation terms.

Wrap up

Storing the click identifier on arrival and writing it into the booking form closes the gap between ad clicks and scheduled meetings. It also gives you the data needed to judge campaigns by leads and qualified outcomes, and to return those outcomes to Google Ads for bidding.

About the author

Aaron Beashel is described as the founder of the original attribution tool and as having over 15 years of experience in marketing and analytics. This byline should be replaced with the new publisher's author details before publishing.

Interactive controls

Use the form-controls-contract module for any interactive controls on this page. No additional form fields, endpoints or SDK details are introduced in the public copy.

GCLID flow from click to offline conversion
StageWhat happensCheck
ArrivalGCLID is read from the URL and stored in the browserIdentifier persists across pages and return visits
BookingStored GCLID is written into the hidden Cal fieldCal booking record contains the GCLID
CRMBooking data is forwarded to the CRMCRM lead record contains the GCLID and UTM fields
Google AdsQualified outcome is uploaded as an offline conversionTest conversion appears in Google Ads

Use as a setup checklist; confirm each stage with a test booking before scaling spend.

Frequently asked questions

Why does storing the GCLID on arrival matter?

No. A method that only reads the landing URL will miss visitors who move to another page before booking, or who return later. Storing the identifier in the browser on first arrival preserves it across pages and return visits.

When should an offline conversion be sent back to Google Ads?

Choose a stage that produces enough qualified events for smart bidding to learn from. Waiting for a closed deal can leave too few signals if volume is low; an earlier qualified-lead stage, such as a newly created deal, may provide a stronger signal.

Can UTM and organic attribution be captured alongside the GCLID?

Yes. The same stored-attribution approach can also record UTM-derived channel fields and attribution for organic search, organic social, referral and direct visits, not only paid clicks.