Skip to content

How to Capture Google Analytics Data in Cal.com Bookings

Cal.com handles the booking, but it does not automatically tell you whether the meeting came from a Google Ads click, an organic search result, or a social post. This guide shows how to attach source data to each booking, what fields get captured, and how to turn that data into reports that show which marketing efforts produce meetings and customers.

Why booking source data matters

Google Analytics can show how many visitors arrive from Paid Search, Paid Social, or Organic Search. It does not show how many of those visitors actually booked a meeting, became a lead, or turned into a paying customer. That gap makes it hard to judge which channels deserve more budget and which are producing meetings without revenue.

Capturing attribution data at the moment of booking closes that gap. Each booking record can carry the visitor's original marketing channel and landing page, so reports can connect meetings to the source that produced them.

What the attribution layer does

A small script on your website examines how each visitor arrived. It reads UTM parameters, referral information, and related signals, then groups the visitor into a marketing channel such as Paid Search, Organic Search, or Paid Social. That attribution is stored in the visitor's browser.

When the visitor completes a Cal.com booking, the stored attribution is passed into the booking form as hidden field values. Cal.com saves those values with the booking, and from there they can be sent to a CRM, a spreadsheet, or another connected tool.

Setup checklist

Use this checklist to confirm each part of the chain is in place before you rely on the reports.

  1. Attribution script installed on every page that can lead to a booking.
  2. Cal.com embed code adjusted so the booking widget accepts the attribution values.
  3. Hidden fields mapped to the attribution field names in the booking form.
  4. A test booking made from a tagged URL, with the resulting record checked in Cal.com.
  5. A downstream sync to your CRM or spreadsheet confirmed with the same test record.
  6. A report built from the synced data, not from Google Analytics alone.

If any step is missing, the booking will still be created, but the source data will be blank or incomplete.

What gets captured

Two categories of data are recorded for each lead: how the visitor arrived (channel) and which content brought them there (landing page).

Channel data identifies the marketing channel and can include deeper detail. For a Paid Search visitor, the record can include the campaign name, ad group, keyword, and similar values. Landing page data records the first page the visitor viewed and the broader page category that page belongs to. Together these fields let you see both the source and the content that produced the booking.

Worked example: a Paid Search booking

Suppose a prospect clicks a Google Ads link, lands on a features page, and books a demo through the Cal.com widget. The hidden fields in the booking record would be populated with values such as:

  • Channel: Paid Search
  • Channel Drilldown 1: Google
  • Channel Drilldown 2: Brand Campaign
  • Channel Drilldown 3: Velocity Software

The record would also store the initial landing page (for example, www.velocitysoftware.com/features) and the page category (for example, features). In a report grouped by channel, this booking appears under Paid Search; grouped by drilldown, it appears under Google and the named campaign.

Field and control map

Use this map to check that each value has a home in the booking form and in the downstream system.

  • Channel: the top-level marketing source. Map to a single-select or text field.
  • Channel Drilldown 1: the platform or network within the channel. Map to a text field.
  • Channel Drilldown 2: the campaign or grouping. Map to a text field.
  • Channel Drilldown 3: the ad group, keyword, or similar detail. Map to a text field.
  • Landing page: the first page the visitor viewed. Map to a URL or text field.
  • Page category: the broader content grouping. Map to a text field.

If a field is missing from the booking form, the corresponding value will not be saved, even if the attribution script captured it.

Reports to run once data is flowing

Once the booking data reaches your CRM or spreadsheet, the reporting tools in those systems can show where bookings come from. Three useful report shapes are:

  • Leads by channel: monthly booking counts broken down by original marketing channel, so you can see which channels produce meetings.
  • Customers by Facebook Ads network: new customers acquired from each network within the wider Facebook advertising system, so you can compare performance across placements.
  • Revenue from Organic Search by search engine: revenue attributed to visitors who arrived through organic search, split by search engine, so you can judge the return on SEO work.

Each report depends on the channel and drilldown fields being populated consistently. A report built on blank fields will undercount the sources you care about.

Troubleshooting: three different failures

When source data is missing from a booking, the cause is usually one of three distinct problems.

  1. Attribution not captured. The visitor's channel and landing page were never recorded, often because the script was absent from the page where the visit began.
  2. Field mapping missing. The attribution was captured, but the booking form has no hidden field for that value, so it was dropped at submission.
  3. Downstream sync missing. The booking record contains the values, but the CRM or spreadsheet connection does not include those fields, so reports show blanks.

Check each layer separately. Fixing the report will not help if the booking record itself is empty, and fixing the booking form will not help if the sync drops the field.

Getting started

The setup involves adding the attribution script to your site, adjusting the Cal.com embed so the booking widget accepts the values, and confirming that the fields arrive in Cal.com and in your reporting tool. A test booking from a tagged URL is the quickest way to confirm the whole chain works before you rely on the numbers.

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

Frequently asked questions

Does Cal.com capture Google Analytics data on its own?

No. Cal.com records the booking, but it does not automatically attach the visitor's marketing channel or landing page. Those values have to be captured on your website and passed into the booking form as hidden fields.

What is the difference between channel and landing page data?

Channel data describes how the visitor arrived, such as Paid Search or Organic Search, and can include campaign and keyword detail. Landing page data describes which page the visitor first viewed and the broader category that page belongs to.

Where does the booking attribution data go after Cal.com saves it?

It stays with the booking in Cal.com and can be sent to a CRM, a spreadsheet, or another connected tool through Cal.com's integrations or a third-party connector such as Zapier.

Why are my reports showing blank source values?

Blank values usually mean one of three things: the attribution was never captured on the page, the booking form is missing the hidden field for that value, or the downstream sync does not include the field. Check each layer in that order.