> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/routing-forms/marketo.md).

# Marketo forms

Distro uses the Marketo Forms 2.0 success callback to start routing after a successful form submission.

1. Identify the embedded Marketo form ID, such as `mktoForm_1234`.
2. Create a [form mapping](https://help.distro.so/routing-forms/overview.md) in Distro with that **Form selector** and the Marketo fields' internal names.
3. Select the mapping in the Form Router, configure the rules and event type, then test and activate it.
4. Copy **Install Router** code onto the page. Initialize Distro after `MktoForms2` and the intended form are loaded.
5. Test the published page and inspect **Routing Logs**.

The Marketo handler returns `false` from `onSuccess` to prevent Marketo's normal follow-up redirect while Distro opens scheduling. Configure the required destinations in the router and test both qualified and disqualified outcomes. This changes the default follow-up behavior; it does not guarantee a CRM meeting record unless the corresponding CRM actions are configured.

For provider callback behavior, see the [Marketo Forms API reference](https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/javascriptapi/forms-api-reference).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.distro.so/routing-forms/marketo.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.
