> For the complete documentation index, see [llms.txt](https://docs.bird.com/taxi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/taxi/connectors/marketo-connector/taxi-and-the-marketo-connector.md).

# Taxi and the Marketo Connector

If you build your emails in Taxi for Email and send them via Marketo, our Marketo connector will save you time and reduce risk throughout the process. It does this by enabling you to automatically send your mailings to any email template within your Marketo account or update existing emails that have already been set up.

Using the connector means you won’t have to manually download the HTML and upload or paste into Marketo. You can export directly out of Taxi at the click of a button meaning a more seamless email creation process in Taxi. This automation and reduced number of manual steps means there is less risk of errors, so you can be confident in last-minute content changes.

The Marketo connector also makes it much easier to create and export targeted emails. The power of Taxi’s [personalisation](https://docs.messagebird.com/taxi/Dynamic%20content,%20segmentation%20and%20personalisation/Personalisation/what-is-personalisation) and [segmentation](https://docs.messagebird.com/taxi/Dynamic%20content,%20segmentation%20and%20personalisation/Segmentation/what-is-segmentation) features can be used with this connector.

You can set up as many Marketo connectors in your Taxi for Email account as you need. This can be useful if you have separate staging and production Marketo environments, or different Marketo accounts for different brands or regions.

The connector enables you to create new emails in Marketo. After creating the email and adding all the content in Taxi you can set what you want to call the email and export from Taxi at the click of the button.

\
Your Email Design System includes all of your modules and these will be fully render tested so you know that any time you use them in your emails, they will appear correctly across email clients and devices. When using the connector to export from Taxi, this consistent rendering is further guaranteed as you don’t have to touch any of the HTML. No code can be edited by accident and there is no risk of copying and pasting the wrong thing into your ESP.<br>

You’re also able to update an existing email through the connector. If a mailing has been exported to Marketo but a last minute change is needed, you can make the change in Taxi and quickly override the email that has previously been exported.Even once the email has been exported to Marketo, there’ll be no need to edit the HTML.

Read Next:

[Setting up the Marketo Connector ](https://docs.messagebird.com/taxi/Connectors/Marketo%20Connector/setting-up-the-marketo-connector)| [Exporting an email to the Marketo Connector](https://docs.messagebird.com/taxi/Connectors/Marketo%20Connector/exporting-an-email-to-marketo)


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bird.com/taxi/connectors/marketo-connector/taxi-and-the-marketo-connector.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.