Capture UTM Parameters in WS Form
Visitor counts alone do not show which campaign produced a lead. Capturing campaign and landing-page data with each WS Form submission connects that lead to its origin, so you can review performance in your CRM or spreadsheet instead of guessing.
Four-step setup
Install the attribution snippet on the site, directly or through a tag manager such as Google Tag Manager. Then add six hidden fields to the WS Form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. Hidden fields are present in the form but not visible to visitors, allowing the snippet to write values into them. When a visitor submits the form, WS Form captures those values alongside the name, email, phone and other details the lead entered.
How persistence and categorisation work
The snippet examines how the visitor arrived, including UTM parameters in the URL, categorises the visit into channels such as Paid Search, Organic Search or Paid Social, and stores the result in a browser cookie. That persistence matters when someone lands on a homepage, navigates to a contact page, or returns later: the origin data is still available when the form is completed, rather than being lost because the form page differs from the landing page. At submission, the stored values populate the hidden fields.
Why channel grouping beats raw values alone
Capturing only raw UTM values covers only visits tagged in the URL and can produce inconsistent labels — for example, google, google.com and adwords for the same advertiser. Grouping normalises those variants under one channel. It also covers untagged origins such as Organic Search, Organic Social, Referral and Direct Traffic, giving a fuller picture of lead sources. Landing page fields add a second dimension: the exact page and its group, such as a blog section or an individual post.
Using the captured data and a pre-launch checklist
After submission you can review values in the WordPress Submissions section, include them in WS Form notification emails, send them to CRM tools, or sync them to Google Sheets or Microsoft Excel. Use this checklist before relying on reports: confirm every form has all six hidden fields, test a tagged visit that navigates to a different form page, check that channel drilldowns match the campaign naming, and verify the values appear in the destination system. Useful reports include leads by channel, leads by social network, customers by campaign, and revenue by keyword when keyword data is included in campaign parameters.
| Hidden field | What it records | Example from captured evidence |
|---|---|---|
| Channel | Broad source category | Paid Search |
| Channel Drilldown 1 | First level of source detail | |
| Channel Drilldown 2 | Second level of source detail | Brand Campaign |
| Channel Drilldown 3 | Third level of source detail | Olmo |
| Landing Page | Page where the visit began | www.olmo.com/features/music-licencing |
| Landing Page Group | Content section of the landing page | Features |
Example values are illustrative captured evidence for a paid search visit, not guaranteed output for every visit.
Frequently asked questions
What are the four setup steps?
Add the attribution snippet to the site, create the six hidden fields in WS Form, let the snippet populate them from the visit, then review or forward the submitted values through WS Form's submissions, notifications, or integrations.
Why group raw UTM values into channels?
Raw URL values can vary in spelling and format, creating separate entries for the same source. Channel grouping normalises those variants so reporting uses a consistent category.
How is data retained across pages?
Storing the visit data in a browser cookie allows it to persist while the person moves between pages or returns later, instead of depending on the form being on the landing page.
What do the landing page fields add?
Landing page and landing page group fields show which page and content section produced the lead, enabling page-level and section-level reporting.