Capture Google Ads Data in Calendly: UTM Setup, Booking Attribution and Reports
Running ads is only half the job. The other half is knowing which campaigns produce booked meetings, customers and revenue — not just visits. This guide explains how to attach Google Ads campaign information to each Calendly booking, why page-to-page browsing breaks native tracking, and which reports become possible once the data travels with the booking.
Why visits alone mislead campaign decisions
Visitor counts and form completions can make one campaign look stronger than another while hiding the outcome that matters. Consider two campaigns with identical spend of $2,000. One brings 200 visitors and 20 leads; the other brings 100 visitors and 10 leads. On volume alone, the first appears to win.
Add customers and revenue and the picture can reverse. If the first produces 2 customers and $8,000, while the second produces 5 customers and $25,000, the smaller campaign is generating more value per lead. Its lead-to-customer rate is about 50% versus 10% in this example, its cost per customer is about $400 versus $1,000, and its return on ad spend is 1,250% versus 400%.
Step 1: Tag every ad with UTM parameters
UTM parameters are short text additions to a destination URL that label where traffic came from. For Google Ads, a consistent convention is:
- Medium: paid search
- Source: Google
- Campaign: the name of the Google Ads campaign
- Term: the name of the ad group the ad belongs to
- Content: the specific ad
Apply the same pattern to every ad so campaign, ad group and ad can be compared later. A URL that originally pointed to a Calendly integration page would carry those five values as query parameters, with the campaign value identifying the campaign that drove the visit.
Step 2: Install the attribution code and configure Calendly
Install the attribution code on the website, then configure it for the embedded Calendly widgets on the site. Setup guidance varies by website builder, so follow the instructions for your platform and then complete the Calendly-specific configuration for each embedded widget.
Checklist before testing:
- The code is present on pages that contain a booking widget
- Every embedded Calendly widget is configured, not just the first one found
- A test visit using a tagged ad URL is ready
- You know where booking details will be reviewed after submission
Step 3: Pass attribution through with each booking
Once configured, the tool records where a visitor came from. When that visitor books through Calendly, the attribution information is passed through with the booking.
Worked example: a marketing manager for a consultancy specialising in sustainable development promotes environmental impact assessment services for construction companies. A booking from that campaign could carry:
- Channel: Paid search
- Channel Drilldown 1: Google
- Channel Drilldown 2: Environmental impact assessment campaign
- Channel Drilldown 3: Construction industry ad
Those drilldowns let you move from a broad channel view to the specific campaign and ad that produced the meeting.
Step 4: Use the data inside Calendly and beyond
With the data stored alongside each Calendly event, you can review it on the event page, send it to a CRM for reporting, or send it to a spreadsheet for filtering, searching and charting. Spreadsheet data can also feed reporting tools for dashboards.
The key distinction is persistence. Native Calendly UTM capture only works when the parameters are in the URL of the page where the widget is submitted. If someone lands on the homepage, navigates to a booking page, or leaves and returns later, native capture can miss the origin. Browser-stored attribution keeps the parameters across browsing and return visits, so they are still available at booking time.
Attribution should also cover more than paid search. The same mechanism can record a Facebook ad visit or an organic search visit, giving a complete view of booking sources rather than only Google Ads. It can also record the first landing page and that page's category — for example, a services page for an environmental impact assessment — so you can see which content areas generate leads and customers.
Three reports to run after capture
Once booking-level attribution is flowing to a CRM or spreadsheet, three reports are especially useful:
- Leads by Channel: monthly lead volume broken down by channel, to check whether budget matches where leads actually come from. Heavy paid-search spend alongside mostly organic leads is a signal to reconsider allocation.
- Customers by Google Ads campaign: monthly customer volume by campaign, to identify which campaigns create customers and which should receive more or less investment.
- Revenue by Keyword: revenue from new customers broken down by the keyword that triggered the ad, to find the keywords worth funding further.
Together, these reports connect spend to bookings, bookings to customers, and customers to revenue.
Wrap up
Tag ads consistently, install and configure the attribution code for every embedded Calendly widget, test a booking from a tagged URL, and confirm the channel and drilldown values appear with the event. Then route the data to the CRM or spreadsheet where you will actually review it, and build the channel, campaign and keyword reports before making budget changes.
Frequently asked questions
Why would Calendly miss the campaign that brought a visitor?
No. Native capture depends on parameters being present in the URL of the page where the booking widget is submitted. If a visitor lands on the homepage, moves to a booking page, or returns later, that origin information can be lost. A browser-stored attribution approach keeps the parameters across pages and visits until booking.
What should the UTM values say for a Google Ads campaign?
Use a consistent convention: paid search for medium, Google for source, the campaign name for campaign, the ad group name for term, and the specific ad for content. Consistency matters more than the exact labels, because those values become the reporting breakdowns later.
What can you do once the data arrives with a booking?
View the details on the booking's event page in Calendly, send them to a CRM such as Salesforce, Pipedrive or HubSpot for dashboards, or send them to a spreadsheet for filtering and charting, including connections to tools such as Google Data Studio or Microsoft Power BI.
| Pool Fencing Campaign | Backyard Fencing Campaign | |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Goal Completions | 20 | 10 |
| Pool Fencing Campaign | Backyard Fencing Campaign | |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Leads | 20 | 10 |
| Customers | 2 | 5 |
| Revenue | $8,000 | $25,000 |