> For the complete documentation index, see [llms.txt](https://docs.powerfulform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powerfulform.com/quick-start/form-field-types/hidden-field.md).
# Hidden field
The **Hidden field** lets you collect data silently in the background β without showing anything to customers on the form.
Itβs one of the most powerful fields because it helps you track where submissions come from, which page or product, and extra metadata without asking users to fill it in.
***
### β
When should I use a Hidden field?
Use a Hidden field when you want to:
* Track page URL or page title
* Capture product info (title, vendor, type)
* Save UTM parameters (marketing campaigns)
* Pass values between fields
* Store internal notes or tags
* Send extra data to email, integrations, or Shopify
Note: Customers never see this field on the form.
***
### 𧩠How to add a Hidden field
1. Open your form in the editor
2. Click **Add element**
3. Select **Hidden**
The field will be added to your form, but it will not appear in the preview.
***
### βοΈ Hidden field settings
#### Label
Internal name for the field (for you only).
**Example**
* `Page source`
* `Campaign`
* `Product info`
This label appears in submissions and emails.
***
#### Data type
Choose where the value comes from.
Most commonly used options:
* **Fixed value**
* **Dynamic value** (page, product, UTM, or other fields)
***
#### Assign value
This is where you define what data is saved.
You can type:
* Plain text
* Or use a dynamic variable (recommended)
***
### π Dynamic values (most used)
You can automatically capture data using built-in variables.
#### Page information
**Page title**
Captures the page name where the form is submitted.
```
{{-page.title-}}
```
**Example result**\
`Miami Location`
***
**Page URL**
Captures the full page URL.
```
{{-page.href-}}
```
**Example result**
[`https://hienxinh.myshopify.com/pages/contact-form-2`
]()
***
#### Product information (on product pages)
If the form is shown on a product page, you can capture product data.
Product title
```
{{-product.title-}}
```
[**Example**\
`A-Line Jacket`](#user-content-fn-1)[^1]
***
Product vendor
```
{{-product.vendor-}}
```
**Example**\
`Fashion Style`
***
Product type
```
{{-product.type-}}
```
**Example**\
`Outerwear`
***
### π UTM tracking (marketing campaigns)
Hidden fields are perfect for tracking ads and campaigns.
#### Common UTM variables
* `{{-utm.source-}}` β Google, Facebook
* `{{-utm.medium-}}` β cpc, email
* `{{-utm.campaign-}}` β summer\_sale
* `{{-utm.content-}}`
* `{{-utm.term-}}`
**Example**\
Hidden field label: `utm_source`\
Assign value:
```
{{-utm.source-}}
```
Result: You know exactly where each submission came from.
***
### π Capture values from other fields
You can also store values entered by customers.
#### Example
Hidden field label: `Customer email`\
Assign value:
```
{{email}}
```
This is useful when:
* Sending data to integrations
* Reusing values in emails
* Creating internal references
***
### π§ Set hidden email address
You can use a **Hidden field** to store an email address and then use it to send admin notifications conditionally.
This is useful when:
* Different submissions should notify different teams
* Each location or department has its own email
* You donβt want users to choose or see the email field
[Learn more](https://docs.powerfulform.com/mail-notification/admin-emails-with-conditions)
***
#### Need More Help?
If you still need assistance, please contact us at . Our team will be happy to help you resolve any issues or guide you further.
[^1]:
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.powerfulform.com/quick-start/form-field-types/hidden-field.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.