Skip to content

Capture UTM Parameters in Fillout Forms and Send Them to Your CRM

Website analytics can show how many visitors a campaign sent, but for a non-ecommerce business that does not reveal how many leads or customers followed. Attaching campaign attribution to each form submission closes that gap: the CRM record itself carries the channel, drilldown and landing page, so reporting can start from outcomes rather than clicks.

1. Tag the campaigns you want to measure

Tag every paid link first. That covers social placements such as Facebook, LinkedIn, Instagram and Twitter, search placements such as Google and Bing, and bespoke placements such as trade-publication ads and email campaigns. Without parameters on the originating link, there is nothing for the form to inherit.

2. Add six hidden fields

Add six hidden fields to the form, using these exact field names so downstream mapping stays consistent: Channel; Channel Drilldown 1; Channel Drilldown 2; Channel Drilldown 3; Landing Page; Landing Page Group. Hidden fields keep the visitor-facing form clean while giving the submission record structured attribution columns.

3. Let the snippet store and fill attribution

A small snippet on the website inspects the technical signals available on arrival, categorises the visit into a channel such as Paid Search or Paid Social, and stores the result in a browser cookie. When a form is later completed, those stored values are written into the hidden fields. Because the cookie persists across browsing, the attribution survives moving from a homepage to a deeper page such as a quote-request page, unlike a method that only reads parameters from the submission URL.

Worked example

Worked example: a visitor clicks a Google ad for a fictional software company and submits a form. The hidden fields could be filled as Channel = Paid Search; Channel Drilldown 1 = Google; Channel Drilldown 2 = Brand Campaign; Channel Drilldown 3 = the company name; Landing Page = the features page URL; Landing Page Group = Features. That single submission now distinguishes the search network, the campaign, the brand term and the entry page without the visitor typing any of it.

4. Use the captured data

On submission, the captured values sit alongside the details the lead entered manually, such as name, email and company. From there they can be reviewed in the submissions table, included in lead notification emails, sent to CRM tools including Salesforce, HubSpot, Pipedrive and Zoho CRM, or synced to Google Sheets or Microsoft Excel for reporting.

Why this approach differs from reading the URL

Four distinctions matter. First, coverage: organic and referral visits without UTMs are categorised too, so the picture is not paid-only. Second, persistence: cookie storage carries attribution across pages. Third, cleanliness: raw URL values can fragment reporting when the same platform is tagged as adwords, google or google-ads, or when capitalisation varies; categorisation normalises those variants into one channel. Fourth, landing context: recording the landing page and its group lets you report by site section, for example blog overall and then individual posts.

Reports worth building first

With channel and drilldown fields in the CRM or spreadsheet, useful reports include: leads by channel per month, to see at a high level where volume originates and where budget or effort should shift; leads by social network, to compare performance across the Meta-owned networks and adjust targeting and cost per lead; and customers by search campaign per month, to identify which campaigns produce buyers rather than only enquiries and decide what to keep funding or pause.

Pre-launch checklist

Before launch, check: every paid and email link carries UTMs; all six hidden fields use the exact names listed above; a test visit with UTMs followed by a submission on a different page still fills the fields; a test visit without UTMs still produces a channel; variant spellings of the same source roll into one channel; and the values appear correctly in the submissions table, notification email, CRM record and spreadsheet. Pricing, trial length and setup time are not stated here; confirm the current plan terms and onboarding steps directly with the provider before committing budget or rollout dates.

Hidden-field map
FieldWhat it recordsReport it enables
ChannelBroad origin such as Paid Search, Paid Social, Organic Search or ReferralLeads by channel
Channel Drilldown 1Platform, for example GoogleLeads by network or platform
Channel Drilldown 2Campaign grouping, for example Brand CampaignCampaign comparison
Channel Drilldown 3Brand or specific term detailBrand-term performance
Landing PageExact page where the visitor first arrivedLeads by individual page or post
Landing Page GroupSection of the site, for example Features or BlogLeads by site section

Field names are the exact hidden-field names required for consistent mapping.

Frequently asked questions

What is the shortest setup sequence?

Add UTM parameters to every paid and bespoke campaign link, add the six hidden fields to the form, install the tracking snippet on the site so it stores attribution in a browser cookie on landing, and let it populate those fields at submission. The values then travel with the lead's name, email and company into the submissions table, notification emails, CRM or spreadsheet.

Does the visitor need to submit on the landing page?

No. A cookie-based approach retains the values across pages, so a visitor who lands on the homepage and later submits on a quote-request page still has the original campaign data attached. Reading parameters only from the submission-page URL would lose them in that journey.

Are non-UTM visits captured too?

Yes. Organic Search, Organic Social, Referral and Direct visits without UTMs are also categorised into channels, so reports are not limited to paid traffic.