How to Capture UTM Parameters in Unbounce and Send Them to Your CRM
Unbounce forms can carry campaign data into your CRM, but only if the source is captured before the visitor submits. This guide walks through the four setup steps, explains what each of the six hidden fields represents, and shows how to read the resulting reports.
Why capture UTM parameters on Unbounce pages
If you only see clicks and form fills, you cannot tell which campaigns produce paying customers. Passing UTM data into the CRM lets you compare channels, campaigns, and ads against revenue instead of traffic. The setup below uses a small script plus six form fields so the original source survives page navigation.
The four setup steps
- Install the tracking script site-wide. In the Unbounce builder, open Script Manager, add a new script targeting all pages, and place the snippet in the head. Google Tag Manager is an alternative if you already use it on those pages.
- Add six hidden fields to each Unbounce form. Drag a Hidden Field from the form fields menu and name it to match one of the six values below.
- Let the script populate the fields. When a visitor lands, the script reads UTM parameters and stores them in the browser. On submit, it writes the stored values into the hidden fields.
- Confirm the data reaches Unbounce and your CRM. The values appear in the Unbounce leads view, can be included in notification emails, and can be sent onward through native integrations or Zapier/Make.
Field map: what each hidden field represents
The six hidden fields are not interchangeable. Use this map when naming fields in Unbounce and when mapping them to CRM properties.
Worked example: a Google Ads lead for a packaging manufacturer
Suppose a marketing manager at a custom packaging company runs Google Ads. A prospect searches for "custom packaging manufacturer," clicks an ad, and submits a quote request on an Unbounce page. The hidden fields would receive:
- Channel = Paid Search
- Channel Drilldown 1 = Google
- Channel Drilldown 2 = Custom Packaging Solutions Campaign
- Channel Drilldown 3 = Custom Packaging Manufacturer
- Landing Page = www.yourpackaging.com/services/custom-design
- Landing Page Group = /services
This shows how the same form can distinguish the network, campaign, ad group or keyword, and the first page the visitor saw.
Raw UTM capture vs. a persistent attribution layer
Unbounce can pass UTM parameters into forms directly, but that approach depends on the visitor submitting on the page where they arrived. If they click through to a second page before filling in the form, the campaign values from the original URL are no longer present. A persistent layer takes a different route: it records the source in the browser at first arrival and replays it into the form at submit time, wherever that form sits. That also covers organic and direct visits where no UTM parameters exist. It can additionally capture click IDs such as GCLID, MSCLKID, and FBCLID for later conversion uploads. Because the script runs across the whole site rather than only on Unbounce pages, a visit that begins on your main site and later reaches an Unbounce form still carries its original source.
Three different failure modes to check
When UTM data does not appear in the CRM, the cause is usually one of three things:
- The script is not on every page. If it only runs on Unbounce pages, a visit that starts on the main site will not be recorded.
- The hidden field names do not match. A field named "channel" instead of "Channel" will not receive the value.
- The visitor's browser blocks or clears storage. In that case the stored source may be unavailable at submit time.
Check the script placement first, then the exact field names, then the browser behavior.
Reports to run once the data is flowing
With campaign data in the CRM, four reports become practical:
- Leads by Channel: compare monthly lead volume across paid, organic, direct, and referral sources.
- Leads by Facebook Ads Network: see which Meta placement produces the most leads.
- Customers by Google Ads campaign: count paying customers per campaign rather than clicks or form fills.
- Revenue by Keyword: use the keyword in UTM parameters to see which search terms generate revenue, which also informs SEO priorities.
Pre-launch checklist
- Script installed in Script Manager with all-pages targeting and head placement, or via Google Tag Manager.
- Script also present on the main website, not only on Unbounce pages, so visits that start elsewhere are still recorded.
- All six hidden fields present on every Unbounce form and named exactly.
- A test submission from an ad URL shows the expected values in the Unbounce leads view.
- CRM mapping confirmed for each of the six fields.
- Notification email includes the attribution fields if sales needs them at first contact.
| Field name | What it captures |
|---|---|
| Channel | High-level source category, e.g. Paid Search, Organic Search, Organic Social, Direct, Referral |
| Channel Drilldown 1 | First breakdown level, e.g. Google, Facebook |
| Channel Drilldown 2 | Second breakdown level, e.g. campaign name |
| Channel Drilldown 3 | Third breakdown level, e.g. ad group, ad, or keyword |
| Landing Page | Full URL of the first page the visitor landed on |
| Landing Page Group | Subdirectory of the first landing page, e.g. /services or /blog |
Field names must match exactly in Unbounce for the script to populate them.
Frequently asked questions
Does this work for organic and direct traffic, not just paid ads?
Yes. The persistent layer records a channel for every lead, including Organic Search, Organic Social, Direct, and Referral, even when no UTM parameters are present.
What happens if a visitor lands on one page and submits a form on another?
The source is stored in the browser when the visitor first arrives, so the original UTM data can still be written into the form on a later page. Raw UTM capture that only reads the current URL would lose it.
Can I capture click IDs as well as UTM parameters?
Yes. The script captures GCLID, MSCLKID, and FBCLID alongside UTM parameters, which lets you send conversions back to the ad platform later.