Setting Up Your Marketo Connector
This article will describe how to:
- Configure Marketo User Permissions
- Connecting Marketo to Smartling
- Marketo Connector Configuration
- Language Configuration
- Configure Marketo Content Parsing
The Smartling Marketo connector allows you to translate Marketo content with context. Translations are requested from within the Smartling platform, and translated content is automatically sent to your Marketo instance. Smartling’s Marketo Connector currently ingests all assets and related assets* within the following Marketo content types, including dynamic content where it is supported
- Emails (template and detached)
- Landing pages
To link your Marketo account to Smartling, complete all sections below:
Create an API user role in Marketo
To use the connector, you first need to create the following in Marketo:
- A dedicated API user
- You only need to grant this role with Read-Write Assets. We recommend creating a custom API role with this access for this API user.
- A LaunchPoint service in the Marketo dashboard
To complete the above, follow the steps in the Quickstart Guide for Marketo REST API.
This role requires Read-Write Assets permissions.
Connect Marketo to Smartling
- Log into Marketo.
- Log into Smartling.
- Create a Marketo Connector project type in your Smartling Account.
- From within this project, click on the gear icon > Project Settings > Marketo Settings
- Click Connect to Marketo.
- Enter the following credentials:
- Client ID: Available from Marketo Admin Dashboard in Integration > Launchpoint.
- Client Secret: Available from Marketo Admin Dashboard in Integration > Launchpoint.
- Endpoint: Available from Marketo Admin Dashboard in Integration > Web Services.
- Identity: Available from Marketo Admin Dashboard in Integration > Web Services.
- Click Save.
Your Marketo instance will now be connected to your Smartling project.
Configure the Marketo Connector
When you have successfully completed connecting Marketo to Smartling, the Marketo Setting page has the following configurations
You can configure the behavior of the connector when source content that has previously been translated in Smartling changes:
- From within your Smartling Marketo Project, click on Project Settings > Marketo Settings
- Click the Automation of Prior Request for Translation dropdown to select your desired behavior.
- Configure publishing options for delivered translations in Marketo
- To apply changes, click Save
Automation of Prior Request for Translation
- Auto: The Marketo Connector will detect changes to source content every 3 hours. Any changes detected to the source content will be submitted to Smartling for translation, batched into a Job and sit in awaiting authorization. However, if auto-authorize is enabled under Smartling Settings, the updated content will be batched into a Job and automatically authorized for translation. Smartling will not detect net new content, only updates to content that have been submitted for translation in the past.
- Manual: The Marketo Connector will detect changes to source content every 3 hours, but will not submit new content for translation.
- Disabled: The Marketo Connector will not detect changes to source content or automatically submit new changes.
3 hours is the recommended shortest time duration between checks. Talk to your Solutions Architect about changing the frequency to longer wave periods using cron.
We recommend that you do not combine Jobs Automation rules with automation of prior requests for translation settings, as doing so may result in unexpected behavior.
The Smartling Marketo Connector allows you to set custom locale codes (ie. fr-FR vs. fr vs. French) in the File Name generated when we return translated assets back to Marketo. You must enter a value in this section otherwise the connector will not pick up that target language.
To enter locale values:
- From within this project, click Project Settings > Marketo Settings.
- Enter your desired locale code in the Target Languages column.
- Click on the checkmark that appears to save.
Talk to your Customer Success Manager or Solutions Architect about options on auto-authorization, visual context, translation retrieval states, namespace, and placeholder formats.
Ready to translate Marketo content? See our Marketo translation guide.