Capture UTM Parameters in Duda Forms: A Practical Setup Guide
Knowing which campaigns create leads, customers and revenue is difficult when form submissions arrive without source context. This guide explains how to add UTM tagging to campaigns, add hidden fields to Duda forms, and use the resulting data in reports.
Why source data matters
Growth decisions depend on evidence about which channels, content and campaigns produce leads and customers with a positive return. Without source data attached to each submission, reporting in a CRM cannot reliably separate effective activity from activity that merely looks busy.
The workflow in this guide connects three parts: tagged campaign links, hidden fields inside the form, and a small website script that classifies each visitor and fills those fields when the form is submitted. Once that chain is in place, each lead carries its channel and landing context into Duda, a CRM, a spreadsheet or notification email.
Step 1: Tag campaigns consistently
Tag every running advertisement and campaign before relying on form attribution. Apply UTM parameters consistently across social platforms such as Facebook, LinkedIn, Instagram and Twitter, search platforms such as Google and Bing, and custom activity including trade-publication advertising and email campaigns.
Consistency matters as much as coverage. Decide naming rules for source, medium, campaign and keyword values before launch, and apply the same spelling and capitalisation everywhere. Inconsistent tags create fragmented reporting later, even if the form capture itself works.
Step 2: Add hidden fields to Duda forms
Add these hidden fields to each lead-capture form:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Landing Page
- Landing Page Group
These fields do not need to be visible to visitors. Their purpose is to receive classified attribution values at submission time, alongside the details a visitor enters, such as name, email and phone number. Use the form builder's hidden-field option for each field name exactly as listed, then test a submission and inspect the stored entry before relying on the setup.
Step 3: Let the script populate the fields
A small script placed on the website reads UTM parameters, referrer information, device details and other technical signals to classify a visitor. Common classifications include Paid Search, Organic Search and Paid Social. The classification is stored in a browser cookie, then written into the hidden fields when a form is completed.
Worked example: a visitor searches for ways to share large files, clicks a paid search advertisement, lands on a features page and requests a demo. The hidden fields could be populated as follows:
- 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
That example shows the distinction between the channel hierarchy, which explains where the visitor came from, and the landing page fields, which explain which page first received the visit.
Step 4: Capture and use the submission data
After a visitor submits name, email, phone number or other requested details, Duda captures the completed hidden fields with the entry. Review entries in the Entries section, include the attribution fields in lead notification emails, send entries to a CRM or other sales and marketing tool, or sync them to Google Sheets or Microsoft Excel for spreadsheet analysis.
Before scaling the setup, run a checklist:
- Confirm every active campaign uses UTM parameters.
- Confirm all six hidden fields exist on every lead form.
- Submit test entries from paid, organic and direct visits.
- Check that channel values are classified, not left blank or raw.
- Check that landing page and landing page group match the entry page.
- Confirm entries appear in Duda, notification email, CRM or spreadsheet as intended.
- Confirm the data survives navigation from the landing page to a different form page.
Why classified attribution differs from raw UTM capture
Raw UTM capture has four practical limits that a classified, cookie-based approach addresses.
First, it covers all traffic, not only tagged campaigns. Organic Social, Organic Search, Direct, Referral and other arrivals can also be classified, giving a fuller picture for budget decisions. For example, if Organic Search produces more leads than Paid Search, that evidence may support shifting effort toward search engine optimisation.
Second, it remembers the visit across pages. If a visitor lands on a campaign page, then moves to a separate quote form, raw parameters on the first URL can be lost. Storing classification in a cookie allows the form page to receive the original attribution even when it differs from the landing page.
Third, it produces cleaner data. Variations such as different capitalisation or shortened source names can split one source into several CRM values. Classification normalises those variants into a single channel, such as Paid Social.
Fourth, it captures landing context. Recording both the exact landing page and its group makes it possible to compare individual pages with broader sections, such as a blog as a whole versus individual posts.
Four reports to build from captured data
Once entries reach a CRM or spreadsheet, four report types are especially useful.
Leads by channel shows monthly lead volume by channel, making it easier to prioritise the channels already producing results and to question budget concentrated in weaker channels.
Leads by Facebook Ads network separates networks such as Facebook, Instagram and Messenger, helping targeting and spend decisions focus on networks with stronger lead performance.
Customers by Google Ads campaign moves beyond lead counts to identify campaigns producing paying customers, which is a stronger basis for allocating advertising budget.
Revenue by keyword uses keyword values included in Google Ads UTM parameters to connect search terms with revenue, supporting bidding, search optimisation and messaging decisions.
Summary
Start with campaign tagging, add the six hidden fields, verify the script populates them, and test submissions from several traffic types. When those checks pass, channel, landing page and drilldown data can support clearer reporting on leads, customers and revenue.
Frequently asked questions
Why not just capture raw UTM parameters?
Raw UTM capture only records tagged paid or custom campaigns and only when the form is completed on the landing page. A cookie-based attribution approach also records organic, direct, referral and other arrivals, persists across pages, normalises inconsistent values, and adds landing page and landing page group.
Which hidden fields are needed in a Duda form?
Add Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group as hidden fields. The attribution script then populates them on submission.
Where can the captured data be used after submission?
Check the Entries section, add the fields to lead notification emails, send the data to a CRM or other sales and marketing tool, or sync it to Google Sheets or Microsoft Excel.