Capture UTM Parameters in FormAssembly Forms
You can connect campaign tagging to form submissions by adding UTM parameters to campaigns, placing hidden fields in FormAssembly, and letting an attribution tool populate those fields before submission. The captured values then travel with the lead's name, email and company details into your CRM, email notifications, spreadsheet or other downstream system, making it possible to report leads, customers and revenue by source.
1. Tag every campaign at the click
Start with the campaigns themselves. Add UTM parameters to paid activity across search engines such as Google and Bing, social platforms such as LinkedIn, Instagram, Twitter and Facebook, and bespoke placements such as sponsored newsletters or display advertising in trade publications. Without consistent tagging at the click, there is nothing reliable for the form to capture.
2. Add hidden fields in FormAssembly
Hidden fields are present on the form but not visible to visitors, which makes them a clean place for attribution data to be written without changing what the visitor sees or completes. In the FormAssembly builder, add the Hidden Field type through the Add Content dropdown, then add one field for each value you want to receive:
Fields to add
Channel Channel Drilldown 1 Channel Drilldown 2 Channel Drilldown 3 Landing Page Landing Page Group
3. Let the tool populate the fields automatically
Once the fields exist, the attribution tool watches where each visitor came from, categorises the visit using the same kinds of technical signals analytics tools use, and stores the result in a browser cookie. When a form is submitted, it writes the stored channel and landing page values into the hidden fields.
Worked example: a paid search visit
Consider a marketer at a company called Olmo Software. A visitor searches Google for Olmo Software, clicks a brand ad, browses the site and then completes a demo request form. Depending on the UTM values used, the hidden fields might be completed as follows:
Example values
Channel = Paid Search Channel Drilldown 1 = Google Channel Drilldown 2 = Brand Campaign Channel Drilldown 3 = Olmo Software Landing Page = www.olmosoftware.com/landing-pages/brand Landing Page Group = Landing Pages
4. Capture and report on submission
On submission, FormAssembly captures those attribution values alongside the details the lead typed in. From there you can route the record to a CRM, view it in email notifications, store it in a spreadsheet, or use it in reporting. Useful questions to answer include how many leads came from Facebook Ads, how many customers came from Google Ads, and how much revenue search engine optimisation generated.
Why this approach covers more than paid ads
A UTM-only approach only records tagged paid traffic. This setup also categorises organic visits, including Organic Search, Organic Social, Direct and Referral, so reports cover every lead rather than only paid campaigns. That fuller picture supports better decisions about where to invest marketing effort.
Failure distinction: same-page capture versus cookie storage
Many capture methods need the UTM parameters to still be present on the exact page where the form is completed. That fails in a common journey: a visitor clicks a Google Ad, lands on a campaign page, then clicks Get A Quote and submits on a different page. The original parameters are lost. Storing attribution in a cookie solves this because the values persist as the visitor browses, regardless of which page the form is submitted from.
Cleaner data from inconsistent tagging
Raw UTM values are often inconsistent. One campaign might use google.com, another google and another adwords as the source, which would look like three separate sources in a CRM report and require manual stitching. The attribution tool accounts for capitalisation and naming inconsistencies and assigns the lead to the correct channel, producing cleaner reporting data.
Landing page data for content reporting
Landing page capture adds another reporting dimension. Alongside the channel data, the tool records the first page the visitor arrived on and its category. With that in place you can ask how many leads and customers the blog generates, and how many Organic Search leads come from the blog compared with other site content.
Pre-publish checklist
Before you publish, run through this checklist: UTM parameters are added to every paid and bespoke campaign; all six hidden fields are present in the FormAssembly builder; a test visit from a tagged link completes the fields correctly; a test visit from an organic channel is categorised; a multi-page journey still passes the original attribution; and the submitted record reaches your CRM or spreadsheet with the attribution values intact.
Get started
Capturing UTM parameters in FormAssembly gives you a complete view of where leads and customers originate, including organic sources. To try the approach described here, check the current trial terms on the signup page before you begin.
Frequently asked questions
Does the visitor need to submit the form on the same page they first landed on?
No. The cookie stores the attribution information in the visitor's browser, so the hidden fields can still be completed when the form is submitted from a later page.
Can landing page information be captured alongside UTM data?
Yes. In addition to UTM and channel information, the setup can also pass the initial landing page and its category, such as a blog path, so content performance can be reported separately.
What happens if UTM values are inconsistent across campaigns?
The attribution tool normalises common variations in capitalisation and naming, so inconsistent UTM values are assigned to the intended channel instead of appearing as separate sources.