Hidden Field

A field that's invisible to the respondent but included in the submission data. Use it to track source, campaign, referrer, or any contextual data.

Configuration

Field	Description
Field name	The variable name (used in workflows)
Default value	Static value always included
URL parameter	Populate from a URL query parameter

How to populate

Via URL parameters

Share the form URL with parameters:

https://capture.tinycommand.com/YOUR_FORM_ID?source=google&campaign=spring2026

Hidden fields named source and campaign auto-populate with "google" and "spring2026".

Via static default

Set a hardcoded default value:

Form version: "v2"
Source: "website"
Team: "sales"

Via conditional logic

Set the value based on previous answers using the canvas logic nodes.

Common uses

Hidden field	Value source	Purpose
`utm_source`	URL param	Track marketing channel
`utm_campaign`	URL param	Track campaign
`referrer`	URL param	Who referred them
`form_version`	Static	Track which form version
`team`	Static	Route to correct team
`lead_score`	Calculated	Auto-score based on answers

Tip

Hidden fields are essential for marketing attribution. Add utm_source, utm_medium, utm_campaign hidden fields to every lead capture form, then pass them to your CRM via a workflow.

Best practices

Use for UTM tracking -- add utm_source, utm_medium, utm_campaign, utm_term, and utm_content hidden fields to every lead capture form for full marketing attribution
Track referral sources -- pass referrer URLs or partner IDs through hidden fields to know where leads originate
Capture session context -- store session IDs, page URLs, or A/B test variants to tie submissions back to user journeys
Keep names consistent -- use the same hidden field names across all forms (e.g., always utm_source, not sometimes source) so your CRM and analytics stay clean
Set sensible defaults -- always provide a static default value as a fallback in case the URL parameter is missing
Don't store sensitive data -- URL parameters are visible in the browser address bar; never pass passwords, tokens, or PII through hidden fields