How to capture UTM parameters in Leadpages
If you can't tell which campaign produced a lead, you can't tell which campaign deserves more budget. Leadpages collects the form submission; the missing piece is the marketing context around it — the campaign tags in the URL and the page the visitor first landed on. This guide walks through tagging your campaigns, adding hidden fields to your Leadpages forms, letting an attribution tool fill those fields automatically, and pushing the result into your CRM so reports can answer channel-level questions.
Why lead source belongs in the CRM, not just in analytics
Growth comes from finding the channels, content and campaigns that produce leads and customers at a positive return, then investing more there. That decision needs lead-level data, not just session counts. If you can't measure how many leads, customers and revenue each activity produced, you're guessing about what works.
Recording the source of every lead and opportunity inside your CRM closes that gap. Once source data sits next to the deal record, you can build reports showing which campaigns, content and channels perform — and compare them on outcomes rather than clicks.
The four-step setup at a glance
The workflow has four stages, and each one depends on the previous:
- Add UTM parameters to the ads and campaigns that send traffic to your Leadpages pages.
- Add six hidden fields to each lead capture form.
- Let the attribution tool read incoming tracking data and write it into those hidden fields.
- Submit the form and confirm the values arrive in your CRM or spreadsheet.
Skipping step 1 leaves the tool with nothing to read. Skipping step 2 leaves the data with nowhere to land. Most broken setups fail at one of those two points.
Step 1: Tag your ads and campaigns
UTM parameters have to exist on the incoming URL before anything downstream can record them. Add them to every paid placement — social platforms such as Facebook, LinkedIn, Instagram and Twitter, and search ads on Google and Bing — and also to less obvious traffic sources such as trade-publication placements and email campaigns.
A useful habit: treat the tag as part of the campaign build, not an afterthought. If a placement goes live untagged, the visit is effectively anonymous by the time it reaches your form.
Step 3: Let the tool fill the fields automatically
Once tagging and form fields are in place, the attribution script reads incoming tracking data — UTM parameters included — and writes it into the hidden fields when a visitor submits.
A concrete illustration helps here. Imagine a visitor searches for a way to share large files, clicks a sponsored result, and requests a demo. Depending on the tags used, the six fields could end up holding:
- Channel = Paid Search
- Channel Drilldown 1 = Google
- Channel Drilldown 2 = Files Campaign
- Channel Drilldown 3 = Large Files Ad
- Landing Page = www.dropbox.com/features/share
- Landing Page Group = Features
Read that list as a hierarchy: broad channel first, then progressively finer detail, with the landing page recorded separately. If your own test submission produces blanks or mismatched values, the problem is almost always in the tags or the field names, not in the reporting layer.
Step 4: Get the values into your CRM
When the form is submitted, the hidden-field values are saved together with the lead's name, email, phone number and any other answers the visitor provided. From that point the record can be forwarded using whichever Leadpages integrations your account includes — check the current integration directory for the CRMs and destinations available to you — or sent to Google Sheets, Excel and similar tools through an automation service such as Zapier. Before relying on any route, submit a test lead and confirm the attribution values actually appear on the receiving record; a connection that accepts the contact but drops the hidden fields is worse than no connection at all, because it looks like it works. Once the data is arriving intact, CRM reports can answer questions such as how many leads a Facebook campaign produced, how many customers came from Google Ads, or how much revenue is attributable to SEO work — along with many variations on those.
What the attribution layer actually does
The mechanism is simpler than the output suggests. Attribution Analytics is a small piece of code placed on the Leadpages site that inspects technical signals about each visitor — UTM parameters, the referrer, device information and similar — to work out how they arrived.
That arrival path is sorted into a channel such as Paid Search, Organic Search or Paid Social, and the result is stored in a cookie in the visitor's browser. When the visitor later completes a form containing the six hidden fields, the stored values are written in. On submission, the attribution data travels with the lead's name, email and phone number into the CRM and any other connected systems.
Why not just pass raw UTM strings through?
Plenty of tools can capture UTM parameters, so the choice comes down to what the captured data can support. Four differences matter in practice.
It covers traffic that has no UTM parameters
UTM tags only exist on links you control. Organic search, organic social, direct visits and referrals arrive without them, so a raw-UTM-only setup leaves those leads unattributed.
A channel-classification approach records the source of all website traffic, including the unpaid channels where tags aren't available. That means CRM reports can account for every lead rather than only the paid ones — a fuller picture of what is and isn't working.
It survives navigation between pages
Most raw-UTM methods require the parameter to be present on the page where the form is completed. That assumption breaks constantly: a visitor clicks an ad, lands on a campaign-specific page, then clicks a 'Get A Quote' button and fills in the form on a different URL. The tags were on the first page, the form is on the second, and the data is gone.
A cookie-based approach stores the attribution data at arrival, so the form's location no longer matters. Whatever page the visitor completes the form on, the original source can still be written into the hidden fields.
It normalises inconsistent tagging
Raw UTM values are only as tidy as the people who wrote them. One Twitter campaign might be tagged UTM Source=Twitter.com, another twitter, another tw. Send those strings straight into your CRM and a single channel fragments into three separate sources that someone has to merge by hand before the report makes sense.
A layer that accounts for capitalisation and similar discrepancies assigns each lead to the correct channel regardless of how the tag was typed, so reports don't require manual clean-up first.
It records the landing page too
Campaign tags say how someone arrived; they don't say which page received them. Capturing the landing page (for example, a specific blog post URL) and the landing page group (for example, /blog) lets you judge content performance in terms of leads, customers and revenue — not just visits.
Because both levels are recorded, you can review a content section as a whole and drill into individual pages or posts within it. That is how you find out whether the long article you spent hours on actually produces pipeline.
Pre-launch checklist
Run through this before you trust the first report:
- Every live campaign URL carries UTM tags, including email and offline placements.
- All six hidden fields exist on every lead capture form, spelled exactly as expected.
- The 'This is a hidden field' box is ticked on each one.
- A test submission from a tagged link shows values in all six fields, not blanks.
- The test record appears in the CRM or spreadsheet with the attribution values attached.
- A second test that navigates to a different page before submitting still carries the original source.
- A test from an untagged organic or direct visit is classified into a channel rather than left empty.
Diagnosing a blank or wrong value
Three failures look similar in a CRM report but have different causes:
- Nothing was ever tagged. The lead arrives with empty attribution because the ad URL had no UTM parameters. Fix the campaign build, not the form.
- Tagged but lost. The visitor landed on a tagged page and submitted on a different one, and the setup reads parameters only from the current page. A cookie-based capture resolves this.
- Tagged but messy. Values arrive, but the same channel appears under several spellings, so totals split. Normalisation at capture time resolves this.
Identify which of the three you're looking at before changing anything — the fix lives in a different place each time.
What good looks like afterwards
Set up carefully, this approach does more than record UTM strings. It keeps source data available as visitors move between pages, standardises the values so reports can be assembled without manual merging, and attaches the result to the lead record where revenue decisions are actually made. The practical test is simple: pick a handful of known campaigns, submit test leads through each path, and check that the CRM shows the channel, drilldowns and landing page you expect. If those match, the reporting layer can be trusted for budget decisions; if not, the gap will point to tagging, field naming or page navigation rather than to the reports themselves. Whether a trial or evaluation period is offered, and on what terms, depends on the provider's current published plan details, so confirm those directly before committing your stack to the workflow.
| Hidden field | What it holds | Report question it answers |
|---|---|---|
| Channel | Broad traffic category, e.g. Paid Search, Organic Search, Paid Social | Which channel types produce leads and customers? |
| Channel Drilldown 1 | First level of detail within the channel, e.g. Google | Which platform within the channel performs? |
| Channel Drilldown 2 | Second level, e.g. a named campaign | Which campaign drives results? |
| Channel Drilldown 3 | Third level, e.g. a specific ad | Which creative or ad unit converts? |
| Landing Page | The URL the visitor first arrived on | Which individual page generates leads? |
| Landing Page Group | The section that page belongs to, e.g. /blog | How does a content section perform overall? |
Values shown in the example rows reflect the illustrative walkthrough in the original guide; your actual values depend on the UTM parameters you apply to each campaign.
Frequently asked questions
Do I need UTM parameters on every campaign for this to work?
You need them wherever you want campaign-level detail. Channels without UTM parameters — organic search, organic social, direct and referral traffic — can still be classified into a channel, but the finer drilldown levels depend on the tags you supply.
Why do my UTM values disappear when the form is on a different page?
Because many capture methods read parameters only from the page the form sits on. If the visitor lands on a tagged page and then navigates to a separate quote or contact page, the parameters are no longer in the URL. Storing the data in a cookie at arrival keeps it available for the later submission.
How many hidden fields do I need in Leadpages?
Six: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Each is a text field with the 'This is a hidden field' option enabled in the Properties editor.
Can the data go somewhere other than a CRM?
Yes. Submissions can be sent to a CRM through the integrations your Leadpages plan supports — review the current integration directory to see which CRMs are covered — and automation tools such as Zapier can route the same data to Google Sheets, Excel and many other destinations. Whichever route you choose, verify with a test submission that the hidden-field values arrive alongside the contact details, since some connections pass the lead through but not the attribution fields.
Why does the same channel show up several times in my reports?
Inconsistent tagging — for example Twitter.com, twitter and tw as three different source values. Normalising at capture time assigns all of them to one channel so totals don't fragment.