How to Capture UTM Parameters in 123 Form Builder
When a lead submits a form, the campaign that brought them in is often invisible unless you deliberately capture it. 123 Form Builder can store UTM parameters and landing page details alongside the contact's name and email, but only if the form is set up with the right hidden fields and a way to persist the data across page views. This guide walks through the setup, shows what the captured fields look like, and explains where raw UTM capture tends to break down.
Four steps to capture UTM parameters in 123 Form Builder
The setup has four moving parts: tag your campaigns, add hidden fields to the form, let a capture tool populate those fields, and confirm the data reaches your CRM or analytics tool. The order matters because the hidden fields need to exist before the tool can fill them.
- Tag your ads and campaigns with UTM parameters. Every link that points to your site should carry UTM parameters so the source, medium, and campaign are identifiable. This includes paid ads, guest posts, social bios, trade publication ads, email marketing, and even email signatures. The goal is to avoid untagged links that arrive with no source information.
- Add hidden fields to every 123 Form Builder form. Hidden fields are invisible to the visitor but are submitted with the form. In 123 Form Builder, drag a Hidden Field from the Add Fields panel into the form. Selecting the field opens a settings box where you can set the Label, Default Value, and CSS Classes. For a capture tool to fill the fields correctly, the form needs six hidden fields: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group.
- Let the capture tool populate the hidden fields. Once the UTM parameters are on your campaigns and the hidden fields exist in the form, the tool reads the visitor's source data and writes it into those fields in the background. The visitor does not see or type anything into them. The tool works by reading signals such as the HTTP referrer, UTM parameters, and device, sorting each visit into a channel, and saving that information in a cookie in the visitor's browser. When the form is submitted, the saved cookie data fills the hidden fields.
How the capture tool works. The tool is a small script that inspects the visitor's HTTP referrer, UTM parameters, and device details. It sorts each visit into a channel such as Organic Search, Paid Social, or Paid Search, and stores that classification in a cookie in the visitor's browser. When a visitor submits a 123 Form Builder form, the tool reads the saved cookie and writes the channel, drilldowns, and landing page into the hidden fields, so the source data travels with the contact record into your CRM.
- Confirm the data is captured on submission. When the visitor submits the form, 123 Form Builder stores the UTM parameters together with the visitor's name, email, phone number, and other form answers. From there, native integrations can send the full record to a CRM such as Salesforce, ActiveCampaign, or HubSpot.
What each hidden field represents
The six hidden fields are not interchangeable. They split the source data into a channel and a set of drilldowns, plus a landing page and its group.
- Channel records the broad traffic category, such as Paid Search or Organic Social.
- Channel Drilldown 1 records the first level within that channel, such as Google.
- Channel Drilldown 2 records the next level, such as a campaign name.
- Channel Drilldown 3 records a further level, such as the specific ad or product.
- Landing Page records the full URL of the page the visitor first landed on.
- Landing Page Group records the subdirectory or category of that landing page.
A useful way to check your setup is to ask whether each field would still make sense if the visitor arrived from a channel with no UTM parameters at all. A categorizing tool should still fill in Organic Search, Organic Social, Direct, or Referral where it can, rather than leaving the fields blank.
Example: what populated fields look like
Imagine a cloud storage company running a Google Ads campaign. A visitor searches for a way to share large files, clicks the ad, lands on a feature page, and later submits a demo request form.
If the hidden fields are set up correctly, the submission might show:
- Channel = Paid Search
- Channel Drilldown 1 = Google
- Channel Drilldown 2 = Brand Campaign
- Channel Drilldown 3 = Data Storage+
- Landing Page = www.datastorageplus.com/features/share
- Landing Page Group = Features
This is more useful than a single raw UTM string because the CRM can group leads by channel and by landing page group without manual cleanup. The same record also carries the visitor's contact details and any other answers from the form.
Why UTM capture often fails without persistence
A common failure mode is simple: the visitor lands on a campaign page with UTM parameters, clicks through to a second page, and fills out the form there. If the capture method only reads UTM parameters from the current page URL, the source data is gone by the time the form is submitted.
A tool that stores the source data in a cookie in the visitor's browser avoids this. It remembers the original UTM parameters and landing page even after the visitor browses several pages, so the form submission still carries the campaign that brought them in. This is the difference between capturing a URL and capturing a journey.
Raw UTM strings versus categorized channels
Raw UTM values are often inconsistent. One campaign might use UTM_Source=Google.com, another UTM_Source=google, and another UTM_Source=gg. A CRM that groups by the raw value will treat those as three separate sources, which distorts reporting.
A categorizing tool can normalize those variations and assign the lead to Paid Search regardless of capitalization or domain differences. That produces cleaner channel reporting and reduces the need for manual data cleanup in the CRM.
Decision checklist before you build
Use this checklist to decide whether raw UTM capture is enough or whether you need a categorizing layer.
- Are all your campaign links tagged with UTM parameters, including email signatures and social bios?
- Does your form appear on the same page as the landing page, or do visitors navigate before submitting?
- Do you need channel-level reporting, or will you manually clean raw UTM values in the CRM?
- Have you added all six hidden fields to every form that should capture source data?
- Do you need landing page and subdirectory data, not just the campaign name?
- Will the captured fields map cleanly to your CRM's source fields?
If visitors often move between pages before submitting, or if your UTM values vary in capitalization and format, a tool that persists and categorizes the data will save significant cleanup time.
Frequently asked questions
Are hidden fields visible to the person filling out the form?
No. Hidden fields are not shown to the visitor. They exist in the form so that a capture tool can write source data into them at submission time.
Why does the form need six hidden fields instead of one?
The six fields split the source data into a channel, three drilldown levels, a landing page, and a landing page group. That structure lets your CRM report on broad channel and specific campaign or page without parsing a single raw string.
Why do UTM parameters sometimes disappear before the form is submitted?
If the capture method only reads the current page URL, the UTM parameters are lost when the visitor moves to a different page before filling out the form. Storing the data in a cookie in the visitor's browser keeps the original source available across page views.
Can the setup capture visitors who arrive without UTM parameters?
A categorizing tool can still populate the hidden fields for organic search, organic social, direct, and referral traffic where possible, rather than leaving them blank.