Skip to content
Join our Slack

Hidden values

Hidden values are form-level keys that accept values from URL parameters or embed code. Respondents do not see them as questions, but Fomr can use them in form text and store them with each submission.

Use hidden values for campaign tags, customer IDs, source tracking, or other context you already know before someone opens the form.

Declare each key before you pass values into a link or embed.

  1. Open a form in the editor

  2. Click Hidden values in the editor dock

  3. Enter a key, such as utm_campaign or customer_id

  4. Click the add button

Keys must start with a lowercase letter. Use only lowercase letters, numbers, dashes, and underscores.

To give a key a default value, used when the link or embed doesn’t pass one, or to delete the key, click the … button on its row.

After you declare keys, the Share panel can build links with values attached.

  1. Open Share

  2. Fill in the fields under Hidden values

  3. Copy the generated link

  4. Share that link with the audience that should carry those values

A link with a hidden value looks like this:

https://fomr.io/s/example?utm_campaign=spring_launch

Only declared keys are captured with responses.

Declare a key in Hidden values, then fill it in on the Share link page and copy the generated link.

Hidden values can also travel through your embed code.

  1. Open Configure > Add to website

  2. Choose an embed type

  3. Turn on Hidden values in the embed options

  4. Fill in the values and copy the embed code

Standard and fullscreen embeds add values as query parameters on the iframe src, for example https://fomr.io/s/embed/YOUR_FORM_ID?utm_campaign=spring_launch. Popup embeds add them as data-fomr-param-KEY="value" attributes on the button that opens the popup, for example data-fomr-param-utm_campaign="spring_launch". Only declared keys are used.

The embed script also passes the URL parameters of the page where the form is embedded, so a visitor who arrives at yoursite.com/pricing?utm_campaign=spring_launch brings that value into the form automatically. If the embed code sets the same key, its value wins.

Declared hidden values appear in the same @ menu as answer pipes. Type @ in supported editable text, then choose a key from the Hidden values group.

If a hidden value might be missing, click the pipe token and add fallback text so the published form still reads naturally.

Hidden values can steer your form, too. A conditional logic rule can check a hidden value, for example to show a partner-only question or to jump straight to a partner page when a link carries source=partner. Calculated values can also use hidden values in their formulas.

Captured hidden values appear as response columns, after your questions and Calculated values. Response details list them last, under a Hidden values heading. CSV exports include them, and Google Sheets workflows can use the same readable labels as the Responses table.

Fomr checks hidden value references when you publish. If form text references a hidden value key that is no longer declared, publishing shows an issue so you can fix it before respondents see the form.

Your next form could be the best-looking thing on your site.

Free forever. Unlimited responses. No signup to start.