# Taxi and the Iterable connector

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

Without the connector you will need to download the HTML from Taxi and then either upload the HTML file or copy and paste it into Iterable.

The Iterable connector makes it much easier to create and export targeted emails. [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) can also be used with this connector.

### Setting up your Taxi account to work with Iterable:<br>

With different languages in Taxi, there are two main ways you can organise your account.

1. The same email is sent in multiple languages and is set up using the version set feature in Taxi.\
   When exporting the email to Iterable you can map each version to a locale in Iterable. For example, mapping the French version to the French locale. When you send the email from Iterable, any recipients with the French locale on their profile will get the French email.

In this set up you can have one connector with all the locales set up in it (see screenshot below), so when you export you can see all the locales and map them to the relevant versions.

![](https://2516523503-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMq0EQG9Ff46ZMsrIBcVn%2Fuploads%2Fgit-blob-292d50e3108a19176fc15629f2a12ee74d80a86d%2Fimage.png?alt=media)

2\. Each language or market is more independent so they have their own projects in Taxi.\
When they go to export, they are only exporting emails that have one locale.\
In the first example, all locales were available when exporting. In this case it makes more sense to only make the relevant locale available. For example, when the German team export, they can only choose the German locale.

To do this, you can set up one connector per market, and then only include one locale per connector. For example, for the German connector, only include the German locale.

![](https://2516523503-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMq0EQG9Ff46ZMsrIBcVn%2Fuploads%2Fgit-blob-282eff3636b8ccc6f248b906e9b33e608b565fb5%2Fimage1.png?alt=media)

You can also permission the connectors, so each language/market can only see their own connector when they go to export.

\
Read Next:

[Setting up the Iterable connector](https://docs.messagebird.com/taxi/Connectors/Iterable/setting-up-the-iterable-connector)


---

# Agent Instructions: 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:

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

The question should be specific, self-contained, and written in natural language.
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.
