Capture UTM parameters in Formsite forms
A Formsite submission is most useful when it carries the campaign context that brought the visitor to your site. This guide explains how to tag campaigns, add hidden fields, populate them from the visit, and verify the result before sending leads onward.
Why campaign context matters
Growth decisions depend on knowing which channels and campaigns create leads and customers. If a form submission arrives without its origin, later CRM reports cannot reliably compare paid search, paid social, organic search, referral, or direct traffic. Capturing campaign context at submission time closes that gap.
Step 1: Tag campaigns before they run
Tag every paid and campaign link consistently, including social and search ads, email sends, and trade-publication placements. Consistent tagging gives the attribution code a reliable starting point for categorizing the visit.
Step 2: Add the hidden fields
In Formsite, drag in a Hidden Field for each value below, or mark an existing field as hidden through its properties. Hidden fields stay invisible to visitors while remaining available for automatic completion.
Step 3: Let the visit data populate the fields
When a visitor arrives, the attribution code examines visit data such as UTM parameters and referrer information, categorizes the visit, and stores it in a browser cookie. At submission, those stored values fill the hidden fields alongside the name, email, phone, and other details the visitor entered. Because the data is stored, it can survive browsing across multiple pages before the form is completed.
Step 4: Send and verify the submission
Use Formsite integrations to forward the completed record to a CRM or other connected tool. Before relying on the data, submit a test form from a tagged link and confirm that every hidden field arrived with the expected value.
What standardized capture adds
Raw UTM values alone can fragment reporting: variants such as Twitter.com, twitter, and tw may appear as separate sources. Standardized channel and drilldown values reduce that cleanup. Capturing the landing page and its group also shows whether a whole site section, such as a blog, or a single page is producing leads.
| Hidden field | What it records | Example value |
|---|---|---|
| Channel | Broad traffic category | Paid Search |
| Channel Drilldown 1 | First-level source detail | |
| Channel Drilldown 2 | Second-level campaign detail | Brand Campaign |
| Channel Drilldown 3 | Third-level source detail | Dropbox |
| Landing Page | Exact page where the visit landed | www.dropbox.com/features/share |
| Landing Page Group | Site section containing that page | Features |
Example values are illustrative from a paid-search visit; actual values depend on the visitor's campaign and landing page.
Frequently asked questions
What is the shortest setup sequence?
Add UTM parameters to paid and campaign links, create the six hidden fields in Formsite, let the attribution code populate them from the visit, then submit a test form and check that channel, drilldown, and landing-page values arrive with the lead details.
Why not pass raw UTM values directly?
Raw values can split one source into several entries when capitalization or naming differs. Grouping the visit into a standard channel and drilldown levels keeps reporting consistent.
Does this only work for paid traffic?
No. Visits from organic search, organic social, direct, and referral traffic can also be categorized, so reporting is not limited to paid campaigns.
What if the visitor lands on one page and submits on another?
Storing the visit data in a browser cookie preserves the original landing context when the form is completed on a later page, rather than requiring UTM parameters to still be present in the form page URL.