> ## Documentation Index
> Fetch the complete documentation index at: https://docs.allgoodhq.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What a form is

> A form is a capture target, not a page — what that separation means and how one form can serve many placements.

A **form** in allGood is the definition of a capture target: what it collects, what consent it records, and what protects it. It holds no HTML.

That's deliberate. Your website's markup and styling stay yours — allGood does not render your form or restyle it. What it owns is what a page cannot credibly do for itself: secure capture, abuse control, and defensible consent evidence.

## One form, many placements

A form gets one stable **Form ID** the moment it's added to your content library. Any number of pages, campaigns, and templates can point at the same form by that ID — one global form, many placements, not a form per page. Editing the form's fields changes every placement that uses it at once; see [Find where a form is used](https://docs.allgoodhq.com/mk/content/forms/finding-where-a-form-is-used.md) before making a change that reaches more pages than you expect.

Every form posts to the same kind of capture endpoint, regardless of which page renders it. [What protects a form](https://docs.allgoodhq.com/mk/content/forms/what-protects-a-form.md) covers what's enforced there.

## What happens after someone submits

The visitor sees a thank-you message in place of the form. Behind the scenes, the submission is matched to a person by email, any extra fields (like UTM tags) are kept, and an activity fires that campaigns can react to. If the form has a consent text bound to it, the submission also records which named consent text, version, and language the visitor saw — and the visitor's answer, if consent is its own checkbox field.

> [!NOTE]
>
> By default, filling a template makes a new form each time, not a shared one — two pages built from the same template collect into two separate places. You can deliberately share one form across every page built from a template instead, by embedding that form's own capture code directly in the template rather than letting the fill generate a fresh one — see [Adding a form to a page](https://docs.allgoodhq.com/mk/content/forms/adding-a-form-to-a-page.md).

## Related articles

* [Creating a form](https://docs.allgoodhq.com/mk/content/forms/creating-a-form.md)
* [What protects a form](https://docs.allgoodhq.com/mk/content/forms/what-protects-a-form.md)
* [Find where a form is used](https://docs.allgoodhq.com/mk/content/forms/finding-where-a-form-is-used.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.