> 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/pardot.md). # Capture Pardot and other embedded forms Use the generic form capture path for a supported Pardot or other form rendered as accessible HTML on your website. ## Check the embed first A normal HTML form in the page can be detected through its form and field elements. A form inside a cross-origin iframe cannot be inspected as if it were part of the parent page. Distro does not provide a dedicated Pardot callback adapter in the current tracker. Do not assume every Pardot embed will be captured automatically. ## Choose a supported path For accessible HTML, install the tracker on an allowed site, make a controlled submission and review the detected form and field mapping. For an iframe or custom component, use a supported integration inside the form's own hosting context, a server-side webhook/API handoff, or a [Distro lead form](/forms/lead-forms.md). Your implementation must be able to supply the submission values deliberately. ## Verify end to end Check the resulting Distro run, lead identity and intended outcome. Confirm the original form still sends data to its own destination and that its success redirect does not interrupt scheduling. Use [Form troubleshooting](/forms/troubleshooting.md) when no form is detected. For a server integration, use [Start a workflow](/developers/start-workflow.md). A tracker installed on the parent page is not proof that it can see every embedded form. --- # 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/pardot.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.