Capture UTM Parameters in WeForms
A form submission alone tells you who contacted you, not which campaign brought them in. By adding invisible attribution fields to a WeForms form and populating them from the visitor's arrival data, each lead can be reported by channel, campaign detail and first landing page.
Tag campaigns and add hidden fields
Start with consistent tagging on paid activity. Add UTM parameters to campaigns on search engines and social platforms, and also to custom placements such as sponsored newsletters or display advertising in industry publications. Without tags on the originating campaign, paid attribution has nothing to capture.
Next, open the relevant form and add hidden fields. In the form builder, drag a Hidden field into the form for each value you want stored. The fields to include are:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Landing Page
- Landing Page Group
These fields stay invisible to visitors while remaining part of the submitted data.
How attribution values reach the form
An attribution snippet placed on the site examines how a visitor arrived, classifies that arrival into a channel, and stores the result in a browser cookie. When a form is later submitted, the stored values are written into the hidden fields and captured together with the visitor's name, email and company details.
Consider a visitor who finds a software company through a branded search ad, browses the site, and then completes a demo-request form. The hidden fields could be populated as follows:
- 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
That example shows the distinction between the broad channel, the progressively more specific drilldowns, and the exact first page the visitor reached.
Use the captured data and check the method
Once submitted, the attribution values travel with the lead record. They can be sent onward to a CRM, shown in email notifications, saved to a spreadsheet, or used in other reporting. With that data attached, you can break results down by source and channel — for example, leads from a social platform, customers from a search platform, revenue by ad channel, or return on investment per channel.
Three practical differences matter when choosing a method:
- Coverage: deriving attribution for organic, direct and referral visits as well as tagged paid clicks gives a complete lead-source picture, rather than only the paid subset.
- Persistence: storing values in a cookie means they survive navigation from the landing page to a separate form page, instead of being lost when the UTM parameters are no longer in the URL.
- Cleanliness: normalising inconsistent source spellings and capitalisation prevents one real source from splitting into several report rows that need manual merging.
Landing-page capture adds a further view. Recording the first page a lead reached, and the group that page belongs to, lets you see how much demand content areas such as a blog generate and which individual pages contribute most.
Pre-publish checklist
Before relying on reports, run a short end-to-end check of the setup you have built. Confirm that every paid campaign and custom placement carries UTM parameters, and that all six hidden fields — Channel, Channel Drilldown 1 through 3, Landing Page and Landing Page Group — are present on each form you intend to track. Then submit a test form after arriving from a tagged link and verify that the channel, drilldowns and landing page are populated. Submit a second test after navigating to a different page and confirm the values persist. Finally, check that the values arrive correctly in whichever destination you use, such as a CRM, an email notification or a spreadsheet. If you need trial or signup terms, check the current offer details on the signup page before proceeding.
Frequently asked questions
What setup is needed before a WeForms submission can carry attribution data?
Add UTM parameters to paid campaigns across search and social platforms, and to custom placements such as newsletter sponsorships or industry-publication display advertising. Then add hidden fields to the form so attribution data can be stored with the submission.
What do hidden fields do in this workflow?
Hidden fields are present on the form but not visible to visitors. An attribution snippet can write channel and landing-page values into them, and those values are submitted alongside name, email, company and other fields the visitor completes.
Does this only work for paid ads with UTM tags?
Yes. Attribution can also be derived for organic and direct visits, not only for paid clicks carrying UTM tags. That gives a fuller view across Organic Search, Organic Social, Direct, Referral and paid channels.
What happens if the form is on a different page from the landing page?
A browser cookie can retain the attribution values after the first landing page, so they are still available when the visitor later reaches a form on a different page, such as moving from a homepage to a quote-request page.
Why normalise UTM values instead of storing them raw?
Normalising variations in source naming helps group them under one channel, for example Paid Search, instead of reporting them as separate sources that need manual consolidation.