> For the complete documentation index, see [llms.txt](https://docs.navless.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navless.ai/integrations/map-crm-integrations/marketo/lead-forms-with-marketo.md).

# Lead Forms with Marketo

👉 [Take a Tour before Getting Started](https://websitetours.tourial.com/pages/marketo-forms)👈

For this, you will need to have a Marketo form created already to map your Tourial form leads into your account. It can be a custom form dedicated to Tourial (ie. Tourial - Marketo Form) or one you're already using (ie. Book a Demo).

1\. In the Tourial studio, select Forms, then Create a new form

![](https://67180079-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKaMCOI4HEb21AIKZlkHe%2Fuploads%2FaVtwuZ2ycoAxHG2rVeO1%2FTourial-04-04-2025_01_54_PM.png?alt=media\&token=a32b29c4-11de-477a-aa99-a04c245ca311)

2\. At the top, add a form name

3\. Below, there are several options to add or edit fields, and style your form. First, click Content to connect your Marketo form

[![](https://67180079-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKaMCOI4HEb21AIKZlkHe%2Fuploads%2FyVjNs3x529ODwupO3s3z%2FTourial-04-04-2025_01_56_PM.png?alt=media\&token=07811125-72b4-4f45-890b-43b8d77d7400)](https://downloads.intercomcdn.com/i/o/604393845/5542bf766b33e63ab6eba175/tourial-new-form-setup.png)

4\. You can add a headline and description text. Select Integration, then Import field

5\. Choose Marketo for the integration and select a form, then Import Field

If you have hidden UTM fields in your form, you'll be able to map these as well. Those fields will be marked Hidden, and then you just need to select the corresponding UTM paramete

*Note: Make sure the number of fields in your Tourial form matches the fields in your Marketo form, otherwise you'll potentially send empty data or the integration will fail.*

6\. Style your form as you wish by using the remaining form settings

7\. If you choose to show the confirmation modal, you can edit and style it under the Confirmation tab

<figure><img src="https://67180079-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKaMCOI4HEb21AIKZlkHe%2Fuploads%2FKTQQPw0b8pQGAhwdBvSg%2Fimage.png?alt=media&amp;token=cfff885b-f176-4ef5-a35d-8c3548a5bd84" alt=""><figcaption></figcaption></figure>

8\. Save your form

### Success! 🎉 Confirm the connection by sending a test lead through the form to make sure it goes through to your Marketo account! <a href="#h_5d8ea178a9" id="h_5d8ea178a9"></a>

***

What's next? Learn how to [send Slack notifications from Marketo](https://tourial.gitbook.io/tourial-customer-product-documentation/integrations/marketo/engagement-data-with-marketo/slack-notifications-with-marketo). This way, your team can get real-time alerts when someone engages with your tours or submits a form!

Also, take the [Marketo Engagement Tour](https://websitetours.tourial.com/pages/marketo-integration) to see some of the ways you can use Tourial Engagement Data to create Smart Lists, Flows and influence your lead scoring model.


---

# 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://docs.navless.ai/integrations/map-crm-integrations/marketo/lead-forms-with-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.
