Definition
A hidden field is an input on a form that the person filling it in cannot see. In marketing it has one main job: to carry information about the visit, rather than about the person, into the record the submission creates. The person supplies their details; the hidden fields supply the context the person would never think to type, such as which campaign brought them, which page they converted on and when.
The sense here is narrow. Forms also use invisible inputs for other purposes, such as catching spam bots, and a CRM can hide properties from its own layouts. Neither is what reporting means when it asks whether the hidden fields are working; that question is always about source and campaign data reaching the lead record.
What hidden fields hold and where the values come from
The values start outside the form. Campaign parameters are added to every tracked link by the marketer, and click identifiers are appended by the ad platforms. The guide to connecting the CRM to ads and analytics lists what is typically captured this way: click identifiers, campaign parameters, the analytics client identifier, and the landing page, referrer, form name and time of submission. The page reads each value on arrival, stores it so it survives the visitor moving to another page before converting, and writes it into the matching hidden field when the form is submitted. From there the values land in the CRM's source fields and are used for reporting, for sending outcomes back to the platforms and for diagnosis when something is missing.
In-platform forms work slightly differently, because the platform hosts the form. The LinkedIn targeting and lead gen forms guide notes that hidden fields there can carry campaign identifiers through to the CRM, so a lead collected without a visit to the website still knows its origin.
In practice: field maps, test submissions and forms that strip fields
Hidden fields fail silently. A form that drops them still submits, the lead still arrives, and only the source column is empty. The CRM connection guide names the usual culprits: embedded, third-party and multi-step forms often strip fields they do not recognise. So hidden fields are treated like any other part of the form:
- Listed in the field map. The lead routing QA checklist asks for a map of each form field and the CRM property it fills, hidden fields included, before any test lead is sent.
- Tested with a real submission. A test lead arriving from a tagged link, then the record read in the CRM, is the only proof the values made the journey.
- Included in audits. The guide to auditing and documenting CRM fields traces every field to whatever writes it, and a form's hidden fields are one of those writers.
- Checked as part of capture. The inbound lead handling playbook has marketing operations confirm that new forms map correctly and source fields are filled, because a lead without a source cannot be credited later.
A payroll software firm finds where its demo requests lost their campaigns
Nainkell Payroll Software noticed that 38% of last quarter's demo requests had no campaign in the CRM, while fewer than 5% had been untagged at the click. The gap appeared in March, when the demo form became a 3-step form. A test submission from a tagged link confirmed it: the first step kept the campaign values, but the form tool dropped any field it did not recognise when moving to step 2. The marketing operations lead added the 5 hidden fields to the form tool's own field list, re-ran the test and read the record, which now showed the campaign, source and landing page. The next month, 96% of demo requests arrived with a campaign attached, and the field map was updated to list the hidden fields by name.
Related terms
The values most hidden fields carry are UTMURL tags identifying traffic source. parameters, and their destination is the CRMThe system that stores an organisation's contacts, companies, deals and interactions, and the processes built around it., where they become the lead's source fields. Lead RoutingRules that assign each new lead to an owner, queue or next step based on territory, segment, score or source. often depends on them, since a rule that sends paid search leads to one team cannot run on an empty source. A Lead Gen FormAn ad format that collects contact details inside the platform, prefilled from the user's profile. hosted inside an ad platform has its own hidden field settings, separate from the website's forms.
Common confusions
- A hidden field is a security or spam measure. Some invisible inputs trap bots, but the source-carrying field is a reporting mechanism, and only that kind belongs in the field map.
- If the form submits, the hidden fields worked. Submission says nothing about them. Only a test record read in the CRM shows whether the values arrived.
- Tagging links is enough. Parameters in the address are lost unless the page stores them and a hidden field writes them into the submission.
- Hidden fields replace click identifiers. They are often the vehicle for click identifiers, not an alternative to them; campaign parameters are the fallback when no identifier is present.
