> 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/data-and-integrations/pre-submit.md). # Pre-submit enrichment Pre-submit enrichment can supply stored lead data before a visitor finishes a supported form journey. ## Configure the early lookup Enable the supported early-enrichment setting and choose a chain supported by the Records lookup path. The tracker needs a usable email identifier and permission to capture it. Records-supported providers run sequentially and stop at the first usable result. See [Provider support](/data-and-integrations/provider-support.md) rather than assuming the workflow provider list applies here. ## Understand timing The early lookup runs asynchronously. A visitor who submits quickly can reach the workflow before enrichment has completed. The pre-enrichment marker limits a repeat early lookup for the same record to approximately once per day. It is not a guarantee that every field is fresh at the moment of submission. ## Avoid assuming reuse A later **Enrich Lead** workflow step executes its own provider calls. It does not automatically reuse the completed pre-submit lookup to eliminate those calls. Decide whether the workflow can use existing stored lead fields or needs a fresh explicit enrichment action. Check provider usage when combining both paths. ## Verify Test a known person, a no-match identifier and a fast submission. Inspect stored Records fields, the submitted workflow input and any later enrichment output separately. Treat missing early data as an expected branch. Do not block a valid lead solely because an asynchronous lookup has not finished. --- # 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/data-and-integrations/pre-submit.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.