How to Capture UTM Parameters in HubSpot Meetings
When a prospect books a meeting through a HubSpot Meetings widget, the booking record usually contains their name, email, and chosen time slot. What it often lacks is the campaign, ad, or keyword that brought them to your site in the first place. This guide explains a practical way to close that gap: store attribution data in the visitor's browser, pass it into HubSpot contact properties at booking time, and use those properties to report on which campaigns generate meetings and customers.
Why meeting attribution is worth setting up
Paid media decisions get sharper when the outcome you measure is a booked meeting rather than a click, but only if each booking carries the campaign that produced it. Google Ads, Meta Ads, and other paid channels all compete for the same budget, and without per-booking source data you are choosing where to spend on instinct rather than evidence. The technical obstacle is well known: UTM parameters live in the page URL, so they survive only while the visitor stays on the page they landed on. The moment they navigate to a separate booking page, the URL changes and the parameters are gone. A browser-stored attribution layer fixes this by capturing the parameters at first arrival and replaying them at the moment of booking, so the meeting record keeps the original source even when the booking page is several clicks downstream.
Four setup steps
The setup sequence is straightforward and does not require custom development on the booking widget itself.
Step 1: Install the attribution script
Sign up for a trial and place the provided snippet on your website. Most site builders expose a settings area where you can paste header or footer code; if you already use Google Tag Manager, the snippet can be deployed there instead. Step-by-step installation guides exist for common platforms. The script needs to run on every page a visitor might land on, because it is responsible for reading and storing the UTM parameters at first arrival.
Step 2: Create the contact properties in HubSpot
In HubSpot, open Settings, then Data Management, then Properties. Use the Create Property button to add each of the following contact properties. The names below match the fields the attribution script expects to write into.
Contact field map
The table below lists each property and the kind of value it receives. Treat the property names as exact strings so the script can populate them without manual mapping.
Step 3: Let the script write attribution data at booking time
Once the script and properties are in place, the script reads UTM parameters and other attribution signals when a visitor arrives, stores them in the browser, and submits them alongside the booking. The visitor does not need to fill in any extra fields. The data travels with the meeting booking and lands on the contact record.
Worked example: a financial consulting firm
Imagine a financial consulting firm running a Google Ads campaign for retirement planning. A prospect clicks the ad, lands on the site, browses a few pages, and eventually books a consultation through an embedded HubSpot Meetings widget. Depending on the UTM parameters attached to the ad, the contact record could receive values such as Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Financial Consulting Campaign, and Channel Drilldown 3 = Retirement Planning. Those values persist even though the booking happened on a different page from the original landing page.
Step 4: Use the data in HubSpot
After the booking completes, the UTM values appear on the contact record alongside the visitor's name, email, and other submitted details. From there you can view the data per contact, build reports showing which campaigns drive meetings and customers, trigger workflows that include the attribution values, or export the data to a spreadsheet for further analysis.
What the attribution layer captures beyond UTM parameters
UTM parameters are only part of the picture. The script also classifies visitors into channels such as Paid Search, Organic Search, Paid Social, Referral, and Direct Traffic, so leads that arrive without UTM parameters still receive a source. It records click identifiers including the Google Click ID, Microsoft Click ID, and Facebook Click ID, which can later be sent back to the relevant ad platform for offline conversion tracking. It also stores the landing page and landing page group, which lets you report on how much business specific content pages generate.
Four reports worth building
Once the contact properties are populated, several report shapes become useful. A channel breakdown report counts meetings each month and groups them by acquisition channel, so paid and organic contribution sit side by side for comparison. A leads-by-Meta-network report breaks down performance across Facebook, Instagram, Messenger, and the Audience Network. A customers-by-Google-Ads-campaign report shows which campaigns produce paying customers rather than just clicks. A revenue-by-keyword report, built by passing the search keyword through a tracking template, shows which terms drive revenue. Each report depends on the attribution values being present on the contact record at the time the meeting is booked.
Decision checklist before you start
Use this checklist to confirm the setup fits your situation. First, confirm that your booking widget is embedded on a page where the attribution script can run. Second, confirm that the six contact properties exist with the exact names the script expects. Third, decide whether you need click ID capture for offline conversion tracking; if you do, confirm that your ad platforms accept the identifiers you plan to send. Fourth, decide which reports you will build first, because the property values need to be present before those reports can be populated. Fifth, confirm that your consent and privacy posture allows browser storage of attribution data.
Why UTM parameters disappear without a stored layer
The parameter is usually present on the ad; what breaks is the path between arrival and booking. A visitor lands on a homepage with UTM parameters in the URL, clicks through a few internal pages, then follows a call-to-action that opens a dedicated scheduling page. That scheduling URL has no campaign parameters attached, so capture logic that reads only the current URL at booking time records nothing. Saving the values in the browser on first arrival and reading them again when the booking is submitted keeps the original source intact across that journey.
| Property name | What it receives |
|---|---|
| Channel | High-level acquisition channel, such as Paid Search or Organic Search |
| Channel Drilldown 1 | First level of detail within the channel, such as the ad platform |
| Channel Drilldown 2 | Second level of detail, such as the campaign name |
| Channel Drilldown 3 | Third level of detail, such as the ad group or keyword theme |
| Landing Page | The page where the visitor first arrived |
| Landing Page Group | A category or grouping for the landing page |
Property names must match the strings the attribution script writes into. Values shown are illustrative examples of the kind of data each field receives.
Frequently asked questions
Do I need to modify the HubSpot Meetings widget itself?
No. The attribution script runs on your website pages and passes data through at booking time. The widget configuration does not need custom code.
What happens if a visitor books without UTM parameters?
The script still classifies the visitor into a channel such as Organic Search, Organic Social, Referral, or Direct Traffic, so the contact record receives a source value even when no UTM parameters are present.
Can I use the captured click IDs for offline conversion tracking?
Yes. The script captures the Google Click ID, Microsoft Click ID, and Facebook Click ID. Those identifiers can be sent back to the relevant ad platform at a conversion moment, such as when a lead becomes a paying customer.
Where do the attribution values appear after a meeting is booked?
They appear on the contact record in HubSpot CRM, alongside the details the visitor submitted. From there you can use them in reports, workflows, or exports.