> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/action-pages/page-builder/custom-form-fields.md).

# Custom Form Fields

Add custom fields to an Action Page form: text, questions, selection lists, dates, birthdays, hidden values, and agreements. Reuse fields across pages.

**Custom fields** let you ask for information beyond the standard contact fields, such as a T-shirt size, a survey question or an agreement to terms. You add them in the Page Builder under **Page > Form**, in the **Custom fields** section. This article covers field types, adding and reusing fields, and each field's settings.

## How Custom Fields Work

Custom fields belong to your fundraising account, not to one page. Once you create a field, you can add it to any Action Page.

{% hint style="warning" %}
Editing a custom field's label or options changes it on every page that uses that field. To use different wording on one page, create a separate field.
{% endhint %}

## Field Types

| Type           | What Donors See                                                                                                    |
| -------------- | ------------------------------------------------------------------------------------------------------------------ |
| Text           | A box for a free-text answer                                                                                       |
| Question       | A question with a free-text answer                                                                                 |
| Selection List | A list of options, shown as radio buttons, checkboxes or a dropdown                                                |
| Date           | A date in MM/DD/YYYY format                                                                                        |
| Birthday       | A date in MM/DD/YYYY format that can't be in the future on the calendar                                            |
| Hidden         | Nothing. The value is saved with the submission. See [Hidden Fields](/action-pages/page-builder/hidden-fields.md). |
| Requirement    | A statement the donor agrees to                                                                                    |

## Add a Custom Field

To add a custom field:

1. Go to **Action Pages > Pages**.
2. Hover over the page you want to edit.
3. Click **⋮ > Edit**.
4. Select **Page > Form**.
5. Under **Custom fields**, click **New** to create a field, or **Existing** to add one your account already has.
6. Set the field's options.
7. Drag fields to put them in order.
8. Click **Save**.

The field appears on the form in the order you set.

## Field Settings

* **Required:** Donors must answer. Not available for Hidden or Requirement fields.
* **Default value:** The value the field starts with.
* **Show on receipt:** Includes the answer on the receipt.
* **Agreement type:** For Requirement fields only. **Submission (default)** counts sending the form as agreeing. **Clickwrap** asks the donor to check a box.

{% hint style="info" %}
A Requirement field is always required. The agreement type only changes how the donor agrees.
{% endhint %}

## Prefill a Field From the Link

You can set a custom field's starting value from the page link by adding the field's internal name as a URL parameter, such as `?tshirt_size=large`. See [URL Parameters](/action-pages/advanced-features/url-parameter.md).

## Related Articles

* [Standard Form Fields](/action-pages/page-builder/standard-form-fields.md)
* [Hidden Fields](/action-pages/page-builder/hidden-fields.md)
* [URL Parameters](/action-pages/advanced-features/url-parameter.md)
* [Page Builder Overview](/action-pages/page-builder.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.anedot.com/action-pages/page-builder/custom-form-fields.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.