Capture UTM parameters in Tally Forms
Connect campaign tags to the leads they create. Hidden fields in Tally can carry channel, campaign and landing-page details into responses, notifications, a CRM, a spreadsheet or an email platform, making it easier to judge which activity produces customers rather than only visits.
Why attribution belongs on the form
A form submission alone rarely explains why someone contacted you. Adding attribution fields gives each response context: the channel that brought the visitor, the campaign or network involved, and the page where the journey began. That context can then be reviewed beside contact details instead of being reconstructed later from separate analytics reports.
Set up the four stages
First, place the attribution code on the website that hosts the embedded form. WordPress setups may use theme settings or a header/footer plugin; Webflow, Squarespace and similar builders generally provide a custom-code area; Google Tag Manager is another installation route. Next, open the Tally form and add hidden fields by typing /hidden and choosing Hidden Field. Create Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. When a visitor arrives, the tool reads campaign information and stores it in the browser. At submission, it fills those fields automatically, so Tally receives attribution beside the name, email, phone number and other answers.
Worked example: a paid-search lead
Consider a mortgage firm advertising to first-home buyers. A visitor clicks a paid-search ad, reaches a rate-quote page and submits the form. The hidden fields could record Paid Search, Google, the campaign name, the ad wording, the full landing URL and its /first-home-buyers group. That example shows how broad channel data and specific campaign detail can coexist on one lead.
What goes beyond raw UTM tags
Raw UTM capture has limits. It may miss organic and referral visits, and it can disappear if the landing page differs from the form page. The method described addresses both gaps: every form lead receives a channel classification, and the original details persist in the browser across browsing and return visits. It also records click IDs and the first landing page with its subdirectory group, which supports content-level reporting.
Use the captured values
After submission, inspect values in Tally responses or include them in new-lead notifications. Tally integrations or webhooks can forward them to a CRM, while Zapier or Make can route them to a spreadsheet, email platform or another connected tool. Before building reports, check that each field is populated, names match the destination fields, and test submissions from paid and organic visits produce the expected classifications.
Reports worth building first
Useful starting reports include leads by channel, leads by Meta network, customers by Google Ads campaign and revenue by keyword. The first compares all sources; the second separates Facebook, Instagram, Messenger and other Meta placements; the third connects campaigns with paying customers; the fourth requires keyword values in the campaign tags. Together they move decisions from traffic volume toward lead quality, customer value and budget allocation.
| Hidden field | What it helps you report |
|---|---|
| Channel | Broad source such as Paid Search or Organic Search |
| Channel Drilldown 1 | Platform or network, such as Google |
| Channel Drilldown 2 | Campaign name |
| Channel Drilldown 3 | Ad, keyword or finer campaign detail |
| Landing Page | First page URL visited |
| Landing Page Group | Subdirectory grouping for content sections |
Field names are taken from the supplied workflow; confirm destination mapping in your CRM before use.
| Report | Decision it supports |
|---|---|
| Leads by Channel | Compare monthly lead volume across all sources |
| Leads by Facebook Ads Network | Shift Meta budget toward stronger placements |
| Customers by Google Ads Campaign | Identify campaigns producing paying customers |
| Revenue by Keyword | Prioritise bids and SEO topics |
Revenue and customer reporting depend on downstream CRM or sales data being joined to the lead.
Frequently asked questions
How do UTM values get into a Tally submission?
Add the site code where the form is embedded, create six hidden fields in Tally, and let the attribution tool fill them at submission. The values then appear with the response and can be forwarded through Tally integrations, webhooks, Zapier, or Make.
Can attribution work when a visit has no UTM parameters?
Yes. The approach described also classifies visits from Organic Search, Organic Social, Direct, Referral and other channels, so reporting is not limited to paid campaigns that use UTM tags.
What if someone browses several pages before submitting?
The data is stored in the browser when the visitor first arrives, so browsing other pages before completing a form does not erase the original campaign information.
Why capture click IDs as well as UTM parameters?
Click identifiers such as GCLID, MSCLKID and FBCLID can travel with the lead. Sending them back at a later pipeline stage lets the ad platform connect the original click with a more valuable outcome.