Hidden fields and URL parameters

What is Hidden fields and URL parameters?

Hidden fields and URL parameters carry campaign, partner, or product context into a submission quietly. Respondents never see those values on the form, but you can read them in Results and exports for attribution.

How it works

1. Decide which attribution keys you need (for example campaign, source, or partner id).
2. Configure matching hidden fields on the form, or plan to pass URL parameters on the share link/embed.
3. Publish the form so the live version accepts those values.
4. Append parameters to the public URL or configure the embed to pass them.
5. Submit a test response from a parameterized link.
6. Confirm the values appear on the submission in Results.

Key capabilities

• Hidden fields

  Store values on the submission without displaying inputs to respondents.

• URL parameters

  Pass context through the link or embed query string into the response payload.

• Attribution-ready Results

  Inspect captured values alongside answers for campaign analysis.

• Works with embeds and links

  Use the same approach on public URLs and embed distributions.

Benefits

• Cleaner forms - no “how did you hear about us?” when the channel is already known.
• More reliable attribution than relying on memory.
• Consistent tracking across ads, email, and partner links.
• Better join keys when syncing to Sheets or other tools.

Use cases

• Tagging paid campaign traffic with UTM-style parameters.
• Passing a partner ID from a co-marketing landing page.
• Attaching an internal product SKU or plan code from an in-app embed.

Example workflow

Growth publishes a demo form and shares `?utm_campaign=spring&partner=acme` on ads. Hidden fields capture those values on submit. In Results, the team filters spring campaign leads and exports CSV for the CRM - respondents never saw the attribution fields.

Tips and best practices

• Document your parameter vocabulary so every campaign uses the same keys.
• Always test a parameterized link before spending ad budget.
• Prefer hidden/URL values for known context; ask visible questions only when you need respondent judgment.

Limitations and plan notes

• Values only arrive if the link or embed actually passes them - broken URLs mean empty attribution.
• Respondents can modify query strings on public links; treat values as useful context, not cryptographic proof.
• You still need a published form; parameters do not make drafts fillable.

Frequently asked questions

What are hidden fields for?

They store values on the submission without showing those inputs to respondents - commonly used for attribution.

Can I pass data through the URL?

Yes. URL parameters can populate context on the submission when configured with your form’s fields.

Will respondents see these values?

Hidden fields are not shown as normal questions. URL parameters may appear in the browser address bar, but not as form inputs.