Skip to content

Capture UTM Parameters in Getform and Send Them to Your CRM

Knowing which campaigns produce leads and revenue helps direct time and budget toward what works. That requires attribution data attached to each contact, so reports can be grouped by traffic source rather than guessed after the fact.

1. Tag every campaign link

Tagging comes first. Every campaign link should carry UTM parameters, covering paid search and social placements, guest contributions, trade-publication advertising and email marketing. Consistent tagging gives the attribution layer something accurate to pass onward. Once that data reaches the CRM on the contact record, contacts can be filtered and campaigns compared on leads and return.

2. Add hidden fields to the form

Getform sits behind a standard HTML form, so hidden inputs can be added directly in markup using the hidden input type. Visitors do not see these fields. On submission, however, they are sent alongside the visible answers and can be stored against the contact.

Hidden-field checklist

Create six hidden fields: Channel; Channel Drilldown 1; Channel Drilldown 2; Channel Drilldown 3; Landing Page; Landing Page Group. Check that each field name matches the expected CRM or downstream destination exactly before going live, and submit a test form to confirm values arrive rather than empty fields.

3. Let attribution populate the fields automatically

A small attribution script placed on the website collects UTM parameters, referrer information and device details, then classifies the visit into channels such as Paid Search, Organic Search or Paid Social. It stores that classification in a browser cookie. When a Getform-connected form is completed, the stored values populate the hidden fields in the background, leaving the visible form unchanged.

Worked example

Consider a visitor who searches for a file-transfer problem, clicks a paid result, lands on a feature page and requests a demo. The hidden fields could record Paid Search as the channel, the search platform as the first drilldown, the brand campaign as the second, and the advertiser name as the third. The first landing page and its group are captured too, for example a cloud-storage feature page grouped under Features. The exact labels depend on the tagging and classification rules in use.

4. Send the captured record downstream

On submission, Getform captures the visible answers together with the populated hidden fields. Native integrations can forward that record to tools such as Mailchimp, Salesforce or Intercom, while a connector such as Zapier can route it to spreadsheets and other systems. Map each hidden field to a dedicated CRM field so reporting does not overwrite contact details.

Why classify and persist instead of capturing raw UTMs only

Raw UTM capture has three common weaknesses. First, it misses traffic that arrives without UTM links, including Organic Search, Organic Social, Referral and Direct visits. Second, it fails when the conversion page differs from the landing page, because the parameters are no longer in the address. Third, inconsistent tagging creates messy reports, for example Facebook, facebook and fb appearing as separate sources. A cookie-based attribution layer addresses all three: it classifies non-UTM traffic, persists across pages and sessions, and normalises variant spellings into one channel.

Add landing-page reporting

Landing-page capture adds a content dimension. Knowing which blog or in-depth page first brought a lead in helps judge whether content investment is producing enquiries, separately from paid campaign performance. Use the landing page group for roll-up reporting and the individual page for detail.

Pre-launch checklist

Before launch, run this check: confirm every campaign link is tagged; confirm all six hidden fields exist in the form markup; confirm the attribution script is present on landing pages; submit a test conversion from a tagged link and from a non-UTM visit; verify channel, drilldowns, landing page and group in the CRM; and confirm downstream routing to email, CRM or spreadsheet tools. Re-test after any tagging or form change.

Frequently asked questions

Which links need UTM tagging before a Getform submission?

Tag every campaign link, including guest posts, paid placements on Facebook, Twitter and Google, trade publications and email sends. Without tags at entry, later form fields have nothing reliable to record.

What hidden fields should a Getform form contain?

Add six hidden inputs to the HTML form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. They stay invisible to visitors but travel with the submission.

Why can UTM data disappear between landing and conversion?

Raw capture only works when the parameters are still in the address on the form page. Storing the attribution in a browser cookie preserves the original visit even if the person browses several pages before converting.

Why normalise UTM values instead of reporting them raw?

Inconsistent values such as Facebook, facebook and fb can split one channel into several reports. Normalising them into a single channel such as Paid Social makes reporting cleaner.

What landing-page data is useful alongside channel data?

Record the first landing page and its group alongside channel data. That shows whether a blog post or other content piece, not only a campaign, generated the lead.