Marketo (TMS)

Content is machine translated from English by Phrase Language AI.

Available for

Enterprise plan (not available for LSP plans)

Get in touch with Sales for licensing questions.

Available for

Enterprise plan (Legacy)

Get in touch with Sales for licensing questions.

Marketo is automation software designed for account-based marketing and other marketing services.

Marketo connector allows the downloading of source content and uploading of translations to/from a Marketo server for the following content types:

Emails
Email templates
Files
Forms
Landing pages
Landing page templates
Segmented dynamic content
Snippets (including landing pages and emails)

Segmentation

Content from all segments is imported into one job for language-neutral segmentation (e.g. gender). Content from each segment is then imported into separate jobs for language-specific segmentation (e.g. preferred language). These translations are stored within the original document as segmented dynamic content.

Mapping between segments and target languages is configured in the connector settings. Multiple segments can share the same target language.

Template Restrictions

Localized templates and assets have the same name as the original-name [language] (e.g. Black Friday Promo [de-de]). A localized asset references a localized version of an object (template, snippet, etc.) provided the object exists in that language. If not, it references the original object.

Only approved templates can be referenced. If the template is localized, the connector automatically moves it to the approved state.

Excluding Modules from Translation

To exclude Marketo modules from translation add data-translate attributed to the module's first HTML tag and set the respective variable that controls its visibility either to false, 0, none, or hidden.

Example:

<div class="mktoText" id="leftsidebar" mktoname="Left Sidebar">
  <h3 data-translate="${leftSitebar}">This heading will be excluded</h3>
  <p>This paragraph will be excluded too</p>
</div>

Variables translation and mapping

Only supported if Create translations -> as separate documents is selected in connector settings.
Variables mappings are specified in connector settings. In the variable name, set the Marketo variable name without the enclosing ${} and in the value field, set the required value that should be used in translated asset. In the value field, the {targetLang} (target asset language), {targetLangDir} (target asset language direction: ltr, rtl) macros can be used.
All string variables in landing pages that are not mapped in connector settings are translated.
Variables translation is not supported for emails (only global variables mapping is supported).

Configure In-Context Preview

The In-context preview feature offers a real-time preview of original or translated text in both the CAT web editor and CAT desktop editor.

Tables, columns, various graphics, formatting, and fonts are supported. The feature is meant to provide context when translating and is not a perfect representation of the original or completed document; some visual differences are expected. It can also be influenced by enabling/disabling Allow loading of external content in editors option in Access and Security settings.

Phrase requirements:

Pass through the enterprise firewall to access the on-premise installation.
Authenticate into the authoring environment.

Firewall configuration for on-premise installation:

Installation must be accessible from the following IP addresses:

34.243.87.13, 34.248.197.209, 108.129.22.31, 3.248.158.93
Domain name must be able to be resolved externally.

Note

Some HTML tags present a risk and the CAT editor removes them from this HTML when displaying the preview. This is to ensure user's data privacy and security.

Examples of removed tags include FORM, IFRAME, SCRIPT, SVG, VIDEO, EMBED, OBJECT or background-image CSS properties.

Use Cases

There are a number of use cases for the connector:

Project managers can add files directly to projects from an online repository.
Set up the submitter portal to allow Submitters to add files to requests directly from the online repository.
Use automated project creation (APC) to have new projects automatically created when a change in the last modified date is detected for monitored files or a folder.
- Selected files are imported the very first time APC runs.

Marketo Settings

Enable REST APIs in the Marketo account.

See Marketo documentation for instructions.
Go to Admin and click on LaunchPoint in the Integration section.
Create a new service or view details of an existing service.
Copy and save your Client ID and Client Secret.
Close the dialog box and navigate back to the Integration section of the Admin page.
Select Web Services.
Copy the subdomain from the Identity URL in the REST API section (e.g. 000-MJB-007).

Phrase TMS Settings

From the Settings page, scroll down to the Integrations section.
Click on Connectors.

The Connectors page opens.
Click New connector.

The Create connector page opens.
Provide a name for the connection and change the Type to Marketo .
Provide the following information:
- Marketo API key
  
  Enter Marketo Client ID.
- Marketo API secret
  
  Enter Marketo Client Secret.
- Marketo API identity URL
  
  Enter the first part of the Marketo Identity URL
- If requested by Technical Support team, select Log debug information.
- Create translations options:
  - If not using language-specific segmentation to store target translations, select as separate documents.
  - If using language-specific segmentation, select as segmented dynamic content, and click Test connection.
    
    Provide Segmentation name and mapping requirements from the dropdown lists and indicate which segment contains the source content.
- Select Translate tokens to include tokens in translation.
If not verified in the previous step, click Test connection.

A checkmark will appear if the connection was successful. A red exclamation point will appear if it wasn't. Hover over the icon to see additional details.
Click Save.

The connector is added to the list on the Connectors page.