You need to take care of a few things before starting your first project in Cloudwords. This includes enabling the Cloudwords for Marketo integration, implementing recommended best practices and configuration tips, structuring Marketo for localization, and using tokens and templates.
Enabling the Cloudwords for Marketo integration
If your account has not yet been enabled, email us at firstname.lastname@example.org request activation.
Once your Cloudwords account has been granted access to the Marketo integration, follow these instructions. Note: You must be an Administrator in Cloudwords in order to access the settings and configuration steps.
- Log in to your Cloudwords account, click your name in the top right corner, and click More. The Settings page displays.
- Select Marketo Integration from the list.
- Click Start Now to enable the integration for your account. Note: This is a one-time action.
- Under the Enable the Marketo Integration? header, select the Yes option to make the integration available to users who’ve been granted permission to use it.
- You can manage Marketo access for other users under the Permission to Use the Marketo Integration header, and change Advanced Settings as well.
- Click Save when you’re done.
How to use tokens and templates
Tokens are custom variables and dependencies that can be used in emails or landing pages. Types of tokens include: calendar files, date values, email scripts, numbers, or regular text. The tokens you create in Marketo are automatically detected by Cloudwords, and then extracted for translation.
Marketo uses an extensive set of templates. Cloudwords automatically recognizes the content and returns translated content to the appropriate templates you've set up -- whether they're emails, landing pages, forms, or other types of assets.
If necessary, you can change target asset templates when first selecting source and target languages.
By default, each translated asset will use the same template as the source asset with the text translated. You can choose to customize this process by following the steps below. To ensure the best result, the source asset must have the same layout as the selected target asset template.
- First select the source materials you want to translate. For details, see Section III: Select source materials.
- From the Language Selection page, when selecting source and target languages for your assets, click Change Target Template. The Change Asset Target Template pop-up box displays, listing each asset you’ve elected to translate.
- Select an asset and one of its target languages. Click the dropdown menu under the Target Asset Template subheader, and select a template.
- Repeat the process for each asset’s target language, as necessary.
- Click Save.
Structure Marketo for localization
First evaluate the structure of your original assets (email, landing page, et cetera) and determine how well it will scale to your translation needs. When you set up a translation project in Cloudwords, you'll decide how you want the translations delivered -- you can choose between New Asset, New Program, or Dynamic Content.
- For New Asset, the translated asset has the same name as the source, appended with language code.
- With New Program, all translatable assets are created in a cloned Marketo program with the identical structure as the source program.
- For Dynamic Content, you set up a preconfigured content segmentation to allow for greater flexibility.
Before you start, consider these tips:
- Make sure all translatable content is editable and doesn’t reside in templates.
- For dynamic content, make sure that all desired elements are segmented.
- The component names should be unique in each asset.
You can read about this in greater detail in Section III: Starting your first project.
To get the most out of Cloudwords, we recommend you spend some time configuring it. For example, consider these tips that are required for certain functionalities:
- For Dynamic Content projects, be sure that all text elements are segmented. Static elements will not be included in Dynamic Content projects.
- Mixed project types must be submitted separately or as a campaign. If you’re combining dynamic emails and static landing pages, for example, these need to be submitted as independent projects. You can group them together under a Cloudwords Campaign.
- Make sure that the assets you select are not already in translation, as Cloudwords prevents such source-file conflicts.
Here are optional suggestions to make your projects easier to manage.
- Customize the target and source language list boxes to contain your company's specific target and source languages (Go to Settings > Project Settings).
- Embedded snippets and forms: these will be included by default, but you can choose to exclude them from an individual project request. There is a checkbox in the project creation wizard that lets you determine whether to include these elements.
- If you work with a translation vendor that is not in the Cloudwords marketplace (see the "Vendors" tab in your Cloudwords account), send us an email at email@example.com, and we will add them to Cloudwords.
- Add your translation Reviewers. (Go to Settings > User Management). Note: User roles are only available in Accounts when using the Professional or Enterprise Edition.
- To help with project management, you can set up Departments (Go to Settings > More > Company Departments). You’ll be able to run reports company wide or by department. Note: Departments are only available in Accounts when using the Professional or Enterprise Edition.
- If you would like vendors to accept your company's non-disclosure agreement (NDA) before they can download your source files or translation memory, add the NDA at Settings > More > NDA. Note: A custom NDA is only available in Accounts under the Professional or Enterprise Edition. Basic accounts inherit the NDA that is in place between Cloudwords and all the vendors in the marketplace.
What can Cloudwords extract for translation?
The following asset elements can be extracted and sent for translation.
- HTML text
- Body copy
- Tokens (all tokens by default, but we can configure your account to avoid inherited tokens)
- Forms and form buttons
- URLs in hyperlinks
What isn’t sent for translation?
The following elements are not sent for translation.
- Documents stored in Marketo (e.g., white papers, et cetera). These can be downloaded and sent as a separate CW project.
- Content in templates
- Social widgets (built in Marketo)