How to capture UTM parameters in WPForms and send them to your CRM
If your WPForms submissions arrive with only a name and email, you can see that a lead exists but not which campaign produced it. This guide shows a repeatable way to attach campaign source, click identifiers, and landing page context to every submission, then carry that data into your CRM and notification emails. The capture mechanism described here is a tracking snippet that reads the visitor's source and writes it into hidden fields on your forms.
What you are actually capturing
Raw UTM parameters describe the link a visitor clicked. That is useful, but it is only part of the picture. A complete setup also records visitors who arrive without UTMs, such as organic search or direct visits, and it keeps the original source even when the visitor browses several pages before submitting a form. The snippet writes six values into hidden fields: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. Those values travel with the lead into WPForms entries, notification emails, and connected CRM records.
A four-step setup
- Install the tracking snippet on your WordPress site. The snippet can go in through the theme settings, a headers-and-footers plugin, or Google Tag Manager if you already use it.
- Add the six hidden fields to each lead-capture form. In the WPForms builder, drag a Hidden Field into the form and configure its label and default value.
- Let the snippet populate those fields. When a visitor lands on the site, the snippet reads the URL and stores the source information in the browser. When the visitor submits a form, the snippet writes the stored values into the hidden fields.
- Confirm the values arrive with the submission. WPForms captures the hidden field values alongside the lead's name, email, phone number, and any other entered details.
Field map: what each hidden field holds
Use this map to check that each field is configured and populated as expected.
Worked example: a roofing campaign
Suppose a homeowner searches for emergency roof repair, clicks a Google Ads result, and submits a contact form. The snippet would write values such as Channel = Paid Search, Channel Drilldown 1 = Google, Channel Drilldown 2 = the campaign name, and Channel Drilldown 3 = the ad or search term. The landing page field would hold the first page the visitor saw, and the landing page group would hold its subdirectory, for example /services. This example illustrates the shape of the data; your own campaign names and URLs will differ.
Where the data can go after submission
Once the values are captured, you have several destinations: the WPForms entries view for each submission, the new-lead notification emails, native CRM integrations such as Salesforce, HubSpot, and Pipedrive, or a Zapier workflow that pushes the data into a spreadsheet or email platform. Choose the destination that matches how your team reviews and acts on leads.
When full attribution is worth the extra setup
A raw UTM capture answers one narrow question: which tagged link did this visitor click? That is enough if every lead arrives from a tagged paid campaign and submits on the landing page. It breaks down in three common situations. If a meaningful share of leads comes from organic search, social, referral, or direct visits, those leads will have no UTM values and will look unattributed. If visitors routinely browse before converting, a form on a later page will lose the original campaign unless the source is stored in the browser. And if you want to send conversions back to an ad platform, you need the click identifier (GCLID, MSCLKID, or FBCLID) attached to the lead, not just the UTM string. The fuller setup addresses all three: it classifies non-UTM traffic, persists the original source across pages and return visits, and captures click IDs alongside landing page and landing page group. The trade-off is one snippet and six hidden fields per form. If your leads are almost entirely tagged paid traffic submitting on the landing page, a simpler raw capture may be sufficient; if you need to compare channels or optimize toward paying customers, the fuller setup earns its keep.
Reports worth building, in priority order
Start with the report that answers your most expensive open question. If you are unsure where to spend next, build a channel breakdown first: it shows the mix of paid, organic, referral, and direct leads and exposes channels that are over- or under-invested. If you run Meta ads across several placements, a network breakdown is the next step, because it lets you shift budget between Facebook, Instagram, Messenger, and other placements based on lead volume rather than impressions. Once you have enough closed deals, move to a campaign-to-customer view: it replaces click and form-fill counts with paying customers, which is the number that should drive budget decisions. Finally, if you include the keyword in your Google Ads UTM parameters, a revenue-by-keyword report shows which search terms produce revenue; use it to set bids and to prioritize SEO topics. Build them in that order so each report rests on data you have already validated.
A failure checklist
If the hidden fields are empty or wrong, check these in order. First, confirm the tracking snippet is present on every page, not only the landing page. Second, confirm all six hidden fields exist on the specific form and that their labels match the expected names. Third, test a URL that includes UTM parameters and submit the form on a different page to verify the source is remembered. Fourth, check whether the visitor arrived through a channel without UTMs; in that case the snippet should still populate the values from other signals rather than leave them blank. Fifth, verify the CRM mapping so the hidden field values are not dropped during the integration.
What to expect from setup
The setup is intentionally small: one tracking snippet and six hidden fields per form. Once in place, the snippet writes the values automatically at submission time, so your team does not need to ask visitors how they found you. The main ongoing task is keeping campaign names and UTM conventions consistent so the reports remain readable. Trial terms and any setup-time estimates are set by the tool owner and should be confirmed on the signup page before you rely on them.
| Field | What it holds | Example value |
|---|---|---|
| Channel | Broad source category | Paid Search |
| Channel Drilldown 1 | Platform or network | |
| Channel Drilldown 2 | Campaign name | Emergency Repair Campaign |
| Channel Drilldown 3 | Ad or search term | Storm Damage Atlanta |
| Landing Page | First page the visitor saw | www.example.com/services/emergency-repair |
| Landing Page Group | Subdirectory of the landing page | /services |
Example values are illustrative; your own campaign names and URLs will differ.
Frequently asked questions
Do I need UTM parameters on every link for this to work?
No. UTM parameters help identify paid campaigns, but the snippet also records visitors from organic search, organic social, direct, referral, and other channels where UTMs are absent.
What happens if a visitor lands on one page and submits a form on another?
The snippet stores the source information in the visitor's browser when they first arrive, so the original campaign data is still written into the hidden fields when they submit a form on a later page, even if they leave and return.
Which click identifiers are captured?
The snippet captures the Google Click ID (GCLID), the Microsoft Click ID (MSCLKID), and the Facebook Click ID (FBCLID) alongside UTM parameters.
Where can the captured values be sent?
They appear in the WPForms entries view, can be included in new-lead notification emails, and can be passed to Salesforce, HubSpot, Pipedrive, or other tools through native integrations or Zapier.