Introduction

The TranslationOS connector for Marketo Engage allows you to outsource your assets to Translated, with no need to manually import and export content or switch between tools.

This connector is event-based, meaning it is triggered by specific actions. To learn which actions trigger the connector, see the section Requesting translations.

Support

For general questions about functionality, our dedicated support team can be reached at [email protected].

If you need technical information or you’re ready to integrate your Marketo Engage instance with TranslationOS, feel free to reach out to us at [email protected] for assistance with onboarding.

The onboarding process may vary depending on your needs, but the following steps are a helpful guideline:

1. Translated will ask you to provide the base URL, the client ID and client secret (see below for instructions to retrieve them).
2. Translated will enable you to test the connector in sandbox mode, which means that you will get back machine-translated content to test the user experience.
3. You will agree with Translated on the required service levels, also known as service types. Translated will take care of configuring the connector for you.
4. We will be ready to receive, process and deliver your translation requests!

Setting up the connector

You will need to retrieve the following three pieces of data from Marketo Engage and communicate them to Translated. We will then complete the connector configuration for you.

Retrieving the base URL

The base URL contains the account ID (aka Munchkin ID) and is therefore unique to each Marketo Engage subscription. Your base URL is found by logging in to Marketo Engage and navigating to Admin > Integration > Web Services. It is labeled “Endpoint:” in the “REST API” section, as shown in the following screenshot.

You will need to copy it and send it to Translated.

Retrieving the client ID and client secret