How to Capture UTM Parameters in Formstack Forms
Formstack forms collect the details a prospect types in. To learn which campaign brought that prospect to you, the form also needs to carry attribution context. This guide walks through the setup, explains the six hidden fields involved, and shows what a completed submission can look like.
Four-step setup
> 1. Tag every link with UTM parameters. Apply them to paid ads, social posts, guest articles, email campaigns, influencer placements, and any other link that points to your site. These tags tell the attribution layer where a visitor came from. > 2. Add six hidden fields to each Formstack form. In the form editor, drag in a Short Answer field and switch it to Hidden. Repeat until you have all six, labelled: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, Landing Page Group. > 3. Let the attribution layer fill those fields. Once the hidden fields exist, the script writes the visitor's captured data into them at submission time. > 4. Submit and route. Formstack stores the hidden values alongside the typed answers, and its integrations or a connector such as Zapier can forward everything to a CRM, email platform, billing system, or spreadsheet.
Checklist before you publish:
- Every active campaign link carries UTM tags.
- All six hidden fields exist on every form that should report attribution.
- Field labels match the expected names exactly.
- A test submission shows non-empty values in all six fields.
- The CRM mapping includes the hidden fields, not just name and email.
What a completed submission looks like
Consider a visitor who searches for a way to share large files, clicks a paid Dropbox result, and requests a demo. Depending on the tags used, the hidden fields could read:
- Channel: Paid Search
- Channel Drilldown 1: Google
- Channel Drilldown 2: Brand Campaign
- Channel Drilldown 3: Dropbox
- Landing Page: www.dropbox.com/features/share
- Landing Page Group: Features
The typed answers (name, email, company) sit alongside these values in the same Formstack submission. That pairing is what makes campaign-level reporting possible later.
How the attribution layer works
A small script on your site inspects signals about each visit: UTM parameters, HTTP referrer, device details, and similar technical information. It sorts the visit into a channel such as Paid Search, Organic Search, or Paid Social, and records the landing page and its parent group. When the visitor submits a Formstack form, those values populate the hidden fields and travel with the submission.
The practical effect is that a form submission becomes a record of both who enquired and how they found you.
Why this beats raw UTM capture
Pulling UTM strings straight from the URL has three common gaps. The approach above closes them.
All traffic, not just tagged traffic. Many leads arrive through organic search, organic social, referrals, or direct visits, where no UTM parameters exist. A channel-classification layer still assigns those visits to a source, so reports cover every lead rather than only paid campaigns.
Persistence across pages. URL-only capture works only if the form sits on the same page as the landing page. A visitor who clicks a quote button and completes the form elsewhere loses the tags. Storing the data in a browser cookie keeps it available wherever the form appears.
Consistent naming. UTM values drift: Twitter.com, twitter, and tw can all describe the same source. A layer that recognises these variations groups them under one channel instead of forcing manual cleanup.
Landing-page context. Beyond channel, the setup records the landing page and its group, so you can compare a whole content section against individual pages.
Two failure modes to distinguish
If hidden fields arrive empty, the cause is usually one of two things. Either the script is not present on the page where the form loads, or the field labels do not match the expected names. Check the labels first, then confirm the script fires on the form page.
If values arrive but look fragmented, the issue is data quality rather than setup. Inconsistent UTM casing or abbreviations produce separate source strings unless a classification layer normalises them. Review your tagging conventions before blaming the form.
Putting it to work
The goal is simple: every Formstack submission should answer both who enquired and where they came from. Tag your links, add the six hidden fields, confirm a test submission carries values, and map those fields into your CRM. From there, campaign and channel reporting becomes a matter of querying the data you already collect.
| Field label | What it records |
|---|---|
| Channel | Broad source category, e.g. Paid Search |
| Channel Drilldown 1 | First level of detail, e.g. Google |
| Channel Drilldown 2 | Second level, e.g. campaign name |
| Channel Drilldown 3 | Third level, e.g. keyword or ad variant |
| Landing Page | Full URL of the first page visited |
| Landing Page Group | Parent section of that page, e.g. Features |
Field labels must match exactly for the attribution layer to populate them.
Frequently asked questions
How long does the Formstack setup take?
Most of the work is adding six hidden fields to each form and confirming a test submission. The larger task is tagging every campaign link consistently, which is ongoing.
What happens when a visitor arrives without UTM parameters?
The attribution layer still classifies the visit using referrer and other signals, so organic, referral, and direct traffic are recorded rather than left blank.
How does the data reach my CRM?
Formstack stores the hidden values with the submission. Its native integrations or a connector such as Zapier can then forward the full record to a CRM, email platform, or spreadsheet.
Does the form need to be on the landing page?
No. Because the attribution data is stored in a browser cookie, the form can sit on any page and still receive the original campaign values.
Why do my UTM reports show duplicate sources?
Inconsistent casing or abbreviations in UTM values create separate entries. A classification layer that recognises these variations groups them under one channel; otherwise, standardise your tagging conventions.