Skip to content

Capture UTM Parameters in Fluent Forms and Keep Them Through the Visit

UTM parameters only explain a lead when they are still present at the moment the form is submitted. A practical setup therefore needs three parts: a site-level code that records the visit, hidden fields on the form to receive the values, and a submission flow that carries those fields into Fluent Forms, email notifications, a CRM or a spreadsheet.

1. Put the attribution code on the site

Install the attribution code on the site first. On WordPress it can be placed through theme settings, a header-insertion plugin, or Google Tag Manager where that is already in use. This code is what analyses technical signals, groups the visitor into a channel such as Paid Search, Paid Social or Organic Search, and stores the result in the browser.

2. Add the six hidden fields

Hidden fields are present in the form but not visible to visitors. In the Fluent Forms builder, drag the Hidden Field type from the Advanced tab into the form and name each field exactly as the attribution code expects. Use this checklist before testing: Channel; Channel Drilldown 1; Channel Drilldown 2; Channel Drilldown 3; Landing Page; Landing Page Group. Missing or renamed fields are the most common reason values do not appear in a submission.

Worked example: what a completed submission should look like

Consider a visitor who clicks a branded Google ad, lands on a campaign page, then moves to a contact page to request a demo. The expected pattern is: Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = Brand Campaign, Channel Drilldown 3 = the advertiser name, Landing Page = the campaign URL, and Landing Page Group = the section that URL belongs to. Those values are illustrative of the field mapping, not a promise about any particular campaign's UTM values.

3. Verify capture and forwarding

When the form is submitted, the hidden-field values are stored with the visitor's entered details and can be viewed in Fluent Forms submissions, included in notifications, and passed on through built-in integrations to systems such as Salesforce, HubSpot, Pipedrive and Microsoft Dynamics, or via Zapier to other destinations including Excel and Google Sheets. Check the destination field mapping after the first test submission rather than assuming every hidden field is forwarded automatically.

Why persist the data instead of reading the URL at submission

UTM-only capture leaves organic traffic unexplained. Channel assignment also covers Organic Search, Organic Social, Direct and Referral, giving a fuller channel picture for budget decisions. Browser storage also solves the multi-page problem: a visitor who arrives from an ad on the homepage and submits on a separate contact page does not lose the original campaign data. Landing page and landing page group add a second dimension, so performance can be compared by site section and by individual page.

Add click IDs for offline conversions

Alongside UTM values, click IDs can be captured: GCLID for Google, MSCLKID for Microsoft and FBCLID for Facebook. Forward those IDs with the lead, and when the lead becomes a customer, return the ID to the ad platform as an offline conversion. That shifts optimisation from page views to paying customers.

Four reports to build from the captured data

Once channel, drilldown, landing page and click ID data reach a CRM or spreadsheet, four reports become straightforward: leads by channel month by month; leads by Meta network such as Facebook, Instagram or Messenger; customers by Google Ads campaign; and revenue by keyword where keyword is included in the Google Ads tracking template. Each report answers a different decision: where to shift budget, which network to favour, which campaign to scale, and which search terms to bid up or down.

Pre-launch checklist

Test with a paid campaign link, an organic arrival, and a multi-page journey before relying on the data. Confirm all six hidden fields populate, the values survive navigation, and the CRM or spreadsheet receives them under the correct field names. For a worked evaluation, imagine a professional-services firm running search and display ads: after a month of test submissions, compare which campaigns produced qualified enquiries versus traffic alone, then decide whether to shift budget toward the campaigns that convert. Treat any such scenario as a planning exercise until your own submission data confirms it.

Hidden-field map
FieldWhat it tells youUse it to decide
ChannelBroad source such as Paid Search or Organic SearchWhich channel deserves more budget
Channel Drilldown 1-3Platform, campaign and advertiser detail from UTM valuesWhich campaign to scale or pause
Landing PageFirst page the visitor arrived onWhich page or post generates leads
Landing Page GroupSection containing that page, such as a blogWhether a whole site section performs

Field names are the exact hidden-field names required by the setup described.

Frequently asked questions

How do UTM values get into a Fluent Forms submission?

Add the site code, then add six hidden fields to the form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. The attribution code stores the data in the browser and writes it into those fields at submission, so it is captured alongside name, email, company and other entered details.

What if a visitor lands on one page and submits on another?

Yes. Because the data is stored in the browser rather than read only from the landing URL, it can survive navigation to another page where the form is completed, and can also cover organic arrivals that have no UTM parameters.

Can click IDs be captured as well as UTM parameters?

Click identifiers such as GCLID, MSCLKID and FBCLID can be captured with the submission and forwarded to a CRM or other tool, so a later customer milestone can be sent back to the ad platform as an offline conversion instead of relying only on a thank-you page visit.