How to capture UTM parameters in QuForms
Analytics platforms tell you how many sessions arrived from an ad. They rarely tell you which of those sessions became a named lead in your form tool. This guide closes that gap for QuForms: you tag your campaigns, place the right hidden fields on the form, let a UTM capture script populate them, and read the source data on each submission.
Why form-level source data matters
Website traffic counts and lead counts answer different questions. A traffic report can show a spike in visitors from a paid campaign while saying nothing about how many of those visitors requested a demo or asked for a quote. Once the source travels with the form submission, you can compare channels on leads rather than clicks, and you can see which campaigns actually produce conversations.
The setup below uses marketing attribution software to write attribution data into QuForms hidden fields. The work splits into four stages: tag the ads, add the fields, let the script fill them, then confirm the values arrive with the submission.
Step 1: Put UTM parameters on your paid campaigns
Every paid placement you want to measure needs UTM parameters on its destination URL. That covers social advertising on LinkedIn, Instagram, Twitter and Facebook as well as search advertising on Google and Bing. If a campaign link has no tags, nothing downstream can attribute the visit to it.
Decide on a naming convention before you tag anything, and write it down. The cleaner your values, the less work you do later reconciling reports.
Step 2: Add hidden fields to the QuForms form
Hidden fields sit on the form but are not shown to the person filling it in. They give the capture script a place to write the attribution values at submission time. In QuForms you add one by dragging a 'Hidden' field onto the form, typically at the bottom.
The capture script needs six hidden fields present for its standard workflow. Create each one with these exact labels:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Landing Page
- Landing Page Group
Use the same spelling and spacing shown here, since the script matches its output to these field names. The field map table below shows what each one holds in a worked example.
Step 3: Let the capture script fill the fields automatically
With the fields in place, the capture script watches how each visitor reached the site and writes the result into the hidden fields when the form is submitted. Nothing is typed by the visitor and nothing is read from the current page URL at submit time.
Take a marketing lead at a fictional company, Olmo Software. A prospect searches for "Olmo Software" on Google, clicks a brand ad, browses the site, and later submits a demo request. The hidden fields would carry values along these lines:
- Channel: Paid Search
- Channel Drilldown 1: Google
- Channel Drilldown 2: Brand Campaign
- Channel Drilldown 3: Olmo Software
The first page the visitor saw is recorded too, so the same submission might also include a landing page such as www.olmosoftware.com/landing-pages/brand and a landing page group of Landing Pages.
Step 4: Confirm the values arrive with the submission
When the form is submitted, QuForms stores the lead's own answers — name, email, company — alongside the attribution values written into the hidden fields. From there the combined record can travel to a CRM such as Salesforce or ActiveCampaign, appear inside QuForms' new-submission email notifications, land in a spreadsheet, or be passed to other tools through Zapier.
How the capture script decides the channel
The capture script is a small piece of code added to your site. On each visit it reads the same kinds of technical signals that analytics tools inspect, groups the visitor into a channel such as Paid Search, Paid Social or Organic Search, and keeps that classification in a cookie on the visitor's browser. Because the classification is stored rather than re-derived, it survives the visitor moving between pages.
When a QuForms form is submitted, the script writes the stored values into the hidden fields, and they are saved together with the lead's contact details.
Two different reasons attribution goes missing
It helps to separate two failures that look similar in a report.
First, untagged traffic. If an ad link carries no UTM parameters, there is nothing for any tool to read, and the lead will not be credited to that campaign. The fix is at the ad platform, not the form.
Second, tags lost in transit. Some capture methods only read UTM parameters from the URL of the page where the form is submitted. Picture a visitor who clicks a Google Ad, lands on the homepage, then clicks 'Get A Quote' and submits the form on the quote request page. The campaign tags were on the homepage URL, not the quote page, so a URL-only method records nothing. A cookie-based capture method avoids this because the values were stored at landing time and are read from there at submission, whichever page hosts the form.
Why stored-and-normalized data reads better in reports
Raw UTM values reflect whoever built the link. One period of Google Ads management might produce UTM_Source=google ads, another UTM_Source=google, and a third UTM_Source=adwords. A tool that simply echoes the raw string shows three separate sources, and someone has to add them up by hand to see total Google Ads performance.
A normalizing capture method accounts for capitalization and naming differences and assigns the lead to the correct channel anyway — in this case Paid Search — so the report stays readable without manual reconciliation.
Beyond paid campaigns: organic sources and landing pages
Attribution is not limited to tagged ads. Leads arriving from Organic Search, Organic Social, Referral, Direct and other organic paths are also classified, which gives a fuller picture of what produces customers and supports budget decisions — for example, shifting spend toward a channel that is already outperforming paid search.
Landing page data is captured as well: the full landing page URL and a landing page group. That lets you report on leads generated by a section of the site, such as the blog, and drill down to individual posts.
Setup checklist before you go live
- Every paid campaign URL carries UTM parameters, and the naming convention is documented.
- The QuForms form contains all six hidden fields the script expects, spelled exactly as listed in Step 2.
- A test submission from a tagged link shows the expected channel and drilldown values.
- A test submission from an untagged organic visit still shows a sensible channel.
- A test where the form lives on a different page from the landing page still records the original campaign.
- You have decided where submissions go next: CRM, notification email, spreadsheet or automation.
| Hidden field | What it holds in the Olmo Software example |
|---|---|
| Channel | Paid Search |
| Channel Drilldown 1 | |
| Channel Drilldown 2 | Brand Campaign |
| Channel Drilldown 3 | Olmo Software |
| Landing Page | www.olmosoftware.com/landing-pages/brand |
| Landing Page Group | Landing Pages |
Field names are the exact labels the capture script expects. Example values illustrate one brand-search scenario and will differ per campaign.
| Symptom | Cause | Where to fix it |
|---|---|---|
| Lead shows no campaign at all | Ad link has no UTM parameters | Ad platform URL settings |
| Lead shows no campaign despite tagged ads | Form submitted on a page whose URL lacks the tags, and no stored value is read | Capture method that persists values across pages |
Distinguishes tagging gaps from capture-method gaps; both can appear as blank source fields in reports.
Frequently asked questions
Do the UTM parameters have to be on the page where the form is submitted?
Not with a cookie-based capture method. It stores the attribution in a cookie when the visitor lands, so the values can be written into QuForms hidden fields no matter which page hosts the form. Methods that read only the current URL will miss the campaign when a visitor lands on one page and submits on another.
What happens if my UTM values are inconsistent between campaigns?
A normalizing capture method accounts for capitalization and different naming conventions and assigns the lead to the correct channel regardless. Raw capture methods would instead show google ads, google and adwords as three separate sources that you would have to total manually.
Does this only work for paid campaigns?
No. Leads from Organic Search, Organic Social, Referral, Direct and other organic paths are also classified, so you can compare paid and organic performance on leads rather than sessions.
Where can the captured data go after submission?
QuForms stores the lead's answers together with the hidden field values. From there the record can be sent to a CRM such as Salesforce or ActiveCampaign, included in new-submission email notifications, stored in a spreadsheet, or passed to other tools via Zapier.
How do I know the setup is working?
Submit a test form from a tagged campaign link and check that the channel and drilldown fields contain the expected values. Then submit from an untagged organic visit and from a page other than the landing page to confirm the values still arrive.