Skip to content

Capture UTM Parameters in Wufoo and Send Them to Your CRM

You can judge marketing by leads and sales, but only if each lead carries reliable information about where it came from. A Wufoo form can carry that information alongside the visitor's name, email and company details, provided the form has the right hidden fields and the visit has been categorised before submission. This guide explains the four steps involved, the six fields to create, and how the resulting data differs from raw UTM values.

1. Tag campaigns consistently

Start by tagging every campaign you run. Use UTM links consistently across paid ads, email marketing, guest posts and trade publication placements. Consistent tagging gives the capture tool something to read on arrival and lets you filter contacts or build reports by campaign later. The key point is coverage: a campaign without tags will not produce campaign-level UTM data, even if other traffic is still categorised.

2. Add six hidden fields to the Wufoo form

Next, prepare the form itself. In Wufoo, add a Single Line Text field for each item below, then enter hide in the Add CSS Layout Keywords setting so the field is not visible to visitors. Create six hidden fields in total:

  • Channel
  • Channel Drilldown 1
  • Channel Drilldown 2
  • Channel Drilldown 3
  • Landing Page
  • Landing Page Group

These fields are the destination for attribution data. Without them, there is nowhere for the tool to write the categorised visit information when a form is submitted. The form-controls-contract module governs the exact field behaviour for implementation.

3. Let the tool populate the fields automatically

Once the fields exist, the tool fills them automatically from the visitor's arrival data. It collects UTM parameters, referrer information and device details, groups the visit into a channel such as Paid Search or Organic Search, and stores that categorisation in the browser. When the visitor submits a Wufoo form, the stored values are written into the hidden fields and submitted with the form. A worked example makes the mapping clear. A visitor clicks a paid search ad, lands on a feature page and requests a demo. The hidden fields might then contain: Channel = Paid Search; Channel Drilldown 1 = Google; Channel Drilldown 2 = Brand Campaign; Channel Drilldown 3 = Dropbox; Landing Page = www.dropbox.com/features/share; Landing Page Group = Features. The exact values depend on the tags used in the original campaign, but the structure stays the same: four fields describe the channel hierarchy and two describe where the visitor landed.

4. Send the submission onward with Wufoo integrations

On submission, Wufoo captures the visible answers together with the hidden attribution values. You can then use Wufoo's native integrations to forward both sets of data to a CRM such as Salesforce, HubSpot or Pipedrive, or to other connected tools. That means a single submission delivers contact details and the campaign context needed to report on which channels and content are working. Before going live, run a short check: submit a test form from a tagged link, confirm all six hidden fields arrive in the receiving system, then submit from an untagged visit and confirm a channel is still recorded. This catches missing fields or broken integrations before real leads are affected.

Why categorised data beats raw UTM values

Passing raw UTM values through is simpler, but it has three practical weaknesses that this approach addresses. First, coverage. Raw UTM capture only records visitors who arrived through tagged links. The tool described records all traffic sources, including organic search, organic social, direct and referral visits, so leads from untagged channels are not left blank. Second, consistency. The same source can be tagged in different ways — for example with different capitalisation, with or without a domain, or with an abbreviation. A CRM or spreadsheet treats those as separate sources, which distorts reporting. Normalising them into a single channel, such as Paid Social, keeps reports accurate. Third, content context. UTM data alone does not show which page a visitor landed on. Recording the landing page and its subdirectory or group reveals which content areas, such as a blog, generate leads and sales. In short, the value is not just capturing parameters. It is capturing every visit, cleaning inconsistent values into standard channels, and attaching landing page detail so CRM reports reflect reality.

Frequently asked questions

Does this only work when a visitor arrives through a UTM link?

No. The tool described also records visits without UTM tags, including organic search, organic social, direct and referral traffic, and categorises them into channels before submission.

Why not just pass raw UTM values through?

Raw values can vary in capitalisation and format for the same source, creating separate entries in a CRM or spreadsheet. The tool normalises those variants into a consistent channel, such as Paid Social, so reporting groups them together.

Is landing page information included?

Yes. In addition to channel data, it records the landing page and its subdirectory or group, so you can see which content areas produce leads and sales.