> 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/marketo.md). # Capture Marketo form submissions Distro's website tracker can capture supported Marketo Forms 2.0 submissions. ## Connect Install the tracker on the allowed page containing the Marketo form. The tracker attaches an `onSuccess` callback when `MktoForms2` becomes available. Submit a controlled test, inspect the detected form in **Website Tracker → Forms**, review its mapping and connect the intended external-form workflow. Marketo forms are identified using their Marketo form ID. ## Check the success behavior Distro captures the success values and allows Marketo's original follow-up behavior to continue. It does not automatically suppress Marketo's redirect or thank-you action. If your intended experience shows a scheduler on the current page, coordinate the Marketo follow-up behavior and use the supported SDK integration where appropriate. Verify the real browser journey from submit to scheduler and confirmation. ## Keep API writes separate The [Marketo connection](/integrations/marketo.md) authorizes workflow writes using a custom service. Tracker capture does not grant those permissions. ## Troubleshoot Check that Forms 2.0 is initialized in time, the tracker loads, the site is allowed and the source form is accepted. Review whether a redirect happens before you can see the workflow outcome. Inspect the workflow input and mapped email before changing downstream routing. A successful Marketo submission can still lack the fields your workflow expects. --- # 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/marketo.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.