> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/forms/review-detected.md). # Review detected forms and field changes Open **Website Tracker → Forms** to inspect the forms discovered on your allowed sites. ## Review a new form Give the form a recognizable name, check its site/path restrictions and map the detected field names to the lead fields your workflow needs. Pay particular attention to the email identifier and qualification fields. If **Review new forms** is enabled, accept the form before relying on live capture. The setting is optional; the default behavior does not require that review for every new form. ## When fields change A changed form can require another review. Inspect the Fields changed state, accept the intended changes and update mappings when a website field was renamed. Field discovery records field names rather than a sample of every visitor's values. A discovered name alone does not prove the eventual submission contains a value. ## Restrict capture Use allowed paths and site settings to keep a similarly named form from the wrong page out of the workflow. Archive sites you no longer use and check whether subdomains should be included. Exclude forms and fields using [Privacy and exclusions](/forms/privacy.md). ## Verify Make a fresh controlled submission after accepting changes. Check that it starts the right workflow and supplies the required fields. If a run has old or missing field names, inspect the actual source payload and mapping before changing routing conditions. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/forms/review-detected.md?ask=&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 `build a script that syncs our docs to a CMS` 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.